Learn how aircraft systems communicate through ARINC data buses, sensors and computers, plus how redundancy and failures affect the cockpit.
In real-world aviation, aircraft systems communicate by sending electrical or optical signals over dedicated wires and standardised digital data buses. Sensors publish measurements, computers validate and combine them, and displays or actuators use the results. Older and simpler aircraft also rely heavily on direct analogue wiring, switches and mechanical connections.
What information do aircraft systems exchange?
Aircraft systems exchange measured values, equipment status, control commands and information about whether the data is valid. Typical examples include airspeed from an air-data computer, attitude from an inertial reference unit, engine parameters, radio tuning, autopilot modes and landing-gear position.
A digital message usually contains an identifier, the value itself and integrity information. Depending on the protocol, that may include status bits, parity, a checksum, sequence information or a time reference. The receiving equipment is configured to recognise the relevant messages and reject missing, corrupt or implausible data.
This is not always a two-way conversation. On ARINC 429, for example, one transmitter repeatedly sends labelled data that one or more receivers can listen to. Other networks allow equipment to exchange messages in both directions or send them through a network switch.
Navigation is a good example: air-data, inertial and satellite-navigation sources feed computers that then supply displays, guidance and autopilot functions. Our explanation of how sensors, the FMS, displays and autopilot share navigation data covers that chain in more detail.
Which aircraft data buses are used?
There is no single communication standard across every aircraft. The design depends on the aircraft's age, size, certification requirements and the amount of data that must be moved.
| Connection or bus | Typical use | Defining feature |
|---|---|---|
| Analogue and discrete wiring | Switches, warning circuits, position sensors and older instruments | A voltage, resistance, frequency, open circuit or ground directly represents a condition |
| ARINC 429 | Commercial and business-aircraft avionics | Simple one-way transmission from one source to multiple listeners over a twisted wire pair |
| AFDX / ARINC 664 Part 7 | Integrated avionics on many modern transport aircraft | Deterministic, switched Ethernet using controlled virtual links and normally duplicated networks |
| CAN-based buses / ARINC 825 | General aviation and local subsystem networks | Multiple devices share a compact message-based network |
| MIL-STD-1553 | Military aircraft and mission systems | A bus controller schedules command-and-response traffic on redundant channels |
One aircraft can use several of these at once. Data concentrators and gateways gather individual sensor wires, translate between protocols and distribute the resulting information. Manufacturers may also use proprietary links inside a particular subsystem.
Not every interaction is electronic. Hydraulic pressure physically moves an actuator, bleed air flows through ducts and a mechanical cable can transmit a pilot input. Sensors and switches convert the resulting pressure, position or temperature into data when another system needs to monitor or control it.
How does sensor data reach a display or actuator?
A measurement normally passes through a defined chain from sensor to computer, data bus and receiving equipment.
- Sense the condition: A transducer measures pressure, temperature, position, acceleration or another physical quantity.
- Convert the signal: A sensor interface or computer turns the analogue measurement into a digital value and attaches status information.
- Transmit the data: The source sends the value over a dedicated connection or shared network at a specified interval.
- Validate it: The receiving computer checks integrity, freshness and plausibility. Safety-critical systems may compare several independent sensors.
- Use the result: A display presents the value, an alerting computer evaluates it, or a control computer calculates a command.
- Monitor the response: Position or status feedback confirms whether the commanded action occurred.
In a fly-by-wire aircraft, this chain links pilot controls, motion and air-data sensors, flight-control computers and powered actuators. The details of how flight-control data becomes an actuator command also show why redundant computers and feedback sensors are essential.
Are data buses the same as electrical buses?
No. An electrical bus distributes power, while a data bus distributes information.
The distinction matters because loss of electrical power can silence several otherwise healthy computers and make the fault look like a communication failure. Generators, batteries, transformer rectifiers and essential buses keep the avionics operating; our guide to aircraft electrical generation and bus distribution explains those dependencies.
A mistake we see constantly is treating an avionics bus as if it were a digital network. In many light aircraft, the term means a switched electrical supply feeding the radios and navigation equipment. It does not carry their messages.
What happens when aircraft systems stop communicating?
A failed or invalid data path normally produces warning flags, missing indications, degraded modes or an automatic switch to a redundant source. The exact cockpit effect depends on where the failure occurs.
- Sensor or source failure: Several receiving systems may reject the same parameter because the original source has stopped transmitting or marked its data invalid.
- Wiring or connector fault: One channel or receiver may lose data while other equipment continues to work.
- Gateway or network-switch failure: A group of otherwise unrelated systems can lose information crossing the same network point.
- Electrical-bus failure: Multiple units may go blank or offline together because they have lost power rather than data.
- Configuration or software mismatch: A replacement unit may power up but fail to exchange the expected labels, addresses or message format.
- Disagreement between sources: Comparators may flag inconsistent airspeed, attitude or position data even though messages are still arriving.
Design protections include parity or checksum testing, message time-outs, reasonableness checks, duplicated networks, independent power sources and physical separation of wiring. Critical systems may use three or more sources and voting logic so that one incorrect value cannot control the aircraft.
In flight, pilots use the approved abnormal checklist, select an alternate source where provided and rely on standby instruments or reversionary displays. Circuit breakers should not be reset unless the aircraft procedure specifically permits it. Maintenance teams then use built-in test reports, wiring checks and configuration records to isolate the source, power, connector or network fault.
How do flight simulators model system communication?
Flight simulators usually represent communication as software variables and events rather than reproducing every electrical waveform on a physical data bus. Detailed aircraft can still emulate source validity, electrical dependencies, redundant channels, bus failures and the cockpit consequences of lost messages.
Less detailed aircraft may connect a sensor value directly to an instrument and omit gateways, timing and failure logic. This is why the same failure can produce very different results between aircraft packages. Before assuming a display is broken, check its power source, avionics switches, bus ties and configured data source; our coverage of system failures and troubleshooting in MSFS 2024 explains how those dependencies appear in the simulator.