What information must be included in a flag carrier flight release under 14 CFR 121.689?

A flag or supplemental flight release must include the carrier's name, aircraft make and model, tail number, flight number, departure and destination airports, any required alternates, minimum fuel supply, type of operation, applicable weather reports and forecasts, and the signatures of both the aircraft dispatcher and the pilot in command. All of these elements must be present before the flight can legally depart.

Can the pilot in command depart with less fuel than what is listed on the dispatch release?

No. The minimum fuel figure entered on the flight release by the dispatcher is a legally binding floor under 14 CFR Part 121—the aircraft may not depart with less fuel than that amount. The PIC always has the authority to take on more fuel than the release specifies, but departing below the dispatched minimum is not permitted under any circumstances.

What is the difference between 14 CFR 121.533 and 14 CFR 121.689 for dispatcher purposes?

14 CFR 121.533 establishes the concept of shared operational control, defining the joint responsibility that the certificate holder's dispatcher and the pilot in command share for the safety of each flag carrier flight. 14 CFR 121.689, by contrast, specifies the actual contents that must appear in the written flight release document itself. In short, 121.533 explains who is in charge and how, while 121.689 dictates what the release must contain.

Required Contents of a Flag and Supplemental Flight Release Under 14 CFR 121.689

The flight release is one of the most consequential documents in air carrier operations. For flag and supplemental carriers operating under 14 CFR Part 121, the flight release serves as the formal, written authorization that both the pilot in command and the aircraft dispatcher must sign before a flight can legally depart. It reflects the shared responsibility for operational control that lies at the heart of the dispatcher's role. Every element required by 14 CFR 121.689 exists for a reason—together they ensure that the crew, the airline, and the dispatching function have verified that the flight is safe and legal before the wheels ever leave the ground.

It is important to note that while 14 CFR 121.689 specifies the contents of the release document itself, the broader concept of shared operational control is codified in 14 CFR 121.533, which establishes that the certificate holder (through its dispatchers) and the pilot in command share authority over the safety of the flight. The flight release is the physical instrument through which that shared authority is exercised and documented. No flag or supplemental flight may depart without a properly completed and signed release.

What Is a Flight Release?

A flight release—sometimes called a dispatch release—is a written document prepared by the aircraft dispatcher before each flight. It is not simply a paperwork formality; it is a legal certification that the dispatcher has evaluated all relevant information and determined that the proposed flight can be conducted safely and in compliance with all applicable regulations. The pilot in command reviews the release, may add limitations or conditions, and then co-signs it, indicating concurrence. Until both signatures are on the document, the flight cannot legally depart under 14 CFR Part 121 flag or supplemental rules.

The release travels with the flight in some form and must be retained by the certificate holder. This creates an auditable record that regulators can examine after the fact to verify that proper dispatch procedures were followed on any given operation.

Required Contents Under 14 CFR 121.689

The regulation specifies a precise list of information that every flag or supplemental flight release must contain. Each item serves a distinct operational or safety purpose.

Company or organization name. The legal name of the air carrier conducting the operation must appear on the release, establishing which certificate holder is exercising operational control.
Make and model of the aircraft. This identifies the specific aircraft type, which determines applicable performance data, fuel requirements, and equipment requirements.
Aircraft registration number (N-number). The tail number ties the release to a specific airframe, allowing maintenance records, airworthiness status, and MEL items to be tracked to that exact aircraft.
Flight or trip number. A unique identifier so the release can be matched to ATC records, crew schedules, and maintenance logs.
Departure airport, destination airport, and alternate airports. These define the planned route structure. For flag operations, the release must include any alternate airports the dispatcher has designated based on destination weather and regulatory requirements.
Minimum fuel supply. The dispatcher must specify the minimum fuel required for the flight. This is not a suggestion—it is a legally binding floor. The pilot in command may add more fuel, but the aircraft may not depart with less than the amount shown on the release.
Type of operation. The release must identify the type of flight (e.g., IFR, VFR, or the applicable operational rule such as flag or supplemental). This determines which set of regulatory requirements governs the flight.
Weather reports and forecasts. Current and forecast weather for the departure point, en route significant weather, destination, and alternate airports must be included or referenced. This documents that the dispatcher reviewed meteorological conditions before authorizing the flight.
Pilot in command and dispatcher signatures. Both the PIC and the aircraft dispatcher must sign the release. The dispatcher signs first, authorizing the flight; the PIC signs, acknowledging review and concurrence. If the PIC disagrees with any element, he or she may add conditions or refuse to sign, which grounds the flight.

