Qantas Cancels Perth-Bound Flight After Engine Fire Flares at Karratha Airport Before Takeoff

A Qantas flight bound for Perth was cancelled after flames were seen under the wing of the aircraft at Karratha Airport before takeoff, in an incident that forced passengers to disembark and left travellers facing delays on a key Western Australian regional route. The aircraft, flight QF1737, an Airbus A320-232 scheduled from Karratha to Perth, did not depart after the fire was spotted, and a Qantas spokesperson has apologised to passengers. No injuries have been reported in the accounts of the incident published so far. The episode is a reminder of how quickly a ground incident can disrupt a regional service, even when it is caught before an aircraft leaves the ground. Qantas QF1737 engine fire Karratha.

According to reports published by PerthNow and 7NEWS, the incident happened on Sunday evening, 1 November 2026, when the aircraft was preparing to leave Karratha for Perth. The departure was reported to be scheduled for about 7:15 p.m., and the flames were described as appearing beneath the wing, from the engine area, as the aircraft was on the runway and beginning its takeoff sequence. The pilot abandoned the takeoff, the aircraft returned to the bay, and everyone on board disembarked safely. Those reported details form the confirmed core of this story, and this article keeps every other detail clearly labelled where it is general background or still unconfirmed.

1. What happened at Karratha

1.1 The flight and the aircraft

Flight QF1737 was scheduled to operate from Karratha Airport in Western Australia to Perth. The aircraft type reported for the service is an Airbus A320-232, a single-aisle jet widely used on Australian domestic and regional routes. Reports describe the departure as scheduled for the evening, and PerthNow placed the incident at about 7:15 p.m. on Sunday, while 7NEWS reported that the flight was due to depart on Sunday evening. Taken together with the publication dates of those reports, 2 and 3 November 2026, the Sunday in question was 1 November 2026. That timing matters because an evening departure is often the last, or one of the last, links of the day for travellers heading to the state capital.

Karratha is not a small outback strip with only occasional traffic. It is a busy regional airport serving a working region, and a Perth service is a central part of its timetable. When a flight on that route is cancelled at short notice, the effect is felt quickly, not only by the people at the gate but also by families, employers and onward travel plans in Perth. The reports do not give a passenger count for QF1737, and this article does not estimate one. What is confirmed is the route, the flight number, the aircraft type and the outcome: the flight did not depart.

1.2 Flames spotted before takeoff

According to published reports, flames appeared under the aircraft’s wing, described as coming from an engine, moments before takeoff. One account described the aircraft as travelling along the runway and beginning to ascend when the flames were seen, after which the pilot abandoned the takeoff. Another account described the aircraft as just about to take off when flames were seen coming from underneath the wing. The precise location and extent of the flames, and what first alerted crew or ground staff, remain part of the reported account rather than independently confirmed detail, and this article does not overstate them beyond what the reports say.

The distinction between a reported detail and a confirmed technical finding is important here. A witness account of flames, and a news report that attributes an engine issue to the airline, are not the same as an engineering report on what failed inside the engine. Readers should therefore treat the description of flames from the engine area as reported, not as a proven mechanical cause. The flight was cancelled rather than departing, the aircraft was returned to the bay, and engineers were reported to have been called to assess it. Those steps, rather than any speculation about a fault, are the verifiable sequence in the reporting so far.

2. How passengers and crew responded

2.1 Disembarkation and apology

Passengers disembarked after the incident, and reports state that all passengers and crew disembarked safely. One report used the word evacuated to describe the move from the aircraft, while another described passengers disembarking after the aircraft returned to the bay. In either description, the outcome reported is the same: people left the aircraft on the ground at Karratha, rather than continuing with the flight. A Qantas spokesperson apologised for the disruption, and that apology is the clearest public comment attributed to the airline in the reporting seen so far.

Reports do not, so far, describe injuries, and this post does not claim any. That absence is itself worth stating carefully. It does not mean that no one was shaken or inconvenienced, and it does not rule out later updates. It simply means that, in the accounts published so far, there is no report of a person being hurt. For travellers reading this story, that is the most reassuring confirmed element, alongside the fact that the problem was spotted before the aircraft left the ground, when the safest options were still available.

