24 Injured, Autopilot Failed, Pilot Drug-Tested: Inside Air India's AI2379 Scare

The aircraft was carrying 137 passengers — including three infants — and eight crew members: two pilots and six cabin crew. Injury counts differ slightly between outlets: The Aviation Herald, an independent incident-tracking site, put the figure at 17 injured, while Indian coverage citing AAIB-linked sources reported 20 passengers and four cabin crew — 24 in total. ZeroPress could not independently confirm which figure the AAIB will use in its final report and is flagging the discrepancy rather than picking one. Either way, the flight continued to Delhi and landed without further incident, but the injury toll and the technical picture that emerged in the following days turned what initially looked like a turbulence encounter into a more serious systems investigation.

Not just turbulence — an autopilot disconnect and a stall warning

What has kept AI2379 in the headlines is not the altitude excursion alone but what reportedly preceded it. Indian outlets including India TV News and Business Standard, citing details emerging from the AAIB's preliminary work, reported that the aircraft had experienced a string of technical issues during the flight before the altitude deviation — among them an autopilot mode disconnect. Soon after the co-pilot took manual control following the disconnect, the flight computer is reported to have generated a stall warning message.

That combination — an unexpected autopilot disconnection followed by a stall alert during manual handling — is a materially different scenario from a simple clear-air-turbulence jolt, and it explains why the AAIB escalated its classification of the event to a "serious incident" under India's civil aviation investigation rules, and why France's Bureau d'Enquêtes et d'Analyses (BEA) — the French investigative authority that participates in incidents involving Airbus-manufactured aircraft — joined the probe. Investigators are examining the flight data recorder, cockpit voice recorder, the aircraft's maintenance logs, and its onboard systems to establish whether a mechanical or software fault triggered the autopilot disconnect, or whether the sequence was a crew response to genuine atmospheric turbulence that happened to coincide with a system anomaly.

As of the most recent reporting, no single cause has been confirmed publicly, and the AAIB has not released a preliminary report. ZeroPress is treating the technical sequence — autopilot disconnect, stall warning, altitude excursion — as reported by AAIB-linked sources, pending the AAIB's own findings.

The pilot drug-test complication

A second thread has emerged alongside the technical investigation: the aircraft's pilot-in-command underwent the psychoactive substance screening that DGCA mandates after any serious incident, and the initial result reportedly required a confirmatory retest rather than returning a clean clearance outright. Coverage from VisaVerge and other outlets described the captain as facing this additional screening step, with the confirmatory test results still pending as of mid-August reporting.

It is important to be precise about what this does and doesn't mean. A screening result requiring confirmatory testing is a standard escalation step in India's post-incident testing protocol — it is not itself a finding of impairment, and DGCA's own procedures require the retest before any conclusion is drawn. Air India has not issued a detailed public statement attributing the incident to crew impairment, and no outlet ZeroPress reviewed has reported a confirmed positive result. This detail is included because it is part of the documented investigative record, not because it establishes a cause.

Why this incident cuts differently than routine turbulence reports

India sees clear-air turbulence encounters on its Southeast Asia routes with some regularity — the monsoon season and the convective weather over the Bay of Bengal make the Phuket-Delhi and similar corridors prone to sudden air-mass changes. What distinguishes AI2379 is the combination of an avionics anomaly with a physical altitude deviation and a double-digit injury count on a single narrow-body flight. A double-digit injury count — whether the 17 tallied by The Aviation Herald or the 24 reported in Indian coverage — is high for a turbulence-linked event out of India this year, and it places AI2379 alongside a small number of incidents that have prompted airlines and regulators globally to revisit seatbelt-sign discipline and pre-emptive turbulence avoidance procedures — without this event itself being framed as a verdict on either.

For Air India, the incident lands at a sensitive moment. The carrier has spent much of 2026 rebuilding its safety reputation and modernizing its narrow-body and widebody fleets under the Tata Group's ownership, while simultaneously managing route rationalization and new aircraft deliveries. A "serious incident" classification — one notch below a full accident investigation — keeps AI2379 firmly on the AAIB's active docket and means findings, when published, will carry regulatory weight for both the airline and, potentially, Airbus's A320 systems documentation.

What the AAIB investigation will need to establish

Investigators typically work through several parallel tracks in a case like this: recovering and analyzing flight data recorder parameters around the exact moment of the autopilot disconnect; cross-referencing cockpit voice recordings against the FDR timeline to establish what alerts the crew actually saw and how they responded; auditing VT-EXO's maintenance and defect-reporting history for any prior autopilot or flight-control anomalies; and correlating meteorological data for the flight's position at the time to determine whether genuine convective turbulence was present independent of the systems issue.

Because BEA is participating as the state-of-design representative for the Airbus airframe, any systemic finding — for instance, if investigators determine a software or sensor fault contributed to the autopilot disconnect — would likely also involve Airbus's own engineering teams and could carry implications beyond this single aircraft if a fleet-wide pattern is identified. Conversely, if the investigation concludes the sequence was driven by severe but undetected turbulence with the stall warning representing a correct system response to genuine aerodynamic conditions, the focus would shift toward operational procedures: seatbelt-sign timing, cabin crew securing protocols, and flight-path planning around known convective zones on the Phuket-Delhi corridor.

What to watch next

The AAIB has not published a timeline for its preliminary report, though Indian serious-incident investigations of this type have typically produced initial findings within one to three months in recent years. Key open questions include: the outcome of the captain's confirmatory drug screening; whether the FDR data shows a system fault or a turbulence-triggered stall protection response; and whether DGCA issues any interim safety directive to Air India's A320 fleet pending the full findings. Air India has continued to operate AI2379 and its broader Phuket network without a public grounding of the fleet type, suggesting regulators have not yet identified an immediate airworthiness concern requiring fleet-wide action — though that could change as the investigation progresses.

ZeroPress will continue to track official AAIB statements as they are released, given the number of unverified technical details currently circulating in Indian media ahead of any formal report.

Sources

• Accident: India A20N enroute on Aug 4th 2026, upset injures 17 people — The Aviation Herald
• AAIB Takes Over Probe Of Air India Turbulence Incident — Deccan Chronicle
• From hydraulic failures to autopilot glitch, Air India Phuket-Delhi flight had major issues before turbulence hit — India TV News
• Air India's plane suffered glitches, turbulence during Phuket-Delhi flight — Business Standard
• Air India AI2379 Pilot Drug Test & Turbulence Probe 2026 — VisaVerge