RECENT TAIL-STRIKE INCIDENTS IN COMMERCIAL AVIATION

 

Causes, Training Implications and Remedial Measures

The recent increase in reported tail strikes during landing and very-low-level go-arounds has raised concerns about flight crew competence and training standards. Several incidents involve several major aircraft types, including the Airbus A321neo, A300-600, A350-900, A350-1000 and Boeing 777-300ER.

These occurrences do not establish that airline pilots are generally incompetent. They do, however, reveal recurring weaknesses in energy management, pitch control, bounce recovery, go-around decision-making and crew coordination in the final seconds before landing.

The typical sequence is:

unstable or disturbed approach → delayed decision → abnormal flare or touchdown → bounce or low-level go-around → excessive or mistimed pitch input → tail strike.

The immediate cause is usually excessive pitch attitude or pitch rate. The deeper causes often include continuation of an unstable approach, poor recovery from a bounce, startle, insufficient awareness of long-body aircraft geometry, and inadequate monitoring and training that does not realistically replicate go-arounds initiated during the flare or after touchdown.

The most effective remedies are stricter stabilised-approach discipline, realistic simulator training, better bounce-recovery instruction, improved monitoring, stronger training on long-body differences, and proactive use of flight-data monitoring.

1. Recent occurrence pattern

An IndiGo A321neo reportedly suffered a tail strike during a low-altitude go-around at Mumbai in heavy rain. The aircraft climbed away and subsequently landed safely. The event combined degraded visual references, a late transition from landing to go-around, and the limited tail clearance margin of a long-bodied aircraft.

A Wizz Air UK A321neo experienced a tail strike on landing at Prague. Although detailed findings were not immediately available, the incident again involved the long A321 variant.

An EAT Leipzig A300-600 reportedly sustained a tail strike during a landing and a baulked-landing sequence at London Heathrow. Such events are particularly demanding because the crew may select go-around thrust while the aircraft is still touching, bouncing, or settling towards the runway.

A Cathay Pacific A350-1000 contacted the runway during a go-around initiated in the flare at Hong Kong. The aircraft sustained damage to its lower aft fuselage. The commander was highly experienced, demonstrating that total flying hours alone do not eliminate vulnerability to a sudden, high-workload event close to the ground.

A Singapore Airlines A350-900 was also reported to have sustained a tail strike during a go-around at Singapore.

An Air India A321neo reportedly sustained a tail strike during a go-around at Bengaluru. Wake turbulence was cited as a possible cause, although final conclusions require analysis of recorded data.

A Kalitta Air Boeing 777-300ER freighter scraped its tail during a go-around at Cincinnati. Video showed a trail of sparks before the aircraft climbed away and later landed safely.

These events share three common characteristics:

a) they occurred mainly during landing or during very-low-level go-arounds;

b) several involved long-bodied aircraft;

c) they affected different airlines, aircraft types and levels of crew experience.

2. Is poor pilot competence the main cause?

Pilot handling is directly involved in most tail strikes because contact generally requires an excessive pitch attitude, an excessive rotation rate, or an inappropriate control response. However, attributing every occurrence solely to poor flying competence is inadequate.

Competence in this area includes:

a) maintaining the correct energy state;

b) recognising an unstable approach;

c) making a timely go-around decision;

d) controlling pitch precisely;

e) recovering correctly from a bounce;

f) executing a go-around after touchdown;

g) monitoring the other pilot;

h) transferring control clearly;

i) responding appropriately under surprise and time pressure.

A pilot may be licensed, experienced and recurrently checked, yet have limited exposure to sudden sink, bounce or go-around initiated during the flare. The concern is therefore not necessarily a general decline in licensing standards. It is more likely a mismatch between conventional training and the scenarios encountered in line operations.

Many recurrent simulator programmes practise go-arounds from stable approaches at predictable altitudes. Far fewer realistically reproduce:

a) an unexpected bounce;

b) a go-around after main-gear contact;

c) delayed engine response;

d) wake-induced sink below 50 feet;

e) degraded visual references;

f) simultaneous control inputs;

g) reduced pitch margin on long-bodied variants.

The problem is therefore better described as a deficiency in scenario-based preparation, judgement and dynamic handling, rather than a simple lack of basic flying skills.

3. Principal causal factors

3.1 Excessive or mistimed pitch

The immediate cause of most tail strikes is an excessive nose-up attitude or a rapid increase in pitch while the aircraft is still on, or very close to, the runway.

