Search report text, read a short matching passage, then open the source page.
Exact phrases match first; otherwise all words must occur close together. Six excerpts maximum. Text extraction cannot search image-only charts. Warsaw uses a report transcription with missing figures and appendices.
10 matching PDF pages. Showing 6 short source excerpts. Open the document for full context.
Printed page 1. PDF page 9.
four flying hours of the engine having been overhauled. 1.6. The fatigue cracking was likely present during the engine overhaul but was not identified as part of the overhaul quality assurance process. The Commission was also unable to determine whyOpen final report at PDF page 9ATR72-600, ZK-MVL Engine fire and evacuation Wellington 1 September 2024
Printed page 13. PDF page 21.
2. The fatigue crack has likely been present since the blade entered service and was likely present at the time of the engine overhaul. 3. The damage to the upstream edge of the blade root occurred after the fatigue crackOpen final report at PDF page 21ATR72-600, ZK-MVL Engine fire and evacuation Wellington 1 September 2024
Printed page 17. PDF page 25.
conclude that the fatigue cracking developed in the root of the blade and the crack was likely present when the blade entered service. Therefore, the crack was likely already present when the engine was overhauled.25 The engine overhaul had includedOpen final report at PDF page 25ATR72-600, ZK-MVL Engine fire and evacuation Wellington 1 September 2024
Printed page 19. PDF page 27.
Although unable to determine when the fatigue cracking originated, the Commission found it likely that the fatigue was present in both LPT blades when the engine was recently overhauled. This finding was based on: � the amount and different typesOpen final report at PDF page 27ATR72-600, ZK-MVL Engine fire and evacuation Wellington 1 September 2024
Printed page 30. PDF page 38.
Commission was unable to definitively determine when the fatigue cracking originated, it was likely that the fatigue on both LPT blades was present when the engine was recently overhauled. 4.6. Despite an initial crossed communication, the actions of the towerOpen final report at PDF page 38ATR72-600, ZK-MVL Engine fire and evacuation Wellington 1 September 2024
Printed page label not indexed. PDF page 17.
exceeded the parameters of the model provided in the advisory material for predicting the likely damage from a UERF. Information from the accident represents an opportunity to incorporate any lessons learned from this accident in the advisory material. The ATSBOpen official document at PDF page 17ATSB AO-2010-089: In-flight uncontained engine failure, Airbus A380-842 VH-OQA, overhead Batam Island, 4 November 2010