SpiceJet Boeing 737 Declares Mayday After Second Diversion Due to Blocked Runway

Casualties unknown • DELHI, IN

A SpiceJet Boeing 737 was forced to perform an emergency landing in Delhi after a runway blockage at its alternate airport left the crew with critically low fuel.

What happened

On January 5, 2014, a SpiceJet Boeing 737, registration VT-SGU, was operating a scheduled flight from Goa to Delhi. As the aircraft approached Delhi, heavy fog had significantly reduced visibility, with runway visual range (RVR) dropping to 50 meters. Due to the deteriorating conditions and the aircraft's fuel state approaching minimum diversion levels, the pilot decided to divert to Jaipur.

Upon approaching Jaipur, the crew discovered that the runway was blocked by another aircraft that had sustained substantial damage during a landing attempt. This blockage forced the crew to initiate a missed approach at 3,000 feet. With fuel levels dropping rapidly, the pilot exercised emergency authority, declared a MAYDAY due to low fuel, and elected to return to Delhi. The aircraft successfully performed a dual-channel auto-landing at Delhi, touching down with only 400 kg of fuel remaining.

The investigation

AAIB India examined the sequence of events, focusing on the meteorological conditions, fuel management, and crew qualifications. The investigation reviewed the flight recorder data and the weather reports for Delhi, Jaipur, and Lucknow. Investigators also looked into the airline's 'Fog Plan' and the suitability of the chosen alternate airport during the period of low visibility.

Findings

  • The primary cause of the emergency landing was the necessity of a second diversion caused by the runway blockage at the alternate airport.
  • The crew's decision to divert to Jaipur instead of Lucknow was a contributing factor, as Lucknow offered more stable weather conditions and higher visibility.
  • There was a discrepancy in crew qualification; while the airline's Fog Plan required CAT IIIA qualified crews for late-evening arrivals during fog season, the pilot in command was only CAT II qualified.
  • The investigation noted a lack of operational oversight and insufficient ground support to assist the flight during the high-stress diversion sequence.
  • The successful outcome was attributed to the pilot's timely initial diversion from Delhi and the decision to utilize the aircraft's automated landing systems.

Probable cause

The emergency landing was caused by the requirement to perform a second diversion following a runway blockage at the alternate airport, compounded by a lack of operational oversight and the selection of an alternate with deteriorating weather.

Frequently asked questions

What happened in the 2014-01-05 SPICEJET B737 accident near DELHI, IN?

A SpiceJet Boeing 737 was forced to perform an emergency landing in Delhi after a runway blockage at its alternate airport left the crew with critically low fuel.

What aircraft was involved and where did it happen?

The accident on 2014-01-05 involved a SPICEJET B737, registration VT-SGU, at DELHI, IN.

What was the probable cause of the accident?

The emergency landing was caused by the requirement to perform a second diversion following a runway blockage at the alternate airport, compounded by a lack of operational oversight and the selection of an alternate with deteriorating weather.

Loading the flight search…