The Singapore Airlines Airbus A330-300 en route from Singapore Dhaka with 105 passengers and 12 crew aboard diverted to Bangkok when they got an internal flight warning. There were no injuries.
In spite of the cargo fire suppression system, there was a burning smell and a fire.
The plane made a safe landing in Bangkok. The plane taxied to the gate, and passengers disembarked and were provided hotel accommodations, meals and transferred to another airline.
An investigation is underway.
Singapore Airlines’ spokesman, Nicholas Ionides said that “Flight SQ446 operating between Singapore and Dhaka diverted to Bangkok as a result of indications of smoke from the aircraft’s rear cargo hold.”
When Thai authorities clear the Airbus, it will be flown back to Singapore.
In George’s Point of View
It has been well documented that Airbus and Boeing are taking different paths regarding their approach on batteries.
But still, it is one of my least favorite things to read (especially while I’m halfway to Singapore) that there has been yet another cargo fire at all, regardless of what kind of plane it is on.
At least I had time to jot down some thoughts.
I hope that the media shines as bright a light on this airbus cargo fire as it has recently on the Dreamliner battery situation. Sure, the Dreamliner is developing new technology and Boeing is responsible for going the distance to keep new developments safe. The Dreamliner battery issue is new. But the fact that Boeing is developing new technologies and new solutions does not provide Airbus and an established plane like a A330-300 a free ticket when it comes to combustion.
Hopefully Airbus is paying attention to all problems and not getting too cocky. It should remember and respect that a plane is still an air-filled bubble hundreds of feet in the air. Until people develop their own wings, random combustion situations like cargo fires on an Airbus A330 are just as potentially hazardous situation–if not more so–than any battery incident that actually occurred on the ground.
Let us please see a fix for this problem.