Skip to main content
Operational Control & the Dispatch ReleaseAircraft Dispatcher

Dispatch Release Recordkeeping and Retention Requirements Under 14 CFR 121.695

Under 14 CFR Part 121, dispatch releases must be signed, carried aboard, and retained by both the airline and the flight crew for specified periods—understanding these requirements is essential for the Aircraft Dispatcher certificate written exam and practical test.

Reviewed & updated · Grounded in current FAA handbooks & the ACS

When an air carrier flight departs under 14 CFR Part 121, the dispatch release is far more than a procedural formality. It is a legally binding operational document that establishes shared authority and responsibility between the aircraft dispatcher and the pilot in command (PIC). Because the dispatch release defines the legal framework of the flight, the FAA imposes strict requirements governing how it must be prepared, signed, carried, and retained. Candidates preparing for the Aircraft Dispatcher Airman Knowledge Test—and ultimately the oral and practical examination—must understand these recordkeeping obligations in detail, because examiners frequently test both the time limits and the parties responsible for compliance.

Although the question title references 14 CFR 121.695, the foundational authority for operational control and the dispatch release system under Part 121 is rooted in 14 CFR 121.533, which establishes the shared responsibility between the PIC and the aircraft dispatcher. The recordkeeping requirements flow directly from that authority structure: because both parties share responsibility for the safety of the operation, both parties—and the certificate holder itself—bear obligations to document and retain the release. This article examines what those obligations are, why they exist, and how they play out in day-to-day airline operations.

The Dispatch Release and Shared Operational Control

Under 14 CFR 121.533, the certificate holder (the airline) is responsible for operational control of each flight. That responsibility is exercised jointly by the PIC and the aircraft dispatcher. The PIC has final authority over the safe conduct of the flight once airborne, but before departure the dispatcher and PIC must both review and agree upon the dispatch release. Neither may legally commence the flight without that mutual concurrence. This joint-authority model is unique to Part 121 and is what separates the aircraft dispatcher's legal role from a mere flight planner or scheduler.

The dispatch release itself must contain specific information prescribed by 14 CFR 121.687, including flight identification, aircraft registration, departure and destination airports, alternate airports where required, type of operation (IFR or VFR), minimum fuel supply, and a brief statement of weather conditions and NOTAMs relevant to the flight. Once that document is prepared by the dispatcher, it must be reviewed and signed by both the dispatcher and the PIC before departure. That co-signature is the operational manifestation of shared control under 121.533.

How Recordkeeping and Retention Work

Once a dispatch release is executed, the regulatory system imposes obligations on three entities: the PIC, the aircraft dispatcher, and the certificate holder (airline). Each has a distinct role.

The Pilot in Command's Obligations

The PIC must carry the dispatch release—or a signed copy—aboard the aircraft for the entire duration of the flight. This means a physical or approved electronic copy must be accessible in the cockpit from engine start to engine shutdown at the destination. The purpose is straightforward: if the flight encounters an en-route diversion, a regulatory inspection, or an emergency requiring reference to the fuel plan or alternate requirements, the release must be immediately available to the crew. After the flight is complete, the PIC's carriage obligation ends, but the retention obligation transfers to the airline.

The Certificate Holder's Retention Obligation

The certificate holder is required to retain a copy of every dispatch release for a period of at least 90 days. This retention requirement exists so that the FAA and the National Transportation Safety Board (NTSB) can reconstruct the operational picture of any flight should an incident, accident, or enforcement action arise. The 90-day window covers the vast majority of complaints, irregularities, and preliminary accident investigations that emerge after a flight. Retention may be accomplished through paper records, microfilm, or approved electronic recordkeeping systems, provided the records are legible and retrievable.

The Dispatcher's Ongoing Role

The aircraft dispatcher who signs the release retains a professional and legal stake in its accuracy even after the flight departs. Under 121.533, the dispatcher continues to monitor the flight and must issue an amended dispatch release if conditions change materially—such as destination weather falling below minimums, a NOTAM closing a runway, or ATC issuing ground delay programs that affect fuel burn. Any amended release carries the same documentation and retention requirements as the original. Dispatchers must also be prepared to present records of their releases during FAA inspector surveillance, known as AAIP (Air Carrier Aviation Safety Inspector Program) checks.

Why These Requirements Matter Operationally

Recordkeeping requirements are not bureaucratic box-checking—they are the paper trail that makes the joint-authority system legally coherent. Consider what happens when an accident occurs: investigators need to know exactly what weather, fuel, and alternate information the crew and dispatcher agreed upon before departure. Without a retained dispatch release, it becomes impossible to determine whether the operation was conducted in compliance with the approved OpSpecs (Operations Specifications) and the airline's approved Dispatch Deviation Guide. The 90-day retention period ensures that records survive long enough for any ordinary post-flight investigation or passenger complaint to be addressed with documentary evidence.

