Commercial aviation operates within a densely layered regulatory framework, and yet the FAA has always recognized that a single written rule cannot perfectly cover every operational scenario. Two distinct mechanisms exist to reconcile real-world operations with regulatory requirements: the Letter of Authorization (LOA) and deviation authority. Both appear on the FAA Commercial Pilot Knowledge Test, both arise regularly in professional flying, and confusing one with the other — or misunderstanding the obligations each creates — can have serious certificate consequences. This article examines each mechanism in depth, explains how they interact, and highlights the nuances most likely to trip up a test candidate.
What Is a Letter of Authorization?
A Letter of Authorization is a formal, written document issued by the FAA Administrator — typically through a Flight Standards District Office (FSDO) or an automated approval process — that grants a specific individual, operator, or aircraft the authority to conduct an operation that would otherwise not be permitted under the standard provisions of the FARs, or that requires explicit FAA approval before it may be conducted. LOAs are creatures of the regulatory system itself; many sections of 14 CFR Part 91 explicitly state that a particular operation requires an LOA before it may begin.
Common examples a commercial pilot will encounter include authorization to operate in Reduced Vertical Separation Minimum (RVSM) airspace (14 CFR 91.180), which requires an LOA for operators not operating under Parts 121 or 135 and who wish to fly between FL 290 and FL 410. Similarly, operating certain advanced avionics under instrument flight rules, flying in certain special-use airspace, conducting ferry flights with inoperative equipment, or operating a U.S.-registered aircraft in foreign airspace can all require LOAs. For commercial operators, LOAs are also used to authorize specific types of low-altitude aerial work, parachute operations, and agricultural application flights.
Anatomy of an LOA
An LOA is not a blank permission slip. It is precisely scoped: it identifies the specific regulation or operational requirement it addresses, names the authorized party, states the conditions and limitations under which the authorization is valid, and may specify expiration dates or recurrent training requirements. The operator or pilot must carry the LOA — or have it immediately accessible — during the operations it covers, and must comply with every condition stated within it. An LOA that has been superseded, expired, or amended is no longer valid, even if the original document is physically present in the aircraft.
Equally important: violating the terms of an LOA is treated the same as violating the underlying regulation. If an LOA authorizing RVSM operations requires specific aircraft equipment to be operational and that equipment fails, the LOA no longer authorizes RVSM operations for that flight — the pilot must exit RVSM airspace. Continuing into RVSM airspace without meeting the LOA's conditions is a regulatory violation, and the FAA can pursue certificate action accordingly.
Requesting and Maintaining an LOA
LOAs are issued by the FAA in response to a formal application. The applicant must demonstrate that the proposed operation meets applicable safety standards and, in many cases, that crew members have received appropriate training. Once issued, the holder bears continuing responsibility to ensure the LOA remains current and that the conditions supporting the authorization — aircraft equipment, crew qualifications, operational procedures — remain in place. The FAA may amend or rescind an LOA at any time if safety concerns arise or if the basis for the authorization changes.
What Is Deviation Authority?
Deviation authority is an entirely different concept rooted in 14 CFR 91.3(b), which states that in an in-flight emergency requiring immediate action, the PIC may deviate from any rule in 14 CFR Part 91 to the extent necessary to meet that emergency. This provision exists because the drafters of aviation regulations understood a fundamental truth: no written rule, however carefully crafted, can anticipate every emergency situation a pilot will face. Safety — not regulatory compliance — must always be the PIC's first obligation when lives are at stake.
The scope of 91.3(b) is deliberately broad. If a sudden engine failure, a rapidly incapacitating medical emergency aboard, a catastrophic weather encounter, or any other immediate threat to the safety of the aircraft or its occupants requires the PIC to deviate from an altitude assignment, an airspace boundary, a required equipment rule, or any other Part 91 provision, the regulation explicitly authorizes that deviation. The PIC does not need to obtain ATC clearance before acting, does not need to call an agency for permission, and does not need to complete paperwork before taking the necessary action.
Accountability After the Deviation
Deviation authority is not immunity from scrutiny. Under 14 CFR 91.3(b), if the FAA requests a written report of the deviation, the PIC must provide it. This is a conditional obligation — the report is required only if the FAA asks for one — but it is a real obligation once triggered. The report must honestly describe what happened, what regulation was deviated from, why immediate action was necessary, and what the PIC did. The FAA will then evaluate whether the deviation was genuinely warranted.
A PIC who invokes 91.3(b) when no actual emergency existed — for example, to avoid an inconvenient reroute or to save fuel — cannot hide behind deviation authority. If the FAA determines the deviation was not the product of a genuine emergency requiring immediate action, enforcement action remains on the table. Conversely, a PIC who handles a legitimate emergency, deviates as necessary, and provides an honest report when requested is generally treated fairly by the system. The NASA Aviation Safety Reporting System (ASRS) report, while not a substitute for a regulatory report, can provide additional context and may offer limited protection against certain certificate actions when filed promptly and in good faith.
How LOAs and Deviation Authority Interact
These two mechanisms solve fundamentally different problems and should not be conflated. An LOA is prospective and planned — it authorizes a known, repeating operational need before the flight departs. Deviation authority is reactive and emergency-driven — it authorizes immediate action in response to an unforeseen threat during flight. A commercial pilot might hold an LOA for RVSM operations on every flight in a high-altitude turbine aircraft, and separately, might one day invoke 91.3(b) if a pressurization failure forces an emergency descent through RVSM airspace without prior ATC coordination. Both mechanisms are in play, but they arise from completely different circumstances and carry different post-event obligations.
Some regulations also permit operators to request advance deviation authority — essentially, a pre-approved plan to deviate from a specific rule under defined circumstances, such as certain equipment requirements during ferry flights. This type of advance deviation is handled through the LOA process and is therefore more closely related to an LOA than to emergency deviation authority under 91.3(b).
Key Numbers and Rules
- 14 CFR 91.3(b) — the source of PIC emergency deviation authority for Part 91 operations.
- 14 CFR 91.180 — requires an LOA for operators wishing to conduct RVSM operations who are not otherwise covered under Parts 121 or 135.
- RVSM airspace — FL 290 through FL 410, where 1,000-foot vertical separation is maintained; an LOA and specific equipment are required.
- Written report obligation — triggered only by an FAA request following a 91.3(b) deviation; not automatically required but mandatory when requested.
- LOA validity — contingent on all stated conditions remaining met; an LOA does not protect an operator who no longer meets the conditions under which it was granted.
- Certificate action risk — violating LOA terms or invoking 91.3(b) without a genuine emergency can both result in FAA enforcement.
Common Test Traps
- The report is conditional, not automatic. Many test questions frame the post-deviation written report as either always required or never required. The correct answer: it is required only if the FAA requests it.
- 91.3(b) does not apply to ground operations. The statute says in-flight emergency. Pre-departure situations are not covered by this provision.
- An expired or amended LOA provides no protection. Candidates sometimes assume that possessing a physical LOA document is sufficient. If the document's conditions are no longer met or it has been superseded, it has no legal force.
- LOAs can be rescinded at any time. There is no vested right to an LOA; the FAA can modify or revoke one whenever safety or regulatory compliance demands it.
- Deviation authority is not a cost-saving tool. It exists solely for safety emergencies — any attempt to use it for operational convenience undermines its purpose and exposes the PIC to enforcement.
- RVSM authorization requires more than just an LOA. The aircraft must also be equipped with the specified avionics and the crew must be trained; the LOA formalizes that the FAA has accepted all of those elements together.