Flight Details
Aircraft Type: Boeing 737-8 MAX Operator: Buzz (Ryanair Group subsidiary) Registration: SP-RZU Flight Number: FR5570 Route: Budapest Ferenc Liszt International Airport (BUD), Hungary to Sofia Airport (SOF), Bulgaria Date of Incident: 22 April 2025 Total Occupants: Not publicly confirmed; typical Ryanair MAX 8 seating up to 197 passengers Weather Conditions: Visual meteorological conditions; no adverse weather reported during climb
Introduction
On 22 April 2025, a Boeing 737 MAX 8 operated by Buzz on behalf of Ryanair suffered a suspected engine failure shortly after departure from Budapest, prompting an emergency return. The aircraft had just departed runway 31L and was climbing through approximately 4,000 feet when the crew reported a loud bang in one of the LEAP-1B engines, consistent with a high-energy bird strike and possible engine damage. The flight crew immediately levelled off, entered a holding pattern, and conducted an emergency checklist review before returning to land safely on runway 31R. The flight was subsequently cancelled.
Sequence of Events
Flight FR5570 departed Budapest as scheduled and initiated a standard climb. Just after gear retraction and climb power stabilisation, the crew reported hearing a sudden, loud bang from the right-hand engine (presumed), consistent with compressor stall or fan blade damage.
The aircraft levelled at 4,000 feet and advised Budapest ATC of a suspected engine failure, attributed to a bird strike. The crew reported indications of severe engine damage, including possible engine vibration, loss of thrust, and abnormal instrument readings.
While holding near Budapest, the crew:
Declared a PAN PAN or MAYDAY with ATC (specific call not yet confirmed) Actioned the Engine Severe Damage or Fire checklist from the Boeing QRH Configured the aircraft for single-engine return Requested vectors for a low workload straight-in approach to runway 31R
The aircraft landed safely approximately 18 minutes after takeoff, with one engine inoperative. Emergency services were on standby but did not need to intervene. The aircraft taxied to stand under its own power using the unaffected engine.
Crew & Communication
The flight crew’s rapid diagnosis and containment of the situation were fully in accordance with Boeing emergency procedures for engine failure after takeoff. Critical steps included:
Identification of affected engine Engine shutdown via fuel cut-off and fire handle (if applicable) Activation of alternate systems as required (e.g. hydraulics, electrics) Coordination with cabin crew and ATC for emergency response preparation Preparation for overweight landing or single-engine landing checklist execution
There were no reports of abnormal cockpit indications prior to the bang, suggesting a sudden external event rather than a progressive engine malfunction.
Aircraft Systems & Technical Analysis
The CFM International LEAP-1B engine powers all Boeing 737 MAX aircraft and includes:
Dual-annular combustor for reduced emissions Forged titanium fan blades Composite fan case and nacelle Full-authority digital engine control (FADEC) system
The symptoms reported—loud bang, engine vibration, and degraded thrust—are highly consistent with:
Bird ingestion into the fan or compressor stages Fan blade deformation or detachment Compressor surge/stall due to disrupted airflow Asymmetric thrust and degraded performance from the affected engine
Post-incident maintenance actions will include:
Borescope inspection of inlet, fan, and low-pressure compressor Engine data download via QAR/FDIMU Fan blade track and balance inspection Examination of cowling and inlet lip for strike evidence Wildlife residue analysis for bird DNA if remains are recovered
The fact that the aircraft remains grounded over 18 hours later suggests a minimum of fan blade replacement or possible full engine removal depending on damage severity.
Passenger Experience & Cabin Conditions
There were no reports of smoke, fire, or pressurisation issues in the cabin. Passengers likely felt a jolt or heard the bang, especially those seated near the right-hand engine.
Cabin crew would have received immediate communication from the cockpit and commenced preparations for a potential emergency return, including securing the cabin and instructing passengers to remain seated with seatbelts fastened.
The landing was uneventful, and passengers disembarked normally at the terminal. The flight was later cancelled, and passengers were rebooked or rerouted.
Emergency Response & Aftermath
Budapest Airport’s fire and rescue teams were deployed to standby positions as per emergency SOPs. No engine fire or fuel leak was observed.
Airport ground operations supported the aircraft’s safe taxi to a stand, where it was shut down and inspected. The surrounding taxiway and runway were checked for debris (FOD) or avian remains to confirm the bird strike scenario.
The aircraft was handed over to Buzz and Ryanair’s engineering teams for post-flight diagnostics.
Investigation Status
At this time, the Hungarian Transport Safety Bureau (KBSZ) has been notified of the event. The Irish Aviation Authority (IAA), as Ryanair’s state of registry, and Poland’s ULC (as the aircraft is SP-registered) may also be consulted.
There has been no indication of NTSB or EASA involvement, as this is a routine, non-injury engine failure event with local oversight.
Investigative focus will include:
Engine performance and fault logs Wildlife strike data from the airport’s bird control records Maintenance history of the engine and recent performance reports
Root Cause & Contributing Factors
Probable Cause (Preliminary):
Bird ingestion into the engine fan section, resulting in mechanical imbalance or blade damage
Contributing Factors:
Aircraft speed at impact zone during low altitude climb Wildlife activity in airport vicinity Potential gap in active bird hazard detection or dispersal at BUD airport
Safety Recommendations & Industry Impact
While no formal recommendations have been issued, this event reinforces:
The ongoing hazard of bird strikes during takeoff and initial climb The importance of engine containment and crew response training The need for airport wildlife management programmes to remain vigilant, especially at dawn/dusk when bird activity peaks Continued review of engine intake design and resistance to bird impact
This incident also highlights the high reliability of modern twin-engine aircraft during single-engine operations, with no degradation to flight safety.
Conclusion
Buzz flight FR5570’s emergency return to Budapest due to an engine failure after takeoff was handled with precision and professionalism. The suspected bird strike triggered appropriate safety protocols and resulted in a successful single-engine return with no injuries or damage beyond the affected powerplant.
Investigators will now focus on confirming the root cause and assessing whether airport wildlife management procedures or engine design limitations played a role.
Disclaimer
This article is based on publicly available information and reports at the time of writing. While every effort has been made to ensure accuracy, we cannot guarantee the completeness of the information provided.
If you are the rightful owner of any referenced content or images and wish them to be removed, please contact takedown@cockpitking.com.
