Six Bursts of Flame Over Queenstown: Inside Qantas QF122's Engine Diversion — and the Bird-Strike Theory That Didn't Hold

Rajkumar Agarwal6 September 20266 min read2 viewsSafety & Regulation
Six Bursts of Flame Over Queenstown: Inside Qantas QF122's Engine Diversion — and the Bird-Strike Theory That Didn't Hold

Passengers on a Sydney-bound Qantas flight out of Queenstown watched flames erupt from the aircraft's left engine not once but repeatedly — witnesses on the ground counted six or seven distinct bursts, accompanied by loud bangs some likened to gunshots — before the crew turned the Boeing 737-800 back over the South Island and diverted to Christchurch. All roughly 160 people on board landed safely. What has proven harder to pin down in the hours since is why it happened, after New Zealand's own civil aviation regulator offered an explanation and then retracted it.

Flight QF122 departed Queenstown Airport on the afternoon of Saturday, September 5, roughly 40 minutes behind its scheduled 3:25pm departure, bound nonstop for Sydney. Shortly after rotation, passengers and observers on the ground reported seeing flames coming from the left engine of the twin-engine jet. The crew declared an emergency, leveled off, and worked the aircraft back to Christchurch rather than continuing toward New Zealand's alpine terrain surrounding Queenstown or pressing on across the Tasman Sea. The flight landed at Christchurch roughly 50 minutes after the engine event was first noticed, with emergency vehicles positioned on the runway as a precaution. No injuries were reported among passengers or crew.

A Bird Strike Theory, Walked Back

In the immediate aftermath, New Zealand's Civil Aviation Authority (CAA) attributed the engine issue to a bird strike — a common and generally well-understood category of event in which wildlife is ingested into an engine during takeoff or climb, sometimes causing visible flame as unburned fuel or debris passes through. Bird strikes are frequent enough in commercial aviation that most produce no more than a maintenance inspection.

But the CAA subsequently revised its position, saying only that the cause of the engine event remained under investigation — without reaffirming the bird-strike explanation. Qantas has not publicly detailed a cause, and no formal investigation finding has been released. That gap between an initial public explanation and a walked-back one is itself notable: it means the actual mechanical trigger — whether foreign object ingestion, a compressor or turbine fault, a fuel system issue, or something else — has not been independently confirmed as of this writing. Readers should treat the bird-strike explanation as unconfirmed rather than dismissed; both possibilities remain open pending formal review.

Under ICAO Annex 13, the state where an aviation occurrence takes place — in this case New Zealand — is normally responsible for leading or coordinating an investigation, particularly where a foreign carrier's aircraft is involved and there was potential for serious harm. Whether this event triggers a formal ATSB (Australian Transport Safety Bureau) or New Zealand investigation process, given the aircraft's Australian operator and the flight's international routing between two Queenstown and Sydney, was not confirmed in available reporting at time of writing.

How a diversion decision unfolds after an in-flight engine event
How a diversion decision unfolds after an in-flight engine event

Why the Diversion, Not a Return to Queenstown

Queenstown Airport sits in a narrow alpine valley ringed by terrain that constrains approach and departure paths more tightly than most commercial airports — a geography that shapes go-around and diversion planning for every crew that operates there. Rather than attempt an immediate return to Queenstown, the QF122 crew continued toward Christchurch, New Zealand's larger South Island gateway with longer runways, more extensive emergency response capacity, and approach paths less constrained by mountainous terrain. That decision — continuing past the departure airport to a better-equipped field roughly 50 minutes' flying time away — is consistent with standard airline procedure for weighing runway suitability, fire and rescue capability, and terrain against the urgency of any given in-flight abnormality, though Qantas has not detailed its own crew's specific reasoning for this flight.

The Boeing 737-800 is one of the most heavily flown commercial aircraft types in the world, powered by CFM56-7B engines with a multi-decade service and safety record. A single engine event resulting in a safe diversion — however dramatic the visible flames appeared to witnesses on the ground — is not itself evidence of a design or fleet-wide problem; twin-engine aircraft are certified and routinely trained to fly and land safely on one engine.

Reading the Visible Flames Correctly

Video and eyewitness accounts describing repeated bursts of flame from a jet engine tend to look far more alarming than they are mechanically. Depending on the underlying cause, an engine can produce visible flame at the exhaust or around the cowling for reasons ranging from a genuine internal fire to something as comparatively benign as unburned fuel igniting after a compressor stall or a surge event, which can itself be triggered by anything from foreign object ingestion to icing to a mechanical fault. A compressor surge is often accompanied by the loud "bang" sound witnesses reported — a signature that has led some early commentary to describe the event as consistent with a surge, though again, that is a description of the acoustic and visual pattern, not a confirmed diagnosis from an inspection.

None of this determines what actually happened aboard QF122. It is included here because early public reporting on any in-flight engine event tends to compress a wide range of possible causes into a single dramatic image — flames streaming from a wing — without the context that visible flame, on its own, is not a reliable indicator of an event's underlying severity. That is precisely why investigators physically inspect the engine's internals — borescope the compressor and turbine sections, check for blade damage, and examine bleed and fuel systems — before publishing a cause.

The Regulatory Backdrop

New Zealand and Australia both operate under ICAO-aligned safety oversight frameworks, and an event involving an Australian-registered and Australian-operated aircraft occurring in New Zealand airspace typically draws coordination between the two countries' safety agencies, alongside input from Boeing and the engine manufacturer as manufacturer state parties. Whether that formal coordination has begun, and which agency has taken investigative lead, has not been confirmed in public statements from either Qantas or New Zealand's CAA as of this writing.

Airlines are generally not obligated to release engine serial numbers, exact flight paths, or internal maintenance logs during an active investigation, and Qantas's public silence on a specific cause beyond confirming the diversion and safe landing is standard practice pending a formal finding — not evidence of an unusually serious event being concealed.

What Comes Next

Qantas has not released a passenger count breakdown, aircraft registration, or a timeline for a technical finding. The investigating authority's identity and scope have not been confirmed publicly. Until an inspection of the affected engine and a formal cause determination are released, any specific mechanical explanation beyond "engine event, cause under investigation" should be treated as unverified. NewsFellow will update this story as investigators or Qantas release further detail.

The episode is a reminder of a broader pattern in how the public first learns about in-flight engine events: an initial, often plausible-sounding explanation — here, a bird strike — can circulate quickly, only to be revised once investigators have had time to actually examine physical evidence. That gap between first report and confirmed cause is why aviation authorities caution against treating early explanations as final.

Sources

Share:

Comments

Leave a comment