Ryanair 737 Fan Blade Separated 253 Cycles After Inspection; Debris Broke Window
A fan blade in the right engine of a Ryanair-operated Boeing 737-800 separated only 253 flight cycles after an inspection found no defect, sending fragments into the airframe and breaking a passenger window. The National Transportation Safety Board’s preliminary investigation update establishes the physical failure and damage but does not yet establish what initiated the blade fracture or why the recent inspections produced no findings.
Malta Air Flight 1879, operating for Ryanair from Thessaloniki, Greece, to Memmingen, Germany, was climbing at about 16,000 feet on July 10 when the crew received a right-engine vibration warning. The pilots reduced power and began the applicable checklist, but the vibration subsequently increased. A loud bang was followed by the autopilot disconnecting and a cabin-altitude warning activating. The crew donned oxygen masks, declared an emergency, descended and returned safely to Thessaloniki.
Investigators found that the right CFM International CFM56-7B26 engine had sustained a fan-blade separation. One blade fractured below its platform, two other blades lost portions of their outer tips, and three loose blade fragments were recovered inside the engine. Fragments struck the fuselage and right horizontal stabilizer, including the row 11 window area and a lower fuselage section behind the right wing-to-body fairing.
The window beside seat 11F was lost, and the occupant was found partially lodged in the opening before other passengers pulled the person back into the cabin. One passenger suffered serious injuries. The other 148 passengers and six crew members were not injured.
The inspection history is important, but not yet explanatory
Maintenance records show that the engine’s fan blades underwent inspections on Nov. 11, 2025, and May 24, 2026. Neither produced a finding, and the second inspection occurred 253 cycles before the accident. Those facts create a central investigative question, but they do not by themselves demonstrate that an inspection was performed incorrectly or that the prescribed method was inadequate.
A clean inspection result establishes only that no reportable indication was identified using the applicable procedure at that time. Investigators still need to determine whether the fracture originated from damage that existed but was not detectable, damage that developed later, or another mechanism. The timing and character of crack development, the blade’s material condition and the relationship between the recovered fragments will be critical to separating those possibilities.
The engine also had four suspected bird-strike reports during the preceding 12 months. Follow-up checks found no engine damage. After the July accident, investigators recovered feathers and other bird remains from the oil cooler, fan case and thrust-reverser components, and samples were sent to the Smithsonian Institution’s Feather Identification Lab.
That discovery makes bird ingestion an investigative subject, not an established cause. The preliminary information does not determine when the remains entered the engine, whether an ingestion event damaged the blade, or whether it had any causal role in the separation. Treating the remains as proof of a bird-initiated failure would move beyond what investigators have confirmed.
A separate FAA proposal should not be mistaken for a finding
The inspection context is broader than this aircraft. The FAA has proposed revised requirements for CFM56-7B fan-blade inspections, including updated ultrasonic procedures and an expanded inspection area intended to improve crack detection. If adopted, the directive would apply to an estimated 4,553 engines on U.S.-registered aircraft and retain initial and repetitive ultrasonic or eddy-current inspections of specified fan blades.
However, the FAA explicitly said it had received no factual information indicating that the Ryanair event was related to the unsafe condition addressed by that proposal. The rulemaking grew from inspection improvements developed after an earlier CFM56-7B blade failure; mentioning the July event in the regulatory notice does not make the proposal a corrective action for Flight 1879.
The NTSB is examining possible similarities with earlier failures involving comparable engines, including the 2018 Southwest Airlines accident, but no connection has been established. Similar outward consequences blade separation, airframe impacts and loss of cabin pressure do not prove a common fracture mechanism.
The investigation must now reconcile three documented facts: a blade separated below its platform, bird remains were present in several engine areas, and two inspections had reported no findings, including one only 253 cycles earlier. Until laboratory examination and maintenance analysis establish how those facts relate, the initiating mechanism and the meaning of the clean inspection history remain unresolved.
By Thomas Caldwell — AMI’s senior editor for mechanical and mobility engineering, covering vehicle electronics, systems integration, electrification, chassis systems, propulsion, and safety policy.
