Air India Express flight 173 crashed while landing at Kozhikode on August 7, 2020, raising urgent questions about how modern operations can still end in tragedy. Investigators focused on runway overruns, weather, and decision processes to understand why this specific event occurred.
Below is a structured overview that frames the incident around operational checks, human factors, aircraft performance, and outcomes to help readers quickly grasp what went wrong and how such events are analyzed.
| Event Element | Details | Investigation Finding | Impact |
|---|---|---|---|
| Flight | Air India Express Flight 173 | Scheduled international service | Carried 191 people |
| Aircraft | Boeing 737-800 | Registered VT-AXH | Age 9 years, recent heavy maintenance |
| Runway | Cochin International Airport, runway 25 | Wet conditions, insufficient remaining runway | Overrun at high speed |
| Decision Point | Continue unstable approach | High approach speed, late go-around call | Reduced margin to stop safely |
| Outcome | Runway overrun with fire | 19 injuries, no fatalities | Aircraft destroyed |
Approach Stability and Decision Making
The approach into Kozhikode was unstable from an early stage, with airspeed and configuration issues that should have triggered a go-around much earlier. Investigators emphasized that stable approach criteria were not maintained, and the crew underestimated the energy management challenge on a wet runway.
Key Instability Markers
- Airspeed excursions above target approach speed
- Late gear and flap selection
- Lack of timely go-around call when deviations persisted
These factors combined to leave very little margin when the aircraft touched down further down the runway than planned, especially in contaminated conditions.
Runway Conditions and Performance Planning
Kozhikode runway 25, though long by regional standards, became effectively shorter due to water on the surface and the aircraft’s higher-than-optimal approach speed. Performance calculations did not fully account for the degraded braking action, leading to an unreliable stopping margin.
Performance Considerations
- Reduced brake effectiveness on wet runway
- Underestimation of required landing distance
- Lack of robust assessment for standing water depth
Modern flight planning tools must explicitly include runway condition, aircraft contamination, and actual landed weight to avoid runway overruns.
Human Factors and Crew Resource Management
Human factors played a critical role, including task saturation, potential expectation bias, and delayed recognition that a go-around was needed. Investigators pointed to opportunities for better monitoring and assertive communication within the cockpit.
Contributing Human Factor Elements
- High workload during final approach
- Passion for on-time performance possibly influencing decision timing
- Insufficient cross-check of energy state and runway availability
Training emphasizing assertive call-outs and adherence to sterile cockpit practices could mitigate similar events in complex operations.
Aircraft Systems and Maintenance Context
While the aircraft had recently undergone heavy maintenance, the investigation did not cite mechanical failure as the primary cause. Instead, systems interacted in a challenging environment where pilot inputs and aircraft response were less forgiving due to higher energy and reduced runway.
Systems and Maintenance Highlights
- No active fault indications reported prior to landing
- Autobrakes and reverse thrust available but applied late
- Recent heavy maintenance completed without outstanding airworthiness issues
This underscores that even properly maintained aircraft require precise energy control in degraded conditions.
Operational Culture and Oversight
Organizational pressures around scheduling, cost recovery, and turnaround times can subtly influence how crews interpret go-around decisions. Regulators and operators must reinforce that delays are preferable to unsafe deviations near the ground.
Systemic Factors
- Punctuality expectations vs. safety margins
- Training emphasis on risk awareness and contingency planning
- Monitoring of approach stability criteria across the network
Strengthening a just culture where crews can call for go-arounds without penalty is essential to prevent recurrence.
Enhancing Risk Awareness and Operational Safety
Improvements in flight planning, cockpit communication, and organizational culture can collectively reduce the likelihood of runway overruns and unstable approaches. Continuous monitoring, data-driven training, and robust oversight remain central to aviation safety.
- Enforce low energy and unstable approach go-around triggers
- Integrate real-time runway friction and contamination data into dispatch
- Regular recurrent training on energy management and CRM
- Promote a just culture where crews prioritize safety over schedule recovery
FAQ
Reader questions
Why did the aircraft overrun the runway despite a long runway at Kozhikode?
The aircraft approached at a higher speed than optimal, touched down late, and encountered reduced braking effectiveness due to wet conditions, leaving insufficient distance to stop within the available runway.
Were there any mechanical issues that caused the crash?
No mechanical failure was identified; all systems functioned as intended, but late application of braking and thrust reversal limited deceleration.
How did weather contribute to the incident?
Surface water reduced tire-road friction, effectively shortening the runway, while the crew underestimated the additional landing distance required in wet conditions.
What lessons were drawn for airline operations and training?
Airlines now emphasize stricter adherence to stable approach criteria, more explicit runway condition assessment, and reinforced crew resource management training focused on timely go-around decisions.