Skip to main content
ShakewellContact

Explainer

What Is a Fault Isolation Manual (FIM)?

A fault isolation manual takes a technician from a reported fault to its cause. It diagnoses; the maintenance manual is where the repair is done.

The Short Answer

From Symptom to Cause

A fault isolation manual (FIM) is the diagnostic document in an aircraft's maintenance library. It starts from what was reported, such as a crew write-up, a maintenance message, or a symptom on the ground, and leads through checks to the cause and the task that repairs it. Without one, troubleshooting tends to become replacing parts until the fault goes away, which is slow and expensive.

The name varies by manufacturer. The FAA's final rule for the 737 MAX lists the Boeing 737 Fault Isolation Manual among the maintenance documents revised, and the Australian Transport Safety Bureau describes Airbus changes to the A330/A340 trouble shooting manual (TSM). Different titles, one job.

Contents

What a FIM Typically Holds

Layouts differ by manufacturer, so treat this as the common shape, not a specification.

Entry points
Where a diagnosis starts: a crew report, a maintenance message from the aircraft, or a symptom a technician observes on the ground. The manual is usually searched by one of these, not read front to back.
Isolation logic
A sequence of checks and results, often drawn as a tree. Each outcome sends the technician to the next check or to a most likely cause.
Conditions and cautions
The aircraft state the checks assume (power on or off, systems configured, test equipment connected) and the safety warnings that go with them.
Pointers to the repair
Once the cause is found, a reference to the task that fixes it: removal and installation in the maintenance manual, a circuit check in the wiring data, or a part in the parts catalog.
Confirmation
The check that proves the fault is gone, so the aircraft is not released on a repair that did not work.

The Library

Where It Sits Among the Other Manuals

The FIM is part of the maintenance stream beside the aircraft maintenance manual, and it typically follows the same ATA system numbering, so a fault in a given system is found under that system. In the FAA's words about the 737 MAX, maintenance uses the FIM and the AMM together to assess the system, isolate the fault, resolve the issue, and return the airplane to service.

It hands work to its neighbors. An electrical diagnosis ends in the wiring diagram manual; a found structural defect goes to the structural repair manual; a component taken off the aircraft goes to its component maintenance manual, which has its own testing and fault isolation section. If the fault cannot be fixed before departure, whether the aircraft may fly is a separate decision made under the minimum equipment list, not in the FIM. The full manual family shows the whole set.

The Rules

What the Regulations Say

Part 25 requires the content, not the title. Appendix H to 14 CFR Part 25 lists what the Instructions for Continued Airworthiness must include, and among the maintenance instructions in H25.3(b)(2) is troubleshooting information describing probable malfunctions, how to recognize those malfunctions, and the remedial action for them. Our guide to instructions for continued airworthiness covers the full set. Maintenance itself is done to the methods in the current manufacturer's manual or ICA (14 CFR 43.13(a)), which is why a diagnostic path that is out of date is a compliance problem and not just an inconvenience.

Upkeep

Who Maintains It, and Why It Changes

The manufacturer writes and revises it, and operators keep their copies current. Revisions often come from fleet experience. In one ATSB case, the Airbus A330/A340 TSM was revised in October 2014 so that a specific maintenance message and cockpit effect pointed to the task that now names the pitot probes as a possible cause. Small logic changes like that are the point of the manual, and they are why a stale copy is risky.

Where the library is built to S1000D, fault isolation is a data module type with its own schema, and the information code list includes 420 for a general fault isolation procedure. Our guides to data module types and information codes explain how that diagnostic logic is structured, and process data modules cover the branching case.

FAQ

Questions We Hear

What is a fault isolation manual?

The manual a technician uses to trace a reported fault to its cause. It starts from a symptom or message, walks through diagnostic checks, and ends at a repair task. It diagnoses; the aircraft maintenance manual is where the repair is performed.

Is a fault isolation manual the same as a troubleshooting manual?

In purpose, yes. The name depends on the manufacturer. The FAA's 737 MAX final rule refers to the Boeing 737 Fault Isolation Manual, and the Australian Transport Safety Bureau refers to the Airbus A330/A340 trouble shooting manual (TSM). Part 25 itself asks only for troubleshooting information, not a document with a particular title.

What is the difference between a FIM and an AMM?

The FIM answers what is wrong and where to look. The AMM answers how to do the work: servicing, removal and installation, tests. The FAA describes the two used together on the 737 MAX: maintenance uses the FIM and AMM to assess the system, isolate the fault, resolve the issue, and return the airplane to service.

Does the FAA require a fault isolation manual?

It requires troubleshooting information, not a document with that name. Appendix H to 14 CFR Part 25 says the Instructions for Continued Airworthiness must include troubleshooting information describing probable malfunctions, how to recognize them, and the remedial action. How a manufacturer packages it is its decision.

How is fault isolation handled in S1000D?

As its own data module type, with its own schema. The information code list includes 420 for a general fault isolation procedure. See our guides to S1000D data module types and information codes for how the diagnostic logic is structured.

Get In Touch

Diagnostic Content That Holds Up

Fault isolation content has to be right the first time a technician uses it. Tell us where your troubleshooting content stands and what it has to be delivered in.