Air India AI2379: Alarming 300-Foot Drop Sparks Safety Questions

Two separate Air India incidents have put the airline’s operational safety procedures under renewed scrutiny. One involved an unexpected 300-foot altitude drop on flight AI2379 from Phuket to New Delhi, while another saw AI2335 from Bangkok to New Delhi halted near the runway after the cockpit crew detected a technical fault.

The AI2379 incident has drawn particular attention after the pilot-in-command reportedly tested positive for marijuana in a confirmatory laboratory test. Both pilots were subsequently grounded, with investigations by the Aircraft Accident Investigation Bureau (AAIB) and the Directorate General of Civil Aviation (DGCA) underway.

Separately, AI2335, carrying more than 250 passengers, was stopped just before takeoff after the crew detected a technical problem. The flight was cancelled and passengers eventually reached Delhi around 24 hours later.

The two incidents are not known to be connected. They involve different circumstances—one occurring during flight and the other before takeoff. Yet together, they raise an important question for Air India: how effectively are its safety systems detecting, managing and investigating unexpected operational problems?

AI2379: 300-Foot Altitude Drop and Pilot Test Result

Air India flight AI2379 was operating from Phuket, Thailand, to New Delhi on August 4 when the aircraft reportedly experienced a sudden altitude drop of approximately 300 feet. An unexpected change in altitude can understandably alarm passengers. However, the figure itself does not establish how serious the event was. Commercial aircraft routinely operate through changing atmospheric conditions, and temporary altitude variations can occur because of turbulence, wind changes or other operational factors. The crucial issue is what caused the reported descent and how quickly it happened.

Modern passenger aircraft continuously monitor parameters such as altitude, vertical speed, airspeed and aircraft position. Flight-data records, cockpit information, air-traffic-control communications and weather data can therefore help investigators reconstruct what happened. The incident has become more significant because of the reported positive marijuana test involving the pilot-in-command.

The pilot tested positive for marijuana in a confirmatory laboratory test following the incident. Both pilots were grounded, while the AAIB and DGCA began investigations. The ongoing AAIB and DGCA investigations will be important in determining what happened inside the aircraft and whether any operational, medical, technical or procedural issues contributed to the incident.

AI2379 at a Glance

Detail	Information
Flight	Air India AI2379
Route	Phuket, Thailand – New Delhi
Incident date	August 4
Reported event	Sudden 300-foot altitude drop
Pilot test	Reportedly positive for marijuana in confirmatory laboratory testing
Crew action	Both pilots reportedly grounded
Investigations	AAIB and DGCA
Cause of altitude drop	Under investigation

The distinction between an unusual flight event and its possible cause is particularly important in aviation reporting. Until investigators publish their findings, it would be premature to describe the altitude drop as a result of pilot impairment.

AI2335: Bangkok–Delhi Flight Halted Before Takeoff

The second incident involved Air India flight AI2335, which was scheduled to fly from Bangkok to New Delhi. Unlike AI2379, the problem occurred before the aircraft became airborne. According to the details provided, the cockpit crew detected a technical fault while the aircraft was near the runway on Thursday evening. The pilot cancelled the departure and the aircraft was brought to a halt using emergency brakes.

More than 250 passengers were on board. The decision to stop the aircraft before takeoff meant that the technical problem could be assessed without exposing passengers to the risks associated with taking an aircraft into the air with a suspected fault. For passengers, however, the decision resulted in a major disruption. The flight was cancelled, and travellers were eventually brought to Delhi on Friday evening—approximately 24 hours behind schedule.

The precise nature of the technical fault has not been established in the information currently available. It is therefore important not to speculate about which aircraft system was affected. Technical problems can involve numerous systems, and only a proper maintenance inspection can establish the cause. From an aviation-safety perspective, however, the sequence is significant: the crew detected an abnormality, the flight was cancelled and the aircraft did not proceed with the scheduled departure.

What These Two Incidents Mean for Air India’s Safety

The AI2379 and AI2335 incidents demonstrate two very different sides of airline safety. In the case of AI2335, the issue was detected on the ground. The cockpit crew identified a technical problem and the flight was stopped before takeoff. In AI2379, the reported abnormality occurred after the aircraft was already airborne. The situation therefore required the crew and aircraft systems to manage an unexpected change during flight, followed by a regulatory examination.

The reported marijuana test involving the AI2379 pilot adds another dimension to the case. Crew fitness is a fundamental part of aviation safety, and airlines and regulators maintain strict standards concerning alcohol, drugs and medical fitness. At the same time, a positive test should not be turned into a conclusion about the cause of an aviation incident without supporting evidence.

The Air India AI2335 incident similarly highlights the importance of maintenance and technical checks. A technical fault discovered before takeoff may cause significant passenger disruption, but the alternative—operating an aircraft with an unresolved safety issue—could carry far greater consequences. These incidents also underline why aviation safety cannot be measured simply by whether a flight arrived on time.

---