Fly-by-wire flight control system

A modern fighter is often built to be aerodynamically unstable on purpose — that instability is what buys agility. The price is that no human pilot can fly it unaided. The aircraft only stays controllable because a computer, sensing its motion hundreds of times a second, corrects the airframe faster than a person can. That computer is the fly-by-wire flight control system, and India first flew a fully indigenous version of it in February 2024 — roughly two decades after the aircraft it flies on took to the air.

Fly-by-wire replaces the mechanical linkages between stick and control surface with electronic signals. Pilot commands become electrical instructions to actuators, which move the surfaces. Airbus, which brought the technology from military jets to airliners with the A320 in 1988, treats it as a foundational safety innovation. For an unstable fighter it is not merely safer — it is the precondition for flight at all.

The difficulty is why so few can do it. The flight control laws must be certified to DO-178C Level-A, the highest airborne software assurance level, because a fault has no benign outcome. The hardware runs quadruplex: four independent digital channels operating at once, so the aircraft keeps flying even if one or more fail. Indigenous design capability for such systems sits with a small set of nations — the United States, France and the United Kingdom pioneered it.

India chose the hard road early. The Tejas design was finalised in 1990 as a tailless compound delta with relaxed static stability — deliberately unstable — with digital fly-by-wire planned from the outset. Dassault-Breguet offered a hybrid system with three digital channels and analog backup; the Aeronautical Development Agency chose instead to pursue a fully quadruplex four-channel digital system. In 1992, the National Aerospace Laboratories set up a dedicated Control Law (CLAW) team to write the indigenous flight control laws, validated across more than 50 hours of pilot testing on an Iron Bird ground rig. IIT Bombay formulated laws for features such as auto low-speed recovery — envelope protection at high angle of attack — and disorientation recovery.

The result flew. The Tejas entered Indian Air Force service in 2015 with a NAL-developed full-authority quadruplex digital fly-by-wire system and an open-architecture flight control computer from Bharat Electronics Limited, driving hybrid electro-hydraulic actuators.

Yet a gap remained inside the achievement. When Lockheed Martin was proposed as a development partner, US sanctions after the 1998 nuclear tests ended the arrangement and cost the programme about 18 months. And the fielded fleet still leaned on some imported flight-control components. Closing that last gap is what took until 2024, when a Digital Fly by Wire Flight Control Computer developed by the Aeronautical Development Establishment in Bengaluru was integrated on Tejas Mk1A prototype LSP7 and flown on 19 February. It carries a quadruplex PowerPC-based processor, a high-speed autonomous state-machine I/O controller, and DO-178C Level-A software. The defence ministry framed it as a step toward self-reliance with a reduced count of special imports.

Why the gap persisted is structural. Fly-by-wire is not one artefact but a stack — certified software, fault-tolerant hardware, actuators, air-data and inertial sensors, wind-tunnel characterisation, a test rig, and airworthiness certification of the whole aircraft. Most of that stack is now demonstrated in India; the avionics-grade microprocessor beneath it remains emerging.

The direction from here is convergence. ADA has developed a new quadruplex fly-by-wire computer, cleared for the Advanced Medium Combat Aircraft. With AMCA targeting prototype completion by 2030 and induction around 2034-2035, the indigenous computer's operational proving still lies ahead.