Qantas Flight 520
This article has been nominated for merging into Sydney Airport § Accidents and incidents. You are welcome to participate in the merging discussion, which will decide whether to merge it into Sydney Airport § Accidents and incidents. This discussion may also result in the article being deleted, redirected, or draftified. |
VH-VYH, the aircraft involved, photographed in 2022 | |
| Serious incident | |
|---|---|
| Date | 8 November 2024 |
| Summary | Contained engine failure during take-off caused by a turbine-blade fatigue crack |
| Site |
|
| Aircraft | |
| Aircraft type | Boeing 737-838 |
| Operator | Qantas |
| IATA flight No. | QF520 |
| ICAO flight No. | QFA520 |
| Call sign | QANTAS 520 |
| Registration | VH-VYH |
| Flight origin | Sydney Airport |
| Destination | Brisbane Airport, Queensland, Australia |
| Occupants | 181 |
| Passengers | 175 |
| Crew | 6 |
| Fatalities | 0 |
| Injuries | 0 |
| Survivors | 181 |
Qantas Flight 520 was a scheduled Australian domestic passenger flight from Sydney Airport to Brisbane Airport. On 8 November 2024, the Boeing 737-838 operating the flight, registered VH-VYH, suffered a contained failure of its right engine as it reached decision speed during take-off. The crew continued the take-off and returned to Sydney for a single-engine landing about 30 minutes later. All 175 passengers and six crew members were uninjured. Engine fragments ignited a grass fire beside the runway and disrupted operations at the airport.[1][2][3]
The Australian Transport Safety Bureau (ATSB) classified the occurrence as a serious incident. Its final report found that a fatigue crack in a high-pressure turbine blade caused the blade to separate from the turbine disc, damaging the engine. It found that the flight crew had responded quickly and appropriately.[1]
Aircraft and flight
[edit]The aircraft was a Boeing 737-838, serial number 34180, powered by two CFM56-7B24E engines. The flight carried two pilots, four cabin crew members and 175 passengers.[1] The right engine had completed 17,656 flight cycles and was scheduled to be removed on 21 November, 13 days after the incident, as it approached the manufacturer's recommended removal threshold of 17,900 cycles. A borescope inspection on 25 September had found no significant defects, but this type of inspection could not examine the below-platform areas of the turbine blades where the fatigue crack developed.[1]
Incident
[edit]The aircraft began its take-off roll on Sydney's runway 34R at 12:34:35 local time. At 12:35:20, as the first officer called the decision speed V1, the pilots heard a loud bang and felt the aircraft shudder. The aircraft reached rotation speed three seconds later. Because the failure occurred at the decision speed, the crew continued the take-off and made a PAN PAN urgency call 28 seconds after lift-off.[1]
Fragments expelled from the engine landed beside runway 34R and ignited a grass fire, closing that runway. The aircraft was slightly above its maximum landing weight and the crew selected the longer runway 34L for the return. While holding south of the airport, they completed the engine-failure checklists and asked an off-duty pilot travelling as a passenger to photograph the right engine. The photograph indicated that the failure had been contained and that there was no visible damage to the wing.[1] Airservices Australia imposed a 47-minute ground stop, and delays at Sydney Airport averaged about 45 minutes.[4]
The aircraft landed on runway 34L at 13:05:50. Airport firefighters inspected the engine before the aircraft taxied to the gate, where the occupants disembarked normally.[1] No injuries were reported.[5]
Investigation
[edit]The ATSB opened a limited-scope investigation. An examination by engine manufacturer CFM International found that two of the engine's 76 high-pressure turbine blades had separated below their platforms. Fatigue cracks in the dovetail of one blade caused it to separate from the disc; the adjacent blade then failed from tensile overstress. The remaining blades fractured from consequential overstress, and the debris caused a contained engine failure.[1]
The failure mechanism had previously been recorded in the CFM56-7B fleet. The manufacturer reviewed the fleet after the incident and determined that the blade configuration used in VH-VYH continued to meet its reliability targets and regulatory guidance, so it did not lower that configuration's recommended removal threshold. The ATSB's final report, released on 29 April 2026, identified the fatigue crack as the contributing factor and praised the crew's response at what it described as a critical point in the take-off.[1][6][7]
Aftermath
[edit]Qantas returned VH-VYH to service after replacing its right engine. The airline also removed two other CFM56 engines earlier than scheduled as a precaution, while saying that no common fault had been identified.[8]
See also
[edit]References
[edit]- 1 2 3 4 5 6 7 8 9 Australian Transport Safety Bureau (29 April 2026). Engine failure involving Boeing 737, VH-VYH, at Sydney Airport, New South Wales, on 8 November 2024 (Report). AO-2024-057. Retrieved 10 August 2026.
- ↑ "Qantas plane makes emergency landing, grassfire breaks out at Sydney Airport". ABC News. 8 November 2024. Retrieved 10 August 2026.
- ↑ Visontay, Elias; Wind, Emily (8 November 2024). "Qantas flight makes emergency landing at Sydney airport after engine failure, sparking grass fire near runway". The Guardian. Retrieved 10 August 2026.
- ↑ "Sydney Airport emergency landing: Engine failure on Qantas plane mid take-off—as it happened". ABC News. 8 November 2024. Retrieved 10 August 2026.
- ↑ Graham-McLay, Charlotte (8 November 2024). "Runway fire breaks out at Sydney Airport after emergency landing". Associated Press. Retrieved 10 August 2026.
- ↑ "ATSB praises 'decisive' flight crew in Qantas engine failure incident". Australian Aviation. 29 April 2026. Retrieved 10 August 2026.
- ↑ "Crew praised after frightening Qantas engine failure". The New Daily. 30 April 2026. Retrieved 10 August 2026.
- ↑ Boscaini, Joshua (22 November 2024). "Qantas engine failure that forced Sydney Airport emergency landing likely caused by mechanical failure". ABC News. Retrieved 10 August 2026.
External links
[edit]- Aviation accidents and incidents in 2024
- Aviation accidents and incidents involving the Boeing 737 Next Generation
- Aviation accidents and incidents in New South Wales
- Airliner accidents and incidents caused by engine failure
- Qantas accidents and incidents
- 2024 in New South Wales
- November 2024 in Australia