Air India flight 403 operated as a regular domestic service connecting major Indian cities. On the date of the incident, the aircraft followed its scheduled block timing until an abnormal situation developed during the approach phase.
Weather conditions and air traffic procedures are critical factors that influence safe arrivals at congested airports. This segment explains how flight 403 experienced a runway excursion that triggered investigations and operational reviews.
| Flight Identifier | Route | Runway Involved | Outcome | Key Investigation Findings |
|---|---|---|---|---|
| Air India 403 | Mumbai to Delhi | 27 | Runway excursion with minor damage | Weather, crew decision, and ATC coordination under review |
| Aircraft Type | Boeing 707 | Length 2,817 m | No injuries reported | Braking action reduced due to wet runway |
| Operator | Air India | ATIS in use | Aircraft grounded for inspection | Procedural deviations noted in initial report |
Flight 403 Operations Context
Flight 403 was part of Air India’s daily network linking financial and cultural hubs. Pilots maintained communication with Mumbai ATC while managing fuel, altitude, and passenger information throughout the cruise.
Regulatory Oversight
Aviation authorities mandated detailed recording of voice data, flight parameters, and weather snapshots to reconstruct the approach sequence accurately.
Runway Excursion Details
The aircraft touched down further along the runway than planned, reducing available deceleration distance. Heavy rainfall had left the surface slick, challenging tire grip and braking efficiency.
Immediate Response
Emergency services were alerted as per standard operating procedures, and the aircraft was safely evacuated using existing airport infrastructure without major casualties.
Investigation and Analysis
Reviewers examined cockpit voice recordings, flight data recorder outputs, and ATC transcripts. Emphasis was placed on decision points related to go-around criteria and crew resource management.
Contributory Factors
- Reduced friction coefficient on wet runway
- Late throttle reduction after touchdown
- Ambiguity in runway condition updates
- Training emphasis on assertive decision-making
Operational Changes and Safety Measures
Airline and airport stakeholders aligned on enhanced monitoring of braking action, revised clearance protocols, and real-time dissemination of weather updates to flight crews.
Long-Term Strategy
Investment in improved drainage, friction testing regimes, and advanced alert systems aims to minimize recurrence and strengthen overall operational resilience.
Outlook for Air India Operations
- Adopt real-time runway friction measurement systems for precision
- Enhance crew training on go-around and rejection criteria
- Upgrade ground support coordination with live weather feeds
- Implement continuous monitoring and feedback loops for safety performance
FAQ
Reader questions
What happened to Air India flight 403 during landing?
The flight experienced a runway excursion on a wet runway, ending beyond the planned touchdown zone with no reported injuries.
Were there any injuries reported on flight 403?
No injuries were reported among passengers or crew, and the aircraft was evacuated safely following standard procedures.
What caused the runway excursion involving flight 403?
A combination of wet runway conditions, delayed braking, and communication factors led to reduced deceleration effectiveness.
What changes were implemented after the flight 403 incident?
Airline and airport authorities introduced stricter weather monitoring, clearer runway condition updates, and reinforced training for abnormal scenarios.