Flight Data Acquisition Unit (FDAU)

The Flight Data Acquisition Unit (FDAU) is a central subsystem that measures, converts into digital format, organizes, and transmits physical, mechanical, and electronic events occurring on an aircraft to Flight Data Recorders (FDR). This unit collects analog, digital, and discrete signals from various sensors during flight, arranges them within a predefined data frame, and transmits them to the FDR at specified time intervals for recording.

The FDAU is critically important for monitoring flight safety, planning maintenance procedures, and establishing cause-and-effect relationships in accident or incident analyses. Hundreds of parameters such as altitude, speed, acceleration, engine performance, control surface positions, system statuses, and fuel quantity are collected via the FDAU and securely recorded. In modern aircraft, this data collection process occurs at rates of hundreds of words per second.

Historical Development

With the evolution of aviation, the need for systematic data recording emerged to facilitate technical analysis of aircraft accidents. In the early period (1930s), only simple mechanical indicators observable by pilots were used. In the 1940s, V-g recorders began mechanically recording speed (V) and g-force. The 1950s marked a transition to actual recording technology. With the growth of civil aviation, devices based on metal foil and photographic film were developed, but these could record only five to six fundamental parameters. As flight complexity increased, magnetic tape-based systems were adopted in the 1960s. These systems digitized analog signals (DFDR), enabling higher resolution data recording, though capacity and analysis time remained limited.

A critical development occurred in the 1970s: the Flight Data Acquisition Unit (FDAU) was introduced as an intermediary to overcome the disadvantage of recorders directly collecting data from sensors. The FDAU assumed the responsibility of collecting signals from sensors, conditioning them, forming digital frames (data frames), and transmitting them to the passive recording device, the FDR. This functional separation created a paradigm shift in data management and led to the emergence of standards such as ARINC 573. In the 1980s, microprocessor-based systems and the ARINC 717 standard significantly increased data recording speeds and the number of parameters. During the same period, magnetic tapes were replaced by more reliable and cost-effective solid-state memory. From the 1990s onward, the concept of flight data collection expanded; the FDAU began to be used not only for post-accident investigations but also in proactive monitoring programs such as FOQA (Flight Operations Quality Assurance) and ACMS (Aircraft Condition Monitoring Systems). The function of the FDAU evolved beyond mere recording to include intelligent data collection capabilities for real-time system health monitoring and fault analysis during flight.

Today, the FDAU has moved beyond classical FDR systems and become part of an integrated Flight Data Acquisition and Management System (FDAMS). Modern FDAMS architectures provide flexibility through reconfigurable hardware and Visual Algorithm Definition (VADAR) methods, enabling easy integration of new sensors into the system.

Basic Components and Operating Principle

The Flight Data Acquisition Unit (FDAU) is a high-reliability avionics module responsible for the centralized collection, conditioning, time-stamping, and transmission of digital and analog information from various aircraft subsystems to flight data recorders. In modern aircraft, the FDAU acts as a “data bridge,” converting physical measurements from sensors into electronic signals, sampling them at a defined time base, and transmitting them to the FDR, QAR, or ACMS systems in predefined data frames.

The architecture of an FDAU system is modular and typically consists of six fundamental components: input interfaces, signal conditioners, digitization unit, timing and synchronization circuit, data framing logic, and output interface. Each of these components ensures the safe, accurate, and standardized processing of different types of data.

Input Interfaces

The input interface, the first component of the FDAU, collects signals from numerous sensors and systems on the aircraft. These signals are classified into three main types:

Analog Inputs: Continuous physical variables such as pressure, temperature, engine RPM, hydraulic pressure, and fuel level fall into this category. These signals typically arrive as voltage levels in the range of 0–5 V or ±32 V. The FDAU’s analog input circuits filter these signals before sampling to bring them into a linear measurement range.

