SQ236 passengers reach Singapore more than nine hours late after cabin smoke diversion

When we first reported the diversion on November 11, Singapore Airlines had only promised a relief flight. Nothing yet showed that anyone had reached Singapore. That is now answered, with one caveat. The departure and arrival times come from a single commercial tracker, FlightStats. The airline has not confirmed them, and it has not said whether everyone from the diverted jet was on that flight.⁠19

The parts we reported on November 11 still stand. SQ236 left Brisbane for Singapore on Wednesday afternoon. The Straits Times put the departure at 2:32pm local time. Lianhe Zaobao, citing FlightAware data, gave 2:35pm. The three minutes may be the difference between a gate time and a takeoff time, but no source settles it. Smoke was detected in the cabin and the crew diverted. A Singapore Airlines spokesperson said the aircraft landed at Rockhampton Airport at 4:09pm local time, about an hour and a half after leaving Brisbane, and called the landing uneventful.⁠1⁠12⁠2

"Uneventful" describes the landing, not the flight. Passengers described smoke filling the cabin and the aircraft's screens going black. Paramedics and fire crews were called to the airport. The airline said all customers disembarked normally, and no injuries were reported. ABC Queensland carried a photo caption saying a group of schoolchildren on an excursion were among the passengers. It did not give their number, school or ages. The passenger accounts tell us what people went through. They do not show that there was a fire, and they do not identify where the smoke came from.⁠1⁠2⁠3⁠20

Aviation trackers have filled in some of the technical picture, though only they report these details. Airportia's incident entry says the crew decided to divert while cruising at flight level 360, about 36,000 feet, roughly 100 nautical miles from Rockhampton, and landed on runway 33. PilotinQ says the jet was on the ground about 20 minutes after turning back. AeroInside and PilotinQ identify the aircraft as an Airbus A350-900, registration 9V-SHA. FlightStats confirms the type but lists no registration. Neither Singapore Airlines nor any regulator has confirmed the registration. The figure of more than 300 passengers comes from The Australian, as cited by Lianhe Zaobao. No exact passenger count or crew figure has been published.⁠17⁠20⁠14⁠19⁠12

After the landing came the wait. Passengers were held in an airport lounge while the airline arranged refreshments and a relief flight, and rebooked onward travel where needed. The Straits Times reported that bad weather in Brisbane could affect when the relief flight left. FlightStats lists an original scheduled departure from Rockhampton of 5:05pm local time. That timetable slipped by more than seven hours.⁠1⁠2⁠19

The airline's own estimates also slipped. On Wednesday evening, The Straits Times reported that Singapore Airlines' flight status website showed a departure from Rockhampton around midnight and an arrival at Changi Terminal 2 at 5:05am. CNA, citing the airline's flight status tracker, reported a midnight departure and an arrival at 5:23am Singapore time. These were successive estimates, not conflicting accounts, and the actual arrival came later than both.⁠1⁠2

Do the arithmetic and the evening looks like this. From touchdown at 4:09pm to pushback at 12:27am, the passengers were on the ground in Rockhampton for more than eight hours. That is longer than the Rockhampton-to-Changi flight itself. For travellers with connections beyond Singapore, a delay of more than nine hours can mean missing the onward flight. Whether every one of those connections was rebooked has not been reported.⁠19

One practical question is still unanswered: what aircraft took them home. The tracker kept the SQ236 flight number and lists an Airbus A350-900, but it gives no registration. So we cannot say whether Singapore Airlines flew in a replacement jet or cleared the original aircraft to carry on. If it was the original aircraft, that would suggest a quick fault assessment that the airline has not described. If it was a replacement, the inspection of 9V-SHA, if that is the diverted jet, would still be under way. Neither possibility should be assumed.⁠19

Singapore Airlines says it is investigating the cause of the smoke. The only explanation so far is indirect. The Straits Times reported a message the airline sent to affected passengers, shared on X by one of them, which put the diversion down to a technical issue affecting the aircraft's safety monitoring systems. The airline has not said publicly which systems, how they were affected, or whether that issue had anything to do with the smoke. Smoke in the cabin is a physical event. A monitoring fault could have caused the alarm, been caused by the same problem, or been unrelated. Without more detail from the airline, readers should treat the message as describing the diversion, not diagnosing it. No defect has been confirmed.⁠1⁠2⁠20

Regulators have said nothing in public. We found no announcement that the Australian Transport Safety Bureau or Singapore's Transport Safety Investigation Bureau has opened an investigation or logged an occurrence for SQ236. The ATSB's occurrence database says new occurrences can take some weeks to verify and add, so the lack of a listing a day after the incident tells us little. A formal review could still come. For now, the only investigation anyone has announced is the airline's own, and that is not an independent safety investigation. We also found no reports of earlier Singapore Airlines smoke or fumes diversions in Australia that would point to a pattern. That is a gap in what we could find, not evidence that none happened.⁠23