Although 14 CFR 121.689 does not itself enumerate NOTAMs among the release's required contents, applicable Notices to Air Missions affecting the route, airports, or navigation facilities are provided to the crew through other required dispatch documentation and briefings, ensuring the crew is aware of hazards, closed runways, unserviceable navaids, or other operational constraints before departure.

For supplemental operations, there is an additional nuance: because supplemental carriers often operate on irregular schedules and may not have the same continuous dispatcher-crew communication infrastructure as domestic carriers, the release may be signed before departure and then carried by the crew. The dispatcher must nevertheless have reviewed all required information before issuing the release.

Why Each Element Matters Operationally

It is easy to view the required contents as a bureaucratic checklist, but each item directly supports safety. The minimum fuel entry, for example, prevents a situation where ground personnel or pressure from above might tempt a crew to depart with less fuel than the dispatcher calculated. Because the dispatcher has studied winds aloft, alternate requirements, and contingency fuel, the fuel figure on the release represents professional analysis—not guesswork.

The weather reports requirement ensures that neither the dispatcher nor the crew can claim ignorance of known meteorological hazards. If a destination airport had deteriorating weather and the release was signed without accounting for it, both parties have failed in their duty. The documentation requirement creates accountability.

The alternate airport requirement is particularly important for flag operations, which often involve overwater or long-range routes where diversion options may be limited. By specifying alternates on the release, the dispatcher has pre-analyzed the feasibility of a diversion and verified that the fuel on board is sufficient to reach those alternates under instrument conditions.

Shared Operational Control and 14 CFR 121.533

The flight release exists within the larger framework of shared operational control described in 14 CFR 121.533. That regulation establishes that the certificate holder is responsible for the operational control of each flight, and that operational control is exercised jointly by the dispatcher and the pilot in command. Neither party can override the other unilaterally when it comes to safety. If the dispatcher believes a flight is unsafe, the dispatcher must refuse to issue the release. If the PIC believes the flight is unsafe after the release is issued, the PIC must refuse to depart or must land as soon as practical if already airborne.

This mutual veto concept is fundamental to the dispatcher certificate. The flight release is the tangible evidence that both parties reviewed the same information and reached agreement that the flight is legal and safe. Courts, the NTSB, and the FAA all look at the flight release when investigating incidents or accidents involving air carriers.

Key Numbers and Rules

14 CFR 121.689 specifies the required contents of the flag/supplemental flight release.
14 CFR 121.533 establishes shared operational control between dispatcher and PIC for flag carriers.
14 CFR 121.595 addresses the dispatcher's authority to restrict or cancel a flight.
The release must be retained by the certificate holder for a period specified in the carrier's operations specifications—typically at least 3 months, though specific retention periods appear in 14 CFR 121.711 for flight release records.
Both the PIC and the dispatcher must sign the release before departure; a release signed by only one party is not valid.
The dispatcher must include all alternates required under 14 CFR 121.617 (flag alternates) or 121.621 (domestic/supplemental alternates) as applicable.
The minimum fuel figure on the release sets a legal floor—the aircraft must not depart with less fuel than the release specifies.

Common Test Traps

Confusing domestic and flag release requirements. The Aircraft Dispatcher Written exam may present questions about domestic releases (14 CFR 121.687) versus flag/supplemental releases (14 CFR 121.689). Know that both require similar information, but flag operations have additional considerations for extended overwater routes and international alternates.
Assuming the PIC can override the fuel figure downward. The PIC can always add fuel but cannot legally depart with less than the minimum specified on the release. Many students assume the PIC as captain has final authority over fuel—but the release figure is a regulatory floor, not a suggestion.
Forgetting that the dispatcher signs first. The dispatcher issues the release (signs first), and the PIC concurs (signs second). Reversing this order on an exam answer is a common error.
Assuming NOTAMs are an enumerated required content item under 121.689. Students sometimes list NOTAMs alongside weather, fuel, and airports as required content, but 14 CFR 121.689 does not enumerate NOTAMs among the release's specified elements—know precisely which items the regulation itself requires.
Misidentifying which CFR governs the release contents vs. operational control. 14 CFR 121.689 governs what goes IN the release; 14 CFR 121.533 governs the shared authority framework. These are separate regulations with distinct purposes, and examiners love to test whether you know which is which.