Everything about the SIA plane catching fire in 60 seconds

While you were sleeping soundly this morning, an SIA plane caught fire and did an emergency landing at Changi Airport.

Flight SQ368 was scheduled to leave Singapore for Milan at around 2:05 a.m. this morning (27 June 2016). The plane, a Boeing 777-300ER, departed from Changi Airport Terminal 3 but after flying for about three hours, the pilot informed the passengers that there was a “leak” and they had to return back to Changi Airport as there would not be enough fuel for the journey.

At around 6:45 a.m., the plane was back in Changi Airport for an emergency landing, and shortly after that, the plane’s right wing caught fire.

Passengers were then ushered to disembark through the stairs and went back to the terminal via bus. There was a total of 222 passengers and 19 crew. No one was injured, and the fire was put out within ten minutes.

Investigations are still ongoing on what caused the leak, the engine failure or the fire.

According to a passenger who owned an online store, the passengers were calm and did not panic. When the plane was in the air, there was a faint smell of gasoline. The crew was professional as well, and SIA has apologized for the incident.

The affected passengers will be taken to their destination with a new aircraft and crew at 9:30 a.m.

The Boeing 777-300ER has one of the highest fuel capacities, with it being able to fly 14,500 km. Singapore Airlines own a total of 27 such aircraft, with 19 of them being ordered in 2004 and its first service in late 2006.

The latest incident that involves a Boeing 777-300 is from Korean Air last month. On 27 May 2016, the plane was accelerating for its take-off when there were strange vibrations and smoke emitting from the engine, leading the pilot to stop. Soon, the engine caught fire. Nine people were injured in the incident.

It was later revealed that a turbine disk, an important, large and expensive rotating component of the engine, was fractured.

This article was first published on goodyfeed.com