LEVEL 3 Final report

Based on the investigation authority's final report.

Date
Show source
Occurrence
Engine fire and evacuation
Location
Wellington Airport, runway 34
Show source
Operator
Air New Zealand
Show source
Aircraft
ATR72-212A-600
Show source
Registration
ZK-MVL
Show source
Route
Christchurch to Wellington
Show source
People aboard
74: 4 crew and 70 passengers, including one infant and one flight deck jump-seat occupant
Show source
Casualties
No fatalities or serious injuries established; report narrative describes minor evacuation injuries, while the data summary lists nil
Show source
Topics
Crew coordination, Evacuation and rescue, Inspection and quality control, Turbine-blade fatigue

This photograph is cropped for the banner. See the full photograph, credit, licence and what it shows.

Photographs and geographic context

Air New Zealand ATR72-600 ZK-MVL at Wellington

ZK-MVL at Wellington on 1 October 2018, before the incident.

Photo: Ev Brown, CC BY 2.0

Image info

The photograph identifies the incident registration, but shows an earlier visit and is not evidence of the occurrence.

Image source

Commons-supplied 1280-pixel JPEG retained without cropping. Responsive WebP copies resized without cropping.

Geographic context

Geographical orientation for Air New Zealand ZK-MVL: engine fire and evacuation at WellingtonChristchurch departure; Wellington landing. Schematic approximate airport markers, not a recorded flight track or navigation chart. Route names are documented in the report.12NORTH UP / SCHEMATIC / NOT A RECORDED FLIGHT TRACK
  1. Christchurch departure
  2. Wellington landing
Schematic approximate airport markers, not a recorded flight track or navigation chart. Route names are documented in the report. Basemap: Natural Earth, public domain.
Read supporting evidence

What happened

A turbine blade fatigue failure caused an engine fire on low approach. The aircraft landed safely, but the evacuation exposed further hazards.

Read the full incident Follow what happened, from the flight to the investigation findings.

What investigators concluded

TAIC found a fatigue failure of a low-pressure turbine blade initiated the engine fire. It considered pre-existing fatigue at overhaul likely, without determining its exact origin, and identified separate evacuation and passenger-management safety issues.

Evidence behind this explanation

An engine fire on final approach, then a difficult evacuation

1,559 words / about 8 minutes to read. Based on the investigation records cited below.

An uneventful flight until the runway was close

On 1 September 2024, Air New Zealand's ATR72-600 registered ZK-MVL left Christchurch for Wellington at 15:16. Four crew and seventy passengers were aboard. The passenger total included an infant on a parent's lap and an adult occupying the flight deck jump seat. The aircraft's cabin had sixty-eight passenger seats. These distinctions explain the occupancy figures without implying that every passenger occupied a separate cabin seat. The captain was flying, and the first officer was monitoring. It was their third sector that day in the same aircraft, after a return trip to Rotorua.

The journey and descent were uneventful. Visibility at Wellington was unrestricted, and the tower reported wind nearly aligned with runway 34. After changing to the tower frequency, the crew were told they were following another aircraft. That aircraft landed, and ZK-MVL received landing clearance. At 16:03:49, about 380 feet above mean sea level, left-engine oil pressure fell and triggered a caution. The first officer announced it, and the captain decided to continue the approach. The caution cleared and returned three more times in roughly fifteen seconds.

As the aircraft passed about 100 feet, an engine fire warning sounded. The first officer transmitted a Mayday, but the tower controller was transmitting a conditional line-up clearance at the same time and did not hear it. The absence of an immediate reply did not mean emergency services remained unaware. Watching the arriving aircraft through binoculars, the controller saw smoke from an engine and activated the airport emergency alarm. Rescue fire vehicles were dispatched towards the landing aircraft. The Commission separates this visual intervention from the crossed radio calls.

Sources for this section

Landing and dealing with the warning

ZK-MVL touched down at 16:04:30 and stopped about halfway along the runway. While it slowed, the first officer repeated the Mayday. This time the controller acknowledged it, confirmed fire vehicles were coming, instructed the next arriving aircraft to overshoot and stopped other ground movements. Cabin crew reported fire outside and smoke or haze inside. Some passengers began standing, but an announcement from the forward flight attendant brought them back to their seats. The aircraft had landed safely, yet its engine warning and cabin observations required further action.

