FirstAlerts
Plane CrashesVersion 6

Air India A320neo drops about 300 feet in cruise on Phuket–Delhi flight; 17 reported injured

India's DGCA has opened an investigation and secured the flight recorders after AI2379 landed safely at Delhi on 4 August 2026.

By AI ReporterFirst reported Aug 4, 2026, 6:15 p.m. ETUpdated Aug 7, 2026, 10:44 a.m. ET

More on this incident

people were injured aboard an operating flight from Phuket to on 4 August 2026, according to Simple Flying, BNO News and The New Indian Express; People's Daily Online put the number of injured at , of whom two were crew members. Accounts of the time differ: Simple Flying said and BNO News gave , while The New Indian Express said the loss of altitude likely occurred around 10.30 am IST. The aircraft landed safely at 's Indira Gandhi International Airport. What follows is the most recent reporting available from the outlets cited here; none of them has published a cause, and the figures below are theirs as they last gave them. The outlets reported the aircraft dropped about 300 feet (91 meters) while cruising above 36,000 feet. BNO News and The New Indian Express reported the flight departed Phuket at 8.27 am with 137 passengers, including three infants, and eight crew members — two pilots and six cabin crew — and landed at Terminal 3 at 11.07 am; the sources also reported 134 passengers on board. The New Indian Express reported the pilot initially announced an emergency landing at Lucknow but continued to , and that the flight did not divert and completed its scheduled route. said 13 passengers and four crew members were injured and taken to hospital, and that five passengers had been discharged by 6.50 pm on 4 August. A DGCA source cited by The New Indian Express said one cabin crew member was seriously injured. Reporting described a passenger with fractured ribs from an armrest and another whose head struck the cabin ceiling; injured people were treated at the airport's Medanta medical centre and then moved to Fortis Hospital, Vasant Kunj and a spinal injury centre, where Civil Aviation Minister Ram Mohan Naidu visited. The Times of reported that the family of an injured passenger alleged there were no ambulances on standby and no senior or airport staff present after landing. Overhead panels and interior fittings were damaged, and a photo appeared to show cracks in several overhead panels, according to the reporting. The aircraft was moved to a hangar after landing and grounded, and is believed to have suffered substantial damage; has not disclosed details. The cause has not been determined. Accounts of the investigation's scope differ: BNO News reported that 's Directorate General of Civil Aviation has opened an investigation and secured the flight data recorder and cockpit voice recorder for examination, and that Airbus was notified; The New Indian Express reported the DGCA has initiated a comprehensive investigation into the occurrence; and the Times of reported the DGCA has launched a probe while said it is cooperating. No finding has been announced in any of the reporting cited here. The aircraft was not identified in any official record in the fact set. A registration of was derived from flight tracking data and has not been confirmed by an authority. Aircraft registry records for list an Airbus, a twin-engine jet landplane, registered in . A weather observation recorded at Indira Gandhi International Airport (VIDP), 9.2 miles away and 30 minutes from the reported time, showed wind from 150° at 3 knots, visibility 2.8 statute miles, scattered cloud at 900 feet, mist and a temperature of 84°F. That is an instrument reading at a field, not a statement by anyone and not a cause.

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
722 ft
Nearest aerodrome
5.7 miles N of Safdarjung Airport (VIDD)

Sources

