Overview
• Operator: HiSky Europe
• Aircraft Model: Airbus A320-200
• Registration: YR-BEE
• Flight Number: H4-762
• Route: Bucharest Otopeni (OTP) → Oradea (OMR), Romania
• Date: 3 March 2025
• Occupants: Not specified
• Casualties: None
• Nature of Incident: Left engine stall during climb, PAN PAN declared, return to base
Incident Summary
A HiSky Europe Airbus A320-200 operating flight H4-762 from Bucharest to Oradea suffered an engine stall shortly after takeoff.
The left-hand engine (V2527) stalled during the initial climb from runway 26R at Bucharest Otopeni Airport, prompting the crew to declare PAN PAN.
The crew returned to Bucharest and landed safely on runway 26L approximately 15 minutes after departure.
There were no reported injuries, and the aircraft taxied to the apron without further incident.
Sequence of Events
Pre-Incident Conditions:
• Weather conditions at Bucharest Otopeni were reported as stable.
• The aircraft departed normally from runway 26R.
• No anomalies were reported prior to takeoff.
Incident During Climb:
• Shortly after departure, the crew experienced an engine stall in the left-hand V2527 engine.
• The crew declared PAN PAN, indicating an urgent but non-life-threatening situation.
• The right-hand engine remained operational, and the crew maintained control of the aircraft.
Decision to Return:
• The flight crew immediately coordinated with ATC for a return to Bucharest.
• The aircraft performed a safe landing on runway 26L approximately 15 minutes after departure.
• Emergency services were on standby but were not required.
Aftermath:
• The aircraft taxied to the apron under its own power.
• Engineers began an inspection of the affected engine.
• The flight was canceled, and passengers were rebooked on alternative flights.
Investigation & Findings
Possible Causes of the Incident:
While the official cause is still under investigation, potential factors include:
1. Compressor Stall: A sudden disruption in airflow within the engine compressor could have led to the stall.
2. Fuel Flow Issues: An irregular fuel supply might have affected engine performance.
3. Sensor Malfunction: A faulty engine parameter sensor could have triggered a false stall warning.
4. Foreign Object Ingestion (FOD): The engine may have ingested debris or a bird, leading to an airflow disruption.
Impact of the Incident:
• No injuries reported.
• Potential engine damage assessment ongoing.
• Flight cancellation, causing delays for passengers.
• Investigation by aviation authorities and airline maintenance teams.
Analysis & Safety Recommendations
For Airlines & Flight Crews:
• Enhance real-time engine monitoring to detect potential issues earlier.
• Refine response procedures for engine stalls to minimize operational impact.
• Review maintenance records for any prior signs of compressor or fuel system issues.
For Airports & Aviation Authorities:
• Monitor runway areas for possible FOD (Foreign Object Debris) to reduce the risk of engine ingestion.
• Ensure proper bird control measures around airports to prevent bird strikes leading to compressor stalls.
Conclusion
This incident highlights the importance of swift crew response and ATC coordination in handling engine malfunctions.
The crew’s decision to return to Bucharest ensured the safety of all passengers and prevented potential further damage to the aircraft.
An ongoing investigation will determine the root cause of the engine stall, with findings likely to inform future safety measures.
Disclaimer
“This report is based on available information as of 4 March 2025. While every effort has been made to ensure accuracy, the completeness of the details cannot be guaranteed. If you are the rightful owner of any referenced materials and wish them removed, please email takedown@cockpitking.com.”