The pilots completed the engine-fire memory actions. Both engines were shut down, the left fire handle was pulled and the first suppressant bottle was discharged into the nacelle. After the required thirty-second wait, the warning remained illuminated, so they discharged the second bottle. The captain alerted cabin crew to their stations. Both pilots removed their headsets to communicate more easily with each other, without selecting the flight deck speaker. That choice subsequently prevented them hearing information from the tower and the rescue fire service.

The continuing warning led the captain to order the evacuation checklist. Its air traffic notification item was read, but no radio call announcing the evacuation was made. At 16:06:30, responders reported only a very small amount of smoke from the left engine. The tower asked the aircraft whether it had anything to add, without receiving a response. At 16:07:11, the captain gave the evacuation announcement. Investigators considered it virtually certain that the fire had already been extinguished shortly after the second suppressant discharge. Residual heat kept the sensing system active; a continuing warning is therefore not evidence of flames continuing throughout the evacuation.

Sources for this section

Leaving the cabin and moving away

Three of the four cabin exits were used: the rear-left door with its built-in stairs, and the two smaller forward emergency exits. The rear-right service door remained closed, although it was available. Cabin crew checked for heat and hazards before directing passengers out. The rear stairs carried most of the cabin passengers. The forward openings required passengers to step up and then jump roughly six feet to the runway. Some found the hatch weight, opening size and drop more difficult than they had expected; one had expected a slide.

The report's findings identify twelve passengers leaving through the forward-left exit, fifteen through the forward-right and forty-two through the rear stairs. Its detailed table reverses the two forward counts. The same source presents evacuation duration in different ways: its safety issue cites two minutes fifty-one seconds, while the table places the last rear-stair passenger three minutes seven seconds after the announcement. Those inconsistencies prevent a single definitive exit-by-exit stopwatch reconstruction here. Both presentations establish an evacuation substantially longer than the ninety-second certification benchmark. That benchmark describes a controlled demonstration, rather than a guarantee for every real emergency.

Many passengers took baggage despite the briefing and cabin crew instructions. Video showed nineteen of the twenty-seven people using the forward exits carrying bags; the rear-door estimate was less precise. Retrieving baggage slowed the aisle, and handling it at the forward openings further interrupted the flow. The Commission also recognised that passengers no longer saw an obvious fire threat. It did not attribute every individual's behaviour to one motive. Several people then walked near the previously burning left engine and propeller while joining another group. Responders shifted from firefighting to helping people at the exits and managing movement outside.

Sources for this section

Tracing the fire to a turbine blade

The replacement left engine had been installed the day before, following overhaul at the manufacturer's Singapore facility. That overhaul included replacing the low-pressure turbine disc and inspecting its forty-seven blades. A satisfactory ground run preceded the aircraft's return to service. The engine had flown only four hours since overhaul when the occurrence happened. Investigators found no recorded operating exceedance or abnormality during those hours. The short interval is significant to the investigation, but by itself it does not prove precisely when a crack began or who should have detected it.

Examination identified a low-pressure turbine blade that had fractured near its root and separated. The resulting imbalance damaged internal seals and associated components, allowing oil into the engine and producing smoke, flames and the falling oil pressure. Canadian laboratory work confirmed fatigue. Later examination found a second cracked blade six positions away from the failed one, with similar fatigue features. The blades had different serial numbers and were not from the same manufacturing batch. The second blade's condition made the quality-assurance question broader than a single isolated fracture.

The laboratories differed over timing. The Transportation Safety Board of Canada considered the fatigue likely present at overhaul. Pratt & Whitney Canada interpreted oxidation, progression marks and the absence of penetrant residue as indicating cracking after the inspection. The Commission reviewed both examinations and requested clarification. Its adopted finding was that the blade failed through fatigue and that fatigue on both blades was likely already present during overhaul, while the exact origin remained undetermined. The draft retains that distinction between a firm failure mechanism and a qualified timing conclusion. It does not turn the manufacturer's interpretation into the Commission's finding or claim a proven manufacturing defect.

Sources for this section

What the response revealed

The Commission credited the flight and cabin crews with achieving a safe landing and evacuation. It also identified opportunities to improve the response. Engine-fire memory actions should have been verbalised so the other pilot could verify them. An acknowledged engine-fire Mayday did not replace notification that passengers were about to evacuate. Keeping a means of hearing the radio would have preserved communication with responders. Those observations concern how information and checking work during an emergency; they are not evidence that the wrong engine was shut down on this flight.

