76-Year-Old Pilot's Crash Landing Ends in Fire short of Runway

The Pilot Lost the View Before Losing the Engine

Besarick Skybolt N27265 was on the first flight of a 10-hour engine break-in period after an overhaul when the problem began. About 35 minutes into the flight, oil appeared on both windscreens and progressively blocked the pilot's forward view.

Accident Facts

The pilot contacted the tower. Controllers reported smoke coming from the engine, and the engine then lost partial power. The pilot could not make the runway and selected a field for the forced landing.

The airplane collided with a ditch after touchdown and the engine caught fire. The pilot escaped. A post-crash fire consumed most of the wreckage.

The Engine Was Already in Trouble

The NTSB found a large hole in the top of the engine case adjacent to the No. 2 cylinder. The No. 2 connecting rod had fractured at the crankshaft, and the investigation concluded that the failure was likely associated with oil starvation.

The extensive post-crash fire prevented investigators from identifying the exact source of the oil leak. That limitation is important. The probable cause identifies the substantial oil leak and connecting-rod failure, but the report does not pretend to know exactly where the leak originated.

The mechanical sequence therefore runs from oil loss to lubrication failure, connecting-rod failure and partial engine-power loss.

The NTSB's probable-cause statement was: “A substantial oil leak, which resulted in a partial loss of engine power and failure of the No. 2 connecting rod.”

The Windshield Problem Changed the Emergency

Engine failures are difficult enough without losing the pilot's forward view. Here, oil on the windscreens created a second emergency at the same time the engine was deteriorating.

The pilot had to judge the aircraft's position, select a landing area and manage the power loss with a progressively impaired view outside. Tower personnel were able to report smoke, but they could not remove the oil from the windscreen or restore engine performance.

The forced landing succeeded in getting the pilot out of the aircraft, even though the airplane was destroyed by the impact and subsequent fire.

Why the Engine Overhaul Matters

The accident occurred during the first flight of a 10-hour break-in period after the engine had been overhauled. The preflight inspection and ground operations had reportedly been normal, with no visible oil leaks.

That sequence is a reminder that a clean preflight does not guarantee that a recently disturbed engine will remain healthy under flight loads. The failure emerged after the aircraft had been airborne for roughly 35 minutes.

The investigation's evidence supports the oil-leak and connecting-rod chain. It does not support assigning a more specific overhaul error without evidence.

The Engine Failure Was More Than a Loss of Power

Oil on the windscreen provided an external warning before the engine stopped producing full power. That warning was also an operational hazard because it reduced forward visibility.

The investigation's evidence therefore connects the symptoms. The oil did not merely appear after the crash; it was already covering the windscreen in flight. The engine did not merely stop after impact; it suffered a connecting-rod failure associated with oil starvation before the forced landing.

The Post-Crash Fire Limited the Investigation

The distinction protects the accuracy of the article. The investigation established what failed and why the engine lost power, but not exactly where the oil escaped.

The Pilot's Escape Was the Final Successful Barrier

Once the engine lost power and the runway was unreachable, the pilot had very few options. The field landing was not gentle enough to preserve the airplane, but it allowed the pilot to exit before the post-crash fire consumed the wreckage.

The sequence also shows why an emergency landing site should be evaluated for survivability rather than aircraft preservation. The aircraft was destroyed, but the pilot survived. In a single-engine forced landing with poor forward visibility, that is the primary safety objective.

The Timing of the Failure Made the Visibility Loss Critical

The oil first appeared about 35 minutes into the flight, after the airplane had already completed the initial climb and was in the break-in phase of the flight. The pilot therefore had to react while the engine condition and forward visibility were deteriorating together.

The tower's observation of smoke provided an independent confirmation that the engine problem was visible from outside the aircraft as well. The forced landing was therefore a response to a developing mechanical emergency, not an unexplained sudden crash.

Conclusion

N27265's crash was driven by two linked problems: a substantial oil leak that damaged the engine's lubrication system and an oil-covered windscreen that reduced the pilot's ability to see.

The NTSB's final finding gives the mechanical chain a clear endpoint while acknowledging that fire damage prevented identification of the leak's exact source. The pilot's successful escape was the final positive outcome in an otherwise rapidly deteriorating engine emergency.

Sources

• Video source (ATC/audio reconstruction)