A320 Flight Crew Operational Manual

Using the A320 FCOM Without Losing Your Mind

The A320 Flight Crew Operational Manual is a thick, poorly indexed set of documents that sits on every Airbus desk somewhere between "essential reference" and "existential threat." It covers normal procedures, abnormal procedures, emergency procedures, limitations, performance data, and system descriptions. That's the textbook version. The reality is different. I spent seven years flying the A320 family across three different operators, and the FCOM was the document I reached for last and cursed the most. Not because it's bad — it's technically thorough — but because the way Airbus organized it makes you jump through three levels of hyperlinks just to find the bleed valve failure checklist you need at 300 feet on a hot day.

A320 Flight Crew Operational Manual: How It Actually Works

Every airline gets a customized version. The core content comes from Airbus, but each operator adds their own supplements, company-specific procedures, and localized regulatory requirements. What you get on the ACDU or in the quick reference handbook is not the full manual. The FCOM lives in the database systems and in the electronic flight bag, split across multiple volumes. Volume 1 covers limitations and normal procedures. Volume 2 is your system descriptions and abnormal/emergency procedures. Volume 3 is performance data. Some operators merge or reorganize these. Yours might look different from mine. The key thing nobody tells you when they hand you the manual during initial training is that the table of contents is almost useless for time-pressured situations. The index is marginally better. But the real navigation path is through the Quick Reference Handbook and the electronic FCOM search function. If you're reading PDF printouts or trying to flip through the bound volumes in a real emergency, you are doing it wrong. Here's the part that catches everyone off guard. The FCOM abnormal procedures are written in a tree format. You start with a symptom, follow the flow, and each decision point branches into sub-procedures. The problem is that the tree assumes you've already diagnosed the problem correctly. If you misidentify the root cause at step one, you'll end up performing procedures for a different malfunction while the actual problem continues unchecked. I saw this happen during a simulator session once. The crew spent four minutes working a pressurization checklist that didn't apply because the actual issue was a cabin altitude sensor fault, not a real pressurization leak. The FCOM tree would have led them there if they'd followed it blindly. The workaround is what we called the "STOP and VERIFY" habit. Before executing any abnormal procedure, you state out loud what you think the actual system failure is and confirm it against your ECAM messages and instrument indications. It takes twelve seconds. It probably saved my license more than once.

What the Manual Doesn't Tell You

The FCOM lists procedures but rarely explains the underlying logic. For example, the memory items for engine fires are short and precise, but the manual doesn't explain why you cutoff fuel before you discharge the agent. That's because the fuel cutoff is the primary fire suppression mechanism on the A320. The agent is a backup. Knowing that matters when you're executing the checklist at night in heavy rain and your brain is trying to autocomplete tasks from muscle memory. If you're second-guessing the sequence, you understand enough to trust it. Another thing the FCOM buries in the system descriptions section: the difference between what the ECAM tells you and what the aircraft is actually doing. The ECAM is a display system, not a diagnostic computer. It triggers alerts based on parameter thresholds and logical combinations, but it doesn't always reflect the true state of the aircraft. During a real electrical fault scenario on a red-eye from Paris to Montreal, we got conflicting ECAM messages suggesting two separate generator failures. The FCOM procedure for dual generator loss was clear, but our actual situation was a single bus tie fault cascading into false indications. The workaround was simple and not obvious from reading the manual: prioritize the master caution, cross-check with the electrical diagram page, and treat conflicting ECAM messages as noise until you confirmed the actual power configuration. It took about 90 seconds of manual switching and verification. The procedure I followed came from memory, not the FCOM, because by the time you find the right page in the electronic manual during that kind of scenario, the aircraft state has changed enough that the checklist you were reading is already obsolete.

Download and Access

The official A320 Flight Crew Operational Manual is not something you can legally download from the internet. It's owned by Airbus and distributed exclusively through authorized channels. Airlines contract it through their type rating training departments or through Airbus' own documentation portal. Pilots don't personally own it. Their employer provides access through the electronic flight bag system or the aircraft's onboard database. If you're looking for a legitimate copy, you go through your training department. They generate the operator-specific version from the Airbus documentation system, which means your manual will have slightly different page numbers, supplemental tabs, and operator notes compared to another airline's version. This is normal and expected. Don't try to use someone else's airline FCOM as your primary reference. The differences matter more than you think. For personal study purposes, some training academies andflight schools provide reference copies. These are usually older revisions but still useful for understanding the structure and content. The revision status matters less when you're learning the layout and learning where things are. It matters enormously when you're using it operationally. Always check the revision date against your airline's latest technical bulletins before relying on anything in the manual during a real flight.

Common Pitfalls

Most pilots make the same three mistakes with the FCOM. First, they don't memorize the location of the emergency procedures index. The electronic FCOM search works, but if your display freezes or the system reboots mid-flight, you need to know exactly where to go in the bound or offline version. Second, they treat the limitations section as background reading instead of a reference they check before every flight. The limitations tell you the envelope. Everything else in the manual tells you what happens when you exceed it. Third, they don't practice navigating the manual under time pressure. Run through a few abnormal procedures in the FCOM with a timer on your phone. Ten seconds to find the right page. Twenty seconds to read through the first decision branch. If you can't do that comfortably in the simulator or during your prep period, you won't do it at all in a real event. The FCOM is not a book you read cover to cover. It's a reference tool you learn to navigate fast. The people who use it well are the ones who have physically flipped through it hundreds of times during training and study, not the ones who read it once and feel prepared. There's no shortcut around that. The manual itself is dense, sometimes contradictory in edge cases, and occasionally wrong when it doesn't account for specific airline modifications. But it's the best single source of truth you have, and ignoring it because it's inconvenient is worse than struggling through it. One last thing. The performance data volume is where most operators get sloppy. The takeoff and landing performance tables are only valid for specific configurations and conditions. If you're operating from a high-elevation field with a long runway overrun area and non-standard temperatures, the default FCOM tables might not include your exact scenario. You'll need to interpolate or use the performance software that your dispatch department relies on. The FCOM performance section gives you the methodology, but it won't calculate the numbers for you in every case. Know when to use it and when to hand off to the performance team. Using the FCOM tables beyond their specified limits is how you get into trouble that no procedure in the manual can fix.