An escalating aviation safety crisis prompted Air India management to issue an emergency corporate directive enforcing immediate psychoactive substance screening for every pilot across its mainline operational roster and its low-cost subsidiary, Air India Express. The internal letter sent to all crew members acknowledged that while the airline maintained baseline compliance with regulations set by India’s Directorate General of Civil Aviation (DGCA), the severity of recent events required immediate, sweeping measures.

Testing protocols were deployed simultaneously across the airline's central training academy in Gurugram, as well as post-flight briefing centers and operational bases nationwide.

In a parallel security advisory, the Chief of Flight Safety for Air India Express initiated a voluntary self-declaration framework, encouraging aviators to report any personal reliance on, dependence on, or misuse of psychoactive substances [cite: text prompt]. The airline promised confidential processing of all disclosures, restricting file access strictly to the Head of Medical Services, the Chief Human Resource Officer, the Chief of Flight Safety, and relevant departmental heads [cite: text prompt]. This institutional mobilization followed toxicological confirmations that Captain Sudeep Vashistha, pilot-in-command of flight AI2379, had failed two consecutive drug tests after a mid-air emergency over the Bay of Bengal.

At the regulatory level, the Ministry of Civil Aviation ordered the Aircraft Accident Investigation Bureau (AAIB) to fast-track its formal inquiry, setting a strict thirty-day deadline for the submission of an interim report. The investigation received direct technical support from France’s Bureau of Enquiry and Analysis for Civil Aviation Safety (BEA) alongside airframe manufacturer Airbus. Senior government officials emphasized that, unlike the fatal crash of London-bound Air India flight AI171 off Ahmedabad fourteen months prior—where severe impact damage destroyed vital evidence—investigators in this instance possessed the intact Flight Data Recorder (FDR), Cockpit Voice Recorder (CVR), maintenance telemetry, and toxicological records. Concurrently, civil aviation authorities launched a broad review of national pilot testing frameworks, benchmarking Indian protocols against international jurisdictions to establish tougher statutory enforcement mechanisms.

August 11–12, 2026: The Leaked Telemetry: Hydraulic Faults and Corporate Messaging

The official narrative surrounding the incident shifted significantly when leaked maintenance records contradicted early airline press statements. On August 11, the Press Information Bureau (PIB) and Civil Aviation Ministry updated the official casualty toll, confirming that twenty-four individuals—twenty passengers and four cabin crew members—suffered physical injuries during the flight. Civil Aviation Minister Ram Mohan Naidu confirmed that two cabin crew members sustained severe spinal and neck trauma after being thrown against the aircraft structure.

Twenty-four hours later, leaked Centralised Fault Display System (CFDS) logs from the aircraft—an Airbus A320neo registered as VT-EXO—revealed a complex technical breakdown in the cockpit minutes before the drop. Maintenance reports generated at 11:14 AM IST upon arrival at Indira Gandhi International Airport in Delhi documented eleven system alerts within a three-minute window, beginning at 9:32 AM IST.

Aeronautical engineers analyzing the CFDS sequence noted that low-pressure warnings toggled rapidly across all three independent hydraulic circuits (Green, Blue, and Yellow) alongside low reservoir level alarms. Technical evaluation indicates that rather than a total mechanical breakdown, rapid negative-G forces caused hydraulic fluid inside the supply reservoirs to shift away from sensor probes, generating transient low-level and low-pressure alerts. However, the logs confirmed that the primary autopilot disengaged automatically during this event, leaving manual control to the First Officer.

This technical exposure highlighted discrepancies in Air India’s public communications. Immediately following the flight's arrival on August 4, the airline issued press statements attributing the injuries solely to "severe clear-air turbulence" (CAT). Hours later, corporate communications revised the statement to scrub references to turbulence entirely, omitting any mention of the multiple cockpit hydraulic failures or flight control alerts. This discrepancy prompted senior ministry officials to summon Air India executive leadership to explain the omission of mechanical telemetry in initial public reports.

August 5–10, 2026: Toxicological Confirmation, Fatigue, and Cockpit Interrogations

Behind closed doors at the Aircraft Accident Investigation Bureau, toxicological evaluations of the flight crew produced critical evidence. Initial post-landing urine samples provided by Captain Sudeep Vashistha returned a "non-negative" result for psychoactive compounds, triggering mandatory secondary testing at a certified laboratory. Subsequent mass spectrometry analysis confirmed the presence of cannabis metabolites, establishing a double-positive result for marijuana.

Under interrogation by AAIB investigators, Vashistha offered details regarding his physical state and activities preceding the flight. He admitted to struggling with chronic sleep difficulty stemming from personal circumstances and acknowledged taking prescription medication supplied by his family doctor. Crucially, regulatory records showed no indication that Vashistha had declared this prescription medication to Air India’s medical department, an omission violating DGCA flight safety regulations.

Vashistha argued that crew scheduling practices contributed to his fatigue. While legally within flight-duty time limitations, his roster compressed available daytime rest periods below what was necessary for recovery. His operational sequence required reporting for duty at 12:10 AM IST, demanding preparation before 10:00 PM, which disrupted his natural circadian rhythm. Following his initial leg into Thailand, post-flight clearance administrative tasks and transportation to his hotel consumed over two hours, further reducing his rest window. For the return flight, Vashistha was required to wake at 3:00 AM IST.

During his layover in Thailand, unable to rest, Vashistha walked around Phuket in an effort to induce sleep. On the return flight to Delhi, he left his station to sleep for approximately 30 to 35 minutes. Upon returning to the flight deck, he remained out of his seat, standing behind the First Officer to discuss the air conditioning system when the sudden drop occurred.