During a low-level go-around, engine thrust does not immediately produce climb. Engine acceleration, aircraft inertia and lift development require time. If the pilot attempts to gain immediate ground clearance mainly by pulling back, the tail may contact the runway before climb performance develops.

The governing principle is:

Thrust creates the climb; pitch must remain within the available aerodynamic and geometric margins.

3.2 Unstable approach and poor energy management

Many tail strikes begin well before touchdown.

Typical precursors include:

a) excessive approach speed;

b) high sink rate below 100 feet;

c) late configuration;

d) inappropriate thrust;

e) repeated vertical corrections;

f) an approach requiring an aggressive flare.

An aircraft may be aligned with the runway and close to the glidepath yet still be unstable in energy. If it crosses the threshold too fast or with excessive sink, the pilot may attempt to salvage the landing with a large flare.

This may result in a firm touchdown, a bounce, a prolonged float, or direct tail contact.

Stabilised-approach monitoring must therefore continue right up to touchdown. An approach that was stable at 500 or 1,000 feet can deteriorate rapidly below 100 feet.

3.3 Delayed go-around

A go-around initiated well above the runway is relatively straightforward. A go-around initiated during the flare or after touchdown is far more demanding.

Late decisions may result from:

continuation bias;

a) belief that the approach can still be recovered;

b) reluctance to accept delay or additional fuel burn;

c) weak intervention by the monitoring pilot;

d) operational pressure to complete the landing;

e) an organisational culture that informally discourages go-arounds.

Some late go-arounds are unavoidable due to sudden wind changes, runway incursions, wake encounters, or loss of visual reference. However, when the approach was already deteriorating, a flare-level go-around often marks the final stage in a chain of missed opportunities.

3.4 Incorrect bounce recovery

A bounced landing is one of the most significant precursors to a tail strike.

The instinctive response may be to pull back to soften the next touchdown or to prevent the nose from dropping. This can increase the aircraft's pitch as it descends back towards the runway.

The risk is greatest when the aircraft is slow, thrust is near idle, and the bounce is pronounced.

Crews must distinguish between a minor bounce that may be recoverable under the manufacturer’s guidance and a significant or worsening bounce that requires a go-around.

Particularly hazardous actions include:

a) forcing the aircraft back onto the runway;

b) making large fore-and-aft control inputs;

c) attempting to soften the second touchdown with excessive pitch;

d) delaying the go-around after a severe bounce.

3.5 Long-body aircraft geometry

Several recent events involved long-fuselage aircraft.

A long fuselage does not make an aircraft unsafe, but it reduces the geometric margin between a normal operational pitch attitude and tail contact.

Tail clearance is influenced by:

1) landing-gear compression;

2) runway slope;

3) pitch rate;

4) aircraft mass;

5) centre of gravity;

6) vertical acceleration;

7) bounce dynamics.

Cockpit commonality can create a false sense of familiarity. A pilot moving from an A320 to an A321, from an A350-900 to an A350-1000, or from a shorter Boeing 777 variant to the 777-300ER may operate in a familiar cockpit, even though the tail-clearance margin has been materially reduced.

Differences training should therefore address handling and geometry, not merely aircraft systems.

3.6 Startle and overcontrol

A sudden sink, bounce, wake encounter, or runway conflict can trigger an instinctive urge to pull the aircraft away from the ground.

On a large transport aircraft, the tail responds immediately to a pitch input, whereas useful climb performance develops more slowly. An abrupt aft input may therefore reduce tail clearance before thrust becomes effective.

This may not reflect a lack of knowledge. It may indicate that the correct response has not been sufficiently practised in realistic conditions.

3.7 Weak monitoring and control transfer

The pilot monitoring should identify:

a) excessive sink rate;

b) abnormal pitch;

c) unstable flare;

d) significant bounce;

e) unsafe continuation;

f) incorrect go-around attitude.

Intervention should be progressive and unambiguous:

1) identify the deviation;

2) issue a corrective call;

3) command a go-around;

4) take control only when necessary.

An abrupt takeover near the runway may result in simultaneous or conflicting control inputs if the transfer is not verbally announced.

3.8 Environmental and operational factors

Heavy rain, gusts, crosswind, wind shear, turbulence and wake can cause sudden changes in flight path near touchdown.

These conditions are generally triggering factors rather than complete explanations. The outcome also depends on the crew’s recognition, pitch response, thrust application and decision timing.

