History of Flight
On 5 January 2014, a SpiceJet Boeing 737 aircraft (registration VT-SGU) was scheduled to operate flights SG-255/256 between Delhi and Goa. The flight crew consisted of an ATPL-licensed captain (CAT II qualified) and a CPL-licensed first officer (CAT IIIA qualified). The aircraft was certified for CAT IIIA operations.
The flight departed Goa at 1230 UTC with 9.5 tonnes of fuel on board, including 500 kg for holding at destination. As the aircraft approached Delhi, it was instructed to reduce speed and was placed 13th in the landing sequence. It was asked to perform two orbits and then descended to 7000 ft.
According to the pilot in command (PIC), when the aircraft was 50 NM from Delhi, it had about 700 kg of extra fuel. The ATIS reported visibility of 150 meters and RVR for runway 28 was 1150 m/950 m/550 m. Later, the rollout RVR for runway 28 dropped to 50 m. The PIC decided to hold at 7000 ft, expecting improvement. After holding for about 26 minutes, the fuel quantity approached minimum diversion fuel (MDF). The PIC checked Jaipur weather: visibility 900 m reducing to 800 m with RVR 1500 m.
As rollout RVR for runway 28 did not improve and RVR for runway 29 was below minima, the PIC decided to divert to Jaipur. The fuel onboard was 3100 kg, and the required minimum diversion fuel to Jaipur was 2573 kg. Many aircraft were diverting simultaneously, causing frequency congestion.
While descending into Jaipur, Jaipur ATC informed that visibility had dropped to 50 m with RVR 200 m for runway 27. The PIC stated commitment to land due to fuel. The flight crew decided to perform a dual-channel autoland. Two aircraft were ahead: one executed a go-around and diverted to Ahmedabad; another (Air India) performed a manual landing in below-minima conditions and met with an accident, blocking the runway. Jaipur ATC and the Air India flight crew confirmed the runway was blocked. SG-256 initiated a missed approach at 3000 ft; fuel onboard was 1715 kg.
The PIC exercised emergency authority and decided to return to Delhi regardless of reported visibility/RVR. The aircraft contacted Delhi ATC, declared MAYDAY due to fuel, and requested straight and short vector for ILS runway 28. During the ILS approach, tower reported RVR for runway 28 as 375 m/900 m/50 m. A dual-channel autoland was performed. Fuel at touchdown was 400 kg. The aircraft vacated the runway via taxiway D1 with a follow-me vehicle escort. No damage to the aircraft or injury occurred. The MAYDAY was cancelled.
Injuries to Persons
No fatalities, serious injuries, or minor injuries were reported. The crew (6) and passengers (176) were all without injuries.
Damage to Aircraft
None. The aircraft carried out a safe emergency landing after declaring MAYDAY due to fuel.
Personnel Information
The captain held an ATPL with 6410 total hours (4512 as PIC, 2003 on type). The first officer held a CPL with 1996 total hours (1743 as FO on B-737, no PIC on type).
Aircraft Information
The aircraft was a Boeing 737 manufactured in May 2011, with MSN 37366. It had valid Certificate of Registration and Certificate of Airworthiness. As of 5 January 2014, the aircraft had 9714:29 hours time since new and 6512 cycles. It was powered by two CFM56-7B24 engines. No maintenance actions were pending.
After the incident, due to low fuel messages in tanks 1 and 2, maintenance actions included fuel boost pump priming (2000 kg uplifted per tank), fuel pump functional checks, and inspection/replacement of case drain filters. All checks were satisfactory.
Meteorological Information
Relevant METARs for Delhi (5 Jan 2014) showed visibility dropping from 150 m to 0 m, with RVR values varying. For Jaipur, METARs indicated visibility dropping from 900 m to 50 m, with RVR for runway 27 ranging from 1500 m to 125 m. The TAF for Delhi forecast visibility of 400 m, becoming 200 m between 1500-1600 UTC. Alternate aerodromes (Lucknow and Jaipur) had forecast visibility of 2000 m.
Analysis
The analysis in the report examined airworthiness, flight crew actions, flight data recorder readouts, fuel position, communications, fog plan, and weather issues. It noted that the aircraft was serviceable and the crew were qualified. The SSFDR data showed fuel at various stages. The CVR data indicated crew coordination. The fog plan and IMD issues were discussed, as well as reasons for diversions to Jaipur.
Conclusions
Findings included that the flight crew were qualified, the aircraft was airworthy, and the diversion decision was based on fuel and weather. The probable cause was identified.
Probable Cause
The cause of the serious incident is company's inadequate contingency planning for low visibility operation at Delhi wherein Captain of flight SG256 took a conscious decision to land at Jaipur which was below minima and ultimately had to divert to Delhi.
Safety Recommendations
Safety recommendations were issued by the investigation board, but specific details are not included in this article.