Discrete Inputs: These are two-state (0 or 1) signals such as on/off switches, warning lights, and position indicators. They usually originate from relay or transistor-based contacts and represent the instantaneous status of aircraft systems (e.g., landing gear extended or retracted).

Digital Inputs: These are high-speed digital data streams from other computer systems on the aircraft. They are based on communication protocols such as ARINC 429, ASCB (Avionics Standard Communication Bus), or Collins Serial Digital Data Bus (CSDB). Parameters from systems such as IRS (Inertial Reference System), EFIS (Electronic Flight Instrument System), and FMC (Flight Management Computer) are received via these lines.

In some systems, separate modules exist for frequency-based signals such as tachometer data or rotational rates. The GEC-Marconi ESD1954 series FDAU can directly process such data with eight frequency inputs and one GMT clock input.

Signal Conditioners

Analog and digital signals cannot be recorded directly; they must be standardized. For this purpose, each input channel passes through a signal conditioner circuit. These circuits perform level conversion, noise filtering, DC offset adjustment, and linearization. Conditioners also amplify low-level signals from sensors such as thermistors or piezoelectric devices, ensuring measurement accuracy at the Analog-to-Digital Converter (ADC) inputs.

Digitization (Analog-to-Digital Conversion)

After signal conditioning, the data is digitized. The FDAU samples measurements from each channel at a specific sample rate. The sampling rate depends on the dynamic characteristics of the parameter; for example, airspeed may be sampled once per second while engine vibration is sampled eight times per second.

Timing and Synchronization

For flight data to be meaningfully analyzed, all parameters must be recorded on the same time base. The frame counter or relative time counter within the FDAU generates a time stamp for each data item. Synchronization is typically provided via a Greenwich Mean Time (GMT) source. ARINC 585-compliant clock signals ensure time alignment with other systems on the aircraft. This feature enables data from different systems to be accurately aligned on a common timeline during analysis.

Data Framing and Formatting

After all sensor data is collected, the FDAU places it into a predefined data frame. The data frame is a parameter sequence defined in a programmable ROM specific to the aircraft. A standard frame is typically completed every four seconds and consists of four one-second subframes. Each subframe contains 64, 128, 256, or 512 words; each word is 12 bits long. This structure, along with timing signals, is transmitted to the FDR using Harvard bi-phase encoding. In Harvard bi-phase encoding, each bit carries both data and synchronization information, allowing correct data reading at the receiver without requiring a separate clock signal.

Output Interface and Data Transmission

The final component of the FDAU is the output interface that transmits data to the Flight Data Recorder (FDR) or Quick Access Recorders (QAR). Standard systems have two types of outputs:

Main Data Bus: Provides a data flow of 64–256 words per second in ARINC 717 or Harvard bi-phase format. This bus is directly connected to the FDR.

Auxiliary Data Bus: Operates in RZ (Return-to-Zero) format for QAR or maintenance analysis systems. This bus enables rapid access to operational data.

During data transmission, the FDAU’s Built-In Test Equipment (BITE) continuously monitors its own functionality. The BITE system instantly detects conditions such as faulty signals, missing parameters, or frame shifts and sends this information to the maintenance logging system.

Integrated Monitoring and Expansion Capability

Modern FDAUs go beyond mere data transmission and also perform system monitoring and maintenance planning functions. For this purpose, they feature four or five expansion slots due to their modular card structure. Modules for engine performance monitoring or airframe usage monitoring can be added to these slots. This expandability has transformed the FDAU’s role from simple data collection to becoming an integral part of a comprehensive flight monitoring system. Especially in modern FDAMS architectures, new sensors can be defined and data flows reconfigured via FDAU software.

General Process Diagram of Operating Principle (Generated by Artificial Intelligence.)

Data Collection Process and Flow Structure

The flight data collection process has a layered structure that involves gathering raw data from sensors and systems on the aircraft and transmitting it to the Flight Data Recorder (FDR) in a specific time sequence and format. This process encompasses both hardware data flow and digital coding organization, ensuring that parameters acquired during flight are stored securely, completely, and in an analyzable form.