Fatigue and operational pressure can further impair judgement, reaction time, monitoring and willingness to go around. These factors should be considered in every serious tail-strike investigation.

4. Root-cause framework

Tail strikes can be considered at four levels.

Immediate event

1) excessive pitch attitude;

2) excessive pitch rate;

3) abnormal rotation;

4) mishandled flare or bounce;

5) excessive pitch during go-around.

Operational precursor

a) unstable energy state;

b) high sink below 100 feet;

c) disturbed approach;

d) delayed go-around;

e) poor thrust-pitch coordination.

Crew-performance factor

a) startle;

b) weak monitoring;

c) poor control transfer;

d) inadequate understanding of aircraft geometry;

e) continuation bias.

Organisational factor

a) unrealistic recurrent training;

b) weak instructor standardisation;

c) limited differences training;

d) inadequate flight-data monitoring;

e) poor fatigue controls;

f) a culture that discourages go-arounds.

Corrective action must address all four levels. Retraining only the crew involved addresses the final symptom rather than the wider safety system.

5. Priority remedial measures

Enforce stabilised approaches to touchdown

Stabilisation criteria should remain below the conventional 500- or 1,000-foot gate.

A go-around should be mandatory for:

1) excessive sink rate;

2) speed outside limits;

3) repeated large corrections;

4) inappropriate thrust;

5) loss of required visual reference;

6) inability to achieve a normal flare.

Train low-level and post-touchdown go-arounds

Recurrent simulator programmes should include:

1) go-around during the flare;

2) go-around after main-gear contact;

3) go-around following a bounce;

4) delayed engine acceleration;

5) wake-induced sink;

6) degraded visibility;

7) long-body pitch-limit management.

Some scenarios should be introduced without warning to assess startle management and judgement.

Reinforce pitch discipline

Training should emphasise:

1) apply go-around thrust;

2) control the descent with measured pitch input;

3) respect prescribed pitch attitudes and pitch-limit indications;

4) allow thrust and speed to establish climb;

5) avoid seeking immediate separation through elevator alone.

Improve bounce-recovery training

Crews should receive clear guidance on minor and significant bounces.

Training should reinforce:

a) maintaining a stable attitude;

b) avoiding large control inputs;

c) not forcing the aircraft onto the runway;

d) going around when bounce severity is uncertain.

Strengthen pilot monitoring

Operators should standardise calls for:

a) deviation;

b) correction;

c) mandatory go-around;

d) control takeover.

The pilot monitoring must be empowered to call a go-around without hesitation.

Improve long-body differences training

Pilots transitioning to long variants should receive practical training in:

a) maximum-weight rotation;

b) high-sink landing;

c) bounced landing;

d) crosswind flare;

e) go-around during flare;

f) go-around after touchdown.

Computer-based familiarisation alone is insufficient.

Use flight-data monitoring proactively

Operators should track:

a) rotation rate;

b) pitch at lift-off;

c) sink 100 and 50 feet below;

d) touchdown vertical acceleration;

e) bounce signatures;

f) pitch after touchdown;

g) low-level go-arounds;

h) unstable approaches continued to land.

The purpose should be early risk detection rather than punishment.

Create a go-around-positive culture

Crews should not be criticised for prudent go-arounds prompted by fuel scrutiny, delay reviews, or informal pressure.

Safety performance should focus on unstable approaches continued to land, late go-arounds, and repeated high-sink or bounce events—not on the total number of go-arounds.

Conclusion

The recent pattern of tail strikes does not prove that commercial pilots are generally incompetent. It reveals a recurring weakness in the management of energy, pitch and decision-making during landing and very-low-level go-around manoeuvres.

The final mechanism is usually excessive or mistimed pitch. The underlying causes commonly include:

a) unstable or disturbed approaches;

b) delayed go-around decisions;

c) incorrect bounce recovery;

d) startle-induced overcontrol;

e) reduced pitch margin on long-bodied aircraft;

f) weak monitoring;

g) inadequate scenario-based training;

h) organisational pressure to continue.

The solution is not simply more frequent checks. It requires realistic simulator training, strict enforcement of the stabilised approach, improved bounce and low-level go-around instruction, stronger monitoring, improved differences training, and proactive use of flight data.

A tail strike may be caused by the final pitch input, but it is usually prevented by earlier decisions, monitoring and organisational safeguards.

Author: GR Mohan