From a safety culture perspective, the requirement that the PIC carry the release aboard the aircraft reinforces crew awareness of the planned fuel load, alternates, and any special conditions that were flagged at dispatch. A dispatcher who annotates the release with a SIGMET affecting the route, for example, is not just meeting a legal formality—that annotation may be the single piece of information that prompts the crew to reassess their fuel state over a weather system. The document travels with the flight because the flight crew may need it.

For the aircraft dispatcher personally, signing a dispatch release is an act with legal consequences. If the release is found to have been issued in violation of Part 121 regulations—such as dispatching below minimums, failing to require a proper alternate, or listing an insufficient fuel load—the dispatcher faces potential certificate action under 49 USC 44709 and FAA enforcement under 14 CFR Part 13. Accurate, well-documented releases therefore protect both the traveling public and the dispatcher's own certificate.

Key Numbers and Rules

  • Retention period: The certificate holder must retain each dispatch release for at least 90 days after the flight.
  • Carriage requirement: The PIC must have the dispatch release (or a signed copy) aboard the aircraft for the entire flight.
  • Co-signature requirement: Both the aircraft dispatcher and the PIC must sign the release before departure; either party may refuse to sign, which grounds the flight.
  • Amendment requirement: If conditions change materially en route, the dispatcher must issue an amended dispatch release, subject to the same documentation requirements as the original.
  • Authority basis: Shared operational control authority flows from 14 CFR 121.533; content requirements for the release itself are found in 14 CFR 121.687.
  • No departure without release: Under Part 121, a flight may not depart unless a dispatch release has been prepared and signed. This is an absolute prohibition, not a best practice.

Common Test Traps

  • Confusing retention periods: The dispatch release retention requirement is 90 days. Do not confuse this with load manifest retention (also 90 days) or other records that may have different windows. The exam may present distractors with 30-day or 6-month options.
  • Who retains the record: The certificate holder retains the dispatch release, not the individual dispatcher. The dispatcher signs it, but the airline's record system holds it. Mixing these up is a common error on the knowledge test.
  • Carriage vs. retention: Carriage (PIC carries aboard) and retention (airline keeps for 90 days) are two separate obligations applying to different parties. The exam frequently tests whether students know which requirement applies to whom.
  • Amended releases: Students sometimes assume that once a flight departs, the dispatch release is static. In fact, an amended release can and must be issued if conditions change, and it carries the same legal weight and documentation requirements as the original.
  • 121.533 vs. 121.695: Examination questions may reference either section number. Know that 121.533 establishes the authority and responsibility framework, while the specific recordkeeping language appears in adjacent sections of Part 121. Do not let section number confusion cause you to miss a question about the underlying concept.

Frequently asked questions

How long must an airline keep dispatch release records under 14 CFR Part 121?

The certificate holder (airline) must retain each dispatch release for at least 90 days after the flight is completed. This retention requirement allows the FAA and investigators to reconstruct the operational details of any flight in the event of an incident, accident, or enforcement action. The records may be kept in paper or approved electronic format as long as they are legible and retrievable.

Who is required to sign the dispatch release before a Part 121 flight can depart?

Both the aircraft dispatcher and the pilot in command must sign the dispatch release before the flight may legally depart. This co-signature reflects the shared operational control authority established under 14 CFR 121.533. If either party refuses to sign—because of disagreement over weather, fuel load, or any safety concern—the flight is effectively grounded until the issue is resolved.

Does the pilot in command need to carry the dispatch release on board the aircraft during a Part 121 flight?

Yes. The PIC is required to carry the dispatch release, or a signed copy, aboard the aircraft for the entire duration of the flight. This ensures the crew has immediate access to the agreed-upon fuel plan, alternate airports, weather conditions, and any special notations made by the dispatcher at the time of departure. After the flight lands, the ongoing retention obligation falls to the certificate holder, not the crew.

See also

FAA source

14 CFR 121.533 (Responsibility for operational control: domestic and flag operations); 14 CFR 121.687 (Dispatch release: domestic and flag operations); 14 CFR Part 121, Subpart U (Dispatching Authority: Domestic Operations)

This page is an original, plain-English summary grounded in the public-domain FAA handbook cited above. Click the citation to open the official FAA handbook PDF. It is a study aid, not a substitute for the official handbook or the regulations.

Test yourself on dispatch release recordkeeping and retention requirements under 14 cfr 121.695

Reading builds understanding — questions build a passing score. Drill ACS-aligned questions free, no account needed.

Take a free practice test →