Data Flow and System Organization

Flight data reaches the FDAU from numerous sources such as sensors, indicators, relays, and system control modules. The data is classified into four main categories: discrete, analog, synchro, and digital (digital data buses such as ARINC 429). These data are collected at a predefined sampling frequency, digitized, and encoded in Harvard bi-phase format for transmission to the FDR. The FDAU’s role is not only to collect data but also to synchronize it with time stamps, perform error checking, and carry out validation procedures before recording.

Data collected by the FDAU is placed onto the data bus via an input/output buffer and managed by the central processing unit (CPU). The CPU controls the timing of the data flow, performs self-test operations, and sends results to the Built-In Test Equipment (BITE) system. The BITE module continuously monitors power supply, data rate, and recording accuracy, generating system status or maintenance alerts in case of potential faults.

Frame and Subframe Structure

The data flow is organized into four-second main frames and one-second subframes within them. Each subframe consists of 64, 128, 256, or 512 words depending on the recording technology, with each word representing a 12-bit binary sequence. This structure ensures sequential storage of flight parameters, with each bit carrying a value of 0 or 1.

Sampling and Encoding Mechanism

During the data collection process, the FDAU gathers signals from sensors at a specific sampling frequency. For example, a system collecting 64 words per second processes a data stream of 64 × 12 = 768 bits per second. These data are then converted into Harvard Bi-Phase format, which allows both clock and data information to be transmitted over the same line and facilitates error detection.

The data collection sequence is determined by a programmable read-only memory (PROM). This structure operates with a user-defined programming logic that defines the content of each data word, its signal type, and its input pin. Thus, the same hardware can be used across different aircraft types simply by changing the software configuration.

Time Synchronization and Data Integrity

Each data frame is stamped by a relative time counter. This counter is synchronized with a GMT (Greenwich Mean Time) signal compliant with the ARINC 585 standard. Simultaneously, time alignment between the Flight Data Recorder (DFDR) and the Cockpit Voice Recorder (CVR) is achieved using a time synchronization signal transmitted in Frequency Shift Keying (FSK) format.

This structure enables accurate temporal resolution of events during post-flight data analysis. Additionally, the continuously operating BITE unit detects data loss, incorrect speed inputs, or corrupted memory conditions and alerts maintenance crews. This mechanism plays a critical role in preserving recording quality and data integrity.

Data Transfer and Storage Layer

Data formatted by the FDAU is continuously directed during flight to both the FDR and quick access units (QAR or DAR). This parallel recording structure enables data analysis not only after accidents but also for maintenance, performance evaluation, and proactive purposes such as FOQA (Flight Operations Quality Assurance). In modern systems, these data are transferred to ground stations via PCMCIA cards or wireless connections and stored in compressed and encrypted form.

Hardware Architecture and Input-Output Interfaces

The hardware architecture of the Flight Data Acquisition Unit (FDAU) is designed as a modular structure capable of processing different types of signals from the aircraft under a unified system framework. This architecture consists of hardware and software components that manage multiple sensor interfaces and ensure high-reliability data transmission.

Modern FDAU architecture comprises four main subsystems: low-level sensor interface, data collection and formatting unit, command and control module, and data output interfaces. The low-level interface receives analog, digital (ARINC 429), synchro, and discrete signals. These signals are processed through signal conditioning circuits for sampling, amplification, and conversion. The data is then transferred to a microprocessor in digitized form and directed to the FDR in compliance with ARINC 573 or 717 standards.

Modular Expansion and Programmability

FDAs are modular, with four or five expansion slots within the system. These slots can be expanded by adding additional signal conditioners or microprocessor-based monitoring modules. This flexibility allows the same device to be used across different aircraft types. The sampling sequence defined via programmable read-only memory (PROM) determines the signal type for each pin and allows users to customize the content of data frames. Thus, a single FDAU hardware unit can be configured to support up to eight different aircraft programs.