Incorrect Take-Off Performance Data: A Persistent Operational Risk in Modern Aviation

Introduction

Incorrect take-off performance data remains a persistent safety risk in modern aviation, despite the widespread adoption of sophisticated digital tools such as Electronic Flight Bags (EFBs) and advanced Flight Management Systems (FMS). While these technologies have significantly improved computational accuracy and operational efficiency, recent incidents show that fundamental vulnerabilities—particularly data-entry errors, inadequate cross-verification, and overreliance on automation—continue to erode safety margins during one of the most critical phases of flight.

A series of events between 2023 and 2025, including a high-profile tail strike involving a LATAM Boeing 777-300ER, illustrate how relatively simple errors can cascade through multiple layers of defence when not detected in time. These events reinforce a key safety insight: the risk is not eliminated by automation but transformed, requiring renewed emphasis on human performance, procedural discipline, and system design.

The Critical Nature of Take-Off Performance

The take-off phase is a uniquely demanding operational environment in which aircraft transition rapidly from ground roll to airborne flight. It is characterised by high workload, rapidly changing aerodynamic conditions, and limited opportunity for corrective action once the aircraft passes decision speed (V1). Accurate take-off performance data is therefore essential to ensure that the aircraft can accelerate within the available runway, achieve appropriate rotation speeds, clear obstacles safely, and maintain adequate climb performance in the event of an engine failure.

Even small discrepancies in performance inputs—such as aircraft weight, runway length, environmental conditions, or configuration—can disproportionately affect safety outcomes. The margins available during take-off are inherently narrow, particularly for long-haul, high-weight operations in demanding environmental or runway conditions.

Although digital tools have largely eliminated traditional calculation errors associated with manual performance charts, they remain fundamentally dependent on the accuracy of input data. As a result, operational risk has shifted to a “garbage-in, garbage-out” paradigm, where incorrect inputs can produce internally consistent yet unsafe outputs.

Automation: Shifting Rather Than Eliminating Risk

The introduction of EFBs and FMS-based performance tools has undoubtedly enhanced operational efficiency. However, these systems are highly sensitive to incorrect inputs, including aircraft weight, flap configuration, runway selection, and environmental parameters. When erroneous data is entered, the resulting calculations—though mathematically correct—may be operationally invalid.

A growing concern in the industry is the erosion of rigorous manual cross-checking practices. As automated systems consistently produce reliable outputs under normal conditions, there is a tendency for flight crews to accept these outputs with less scrutiny. This over-reliance can be compounded when both pilots independently enter the same incorrect data, or when values are communicated verbally and replicated, effectively contaminating what is intended to be an independent verification process.

Human factors play a central role in this dynamic. Expectation bias may lead crews to accept performance figures that “look about right” for a given operation, while confirmation bias reinforces acceptance of outputs that align with preconceived expectations. These tendencies are especially pronounced under time pressure, such as during rapid turnarounds at congested airports, where operational demands can compress decision-making timelines.

The growing complexity of airport environments further exacerbates these risks. Frequent runway changes, temporary displaced thresholds, construction-related NOTAMs, and intersection departures introduce variability that must be accurately reflected in performance calculations. Any mismatch between assumed and actual conditions can significantly erode safety margins.

Case Study: LATAM Boeing 777-300ER Tail Strike, Milan (2024)

A particularly instructive example occurred on 9 July 2024 at Milan Malpensa Airport, when a LATAM Boeing 777-300ER on a long-haul flight to São Paulo sustained a severe tail strike during take-off from Runway 35L. The aircraft sustained substantial structural damage and was later classified as an accident.

The investigation revealed that the crew had used an incorrect gross take-off weight of 228.8 tonnes instead of the actual 328.4 tonnes—an underestimation of about 100 tonnes. The error occurred when the line training captain mentally subtracted expected taxi fuel from the displayed weight, yielding an incorrect figure. Crucially, this value was then communicated verbally in the cockpit and entered into both pilots’ EFBs for performance calculation using Boeing’s Onboard Performance Tool.

Because both devices received the same erroneous input, they produced identical thrust settings and V-speeds. This apparent consistency masked the underlying error and rendered standard cross-checks ineffective. The calculated rotation speed was more than 30 knots below the required speed for the actual aircraft weight.

During the take-off roll, the aircraft reached the erroneously computed rotation speed, prompting the crew to rotate prematurely. The aircraft pitched up rapidly but failed to generate sufficient lift for its actual weight, resulting in prolonged tail contact with the runway. The tail remained in contact for over 700 metres, causing extensive structural damage.

