Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

August 14, 2024 · Yates Elden H Avipro Bearhawk · N652BH

Roxbury, ME

Overview

Report Status
Probable Cause
Event Type
Accident
Date
August 14, 2024
Injury Outcomes
No injuries (1 uninjured)
Location
Roxbury, ME
Aircraft
Yates Elden H Avipro Bearhawk (2008)
Tail Number
N652BH
Injuries
None
Aircraft Damage
Substantial
NTSB Number
ERA24LA355

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 rotor coolant seal may have been compromised, which allowed 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.

NTSB 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.

Full Narrative

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.

Flight

Event TypeAccident
Event Time11:30 EDT
Nearest AirportTHOMAS (0.2nm NNE)
Runway01
Runway Length1800 ft
Runway Width75 ft
Flight Plan FiledNone
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftYates Elden H Avipro Bearhawk
Tail NumberN652BH
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsMazda · 13B · Reciprocating · 146
Seats4

People & Injuries

Injury SummaryNo injuries (1 uninjured)
Fatal0
Serious0
Minor0
Uninjured1
Total1
Crew 1Age 66 · Third Class · None

Conditions

ConditionsVMC
LightDaylight
Wind180° @ 3 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point59 F
Altimeter30.10 inHg
Observation Time11:15
Weather SourceWFAC

Appendix: Source Data