Additionally, the BITE (Built-In Test Equipment) system operates in accordance with EUROCAE ED-55 principles, testing both unit functionality and the logical validity of data. This enables the system to continuously verify whether recorded parameters fall within reasonable value ranges and detect potential faults early.

Input Interfaces

The FDAU’s input architecture enables simultaneous processing of multiple signal types:

• Analog Inputs: Acquired via synchro, voltage ratio, DC/AC inputs, potentiometers, and thermobulb connections. These signals are digitized by analog-to-digital converter (ADC) circuits with 12-bit resolution.
• Discrete Inputs: Simple logic lines representing open circuit, grounded (0V), or 28V states. These lines typically carry parameters such as flight control status, landing gear position, or indicator signals.
• Digital Inputs: Received via ARINC 429 data buses (up to eight, three of which are high-speed), frequency inputs, or CSDB/ASCB data paths.
• Time Input: A GMT time input line compliant with ARINC 585 standard ensures time synchronization of all data.

All of these inputs undergo filtering, amplification, and sampling before being connected to the unified data bus. Short line distances are preferred or external amplification modules are used, especially for low-level DC inputs, to prevent signal loss.

Output Interfaces

The main data output of the FDAU is a data stream of 64 words per second encoded in Harvard Bi-Phase format. This data is transmitted directly to the Digital Flight Data Recorder (DFDR). When required, the data rate can be increased to 128 or 256 words per second. Additionally, an auxiliary output line in Return-to-Zero (RZ) format provides data transfer to Quick Access Recorder (QAR) units.

The system also generates a time synchronization output based on Frequency Shift Keying (FSK). This signal ensures time alignment between the DFDR and the Cockpit Voice Recorder (CVR), aiding in maintaining temporal integrity during post-flight analysis.

Power, Environmental Robustness, and Physical Characteristics

The FDAU operates on a nominal 28 V DC supply and has a maximum power consumption of 15 W. The hardware has been tested according to the RTCA DO-160B environmental standard and meets requirements for temperature, vibration, electromagnetic compatibility, and humidity tolerance. It is typically manufactured in a ½ ATR short chassis (ARINC 404A) form factor and weighs approximately 5 kg.

Transducer power lines are dedicated to 5 V DC (for potentiometers) and 28 V DC (for accelerometers). These lines enable the FDAU to directly power sensors, eliminating the need for external power circuits. This feature enhances reliability, particularly in high-accuracy measurements such as those from engine vibration sensors and airframe accelerometers.

Modern Hardware Trends

In新一代 data acquisition units, the hardware architecture has evolved into a dual-domain structure. The primary domain (time-sensitive domain) manages low-latency sensor communication at the nanosecond/microsecond scale, while the secondary domain (compute-heavy domain) handles data processing, storage, and communication tasks at the millisecond/second level. This architecture provides advantages for high sampling rates and real-time telemetry, especially in unmanned aerial vehicles.

Parallel to this, PCMCIA or modern ATA/Flash memory card interfaces have replaced older magnetic or optical media. These cards not only store data but also perform system configuration loading (data loader) functions and can load all software updates in approximately five minutes.

Data Frame and Coding Structure

The foundation of the flight data acquisition process is the data frame structure, which defines how data is organized, sampled, and encoded. This structure ensures that all parameters from aircraft systems are sequentially transmitted to the Flight Data Recorder (FDR) according to a specific time base. The data frame guarantees that information collected during flight is stored in a chronological, consistent, and engineerable format.

The data frame is a data block generated by the Flight Data Acquisition Unit (FDAU) at second-long intervals, with parameters organized as digital data words. Each frame represents a specific time interval and forms a digital “snapshot” of the flight. These frames collectively create a continuous temporal sequence throughout the entire flight duration.