Despite the severity of the event, the crew managed the situation effectively after the incident by dumping fuel and returning safely to Milan. There were no injuries among the 398 occupants. However, the incident clearly illustrates how a single mental arithmetic error, combined with shared data entry and ineffective cross-checking, can breach multiple layers of defence.

Recurring Patterns in Recent Occurrences

The LATAM event is not an isolated case but part of a broader pattern observed in recent years. Several incidents have involved crews initiating take-off using performance data calculated for full-length runways, despite temporary reductions in available runway length. In other cases, aircraft have commenced take-off from intersection points without recalculating performance data, thereby reducing the usable runway length.

These occurrences are often linked to incomplete briefings, misinterpretation of runway markings, or failure to incorporate updated NOTAMS. In each case, the root cause is not the absence of procedures or tools, but a breakdown in verification processes and situational awareness.

Weight-related discrepancies have also been prominent, leading to incorrect V-speeds and thrust settings that increase the risk of tail strikes, runway excursions, or degraded climb performance. These events consistently follow a similar progression: a relatively minor input error is introduced, cross-checking is ineffective or compromised, and the resulting incorrect outputs are executed without challenge.

The Error Chain and Layered Defences

These incidents can be understood through the concept of an error chain, in which an initial mistake propagates through successive stages without detection. The failure typically begins with an incorrect input or assumption, followed by inadequate cross-verification, leading to incorrect performance outputs and, ultimately, unsafe execution during the take-off roll.

Aviation safety relies on multiple layers of defence to intercept such errors. These include organisational measures such as standard operating procedures and training; technical systems such as EFB validation logic and FMS safeguards; human factors such as disciplined challenge-and-response procedures; and operational elements such as thorough briefings and situational awareness.

When these layers function effectively, errors are detected and corrected before they compromise flight safety. However, when gaps align across these layers—as described in the Swiss Cheese model—errors can pass through all defences, leading to serious incidents or accidents.

Performance Margins and Operational Sensitivity

Take-off performance is highly sensitive to changes in aircraft weight, temperature, altitude, and runway conditions. As these factors increase, performance margins shrink, leaving less tolerance for error. High-weight, long-haul departures are particularly vulnerable because they operate closer to performance limits.

In such conditions, even minor inaccuracies in input data can significantly affect the required take-off distance, rotation speeds, and climb capability. This underscores the importance of accurate data entry and robust verification processes.

Strengthening Defences

Mitigating the risk of incorrect take-off performance data requires a combination of disciplined operational practices, technological enhancements, and organisational support. At the flight crew level, truly independent calculation and verification of performance data are essential. This requires avoiding verbal contamination of inputs and ensuring that each pilot conducts a separate, unbiased assessment before comparing results.

Reasonableness checks provide an additional layer of defence by prompting crews to assess whether computed values align with expected performance under the given conditions. Such checks can help identify anomalies that might otherwise go unnoticed.

Technological solutions are also evolving. Take-Off Performance Monitoring Systems (TOPMS) are being developed to compare actual aircraft acceleration during the take-off roll with predicted performance and to provide real-time alerts when deviations are detected. Enhanced EFB systems with improved validation logic and integration with aircraft and airport databases can further reduce the likelihood of input errors.

At the organisational level, scenario-based training that replicates real-world challenges—such as last-minute runway changes, intersection departures, and high-weight operations—can enhance crew preparedness. Flight Data Monitoring programmes can identify trends and detect anomalies.

Future Outlook

The industry is transitioning from:  Error prevention → Error detection and recovery 

Key developments include:

a) AI-driven anomaly detection

b) Real-time performance validation

c) Integration of aircraft and ground data systems

However, technology alone cannot eliminate the risk. The human-machine interface and operational discipline remain decisive.

Conclusion

Incorrect take-off performance data remains a persistent, systemic safety threat, not because of complexity but because of the failure to detect simple errors in time.

Recent incidents demonstrate that:

a) The hazard is not diminishing despite technological advances.

b) It is increasingly influenced by operational complexity and human factors.

The most effective mitigation is a multi-layered defence strategy:

a) Human vigilance

b) Technological safeguards

c) Organisational resilience

“Take-off performance errors are rarely unavoidable—they are almost always detectable before they become irreversible.” 

Author: GR Mohan

