Summary
An Air India Boeing 777-300ER operating flight AI816 was forced to abort a high-speed takeoff at Mumbai’s Chhatrapati Shivaji Maharaj International Airport on July 7, 2026 after air traffic control spotted an Air India Express Boeing 737 still occupying the active runway. The crew halted the jet safely, averting a potential collision.
No injuries were reported, and the aircraft returned to the gate for mandatory post-abort inspections. Passengers are being transferred to alternative Delhi flights while the Directorate General of Civil Aviation investigates the runway incursion.
A routine pushback turned into a high-stakes abort Tuesday evening when Air India flight AI816 was accelerating down Mumbai’s runway 27. An urgent call from air traffic control forced the widebody’s pilots to slam the brakes, stop the 777 on the runway, and return to the bay—all because another aircraft was still in the way.
The Boeing 777-300ER, registered VT-ALT, was carrying several hundred passengers bound for Delhi.
Air India confirmed that the crew followed the ATC instruction precisely. “The crew operating flight AI816 discontinued the takeoff run after receiving an instruction from air traffic control and returned to the bay. The aircraft will undergo necessary checks as per standard operating procedures,” the airline stated, adding that passengers were being rebooked at the earliest. The aborted departure came just seconds before the 777 would have been committed to flight, illustrating the razor‑thin margins at one of India’s busiest airports, where high runway occupancy can leave no room for error. The incident, while confined to a domestic route, disrupted the critical Mumbai–Delhi corridor and underscored how quickly a routine departure can transform into a safety-critical event.
The details
Flight AI816 had begun its takeoff roll when Mumbai air traffic control issued an immediate “stop” command. Airport sources later indicated the abort was triggered because an Air India Express 737 that had just landed had not cleared the runway. The 777’s crew complied, brought the jet to a halt on the runway, and then taxied back to the terminal. The aircraft was taken out of service for the mandatory brake‑cooling and engineering inspections that follow any high‑energy rejected takeoff.
Passengers were deplaned and offered alternative seats on later flights to Delhi. Air India emphasized that safety remained the overriding priority and that the decision to abort aligned with established protocols. The runway at Chhatrapati Shivaji Maharaj International Airport was briefly closed while the sequence was reviewed and the aircraft was cleared from the active strip.
| Date/Event | Incident detail | Impact | Status |
|---|---|---|---|
| Evening, 7 July 2026 | AI816 begins takeoff roll; Air India Express 737 lands and does not immediately vacate | Takeoff roll aborted | No damage or injuries |
| Immediately after ATC call | Pilots reject takeoff, stop on runway, return to gate | Aircraft removed from service for mandatory checks; runway briefly closed | Passengers rebooked |
| Ongoing | DGCA launches investigation into simultaneous runway occupancy | Possible procedural review | Preliminary report expected within 7–10 days |
Flight deals most people never see
Our AI monitors 150+ airlines for pricing anomalies that traditional search engines miss. Air Traveler Club members save $650 per trip per person on average: see how it works.
Each deal saves 40–80% vs. regular fares:
Why the near‑miss raises hard questions for Mumbai ops
The successful coordination between Mumbai’s air traffic controllers and the Air India cockpit was textbook—the crew responded instantly, and no metal touched. Yet the event also exposes the chronic congestion at an airport where heavy international and domestic traffic share a single runway complex. For premium travellers on the Mumbai–Delhi trunk route, the 777’s reliability matters; the flagship jet is a backbone of Air India’s premium offering, and any prolonged inspection could ripple through schedules. Air Traveler Club’s analysis of the LaGuardia runway incursion in March 2026 highlighted how an ATC misjudgement can cascade into tragedy—the Mumbai abort is a stark reminder of just how narrow the margin can be.
What the DGCA investigation means for Mumbai runway operations
The Directorate General of Civil Aviation is now examining how two aircraft were simultaneously cleared onto the same runway. Preliminary findings are expected within 7 to 10 days. If investigators determine that the Air India Express crew failed to promptly vacate, or that ATC coordination gaps allowed the conflict, the regulator is likely to impose mandatory new procedures for runway occupancy clearances at Mumbai. Such changes could tighten the already constrained operation, potentially affecting on‑time performance at India’s second‑busiest airport. Watch for the DGCA’s initial statement—it will signal whether this was an isolated lapse or a systemic weakness.
FAQ
What caused the aborted takeoff?
Air traffic control ordered the halt after spotting an Air India Express Boeing 737 that had not cleared the runway after landing, creating a conflict with the accelerating Air India 777.
Were there any injuries or damage?
No injuries or damage were reported. The aircraft stopped safely on the runway and returned to the gate for mandatory post-abort inspections.
Will my upcoming Mumbai–Delhi flight be affected?
The incident involved only a single aircraft. However, if the 777 remains under inspection, some flights may be consolidated or delayed. Affected passengers are being rebooked, and Air India has prioritized getting all customers to Delhi as soon as possible.
Read more
