Singapore Airlines jet catches fire, but all passengers safe
Posted June 26, 2016 7:00 am
SINGAPORE (AP) - Singapore Airlines said Monday that there were no injuries when a jetliner caught fire after the plane returned to Changi Airport because of an engine warning.
An airline statement said the Boeing 777-300ER was on its way to Milan when it turned back "following an engine oil warning message."
It said the aircraft's right engine caught fire after Flight SQ368 touched down more than four hours after takeoff.
"The fire was put out by airport emergency services and there were no injuries to the 222 passengers and 19 crew on board," it said.
The airline says the passengers were transferred to another aircraft that was to depart for Milan later Monday.
This image provided by Lee Bee Yee shows passengers disembarking a Singapore Airlines flight after an engine fire, at Changi International Airport in Singapore on Monday, June 27, 2016. A Singapore Airlines statement said the Boeing 777-300ER was on its way to Milan when it turned back "following an engine oil warning message." It says the aircraft's right engine caught fire after Flight SQ368 touched down more than four hours after takeoff. (Lee Bee Yee via AP) MANDATORY CREDIT
The Associated Press
This image provided by Lee Bee Yee shows the aftermath of an engine fire on a Singapore Airlines flight, at Changi International Airport on Monday, June 27, 2016. A Singapore Airlines statement said the Boeing 777-300ER was on its way to Milan when it turned back "following an engine oil warning message." It says the aircraft's right engine caught fire after Flight SQ368 touched down more than four hours after takeoff. (Lee Bee Yee via AP)
The Associated Press
Article Comments
Guidelines: Keep it civil and on topic; no profanity, vulgarity, slurs or personal attacks. People who harass others or joke about tragedies will be blocked.
If a comment violates these standards or our terms of service, click the "flag" link in the lower-right corner of the comment box. To find our more, read our FAQ.