Fly-by-wire is a method of controlling an aircraft in which the pilot’s stick, pedals, and switches no longer move the flight surfaces through direct mechanical cables, rods, or hydraulics. Instead, the controls send electrical signals to flight-control computers, which interpret the pilot’s intent and command actuators to move the elevators, ailerons, rudder, and other surfaces. The connection from human to aircraft becomes a chain of sensors, software, and wires rather than steel and fluid.
This indirection unlocks capabilities that pure mechanical controls cannot offer. Because software sits between the pilot and the surfaces, the computers can apply envelope protection - limiting the aircraft to a safe range of angle of attack, bank angle, and load so it is harder, or in some designs impossible, to stall or overstress the airframe. The software can also smooth handling, reduce pilot workload, and compensate for an airframe that is deliberately designed to be aerodynamically less stable for better performance. Airbus introduced full digital fly-by-wire to commercial airliners with the A320 in the late 1980s, and the approach is now standard across modern jets.
The cost of this power is that flight software becomes safety-critical: if the computers fail or misjudge the situation, the pilots may have limited ability to override them. Fly-by-wire systems answer this with redundancy and fault tolerance - multiple independent computers, often built by different teams or with different processors, that cross-check each other and vote, plus redundant sensors and power. The goal is that no single failure, and ideally no plausible combination of failures, can leave the aircraft uncontrollable.
To certify such software, the avionics industry relies on rigorous standards. RTCA’s DO-178, “Software Considerations in Airborne Systems and Equipment Certification,” is, as NASA’s adoption record states, the document that “provides recommendations for the production of software for airborne systems and equipment that performs its intended function with a level of confidence in safety that complies with airworthiness requirements.” Fly-by-wire flight software sits at the highest assurance levels under that standard, demanding the most exhaustive verification.
Fly-by-wire also reshapes how accidents are investigated. When something goes wrong, inquiries must reconstruct not only the aerodynamics but the interaction between the pilots and the computers - what the system was doing, what it told the crew, and whether the automation and the humans had a shared understanding of the situation. That tension runs through cases from the 1988 Air France A320 crash at Habsheim to the Boeing 737 MAX MCAS disasters, and it remains the central design challenge of putting computers in command of flight.