2.2 What passengers were told next

According to 7NEWS, affected passengers were accommodated on Sunday night and were to be placed on replacement flights by 8:20 a.m. on Monday, or on the next available flights. That reported plan gives a concrete sense of the immediate aftermath: an overnight stay in Karratha, followed by a morning attempt to get travellers moving again. It does not, however, confirm how many travellers took up that offer, whether every passenger was accommodated in the same way, or whether any traveller chose a different arrangement. Those finer details are unconfirmed, and this article does not fill them in with guesswork.

Travellers on a cancelled regional service typically face rebooking onto later flights, but whether that general pattern fully describes what happened here, and on what timescale for each individual, is not confirmed beyond the reported overnight accommodation and Monday replacement flights. This section therefore explains the usual options in general terms without presenting them as what happened to these passengers in every case. In general, a cancelled evening flight can mean a new booking, a refund or credit under the airline’s policies, or a wait for the next service, depending on availability and the traveller’s own plans.

3. What Qantas has said so far

3.1 The airline’s statement

The confirmed public element is the apology from a Qantas spokesperson and the cancellation of the flight. PerthNow reported that the spokesperson said the flight was cancelled due to a believed engine issue, that passengers were accommodated on Sunday night, and that they would be placed on replacement flights by Monday morning. 7NEWS reported a similar apology and the same outline: an engine issue, disembarkation, overnight accommodation and replacement flights. This article quotes or paraphrases only what those sources actually attribute to Qantas, and does not invent further airline comment.

An apology in this context is more than a courtesy. It acknowledges disruption to people who had planned to be in Perth that night, and it signals that the airline accepts that the cancellation, even though it was a safety decision, had a real cost for its customers. At the same time, an apology does not by itself explain the technical cause, and readers should not read more into it than the words reported. The airline’s reported position, as published, is narrow: an engine issue was believed to be involved, the flight was cancelled, passengers were looked after overnight, and replacement travel was arranged.

3.2 What remains unexplained

The cause of the fire has not been publicly confirmed in the reporting seen. Whether it was an engine fault, a fuel or ground-equipment issue, or something else is unconfirmed, and this post says so plainly rather than speculating. The word believed, used in the reported airline comment about an engine issue, is important. It suggests a working assessment at the time, not a completed investigation. Until engineers report findings, or the airline issues a fuller statement, any attempt to name a single mechanical cause would go beyond the evidence.

There is also no confirmed detail in the reporting seen about how long the aircraft remained out of service, what repairs were required, or whether the same aircraft later operated other flights. Reports said engineers would assess the aircraft before it returned to service, which is a standard precaution, but the timing and findings of any inspection in this case are unconfirmed. Readers who want a definitive technical answer will need to wait for a further statement, and this article will not pretend that answer is already available.

4. Why an engine fire on the ground matters

4.1 Ground fires versus in-flight emergencies

A fire discovered on the ground, before takeoff, is handled very differently from one in the air: the aircraft is stationary, ground fire crews can reach it immediately, and evacuation or disembarkation can happen on the apron. That difference is general background, not a claim about the specific crew actions in this incident. In the air, a crew must manage altitude, speed, diversion airports and a pressurised cabin at the same time. On the ground, the priorities are simpler in one sense and urgent in another: stop the aircraft safely, shut down the affected systems, get people away from the aircraft, and let fire crews work.

The Karratha case illustrates why catching a problem before departure is so valuable. Once an aircraft is airborne, every option becomes harder and slower. On the runway, the aircraft can be stopped, the engines can be shut down, and passengers can leave by steps or slides onto a hard surface with emergency services nearby. That does not make a ground fire trivial. Fuel, hot engine parts and electrical systems still demand caution, and the decision to abandon a takeoff itself requires judgement under pressure. It does, however, explain why the reported outcome, with everyone disembarking safely, is the outcome crews train to achieve.

4.2 How crews train for this

