A 2005 Cessna 172S operating out of Rochester International Airport suffered a cascading in-flight emergency on May 28th that progressed from cockpit smoke to fire, oil-obscured windscreen, catastrophic engine failure, and ultimately propeller separation — all within minutes of departure. The aircraft, N225RA, was conducting a local instructional flight with CFI Scott Murphy and a student early in his training when the sequence began at approximately 3,500 feet MSL, roughly 6 miles northeast of Ledgedale Airport (7G0). Despite deteriorating conditions including loss of forward visibility through an oil-covered windscreen, Murphy declared a Mayday, coordinated professionally with Rochester Approach, and successfully glided the aircraft to a safe landing at Ledgedale. No injuries or fatalities were reported. The propeller and spinner were later found largely intact in a residential yard, with evidence of tree strike suggesting some rotational energy remained at separation.
The aerodynamic dimension of this incident carries significant instructional weight for pilots across all categories. The Cessna 172S POH predicts approximately 4.5 nautical miles of glide range under standard conditions with a windmilling propeller at 68 knots — yet Murphy covered 6 statute miles in the glide. The analysis credits the separated propeller as the primary performance variable: without the prop, the aircraft shed the substantial parasitic drag of a windmilling blade assembly. This aligns with documented flight testing conducted by AOPA contributor Barry Schiff in 2011, in which deliberately stopped props on 172s produced a 20-percent improvement in glide distance. A prop physically absent from the airframe likely produces an even more dramatic drag reduction. A modest tailwind component from the northwest-to-north flow may have contributed marginally, but the drag elimination from prop loss appears to be the dominant factor in why the aircraft outperformed its published glide specs.
The communications conduct of CFI Murphy during this emergency warrants particular attention from flight instructors and training operators. ATC audio captured a calm, measured sequence of Mayday calls, clear situation reports, and specific requests — all while managing a student, navigating without forward visibility, and executing a forced landing approach to an unfamiliar airport. Murphy's professionalism illustrates the value of scenario-based emergency training and cockpit resource management doctrine, particularly for instructors who must manage emergencies while simultaneously serving as crew resource for a low-time student. The fact that Rochester Approach was providing VFR flight following at the time also proved critical: Murphy had an active frequency, immediate radar contact, and ATC proximity awareness that facilitated vectors and traffic separation during the emergency descent.
This incident reinforces several systemic lessons for flight training operations. The progression from smoke to fire to engine failure to prop separation happened rapidly, underscoring the importance of immediate smoke-in-cockpit checklists and early Mayday declarations rather than extended troubleshooting at altitude. For Part 61 and Part 141 training organizations operating piston singles, this event is a reminder that even routine local instructional flights under benign VMC conditions can deteriorate without warning, and that practice area altitudes and proximity to suitable landing areas should be part of pre-departure route planning. The incident also contributes, however anecdotally, to a thin but meaningful body of data on prop-off glide performance — a scenario the POH does not address and that most pilots have never considered. Emergency procedures typically instruct pilots to attempt a restart or feather to reduce windmilling drag, but in a prop-separation scenario the aerodynamic environment changes entirely, and pilots should understand that their glide performance may actually improve beyond published figures.
The broader context here is the reliability profile of piston training fleets, particularly aging singles operated at high cycle rates. The Lycoming IO-360 series is among the most widely operated engines in general aviation, with an excellent overall service record, but training aircraft accumulate time and cycles rapidly, and catastrophic failures — while rare — are not unprecedented. Aviation Safety Institute analysis of FlightAware track data and ATC audio as part of early incident review reflects an increasingly valuable practice of correlating surveillance and voice data to reconstruct accident geometry, a methodology that enhances the quality of safety reporting and crew performance evaluation. As the NTSB investigation proceeds, the findings on the root cause of the engine failure and prop separation will be critical to determining whether maintenance factors, operational anomalies, or manufacturing discrepancies contributed — information that will be directly relevant to operators of the same airframe and powerplant combination across the training and light-aircraft fleet.