Probable cause
The pilot’s unstable approach which resulted in a landing with insufficient runway remaining to stop and subsequent impact with a river embankment. Contributing was the engine coolant system anomaly.
NTSB analysis
The pilot reported that after takeoff he climbed and proceeded to complete a circuit of the airport traffic pattern. While in the traffic pattern, he saw a puff of white smoke, indicative of burned coolant, near the rudder pedals and he elected to perform a precautionary landing. On approach to the runway the pilot was above the glide path but he elected to continue the approach. During the landing flare the engine lost power completely, and the airplane continued to float about ¾ of the way down the runway before touching down. As the airplane approached the end of the runway the pilot elected to force a “ground loop” to prevent the airplane from exiting the runway and going into a river.
A postaccident examination of the airplane by a Federal Aviation Administration (FAA) inspector found substantial damage to the fuselage from impact with the river embankment. The FAA inspector also noted that there was residual coolant in the cowling. The pilot reported that there was also residual coolant around the radiator cap. The pilot speculated that the automotive, rotary engine’s the rotor coolant seal may have been compromised, which allowing air from compression to enter the coolant system, and resulted in an over pressurization of this system and subsequent coolant expulsion through the radiator cap.
Text from the NTSB. Open the NTSB docket for ERA24LA355 for the full record.
Event
- Date
- Aug 14, 2024
- Type
- Accident
- Place
- Roxbury, Maine
- Nearest airport
- Thomas (ME17)
- Highest injury
- None
- Weather
- Visual (VMC)
- Light
- Day
Amateur-built AVIPRO BEARHAWK
- N-number
- N652BH
- Category
- Airplane
- Year built
- 2008
- Damage
- Substantial
- Operating rule
- Part 91 (general aviation)
- Purpose of flight
- Personal
From the NTSB aviation accident database: N-registered aircraft, events since 2008, data through Oct 28, 2026. The file is published monthly, so the latest weeks are incomplete and recent records can change. The official source is the NTSB aviation investigation search. CheckAero is independent and not affiliated with the NTSB.