Revision history

  1. Version 1413 Aug 2026, 08:29current

    Added the 10–15 day preliminary-report timeline and DGCA's pending decision on action, the AAIB's summons of the crew and scope of its examination, the maintenance report's elevator fault and "AUTO FLT AP OFF" entry, and unconfirmed sourced claims about controlled rest and a failed secondary drug test.

  2. Version 1313 Aug 2026, 08:23

    Added Economic Times reporting of a purported maintenance report listing hydraulic low-pressure alerts and two autopilot disconnections, its higher injury figure (20 passengers and four cabin crew), the drop's location over Odisha, and its A320 type description.

  3. Version 1212 Aug 2026, 11:32

    Added Daily Mail reporting on the pilot (found on the cockpit floor, denial of substance use, investigator assistance with the sample, alleged layover party and a crew complaint over alleged marijuana use), its 12-injured figure, and noted The Hindu BusinessLine leaves the cause unstated.

  4. Version 1112 Aug 2026, 00:34

    Added Economic Times reporting that the AAIB has taken up the investigation under ICAO protocols with BEA and Airbus technical assistance, the ministry's summons of Air India CEO Campbell Wilson, the "non-negative" initial screening description, and unconfirmed reports of technical glitches and hydraulic failures.

  5. Version 1011 Aug 2026, 00:16

    Added the ministry's classification of the occurrence as a serious incident under AAIB investigation, the DGCA taking both flight crew off roster, the pilot in command's screening test sent for confirmatory analysis, the minister's account of two crew with spinal injuries, Air India's 'brief turbulence-related event' description, and public reaction reported by The Hindu BusinessLine.

  6. Version 97 Aug 2026, 14:43

    No new facts; the tracking-derived registration VT-EXO is now attributed to the outlets that reported it.

  7. Version 85 Aug 2026, 23:53

    Added People's Daily Online's competing injury count of 12, including two crew members, alongside the 17 reported elsewhere.

  8. Version 75 Aug 2026, 23:47

    Added New Indian Express reporting: departure and arrival times, cruise above 36,000 feet, a third time estimate, the announced then abandoned Lucknow emergency landing, aircraft grounded with believed substantial damage, a seriously injured cabin crew member per a DGCA source, hospital treatment details and the civil aviation minister's visit.

  9. Version 65 Aug 2026, 23:43

    Added conflicting reported times (11:00 vs 11:07), BNO News details on recorders secured, Airbus notified, aircraft moved to hangar, and occupant breakdown; corrected the weather observation to the reading at Indira Gandhi International Airport.

  10. Version 67 Aug 2026, 14:44current

    Removed the "This remains a developing story and details may change" line and any live-coverage framing, replacing it with an explicit statement that the piece reflects the most recent reporting available from the cited outlets and that no cause has been published. Added a closing sentence to the investigation paragraph noting no finding has been announced, so the reader still learns the matter is unresolved without the story claiming to be actively updating. All sourced content is unchanged: the 17-injured figure (Simple Flying, BNO News, The New Indian Express) still leads with the competing 12 from People's Daily Online in the same breath; the three time accounts (11:00 local time / 11:07 a.m. local time / around 10.30 am IST) and the three investigation accounts are still reported as sourced ranges naming each outlet; the VT-EXO registration is still flagged as tracking-derived and unconfirmed; the weather observation retains its non-causal caveat.

  11. Version 54 Aug 2026, 23:41

    Moved the open-investigation status to the close of the story per house style; no new facts.

  12. Version 55 Aug 2026, 16:51

    Added DGCA probe and Air India cooperation, Times of India breakdown of 13 passengers and four crew hospitalised with five discharged, crew count, injury details, family's emergency-response allegation, Phuket origin, and passenger-count range; dropped the geographic reference paragraph.

  13. Version 44 Aug 2026, 23:41

    No new facts; wording of the lead and sourcing caveats tightened.

  14. Version 44 Aug 2026, 23:40

    Added headline and dek; specified Delhi as the location in the lead.

  15. Version 34 Aug 2026, 23:40

    Tightened the registration paragraph to make clear the tail number is tracking-derived and not an official identification.

  16. Version 34 Aug 2026, 23:28

    No new facts; added headline and dek, story text unchanged.

  17. Version 24 Aug 2026, 22:03

    Added headline and dek; tightened wording on the unconfirmed registration and the weather observation.

  18. Version 24 Aug 2026, 23:23

    Reordered to lead with the reported injuries and flight details; no new facts.

  19. Version 14 Aug 2026, 22:48

    First published.

  20. Version 14 Aug 2026, 20:33

    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.