Traditional aircraft flight control systems rely on a direct mechanical connection between the cockpit controls and the control surfaces — cables, pulleys, pushrods, and hydraulic actuators that transmit the pilot's physical inputs to the wings and tail. Fly-by-wire (FBW) technology replaces the majority of these mechanical pathways with an electronic architecture: sensors detect pilot inputs, computers process those signals, and electrically commanded actuators move the control surfaces. The result is a system that is lighter, more responsive, more easily adaptable, and capable of protecting the aircraft from departing its certified flight envelope — something no cable-and-pulley system can do on its own.
Understanding FBW systems is essential for today's AMT candidates and working airframe technicians. Modern transport-category aircraft — from the Airbus A320 family to the Boeing 777 and beyond — rely on FBW for primary flight control. Knowing the components, redundancy architecture, and safety features is both an exam requirement and a practical necessity for anyone who will inspect, troubleshoot, or return these systems to service.
Core Components of a Fly-By-Wire System
A complete FBW flight control system contains several interconnected subsystems. Each must function reliably — and, when it fails, must fail safely. The major components are as follows.
Pilot Input Devices
The pilot's physical input is captured either by a conventional control column and rudder pedals fitted with position sensors, or by a sidestick controller (as used on Airbus aircraft) or a force-sensing inceptor. These devices contain linear variable differential transformers (LVDTs) or rotary variable differential transformers (RVDTs) — electromechanical transducers that convert mechanical displacement into a proportional analog voltage signal. LVDTs and RVDTs are prized for their smooth, essentially stepless analog output and long service life because there is no direct electrical (sliding) contact between the moving core and the housing — only contactless magnetic coupling. The raw position or force signal is converted to a digital value and forwarded to the flight control computers.
Flight Control Computers (FCCs)
The flight control computers are the intelligence of the FBW system. They receive pilot commands, air data (airspeed, altitude, angle of attack), inertial data (pitch rate, roll rate, yaw rate), and control surface position feedback, then compute the exact actuator commands needed to achieve the desired aircraft response. Most transport-category aircraft employ multiple dissimilar computers — meaning not just redundant units running identical software, but physically separate processors using different hardware designs and often different software languages. This dissimilar redundancy strategy guards against a common-mode software fault that could simultaneously disable all computers. For example, a system might employ three primary flight control computers and two secondary or backup computers, with voting logic that compares outputs and isolates any computer producing an out-of-range command.
Actuators and Electrohydraulic Servo Valves
In most transport FBW installations, the final muscle of the system is still hydraulic — but the command that directs hydraulic flow is electrical. An electrohydraulic servo actuator (EHSA) contains an electrically driven servo valve that meters hydraulic fluid to a conventional hydraulic cylinder, which moves the control surface. The servo valve receives a small electrical current from the FCC, converts that current to fluid flow, and the high-power hydraulic actuator does the actual work of moving the surface against aerodynamic loads. Some newer aircraft additionally use electromechanical actuators (EMAs) — motor-driven ballscrew devices that eliminate hydraulic fluid entirely from certain surfaces, reducing fire risk and maintenance burden. Position feedback from the actuator is sent back to the FCC in a closed-loop arrangement, allowing the computer to verify that the surface has actually moved to the commanded position.
Sensors and Air Data Systems
FBW computers rely on a rich sensor suite. Air data computers (ADCs) supply calibrated airspeed, Mach number, altitude, and angle of attack. Inertial reference systems (IRSs) supply body-axis acceleration and angular rate data. Angle-of-attack (AOA) vanes provide a direct measure of the wing's aerodynamic angle relative to the oncoming airflow. All of these sensor channels are multiplied — typically three or more independent sets — so that the FCC can perform a majority-vote comparison and identify a faulty sensor without losing control authority.
Redundancy Architecture and Safety Features
Safety is the defining design priority of any FBW system. Because the electronic path is the only path to the control surfaces, a single-point electronic failure cannot be allowed to cause loss of control. Designers achieve this through layered redundancy at every level.
Hydraulic System Redundancy
Transport aircraft typically have three independent hydraulic systems (commonly called Left, Center, and Right on Boeing aircraft; Green, Blue, and Yellow on many Airbus types). Each primary control surface actuator is powered by at least two independent hydraulic systems. Even if one system loses pressure due to a leak or pump failure, the remaining systems can continue to drive the actuators. Some surfaces have three independent actuators, each connected to a different hydraulic system, ensuring full control even with two hydraulic systems failed.
Electrical Power Redundancy
The FBW computers and their associated electronics require reliable electrical power. Aircraft FBW systems are connected to multiple AC and DC buses, and they include a ram air turbine (RAT) — a small turbine that deploys into the airstream to provide emergency power when normal power sources are lost. The exact deployment logic varies by aircraft type — some designs deploy the RAT on loss of all normal AC electrical power, others on combined loss of hydraulic and electrical power, and the RAT can typically also be deployed manually by the crew using a cockpit switch. The RAT provides emergency hydraulic and/or electrical power sufficient to maintain control of the aircraft for a safe landing. Battery-backed buses ensure that critical computers remain powered even during the worst-case total generator failure scenario.
Flight Envelope Protection
One of the most significant safety advances enabled by FBW is flight envelope protection. Because a computer processes every pilot command before it reaches the actuator, the software can limit or modify that command to prevent the aircraft from exceeding its certified structural and aerodynamic limits. Typical protections include:
- High angle-of-attack (alpha) protection: The computer prevents the pilot from commanding an AOA that would produce an aerodynamic stall, regardless of how far back the stick is pulled.
- Overspeed protection: As airspeed approaches VMO/MMO, the system commands a nose-up pitch trend and increases resistance to further nose-down input, helping to keep the aircraft from exceeding its structural design speed limits. The exact behavior varies by manufacturer and should not be oversimplified as a single automatic pitch-up input.
- Bank angle protection: The system limits commanded bank angle — for example, on some Airbus FBW aircraft, normal sidestick deflection commands a maximum of about 33° of bank, while holding the stick at the full lateral stop allows up to about 67°; the system halts further bank increase at the limit but does not necessarily return the aircraft to wings-level automatically once the pilot releases the input.
- Load factor (g) limiting: Commands that would exceed the aircraft's maximum certified load factor — typically +2.5 g to –1 g for transport category (Part 25) aircraft — are automatically rejected or softened.
- Pitch attitude protection: Excessive nose-high or nose-low attitudes trigger automatic corrective inputs.
These protections operate in what is called Normal Law — the full-authority, fully-protected mode of the FBW system. If sensor failures reduce the computer's confidence in its data, the system may revert to Alternate Law (reduced protections) and ultimately to Direct Law (a nearly one-to-one electrical connection, analogous to a conventional aircraft without augmentation). Technicians must understand these degraded modes because maintenance actions, sensor failures, or improper return-to-service can trigger law changes detectable during pre-flight built-in test.
Built-In Test Equipment (BITE) and Maintenance Interface
FBW systems incorporate extensive built-in test equipment (BITE) that continuously monitors system health. During power-up, the BITE performs automated self-tests of computers, actuators, sensors, and wiring integrity. In flight, BITE records fault codes with time stamps, parameter snapshots, and failure context data in non-volatile memory. Technicians access this data through a centralized fault display system (CFDS) or equivalent maintenance terminal to retrieve fault histories, run ground tests, and confirm that repairs have resolved the underlying fault. Because FBW faults are often transient or software-related, the AMT must follow the aircraft maintenance manual (AMM) rigorously — clearing faults without systematic diagnosis is a common and dangerous error.
Why It Matters for AMTs
An airframe technician working on FBW components must appreciate that improper maintenance of a sensor, actuator, or wiring harness can silently degrade a redundancy layer without triggering an immediately apparent failure. The aircraft may dispatch legally while operating with reduced protection. This is why periodic functional checks, torque verification on actuator attachments, cleanliness of servo valve hydraulic supplies, and proper shielding of signal wiring are all critical maintenance practices — not optional niceties. Any work on FBW components requires strict adherence to the AMM and return-to-service functional checks as specified, typically including a ground control surface check and BITE verification.
Key Numbers and Rules
- LVDTs and RVDTs operate on the principle of electromagnetic induction with no sliding electrical contact — providing a smooth analog output and essentially infinite mechanical life for the transducer element.
- Most transport FBW systems use a minimum of three independent hydraulic systems for primary control surface power.
- A typical transport (Part 25) aircraft's normal law g-limit is +2.5 g / –1.0 g for the normal envelope.
- The ram air turbine (RAT) deploys automatically or manually depending on aircraft type and design, providing emergency power when normal power sources are lost, and must be reset on the ground by maintenance before the next flight.
- Dissimilar redundancy means redundant computers use different hardware AND different software to prevent a single software bug from failing all channels simultaneously.
- BITE fault codes are stored in non-volatile memory and survive a power cycle — technicians must retrieve and clear them per AMM procedures.
Common Test Traps
- Mechanical backup confusion: Many FBW aircraft have no direct mechanical reversion to the control surfaces. Do not assume that a cable backup exists; in true FBW designs, the electronic path is the only path (though some aircraft retain a mechanical pitch trim backup).
- LVDT vs. RVDT distinction: An LVDT measures linear displacement; an RVDT measures rotary (angular) displacement. Test questions may require you to select the correct type for a given application such as a control column (rotary) vs. a linear actuator position sensor (linear).
- Normal Law vs. Direct Law: Envelope protections only operate in Normal Law. In Direct Law, the pilot has much more authority — including the ability to exceed structural limits — so understanding degraded mode triggers is important.
- RAT maintenance: After the RAT has deployed, it must be stowed and reset by a qualified technician before the next flight. The test may ask who is responsible for this action — it is a maintenance function, not a flight crew reset.
- Dissimilar redundancy purpose: The reason for using different hardware and software in redundant computers is to guard against common-mode failures — not simply to have extra units. A test question may try to conflate simple redundancy with dissimilar redundancy.