The frame structure is defined by the international ARINC 573 and ARINC 717 standards. According to these standards, the data frame is structured as a four-second full frame composed of four one-second subframes. This timing arrangement may vary depending on the sampling frequency of the data acquisition unit, but time synchronization remains fixed across all subsystems.

Each subframe consists of a specific number of 12-bit data words. These words represent the digital form of raw data from sensors, with each word corresponding to a specific parameter. Depending on the system type, a subframe may contain 64, 128, 256, or 512 words. This structure allows more parameters to be recorded within the same time window in aircraft with high sampling rates.

Subframe Organization and Sampling Structure

Subframes enable the recording of aircraft parameters at specific time intervals. For example, a parameter measured once per second appears once in each subframe, while dynamic parameters such as vibration or control surface position may be recorded four or eight times per second. This structure is explained by the concepts of “sampling rate” and “parameter word.” The FDAU defines a sampling frequency for each parameter, which determines its repetition sequence within the frame.

Data Word Structure

A data word is a 12-bit digital encoding. The meaning of these 12 bits is defined by the system’s data decoding function. The most commonly used “12-bit Binary” encoding represents numerical values from 0 to 4095. These values are later converted into physical engineering units such as knots, feet, PSI, or °C.

Encoding and Data Transmission

The data frame generated by the FDAU is transmitted to the FDR using the Harvard Bi-Phase encoding method. In Harvard Bi-Phase encoding, each data bit carries both data and timing information. This method eliminates the need for a separate clock line, as each bit transition conveys both the 1/0 value and a time reference. Thus, the receiving system (FDR) can derive its internal clock from the transitions of the transmitted signal.

Bi-Phase encoding provides two advantages:

1. Temporal integrity: Since timing information is embedded in every data transition, bit drift does not occur.
2. Error detection: Irregular transition patterns can be flagged as corrupted data by automatic error detection systems.

After conversion to the Harvard Bi-Phase format, the data is directed to the FDR in accordance with the ARINC 573 or 717 standard. This data link can carry 64, 128, 256, or 512 words per second. The system also includes an auxiliary output line in Return-to-Zero (RZ) format, typically used for data transfer to the Quick Access Recorder (QAR).

Data Frame Documentation and Calibration

The content of the data frame for each aircraft type is defined in Data Frame Layout (DFL) documents. These documents specify which parameter is located at which word address, how many bits are used for encoding, the sampling frequency, and the conversion coefficients. Additionally, DFL documents work in conjunction with calibration control reports used during data decoding.

During calibration procedures, the accuracy of each measurement channel is tested by comparing recorded digital values with physical measurement values. This allows the coefficients of the conversion functions to be updated and measurement errors to be minimized. This calibration is mandatory during FDR maintenance cycles; according to international regulations, flight data systems must undergo verification tests at specified intervals.

Time Tagging and Data Synchronization

Each parameter in the data frame is associated with a time tag. The FDAU generates these tags using the Relative Time Counter and GMT Clock signals. Time synchronization is performed using an incrementing counter that starts at flight initiation. This enables sequential analysis of events and ensures time alignment between the FDR and the Cockpit Voice Recorder (CVR).

In some systems, the time signal is transmitted in compliance with the ARINC 585 standard. Decoding this signal allows all flight events to be aligned at the millisecond level. Time tagging is particularly critical in accident investigations, where analysis of system responses during the final seconds of flight is essential.

Data Integrity and Error Control

The FDAU performs error control during data transmission via the Built-In Test Equipment (BITE). The BITE system conducts logical integrity tests on each subframe of the data frame. When a corrupted word, missing data, or incorrect frame count is detected, the system reports the status with error codes.

In addition, the natural error detection feature within the Harvard Bi-Phase format is based on the regularity of signal phase transitions. Since each frame generated per second is recorded together with both data and synchronization signals, missing or corrupted frames can be easily identified during post-flight data analysis.