Cabin training facilities could not realistically reproduce both flight-attendant positions and all four exits simultaneously. Passengers' difficulties at the forward hatches, the unused rear service door, baggage retrieval and movement near the engine all informed the recommendations. Personal headphones prevented at least one passenger hearing the initial command, but the Commission said this did not materially affect the overall duration. The account therefore distinguishes an observed communication concern from a demonstrated major delay. It also avoids attributing all evacuation time to baggage alone.

The report describes minor injuries, mainly strains associated with jumping from the forward exits, in its analysis and summary. Its data table lists no injuries, and the airline's appended response also describes evacuation without injury. This account follows the investigation's substantive narrative while disclosing the conflict. No death or serious injury is established. The compelling scope basis is the actual engine fire on very low approach, followed by an evacuation whose delays and external hazards the official investigation examined. It is not a claim that the aircraft remained on fire while people escaped.

Sources for this section

Recommendations and the limits of completion

On 26 August 2026, the Commission recommended that Pratt & Whitney Canada ensure overhaul quality-assurance procedures identify pre-existing fatigue. In its September response, the manufacturer said its inspection methodology and assessment processes already met the recommendation's intent and that it would continue monitoring reliability. The final report records that response alongside the recommendation. It does not establish an independently verified new inspection programme. The safety issue and disagreement must remain visible rather than being resolved by editorial assumption.

Air New Zealand accepted the evacuation recommendation and described a mixture of implemented and progressing measures. These included reinforced procedures, aligned commands, stronger rear-service-door training and more realistic flight crew scenarios. Passenger briefing and safety-card changes were being taken through approval, with implementation targeted for December 2026. A dedicated ATR evacuation trainer remained a proposal subject to business-case and funding approval. The report also records improved emergency transport arrangements at Wellington. These are dated findings and organisational responses. Acceptance, a target date and a proposed trainer each mean something different from completed implementation, and none is presented here as a later audit of actual airline practice.

Sources for this section

Return to the short summary / Source status and limitations

How the sequence developed

Follow the main stages, then open the evidence beneath each step.

  1. Fatigue fracture

    A low-pressure turbine blade failed, causing vibration and seal damage.

    Read supporting evidence
  2. Oil-fed engine fire

    Oil entered the engine, producing smoke and flames and activating the fire warning.

    Read supporting evidence
  3. Warning after extinguishment

    Residual heat sustained the warning after the fire was virtually certainly extinguished.

    Read supporting evidence
  4. Evacuation hazards

    Baggage, difficult forward exits and unsafe movement outside compounded evacuation risk.

    Read supporting evidence

A simplified reading of the investigation findings. The sequence does not replace the full report or imply that every contributing factor is shown.

Sequence of events

Report narrative times are local New Zealand time. Some report evacuation timing and injury entries conflict; those differences are disclosed. Expand an event to see its evidence.

  1. 15:16Departure

    The passenger flight departed Christchurch.

  2. 16:03:49Oil pressure caution

    A left-engine low oil pressure caution began on approach.

  3. About 100 ftFire warning

    The warning activated; the first Mayday overlapped a tower transmission.

  4. 16:04:30Landing

    The ATR landed and stopped on the runway.

  5. After stoppingFire actions

    Both suppressant bottles were discharged; the warning remained.

  6. 16:07:11Evacuation announcement

    Three cabin exits were used; the report documents delays and baggage retrieval.

  7. 16:47Runway reopening

    The aircraft was moved and the runway inspected before reopening.

Search the report evidence

Search extracted report prose, with original page references. Short results link to the full document.

Questions readers ask

Was the engine still burning during evacuation?

TAIC considered it virtually certain the fire was extinguished shortly after the second bottle. Residual heat kept the warning illuminated.

ATR72-600, ZK-MVL Engine fire and evacuation Wellington 1 September 2024Was the engine still burning during evacuation? | Printed page 16 | PDF page 24Find this passage in evidence search
Why does the account mention minor injuries?

The summary and analysis describe minor injuries; the data summary and appended airline response say nil. This conflict is preserved, and no serious injury is claimed.

ATR72-600, ZK-MVL Engine fire and evacuation Wellington 1 September 2024Why does the account mention minor injuries? | Printed page 16 | PDF page 24Find this passage in evidence search
Did the fire prove the overhaul caused the crack?