Flight and cabin crews train for ground emergencies including engine fires, with rehearsed roles for stopping the aircraft, shutting down systems, communicating with passengers and coordinating with airport fire services. This is general context, not a description of what this crew did. In training, pilots practise rejected takeoffs at different speeds, cabin crew practise clear, calm instructions and door operation, and the whole crew practises the handover to ground emergency services. The goal is that, when a real alarm sounds, no one has to invent a procedure on the spot.

Communication is a large part of that training. Passengers need to know whether to leave belongings behind, which exits to use, and where to gather once outside. They also need reassurance, because a fire warning is frightening even when it is handled well. Ground staff, meanwhile, need to know where the aircraft has stopped, which systems have been shut down, and whether fuel or other hazards are present. Again, this article does not claim that any particular instruction was given on QF1737. It describes the kind of preparation that exists behind the scenes for incidents of this type.

5. The aircraft: Airbus A320-232

5.1 The jet’s role on regional routes

The A320 family is a workhorse of Australian domestic flying, and the -232 variant is configured for short- and medium-haul services like Karratha-Perth. Its size suits routes that need more capacity than smaller regional turboprops can offer. On a route that carries workers, families and business travellers between a resource region and a capital city, a jet of this size can move a substantial number of people in a single departure, which is why a cancellation is felt more widely than a cancellation on a very small service.

The A320-232 designation refers to a specific engine and configuration variant within the wider A320 family, a family that has been in service around the world for decades. That long service history means maintenance, spare parts and engineering knowledge are well established, and it also means that a single incident is examined against a large body of operating experience. None of that history, however, tells us what happened to this particular aircraft on this particular evening. It provides context for the type of aircraft involved, not an explanation for the flames reported.

5.2 Engine checks after an incident

After any reported engine fire, the affected engine and related systems are inspected before the aircraft returns to service, and the jet does not fly again until engineers clear it. The timing and findings of any inspection in this case are unconfirmed. Reports on QF1737 said engineers were to assess the aircraft, which matches that general practice: a visual inspection, checks of engine components, fuel and electrical systems, and a review of flight data and crew reports would normally be part of such an assessment, although this article does not claim that each of those steps was completed in this case.

That inspection process also protects the airline and its passengers in a second way. It creates a record that can be reviewed later, whether by the airline’s own safety teams or by an external authority, if one becomes involved. If a fault is found, the fix may be a component replacement, a more extensive repair, or a return to the manufacturer for detailed examination. If no fault is found, the aircraft may still remain out of service while checks are completed. Until a statement confirms the outcome for QF1737, the only safe statement is that an assessment was reported to be under way, and that the aircraft was not to fly until cleared.

6. Karratha Airport and the Perth route

6.1 A lifeline route for the Pilbara

Karratha Airport serves the Pilbara region, where mining, energy and port activity make the Perth connection economically important and, for many residents, the practical link to the state capital. A cancellation on this route therefore matters beyond a single flight’s passengers. Workers travel to and from rosters, families travel for medical care, education and holidays, and businesses rely on the route to move staff and supplies. When an evening flight is cancelled, those plans do not simply pause; they have to be rebuilt around the next available departure.

The Pilbara is vast, and road travel to Perth is not a practical substitute for most travellers on a Sunday evening. That is why regional air routes are often described as lifelines, even when they are operated by large airlines on jet aircraft. The description is not dramatic language for its own sake. It reflects the reality that, for many people in Karratha and nearby towns, the flight to Perth is the connection to specialist services, to family, and to onward domestic and international travel. A disruption on that route is therefore a community story, not only an aviation story.

6.2 Disruption for travellers

A cancelled evening departure can mean missed connections, overnight stays or a wait for the next available service, particularly on regional routes with fewer daily frequencies. Whether any of that applied to QF1737 passengers is unconfirmed beyond the reported overnight accommodation and Monday replacement flights, and must be flagged as such. In general, a traveller who misses a connection in Perth may need to rebook onward travel, rearrange accommodation, or inform an employer or family member of a delay. Those are the kinds of knock-on effects that make a single cancellation feel much larger to the people involved.