Systemic Failures in India’s Indigenous Fighter Engine Development

 A Critical Assessment of GTRE’s Kaveri Program

The development of a modern fighter-class turbofan engine represents one of the most technologically demanding undertakings in aerospace engineering. It requires mastery over high-temperature metallurgy, advanced aerothermodynamics, precision manufacturing, control systems integration, long-duration reliability validation, and a deeply integrated industrial ecosystem. Over the past several decades, India’s principal institutional vehicle for achieving this capability has been the Gas Turbine Research Establishment (GTRE), a laboratory under the Defence Research and Development Organisation (DRDO).

The most ambitious expression of this mandate was the GTX-35VS Kaveri engine program, launched in 1989 to power the Light Combat Aircraft, later known as the HAL Tejas. The program was intended to deliver a fully indigenous, afterburning turbofan capable of producing approximately 52 kN of dry thrust and 81–90 kN of wet thrust. After nearly four decades of effort, the engine failed to qualify for fighter service and was delinked from the Tejas program. The consequences were strategic: India’s indigenous fighter entered service powered by foreign engines.

While aero-engine development is universally complex and often prolonged, the Kaveri experience reveals not merely technical difficulty but a pattern of systemic failure. These failures spanned thermodynamic design assumptions, materials capability, governance structure, infrastructure readiness, and ecosystem integration. By 2021, the program had expended over ₹20 billion (equivalent to ₹50 billion in 2023), with only partial milestones met.

The Core Technical Problem: Failure to Achieve Rated Dry Thrust

The Kaveri engine's primary technical failure centres on its inability to consistently achieve targeted dry thrust levels across the full operational envelope, a critical measure of core integrity. Dry thrust, generated without afterburner, hinges on the efficient integration of compressor, combustor, and turbine stages, encompassing airflow management (designed at 78 kg/s), pressure ratios (21.5:1 overall), and thermal tolerances.

Despite efforts, the engine attained only 48.5–51 kN in dry thrust during high-altitude tests by 2022—below the 52 kN design goal—and fell short of the 83–85 kN wet thrust required for advanced Tejas variants. As DRDO Chairman Samir V. Kamat noted in 2025, while the engine performs adequately at 72 kN wet thrust, it lacks the scalability for Tejas integration.

Analyses, including the 2011 Comptroller and Auditor General (CAG) report, identified key deficiencies: inefficiencies in compressor stages (featuring transonic blading in low-pressure sections and variable inlet guide vanes in high-pressure), constraints on turbine inlet temperature (TIT ≈1,427°C) due to material limitations, and airflow mismatches. Absent advanced single-crystal superalloy turbine blades with internal cooling channels and thermal barrier coatings, the thermodynamic cycle was inherently restricted, necessitating derating to avert creep, thermal fatigue, and structural failure.

This underperformance arose from an overly ambitious cycle design that surpassed India's domestic materials and manufacturing capabilities at the time. Repeated turbine blade failures in the early 2000s prompted imports from France's Snecma (now Safran), underscoring the gap. Fundamentally, dry thrust shortfalls—not merely afterburning deficits—exposed core-level flaws in compressor efficiency, achievable TIT, and integration, as thermodynamic aspirations outpaced available ecosystem support.

Ambition–Capability Mismatch in Cycle Design

The Kaveri was conceived as a near fourth-generation class engine in a country without prior operational turbofan production experience. Its targeted pressure ratios and temperature regimes required advanced single-crystal turbine blades, sophisticated internal cooling passages, and high-precision casting technologies.

India did not possess a mature ecosystem for single-crystal superalloys during critical development phases. Without this capability, sustained high-temperature operation at design limits becomes structurally unviable. Turbine blades experience creep, thermal fatigue, and life-cycle instability. As a result, TIT must be reduced, which in turn lowers thrust.

This created a structural contradiction: the engine’s design cycle demanded performance levels that the industrial base could not yet support. Instead of recalibrating ambition to ecosystem readiness, the program attempted incremental fixes within an over-ambitious architecture.

Weight Growth and Performance Degradation

As development progressed, the engine reportedly gained weight relative to its original targets. Weight growth in turbofan programs typically reflects structural reinforcement, redesign for stress tolerance, or compensatory adjustments to address performance shortfalls.

An increase in mass reduces thrust-to-weight ratio and further constrains fighter integration viability. In high-performance aircraft, propulsion margins are unforgiving. Even moderate weight escalation can render an engine noncompetitive.

