Incident Overview
On January 8th, 2025, an EgyptAir Boeing 737-800, registration SU-GDZ, operating flight MS-852 from Addis Ababa (Ethiopia) to Cairo (Egypt), encountered an engine failure while cruising at FL380 approximately 120nm northwest of Jeddah, Saudi Arabia. The engine (CFM56) experienced a stall, causing severe vibrations. The crew responded by reducing thrust to stabilize the situation and initiated a diversion to Jeddah. The aircraft landed safely on Jeddah’s runway 16C approximately 30 minutes after leaving cruising altitude.
Post-landing inspection revealed significant damage to the affected engine, which had seized. The aircraft remains grounded in Jeddah as of 57 hours post-incident.
Sequence of Events
1. Cruise Flight at FL380:
• The flight was proceeding normally until the left-hand engine experienced a stall, leading to severe vibrations.
• Engine parameters indicated abnormal performance, prompting the crew to take immediate action.
2. Emergency Action by Crew:
• The crew reduced thrust on the affected engine to mitigate the vibrations and prevent further damage.
• They declared an emergency and coordinated with air traffic control for a diversion to Jeddah.
3. Diversion and Landing:
• The aircraft descended from FL380 and landed safely on Jeddah’s runway 16C.
• Emergency services were on standby, but no injuries or further complications were reported.
4. Post-Landing Inspection:
• Maintenance teams discovered substantial damage to the engine, including a seized condition.
• The aircraft was deemed unfit for further operation and remains grounded.
Technical Analysis
• Engine Stall:
• Likely caused by either an internal failure, ingestion of foreign objects, or mechanical wear.
• The vibration suggests damage to rotating components, potentially the compressor or turbine stages.
• Engine Seizure:
• Indicates catastrophic failure involving significant mechanical damage, such as fractured blades or bearings.
• Crew Response:
• Proper application of emergency procedures ensured the aircraft’s safe return to an alternate airport.
• Reducing engine thrust minimized vibrations and prevented escalation of the failure.
Passenger Impact
• Passengers were rebooked onto two separate flights from Jeddah to Cairo.
• EgyptAir provided accommodations and assistance during the delay.
Safety Recommendations
1. Engine Inspections:
• Comprehensive inspection and teardown of the failed engine to identify root causes.
• Review maintenance history for potential indicators of wear or prior anomalies.
2. Fleet Monitoring:
• Conduct targeted inspections of similar engines across the EgyptAir fleet for early detection of similar issues.
3. Emergency Training:
• Reinforce engine failure and in-flight vibration response protocols for flight crews.
4. Incident Reporting:
• Ensure timely reporting to regulatory authorities and engine manufacturers for detailed investigation.
Conclusion
The swift actions of the crew ensured the safety of all onboard, preventing a potentially catastrophic outcome. The engine failure underscores the importance of rigorous maintenance practices and real-time monitoring of engine health. Investigations are ongoing to determine the precise cause of the failure.
Disclaimer:
This report is based on facts and observations available as of January 10th, 2025. While efforts have been made to ensure accuracy, findings remain subject to ongoing investigations. If you are the rightful owner of referenced materials and wish to raise concerns, contact takedown@cockpitking.com.