For the QF1737 passengers, the reported plan of overnight accommodation followed by replacement flights by Monday morning suggests that the airline aimed to limit that knock-on effect, but this article does not claim that every passenger’s journey was restored by that time. Some travellers may have had onward flights that could not be recovered, and some may have chosen to make their own arrangements. Without a further airline update, those individual outcomes remain unconfirmed, and it would be wrong to present the reported plan as a guarantee that every traveller arrived on time the next day.

7. How incidents like this are examined

7.1 Who looks into it

In Australia, serious aviation incidents can be examined by the airline, the operator’s safety teams and, where the criteria are met, the Australian Transport Safety Bureau. Whether this incident meets the threshold for an ATSB investigation is unconfirmed and must not be asserted. The airline’s own safety process will normally review crew reports, maintenance records and any available data, regardless of whether an external body becomes involved. That internal review is a routine part of aviation safety, and it does not by itself imply that a serious safety failure occurred.

The ATSB, by contrast, investigates a defined range of accidents and serious incidents, and it publishes its findings when an investigation is completed. If it were to examine this incident, it would do so under its own criteria and timetable, and any findings would come later. At the time of writing, no source seen for this article confirms that the ATSB has opened an investigation into QF1737, and this article therefore does not claim that one exists. Readers should be wary of any account that presents an ATSB investigation as fact without a source.

7.2 What the checks typically cover

A typical examination would look at the engine, maintenance history, ground handling and the sequence of events on the apron. Findings, if any are published, would come later; none are claimed here. Investigators would normally ask when the engine was last serviced, whether any defect had been reported before the flight, what the crew observed and when, and how ground services responded. They would also look at whether any ground equipment was near the aircraft at the time, and whether weather or other conditions played a role, although no such factor is reported in this case.

That kind of examination is methodical by design. It separates what was seen from what caused it, and it tests each possible explanation against physical evidence. That is why a first news report, however detailed, is rarely the final word on cause. The first report tells us that flames were seen and that a flight was cancelled. A later examination, if one is published, may tell us why. Until then, the responsible approach is to keep the reported facts and the unconfirmed questions in separate columns, as this article does.

8. What remains unconfirmed

8.1 Questions still open

The number of passengers and crew on board, the precise source and cause of the flames, what happened to passengers afterwards beyond the reported overnight accommodation and Monday replacement flights, and whether any formal investigation has been opened all remain unconfirmed on the reporting available. The date and time are now clearer than in the first draft of this story: reports point to Sunday evening, 1 November 2026, at about 7:15 p.m., but even that timing is reported, not independently verified from flight records, and it is presented here as reported. Any reader who needs an official record should look for a statement from Qantas or an aviation authority, rather than relying on news reports alone.

Other open questions include the condition of the aircraft after inspection, whether it returned to service on the same route or elsewhere, and whether any safety recommendation will follow. Those questions may seem secondary to the drama of flames on a runway, but they are the questions that determine whether this incident was a one-off fault, a maintenance issue, or a sign of a wider problem. Until they are answered with evidence, this article will not guess at them, and it will not present a general description of typical checks as if it were a finding about QF1737.

8.2 What to watch next

Watch for a fuller Qantas statement, any update on the aircraft’s return to service, and any statement from aviation safety authorities. Until then, the confirmed core of this story is narrow: a Perth-bound Qantas jet at Karratha, flames seen before takeoff, a cancelled flight, an apology, and no injuries reported so far. That narrow core is still a significant story, because it shows a safety system working as intended at the moment it mattered most: a problem was spotted, a takeoff was abandoned, and people left the aircraft safely.

If a fuller statement does appear, it will be worth checking it against the questions listed above, rather than assuming it answers all of them. A statement may confirm the cause, or it may confirm only that checks are continuing. Either way, the next update should be judged on what it actually says, with the same care applied here: reported facts attributed, general background labelled as background, and unknowns left clearly flagged. For now, travellers on the Karratha-Perth route can take from this story a simple, verified message: on Sunday evening, 1 November 2026, flight QF1737 did not depart after flames were seen at Karratha Airport, its passengers disembarked safely, and Qantas apologised for the disruption.

Comments

comments