Welcome to EverybodyWiki 😃 ! Nuvola apps kgpg.png Log in or ➕👤 create an account to improve, watchlist or create an article like a 🏭 company page or a 👨👩 bio (yours ?)...

Singapore Airlines Flight 368

From EverybodyWiki Bios & Wiki

Singapore Airlines Flight 368
Singapore Airlines Boeing 777-312 ER 9V-SWB MUC 2015 02.jpg
9V-SWB, the aircraft involved, pictured in 2015
Incident
Date27 June 2016 (2016-06-27)
SummaryEngine fire following oil leak
SiteSingapore Changi Airport, Changi, Singapore
1°21′52″N 103°59′29″E / 1.3644°N 103.9915°E / 1.3644; 103.9915Coordinates: 1°21′52″N 103°59′29″E / 1.3644°N 103.9915°E / 1.3644; 103.9915
Fatal error: The format of the coordinate could not be determined. Parsing failed.


Aircraft
Aircraft typeBoeing 777-312ER
OperatorSingapore Airlines
IATA flight No.SQ368
ICAO flight No.SIA368
Call signSingapore 368
Registration9V-SWB
Flight originSingapore Changi Airport, Singapore
DestinationMalpensa Airport, Milan, Italy
Occupants241
Passengers222
Crew19
Fatalities0
Injuries0
Survivors241 (all)

Singapore Airlines Flight 368 was a scheduled international passenger flight from Singapore Changi Airport to Milan–Malpensa Airport in Italy.[1] 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.[2]

Aircraft[edit]

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, equipped with two General Electric GE90-115B engines. At the time of the incident, the aircraft was nine years old, having been delivered new to Singapore Airlines on 5 November 2006.[3] It underwent major repairs for four months before returning to service on 12 November 2016.[citation needed]

Investigation[edit]

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.[4]

See also[edit]

  • British Airways Flight 2276
  • Korean Air Flight 2708
  • Emirates Flight 521

Notes[edit]

  1. The aircraft is a Boeing 777-300ER (Extended Range) variant. Boeing assigns a unique code for each company that buys its aircraft, which is applied as an infix to the model number at the time the aircraft is built, hence "777-312ER".

References[edit]

  1. "SQ368 Flight, Singapore Airlines, Singapore to Milan". www.flightr.net. Archived from the original on 1 November 2016. Retrieved 1 November 2016. Unknown parameter |url-status= ignored (help)
  2. Lee, Min Kok; Kaur, Karamjit (27 June 2016). "Singapore Airlines plane catches fire on Changi Airport runway; no injuries reported". The Straits Times. Retrieved 29 September 2019.
  3. "9V-SWB Aircraft Information". FlightRadar24. Retrieved 27 June 2016.
  4. "ASN Aircraft accident Boeing 777-312ER 9V-SWB Singapore-Changi International Airport (SIN)". Aviation Safety Network. Flight safety Foundation. Retrieved 2017-01-24.

External links[edit]


This article "Singapore Airlines Flight 368" is from Wikipedia. The list of its authors can be seen in its historical and/or the page Edithistory:Singapore Airlines Flight 368. Articles copied from Draft Namespace on Wikipedia could be seen on the Draft Namespace of Wikipedia and not main one.