Air India A320 lands safely in New Delhi after in-flight altitude variation; 12 taken to hospital
India's Directorate General of Civil Aviation has opened an investigation into the August 4 occurrence on flight AI2379, which landed at Indira Gandhi International Airport.
More on this incident
Was this report accurate and useful?
Reference data
From aircraft and geographic registries, not from the news sources. Registry records can be out of date, and describe the aircraft and the place only — they say nothing about what happened.
- Registration
- VT-EXO
- Type
- AIRBUS — twin-engine jet landplane
- Terrain elevation
- 702 ft
- Nearest aerodrome
- 2.0 miles N of Safdarjung Airport (VIDD)
Sources
- Air India flight suddenly loses 300 ft altitude, 15 injuredsiasat.com
- Civil Aviation Minister Ram Mohan Naidu visits injured Air India flight passengers, assures assistancenews.webindia123.com
- "Life-threatening, serious": Aviation expert on Air India turbulence incident; seeks DGCA probemexicostar.com
- "Life-threatening, serious": Aviation expert on Air India turbulence incident; seeks DGCA probeasiabulletin.com
- "Life-threatening, serious": Aviation expert on Air India turbulence incident; seeks DGCA probecalcuttanews.net
- "Life-threatening, serious": Aviation expert on Air India turbulence incident; seeks DGCA probethailandnews.net
- "Life-threatening, serious": Aviation expert on Air India turbulence incident; seeks DGCA probenews.webindia123.com
- "Life-threatening, serious": Aviation expert on Air India turbulence incident; seeks DGCA probeindiagazette.com
- DGCA summons Air India management over Phuket-Delhi turbulence incidentthehindubusinessline.com
- 'Four to five minutes of severe turbulence': Minister details Air India flight ordeal that injured 17 | Indiablooms - First Portal on Digital News Managementindiablooms.com
- Air India Phuket-Delhi flight incident French agency BEA Airbus to assist in AAIB probedailypioneer.com
Revision history
- Version 512 Aug 2026, 00:06current
Added dailypioneer.com report that France's BEA and Airbus will assist the AAIB probe, removed the note that no update had been published, and added Indian registry details for VT-EXO.
- Version 47 Aug 2026, 13:23
Removed the live/developing framing ("details are still developing") and replaced it with an explicit statement that the account is fixed to the available reporting and that no further information has been published since; headline and dek reworded to match. Added a closing note that no DGCA committee has been announced as of the latest reporting. Deleted an unsupported sentence about Indian aircraft registry records for VT-EXO, which is not in the fact set. Preserved both aircraft-type readings (Airbus A320neo / Airbus A320 / A320) and both injury figures (15 per siasat.com, 17 per indiablooms.com) as sourced ranges without picking one, and set out the four differing descriptions of the investigation's status with attribution. All figures, times and identifiers printed exactly as given: AI2379, VT-EXO, 300 feet, 137 passengers and eight crew, 134 passengers and 8 crew members, 11:07 hrs IST, around 11.30 am, 18:50 hrs on August 4, 3:30 p.m. Tuesday.
- Version 36 Aug 2026, 00:02
Restructured lead around the DGCA investigation, added mexicostar.com to the attributed source lists and cited a second news.webindia123.com report.
- Version 25 Aug 2026, 23:57
Added calcuttanews.net and asiabulletin.com to the A320neo attribution, plus the hospital-admission breakdown (eight passengers and four cabin crew), the 11-passenger/four-crew injury account, the Tuesday discharge time and a passenger's account of an unbelted passenger striking the cabin roof.
- Version 27 Aug 2026, 13:24
Added the Phuket–Delhi routing, severe turbulence and ~300 ft altitude loss, conflicting injury (15–17) and occupant figures, hospital discharges, the DGCA summoning Air India management, and expert comment; noted the aircraft type conflict.
- Version 15 Aug 2026, 23:47current
First published.
- Version 15 Aug 2026, 23:52
First published.
How we work
This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.
Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.
Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.
None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.