Case Study
What happened here
1 / 2 Fatalities or injuries0
Aircraft taking offAir India AI657
Aircraft landingIndiGo flight from Indore
RunwayMumbai single active-runway operation
Immediate actionController de-rostered pending investigation
What we can say safely
An Air India A320 was taking off as an IndiGo A320 landed on the same runway shortly afterward. No collision or injury occurred, and DGCA de-rostered the controller while investigating.
- Air India aircraft begins take-off roll
- IndiGo aircraft continues approach with landing clearance
- Landing occurs shortly after departing aircraft becomes airborne
- Public attention focuses on spacing
- DGCA de-rosters controller and investigates
Why consequences escalated
- Runway separation depends on controller judgement, crew compliance and predictable aircraft performance
- A stable approach does not remove the option to go around
- Read-back and runway-occupancy monitoring are critical defences
- Viral video cannot by itself establish exact separation or culpability
- Near misses should be investigated without waiting for harm
Failures and risk multipliers
- Ignoring foreseeable occupancy and access hazards
- Depending on a single protective layer
- Failing to maintain separation, warning or escape space
- Treating early reporting as a final finding
- Failing to document and close corrective actions
People closest to the evidence
“Safety principle”
Human error must be anticipated through separation, warning, supervision and independent barriers.
Actions that reduce risk
- Identify two safe escape routes
- Control speed, ignition sources and combustible loading
- Maintain emergency access
- Inspect alarms and protective equipment
- Record occupants, vehicles and hazardous stock
- Call 112 or the local emergency service promptly