August 4, 2026: Mid-Air PR Management, Inappropriate Behavior, and Landing in Delhi

In the immediate aftermath of the altitude loss, scenes inside the cabin were documented by passenger mobile devices. Restabilized at 36,000 feet, Captain Vashistha exited the flight deck and entered the passenger cabin, where cabin crew members were attempting to assist injured travellers.

Eyewitness accounts and video recordings captured the commander's erratic behavior. Visible physical distress and unsteadiness marked his movements as he walked down the aisle. Rather than focusing purely on emergency first aid coordination, Vashistha addressed passengers directly, repeatedly instructing them to cease filming: "Don’t take photos. Don’t record videos. Don’t post this on social media." [cite: text prompt, 6, 8, 11, 14].

Passengers recorded the commander as he offered disjointed explanations regarding atmospheric air currents and crew injuries, appealing to the cabin "for the sake of humanity and our mutual futures" [cite: text prompt]. Eyewitnesses noted that amid medical emergencies in the cabin, the commander appeared focused on managing public perception and social media coverage [cite: text prompt].

When flight AI2379 landed at Indira Gandhi International Airport at 11:14 AM IST, ground medical crews and airport security personnel met the aircraft. Observers on the tarmac and gateway reported that Captain Vashistha was unsteady on his feet and required physical assistance to navigate the jet bridge. Investigating officers subsequently accompanied him to the airport medical facility, where he required physical support while providing the urine sample that initiated his double-positive drug test sequence.

August 4, 2026 (09:32–09:35 AM IST): The Negative-G Plunge Over Odisha

The flight had proceeded without incident across the Bay of Bengal, carrying 137 passengers—including three infants—alongside eight crew members. Cruising at 36,160 feet over the Odisha coastline, the aircraft entered a sudden vertical altitude excursion. Flightradar24 telemetry logged the anomaly at precisely 9:33 AM IST, recording a descent of approximately 360 feet down to 35,800 feet before control was re-established.

Inside the cabin, the rapid descent created a negative-G environment. Unrestrained passengers and cabin crew members were thrown upward, striking overhead storage lockers and structural ceiling panels. Loose items, serving carts, and personal baggage shifted violently throughout the aisle. Overhead interior panels cracked, and oxygen masks deployed in several sectors due to physical impacts.

Passengers reported sudden screams as people were tossed from their seats. Individuals who were asleep without fastened seatbelts suffered blunt force head trauma, back injuries, and neck hyperextension. Rapid cabin pressure variations caused ear barotrauma, resulting in ruptured eardrums for several passengers. Among the crew, two flight attendants attending to the cabin sustained spinal trauma near the tailbone and neck.

Inside the cockpit, Captain Vashistha was out of his seat, standing directly behind the First Officer while discussing thermal air conditioning parameters. When the negative-G drop occurred, Vashistha was thrown onto the cockpit floor. A flight attendant occupying the cockpit observer seat assisted the captain up. The First Officer maintained control at the sidestick, managing the manual flying phase while primary autopilot systems disconnected and multiple hydraulic sensors alarmed across the primary instrument displays.

August 3–4, 2026: The Phuket Layover and Operational Antecedents

The operational issues surrounding Flight 2379 began prior to departure during the layover in Thailand. Captain Vashistha arrived in Phuket experiencing fatigue caused by roster timing and personal circumstances.

During his layover at the Phuket crew hotel, Vashistha found himself unable to achieve restful sleep. Attempting to manage his insomnia, he walked around the local area, hoping physical exertion would help him rest. Unable to rest, he relied on an undisclosed prescription sleep aid provided by his family doctor.

When Vashistha reported for pre-flight operations at Phuket International Airport early on August 4, no formal pre-flight substance screening was conducted due to cross-border operational protocols, which rely primarily on self-declaration and random sampling at foreign outstations. He boarded the Airbus A320neo (VT-EXO) alongside the First Officer and six cabin crew members. One hundred and thirty-seven passengers boarded shortly after, unaware that the captain was suffering from sleep deprivation, operating on undeclared prescription medication, and carrying psychoactive cannabis metabolites in his system.

Systemic Risk Synthesis and Regulatory Outlook

The investigation into Air India Flight 2379 highlights critical gaps across pilot wellness monitoring, duty-time scheduling, and corporate emergency communications. The convergence of crew impairment, undeclared medication usage, and technical hydraulic anomalies demonstrates how multiple safety vulnerabilities can align to compromise flight safety.

To address these vulnerabilities, aviation regulatory bodies and airline operators are evaluating several critical safety measures:

• Outstation Psychoactive Screening: Expanding random drug and alcohol testing frameworks to include international layover destinations, ensuring crew members are screened regardless of departure point.

• Prescription Disclosure Systems: Establishing mandatory digital reporting platforms for flight crews to log any prescribed medications, backed by clear medical clearance protocols from aviation medicine specialists before operational duty.

• Fatigue Risk Management System (FRMS) Reform: Re-evaluating crew rostering practices to address duty compression, ensuring daytime rest periods account for circadian disruption during night-to-day transitions.

• Transparent Emergency Telemetry Reporting: Implementing strict protocols governing corporate communications during operational incidents, preventing the omission of maintenance alerts and mechanical data in public disclosures.

• Cabin Safety Compliance Enforcement: Reinforcing passenger compliance policies regarding continuous seatbelt usage during cruise phases, mitigating injury risks associated with clear-air turbulence and sudden vertical flight path deviations.