Aircraft fly-by-wire replaces mechanical control links with electronic commands. Learn how control laws, redundancy, actuators and failures work.
An aircraft fly-by-wire system converts the pilot’s control inputs into electrical signals, which flight-control computers interpret and send to powered actuators that move the control surfaces. In real-world aviation, it replaces some or all direct mechanical linkages, allowing control laws, stability augmentation and, on some aircraft, envelope protection.
How does fly-by-wire work?
A fly-by-wire system works as a closed feedback loop between the cockpit controls, flight-control computers, actuators and aircraft sensors.
- The pilot makes an input. Position or force sensors detect movement of the sidestick, yoke or rudder pedals. The cockpit control may have no direct cable connection to the corresponding surface.
- Computers interpret the request. Flight-control computers combine the input with data such as airspeed, attitude, acceleration, angle of attack and control-surface position. They then apply the aircraft’s active control law.
- Actuators receive commands. Electrical signals operate hydraulic servo-valves, electro-hydraulic actuators or, on some aircraft, electromechanical actuators.
- Feedback confirms the result. Position sensors report how far each surface actually moved. The computers compare commanded and measured positions, correcting errors and detecting faults.
The moving parts are still elevators, ailerons, rudders, spoilers and stabilisers; our explanation of what each flight-control surface does covers their individual roles. Fly-by-wire describes the command path, not necessarily the source of physical power. Many systems still rely on hydraulics, as shown in our guide to how hydraulic pressure moves aircraft controls.
Fly-by-wire can be analogue or digital, although modern transport-aircraft installations are normally digital and multiply redundant. The term does not mean wireless: commands travel through electrical wiring and data buses.
What do fly-by-wire control laws do?
A control law defines how a pilot input should change the aircraft’s motion rather than merely specifying a fixed control-surface deflection.
For example, moving a sidestick sideways may command a roll rate. The computers select suitable aileron and spoiler movements, compensate for airspeed and coordinate other surfaces. A pitch input may command pitch rate or load factor, with automatic trimming used to maintain the requested response.
| Generic operating mode | Typical behaviour |
|---|---|
| Full or normal law | All intended stability functions are available, together with any envelope protections provided by the design. |
| Degraded or alternate law | Some protections, automatic functions or sensor-dependent features are lost after particular failures. |
| Direct law | Pilot input has a more direct relationship with surface command, usually with reduced augmentation and possible manual-trim requirements. |
These mode names and capabilities are not universal. Even “direct law” normally remains an electrical path through computers and powered actuators; it does not automatically restore a mechanical cable connection.
The operation of an A320 sidestick, its control laws and autotrim provides a familiar practical example. Other manufacturers make different choices about control feel, authority and pilot override, reflected in the comparison of Airbus and Boeing flight-control philosophies.
Why do aircraft use fly-by-wire?
Fly-by-wire is used because electronic control can coordinate an aircraft’s surfaces more precisely and flexibly than a simple network of cables and pushrods.
- Electrical wiring can be lighter and easier to route than long mechanical linkages.
- Computers can provide stability augmentation, automatic trim and consistent handling across a wide speed range.
- Several surfaces can be blended to produce one commanded response.
- Some designs limit excessive angle of attack, load factor, bank angle or speed when the appropriate control law is available.
- Built-in monitoring can isolate failed channels and reconfigure the system.
Envelope protection is not an automatic feature of every fly-by-wire aircraft. Some systems impose firm limits, while others supply warnings, increasing control forces or authority that the pilot can override. The exact behaviour depends on the aircraft and active control mode.
Is fly-by-wire the same as autopilot?
No. Fly-by-wire carries out flight-control commands, while an autopilot generates commands intended to follow a selected heading, altitude, route or other target.
With the autopilot disconnected, the pilot still controls a fly-by-wire aircraft through the same computers and actuators. With it engaged, the autopilot feeds requests into that control architecture instead. Fly-by-wire therefore does not mean that the aircraft flies itself.
What happens if fly-by-wire fails?
A transport-category fly-by-wire aircraft is designed so that one failed computer, sensor or power source does not normally cause a complete loss of control.
- Multiple computer channels calculate commands independently and monitor one another.
- Sensor comparison and voting help identify an air-data, attitude or position sensor producing implausible information.
- Separated power sources and wiring reduce the chance that one electrical fault disables every channel.
- Multiple hydraulic circuits or actuators prevent one pressure loss from stopping every primary surface.
A detected fault may isolate one channel or change the aircraft to a degraded control law. The crew may lose envelope protection, automatic trim or some surface authority while retaining basic control. Handling and checklist actions then depend on the exact failure.
A mistake we see in discussions is treating a computer reset or circuit-breaker cycle as a universal fix. In an actual aircraft, crews use the approved warning-system and checklist procedure; randomly resetting flight-control equipment can remove information, disable a remaining channel or cause an intermittent fault to return unnoticed.
Does every fly-by-wire aircraft have mechanical backup?
No; mechanical backup is aircraft-specific and may be absent, partial or intended only to maintain limited control while electrical functions are recovered.
Some designs retain mechanical control of selected functions such as stabiliser trim or rudder. Others depend on redundant computers, power supplies, sensors and actuators as their primary protection against total failure. A mechanical backup should not be assumed to provide normal control of every axis.
Why can fly-by-wire feel wrong in a flight simulator?
Desktop simulation can reproduce control laws, but ordinary joysticks and yokes do not naturally reproduce the force sensing, artificial feel or powered feedback found in the real cockpit.
The aircraft model also matters. A detailed simulation may calculate roll rate, load factor, protections and autotrim, while a simpler one may apply little more than a modified input curve. When a simulated fly-by-wire aircraft feels twitchy or fights the pilot, we check these points first:
- Calibrate every control axis and add only enough dead zone to suppress genuine sensor noise.
- Remove duplicate bindings, especially when both a joystick and yoke are connected. Two pitch or roll assignments commonly cause unexplained movement.
- Check response curves against the aircraft developer’s guidance. A curve suitable for a conventional light aircraft may distort a rate-command sidestick.
- Disable conflicting assistance that applies its own control or trim inputs.
- Account for autotrim. Constantly trimming against a simulated normal-law system can produce oscillation or unexpected pitch behaviour; degraded or direct modes may behave differently.