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.
4 matching PDF pages. Showing 4 short source excerpts. Open the document for full context.
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 14. PDF page 22.
however, the presence of the micro- shrinkage porosities in the fracture initiation regions likely acted as localized stress concentrators. The Microstructural composition of the blades confirmed that no anomaly was observed and that the base material was consistent with theOpen final report at PDF page 22ATR72-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