This weight spiral was not merely a numerical inconvenience; it was symptomatic of deeper, unresolved engineering trade-offs.

Altitude Testing and Operational Envelope Collapse

A pivotal moment in the Kaveri program occurred during high-altitude testing conducted abroad in the early 2000s. These tests revealed that the engine could not consistently demonstrate stable performance across the required operational envelope.

Altitude testing exposes surge margin deficiencies, airflow instability, temperature stress behaviour, and transient response weaknesses. Failures at this stage indicate that laboratory-level validation had not translated into flight-representative robustness.

Following these setbacks, the engine was removed from the Tejas integration roadmap. That decision marked the effective termination of its fighter role.

Governance and Systems Engineering Deficiencies

Technical challenges alone do not fully explain the program’s outcome. Several systemic governance weaknesses appear to have compounded the engineering problems.

First, there were reports that external consultants and international experts raised concerns about core sizing, achievable pressure ratios, and realistic temperature limits. Allegations persist that more radical redesign options were not adopted decisively when these warnings emerged. In complex aerospace programs, early architectural reset is often painful but necessary. Delayed course correction can lock a project into incremental compromise rather than structural resolution.

Second, the design freeze discipline appears to have been weak. The Tejas airframe itself evolved over time, gaining weight and altering performance demands. Instead of resetting the propulsion architecture to match revised aircraft requirements, the engine program continued along its established trajectory. Requirement drift layered complexity onto an already stressed design.

Third, the institutional structure under which GTRE operated was oriented toward research and prototype development rather than industrial-scale certification and reliability growth. Fighter engines require not only technological innovation but thousands of hours of endurance validation, statistical reliability tracking, and production engineering culture. That industrial maturity was not fully aligned with program ambition.

Infrastructure and Ecosystem Constraints

At the time of critical development phases, India lacked comprehensive indigenous high-altitude test facilities and long-duration endurance test cells for fighter-class engines. Reliance on foreign testing infrastructure meant that key performance truths emerged late in the program lifecycle.

Equally significant was the limited integration of private-sector metallurgy, precision manufacturing, and advanced coating technologies. A fighter turbofan is not the product of a single laboratory; it is the output of a coordinated industrial ecosystem. That ecosystem was still embryonic during Kaveri’s formative years.

Moreover, coordination between designer (GTRE), manufacturer (HAL), and end user (Indian Air Force) appears to have lacked the tight iterative feedback mechanisms seen in established engine houses. Effective propulsion development requires continuous user-informed refinement.

Strategic Consequences

The delinking of the Kaveri engine from the Tejas program had significant strategic consequences. Tejas entered service with GE engines under contracts exceeding $105 million in 2004, reinforcing foreign propulsion dependence and increasing cost and schedule exposure. The move also affected DRDO’s propulsion credibility, with implications for future ambitions such as the AMCA, where engine autonomy is critical.

However, the program yielded technological spin-offs. A dry-thrust Kaveri Derivative Engine (48–50 kN) is being positioned for the Ghatak UCAV, while a 12 MW marine variant (KMGT) has been explored for naval use. Industrial partnerships, including with BHEL, and advances in combustor technology, indigenous FADEC (KADECU), and metallurgy have strengthened technical foundations for future efforts, including a potential 75–79 kN “Kaveri 2.0.”

Despite these gains, India has yet to field an operational indigenous fighter-class turbofan, leaving the original strategic objective unfulfilled.

Inference

The Kaveri program did not fail simply because aero-engines are difficult to build. It failed because systemic misalignments were never fully corrected.

1) Thermodynamic ambition exceeded material capability.

2) Cycle design was not recalibrated when ecosystem constraints became evident.

3) Dry thrust shortfalls exposed core-level limitations.

4) Altitude testing revealed operational fragility.

5) Governance mechanisms did not enforce early architectural reset.

6) Infrastructure lagged performance targets.

Taken together, these factors constitute a systemic failure rather than an isolated technical setback.

GTRE did build valuable knowledge in gas turbine science, combustor design, and control systems. However, the central strategic mandate—to deliver a certified indigenous fighter turbofan—remains unmet.

If future propulsion programs are to succeed, ambition must be synchronised with industrial readiness, design governance must enforce hard reset decisions when required, and ecosystem development must precede rather than follow thermodynamic aspiration.

Only then can propulsion sovereignty move from aspiration to operational reality.