Singapore Airlines Flight 368
9V-SWB, the aircraft involved, pictured in 2015 | |
Serious Incident summary | |
---|---|
Date | 27 June 2016 |
Summary | Aircraft fire following oil leak |
Site |
Singapore Changi Airport, Changi, Singapore 1°21′52″N 103°59′29″E / 1.3644°N 103.9915°E |
Passengers | 222[1] |
Crew | 19[1] |
Fatalities | 0 |
Injuries (non-fatal) | 0 |
Survivors | 241 (all) |
Aircraft type | Boeing 777-312ER[2][1] |
Operator | Singapore Airlines |
Registration | 9V-SWB |
Flight origin | Singapore Changi Airport, Changi, Singapore |
Destination | Milan–Malpensa Airport, Ferno, Italy |
Singapore Airlines Flight 368 (SQ368) was a scheduled international passenger flight from Singapore Changi Airport to Milan–Malpensa Airport in Italy.[3] On 27 June 2016, the Boeing 777-300ER operating the flight to Italy turned back to Singapore after an engine oil warning. While landing at Changi Airport, the plane's right engine caught fire. All passengers successfully evacuated the aircraft. There were no injuries among the 241 passengers and crew involved.
Aircraft
The aircraft involved in the incident was a Boeing 777-312ER,[note 1] registered as 9V-SWB, bearing the manufacturing serial number (MSN) of 33377. At the time of the incident, the aircraft was nine years old, having been delivered new to Singapore Airlines in November 2006.[4]
Flight and engine failure
The flight took off at 2:05 SST on 27 June 2016. When the 777 was about two hours into the flight, the right (#2) engine, a General Electric GE90-115B, developed an oil leak, according to the captain.[5] The crew decided to return the aircraft to Changi Airport where it touched down safely at around 6:50 SST.[6][1] As the aircraft was slowing down on the runway, a spark was seen, and the right engine caught fire, eventually leading to the right wing becoming engulfed in flames. A Civil Aviation Authority of Singapore (CAAS) spokesman said that airport fire services extinguished the fire in five minutes.[5] There were no injuries, but the aircraft sustained serious fire damage to the right wing.[1][7][8]
Investigation
The Air Accident Investigation Bureau of Singapore (AAIB), which is responsible for investigating aviation accidents in Singapore, opened an investigation into the occurrence. Their investigation found that the right engine's oil system was contaminated with fuel due to a crack in the engine’s main fuel oil heat exchanger (MFOHE). The engine's manufacturer General Electric had already identified that certain MFOHEs were cracking and instructed that they be removed from the engines and inspected then repaired if necessary. The Service Bulletin issued by General Electric detailing the inspection and repair recommended that the inspection of the MFOHE be done the next time the engine was sent to a workshop for maintenance. In the case of the engine that failed, the most recent time it had gone to a workshop was March 2014, several months before the bulletin had been issued.[9]
See also
Notes
References
- 1 2 3 4 5 Devlin, Peter (27 June 2016). "Terrified passengers film a Singapore Airlines plane bursting into flames on the runway after making an emergency landing". Daily Mail. Retrieved 27 June 2016.
- ↑ "Flight history for aircraft - 9V-SWB". FlightRadar24. Retrieved 27 June 2016.
- ↑ "SQ368 Flight, Singapore Airlines, Singapore to Milan". www.flightr.net. Retrieved 2016-11-01.
- ↑ "9V-SWB Aircraft Information". FlightRadar24. Retrieved 27 June 2016.
- 1 2 "Singapore Airlines plane catches fire on Changi Airport runway; no injuries reported". Straits Times. 2016-06-27. Retrieved 2016-06-29.
- ↑ "SIA flight catches fire while making emergency landing in Singapore". Channel News Asia. Retrieved 27 June 2016.
- ↑ "Accident: Singapore B773 enroute on Jun 27th 2016, engine oil leak". The Aviation Herald. 27 June 2016. Retrieved 27 June 2016.
- ↑ Waldron, Greg (27 June 2016). "Fire damage apparent on SIA 777 wing". Flight Global. Retrieved 27 June 2016.
- ↑ "ASN Aircraft accident Boeing 777-312ER 9V-SWB Singapore-Changi International Airport (SIN)". Aviation Safety Network. Flight safety Foundation. Retrieved 2017-01-24.