No. TAIC found fatigue likely present at overhaul but could not determine its origin; laboratory timing interpretations differed.

ATR72-600, ZK-MVL Engine fire and evacuation Wellington 1 September 2024Did the fire prove the overhaul caused the crack? | Printed page 30 | PDF page 38Find this passage in evidence search

What the evidence can and cannot establish

Evacuation duration

The safety issue gives 2:51, while Table 1 gives 3:07 to the last rear-stair passenger. Both exceed the benchmark; neither is silently substituted for the other.

Read supporting evidence

Safety follow-up

Actions and recommendations are described at the dates of the cited records. A recommendation is not proof of implementation.

Classifications, with reasons

These labels organise the evidence. They are not a ranking of causes. A shared label means a shared research topic, not an identical mechanism.

Initiating eventTurbine-blade fatigue

A low-pressure turbine blade failed through fatigue.

Safety issueInspection and quality control

TAIC considered fatigue likely present during overhaul and called for quality assurance capable of identifying it; timing remains uncertain.

Survival factorEvacuation and rescue

A slow evacuation, unused exit, baggage retrieval and movement near the engine introduced risk after landing.

Crew actionCrew coordination

Landing and evacuation succeeded, while missed radio communication and checklist-verbalisation opportunities were examined separately.

Read alongside

These comparisons connect specific research topics. Shared circumstances do not establish identical causes. Evidence from both investigations is provided below.

Qantas Flight 32

Both investigations examine flight and cabin crew management of an engine emergency. Wellington involved an ATR turbine-blade fatigue failure and evacuation; Qantas 32 involved a different uncontained rotor failure and extensive system damage. Their failure mechanisms and exit decisions are not identical.

Read supporting evidence
ATSB final reportComparison final-report findings | Printed page 146 | PDF page 166Find this passage in evidence search

Further investigation records

Explore the records below for additional context. They open on the publisher's site and are not all included in our report search. Source reuse terms apply.

Sources and transparency

Prepared 7 October 2026 from the cited final investigation. Unpublished; editorial approval and independent expert review have not been completed.

Source limitations

The report gives inconsistent injury summaries, forward-exit counts and evacuation timings. Fatigue failure is established, but its exact origin is not. Report-era action responses are not a later implementation audit.

ATR72-600, ZK-MVL Engine fire and evacuation Wellington 1 September 2024

TAIC
Official final report; cached original bytes and complete extraction checked 7 October 2026

Official report PDF, hosted by taic.org.nz

Open source document

Retrieved 4 October 2026. 56 PDF pages. 2,801,572 bytes.

File fingerprint (SHA-256). It identifies the exact version of the report this page was checked against.

cb48be898d018ebff43b052f79bf0300f70234532e1bf5ce6219e650e4b33da8

Source used for original commentary and short verification snippets; illustrations not reused unless separately licensed. Source terms / provenance.

ATSB AO-2010-089: In-flight uncontained engine failure, Airbus A380-842 VH-OQA, overhead Batam Island, 4 November 2010

Australian Transport Safety Bureau (ATSB)
Final report, 27 June 2013

Official report PDF, hosted by atsb.gov.au

Open source document

Retrieved 4 October 2026. 305 PDF pages. 21,149,715 bytes.

File fingerprint (SHA-256). It identifies the exact version of the report this page was checked against.

54863471db175f0e0eddb7e051c1238ddd7c64893f037c037567afd9d2fe5828

Source: Australian Transport Safety Bureau. Commonwealth content licensed CC BY 3.0 Australia; Coat of Arms, ATSB logo and third-party photos/graphics excluded. Only limited text excerpts used. Source terms / provenance.

Read the extraction, classification and review methodology.

Suggest a correction to this dossier

Editorial record

Kevin Murphy writes the incident accounts on AirlineIncidents.com, out of a long interest in aviation safety and the lessons each investigation leaves behind.

Prepared by
AirlineIncidents editorial desk
Report citation check
Independent expert review
Not completed

Citation checks compare supporting text with the indexed report pages. They do not constitute independent expert review. How these pages are prepared.

Revision history

: Published sourced incident account, timeline, photographs and investigation findings.

Source-based corrections are reviewed before changes appear here. Suggest a correction to this dossier.