The Flight Data Recorder (FDR) is one of the most critical safety systems on a transport-category aircraft. Often called a "black box" — though in practice it is painted bright orange for visibility — the FDR continuously captures a defined set of aircraft performance and environmental parameters during flight. When an accident or serious incident occurs, investigators from the NTSB rely on FDR data to reconstruct the sequence of events with precision that no witness account can match. For the Aviation Maintenance Technician (AMT) working on the airframe side, the FDR is more than just a sealed recorder unit: it is the downstream endpoint of a complex web of sensors, data buses, and power interfaces that must be maintained, tested, and documented with extreme care.
This article covers how the FDR system is architected, what parameters are legally required, how sensor data reaches the recorder, and what the regulations demand of both operators and the technicians who service these systems. Understanding this material prepares an AMT not only for the FAA Airframe Knowledge Test but also for real shop decisions that directly affect flight safety and regulatory compliance.
FDR System Architecture
A modern FDR installation is not a standalone device. It is the final link in a data chain that originates at dozens — sometimes hundreds — of individual sensors and transducers distributed throughout the aircraft. Data from these sensors is collected, formatted, and forwarded to the recorder by the Flight Data Acquisition Unit (FDAU), sometimes called a Flight Data Acquisition and Management Unit (FDAMU) on newer aircraft. The FDAU reads both analog signals (such as pressure transducer voltage outputs) and digital data streams from the aircraft's avionics buses.
Most modern transport-category aircraft use an ARINC 429 data bus as the primary digital backbone. Avionics systems — including the Air Data Computer (ADC), Inertial Reference System (IRS), and the Flight Management System (FMS) — transmit parameter words onto ARINC 429 buses, which the FDAU monitors and samples at the rates required by regulation. On newer fly-by-wire aircraft, ARINC 629 or proprietary buses may supplement or replace ARINC 429 in certain subsystems. The FDAU formats all incoming data into a standardized data frame and forwards it to the recorder unit itself.
The recorder unit stores data on a Solid-State Memory Module (SSMM). Older aircraft may still use metallic foil or magnetic tape recorders, but the industry has moved almost entirely to solid-state technology because it is far more reliable, offers greater storage capacity, and is more survivable in crash environments. The memory module is housed in a crash-survivable enclosure that is designed to withstand extreme impact forces, fire temperatures up to 1,100°C for 30 minutes, deep-water immersion, and prolonged saltwater exposure — requirements outlined in TSO-C124 and the associated EUROCAE/ED-55 or ED-112 performance standards that the FAA references.
An underwater locator beacon (ULB) is attached to the recorder housing. This battery-powered device activates automatically on water immersion and emits a 37.5 kHz acoustic pulse to help recovery teams locate the recorder at depths up to 6,000 meters. Regulations require the ULB battery to be replaced or certified before its expiration date, a routine maintenance task the AMT must track in the aircraft records.
Mandatory Parameters and 14 CFR Requirements
The specific parameters an FDR must record — and how precisely — are set by 14 CFR Part 91.609, Part 121.343, Part 121.344, Part 125.226, and Part 135.152, depending on the type of operation and the aircraft's certification vintage. The FAA has expanded the parameter list significantly over the decades as aircraft became more complex and as accident investigations revealed gaps in the data record.
For large transport-category aircraft operated under Part 121, the regulations establish tiered requirements based on the aircraft's manufacture date and the date it was first equipped with an FDR. Aircraft manufactured after specific cut-off dates must record progressively more parameters. The most modern requirements mandate a minimum of 88 parameters, while the baseline for older aircraft may be as few as 11. The FAA's regulatory history reflects lessons learned: after investigations that could not fully reconstruct events due to missing data, new parameters were added to the mandatory list.
Core parameters required across virtually all FDR-equipped aircraft include:
- Time — UTC time or elapsed time, providing the reference frame for all other data.
- Pressure altitude — derived from the Air Data Computer, recorded in feet.
- Indicated airspeed — also from the ADC, in knots.
- Heading — magnetic or true, from IRS or compass system.
- Normal acceleration (vertical g) — from an accelerometer, critical for structural analysis.
- Pitch attitude — from the IRS or attitude and heading reference system (AHRS).
- Roll attitude — also from IRS or AHRS.
- Radio transmission keying — records when the crew transmits, correlating with CVR recordings.
- Thrust of each engine — typically engine pressure ratio (EPR) or N1 fan speed.
- Autopilot/autothrottle engagement status.
- Control surface positions — on newer-generation aircraft, individual positions of elevator, aileron, rudder, and spoilers.
- Flap and slat positions.
- Landing gear position.
- Warnings — such as GPWS/TAWS alerts, TCAS RAs, and stall warnings.
Sampling rates vary by parameter importance. Normal acceleration may be sampled at 8 times per second, while a relatively stable parameter like flap position may be sampled only once every 2 or 4 seconds. The FDAU is programmed with a specific data frame structure that ensures each parameter is sampled at its required rate and that the recorder's frame format is consistent with the aircraft's configuration documentation.
Why the FDR Matters to the AMT
The FDR system's value in accident investigation is obvious, but its day-to-day importance to the AMT is sometimes underestimated. The recorder captures data continuously from the moment power is applied through engine start, taxi, flight, and shutdown. This means FDR data can also be used for Aircraft Health Monitoring (AHM) and routine maintenance analysis — identifying developing trends in engine performance, exceedances of structural load limits, or repeated activation of warning systems long before they become serious problems.
From a regulatory standpoint, operators are required to periodically read out and verify FDR data under 14 CFR 121.343(c) and 121.344, with the operational readout, correlation, and evaluation program detailed further in guidance such as AC 121-344 (Digital Flight Data Recorder Data Recovery, Readout, and Analysis) and the operator's approved operations specifications, to confirm the system is functioning correctly and that all required parameters are being recorded within their specified accuracy ranges. This readout is performed using specialized ground support equipment that interfaces with the recorder's data output port. The AMT may be responsible for connecting this equipment, initiating the readout, and documenting the results. If a parameter is found to be out of tolerance or missing, the FDR system is considered unairworthy and the aircraft cannot be dispatched until the fault is corrected.
Significantly, 14 CFR 91.609 makes it illegal to operate an aircraft with a deactivated or inoperative FDR unless the aircraft is being flown to a maintenance facility for repairs. There is no MEL (Minimum Equipment List) provision that simply allows indefinite continued operation with a failed FDR; the system must be repaired promptly. The AMT must be familiar with this operational restriction because a deferred maintenance decision on an FDR can ground an aircraft.
Key Numbers and Rules
- FDR must retain the last 25 hours of recorded data (Part 121.344); older requirements specified shorter durations, but 25 hours is the current standard for most transport aircraft.
- The ULB must operate for a minimum of 30 days after activation and must be replaced before its battery expiration date.
- Periodic FDR readout and verification is required by regulation for Part 121 operators, per 14 CFR 121.343(c)/121.344 and associated guidance such as AC 121-344.
- The crash-survivable enclosure must withstand a 3,400 g impact (per TSO performance standards), fire at 1,100°C for 30 minutes, and immersion to 6,000 meters depth.
- Minimum parameter counts range from 11 parameters (earliest FDR rules) to 88 or more parameters for modern Part 121 aircraft depending on manufacture date.
- There is no FAA proximity requirement that the FDR and CVR be installed near each other; in fact, where two combination recorders are installed, 14 CFR 121.359(h) requires them to be as far apart as practicable. A single recorder unit is often installed toward the aft of the aircraft for crash survivability, but this is not a universal proximity mandate.
- An FDR cannot be installed as a replacement unless it holds the appropriate Technical Standard Order (TSO) authorization, such as TSO-C124b.
Common Test Traps
- Color confusion: Students often write that the FDR is black. It is bright orange (sometimes described as international orange) to aid post-crash recovery. The nickname "black box" is informal and historically rooted, not descriptive of the actual color.
- FDR vs. CVR roles: The FDR records flight parameters (performance data); the Cockpit Voice Recorder (CVR) records audio from the cockpit area microphone and crew headsets. They are distinct systems with separate regulatory requirements, though they are often installed near each other.
- Data retention duration: Some questions try to confuse the 2-hour CVR retention requirement with the 25-hour FDR retention requirement. Remember: the CVR retains the last 2 hours; the FDR retains the last 25 hours.
- Annual readout obligation: The FDR is not a fit-and-forget installation. Regulations require periodic readout and verification of parameter accuracy under 121.343(c)/121.344 and related guidance. Failing to perform this check is a regulatory violation, not just a maintenance oversight.
- ULB battery currency: A common trap is to assume that the ULB is serviceable if it has never been activated. The battery has a calendar expiration date and must be replaced by that date regardless of activation history — much like an ELT battery requirement under 14 CFR 91.207.