CEN23LA265 · Bearhawk Aircraft Model 5
Bearhawk Aircraft Model 5 · Accident: loss of control on ground during landing
From Center Municipal Airport (F17) to an unrecorded destination
Event
- NTSB case
- CEN23LA265
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- 0
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Bearhawk Aircraft Model 5
- Aircraft type
- Bearhawk MODEL 5
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N619MS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Center Municipal Airport (F17), Center, TXTo not recorded
- Aircraft age
- About 3 years (built 2020)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · landing roll
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Loss of control on ground
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Physical environment
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot reported that he performed a landing to a remote private grass airstrip surrounded by about 80 ft tall trees, on all sides. At about 40 mph during the rollout on the dry grass, a “strong wind gust lifted the right wing.” The pilot applied full right aileron and full right rudder, but they had “no effect,” nor was the right brake “effective.” The airplane departed the runway, impacted a hangar, and came to rest upright. The pilot and passenger were able to egress from the airplane without further incident. The airplane sustained substantial damage to the fuselage and the right wing. The pilot reported there were no preimpact mechanical malfunctions or failures with the airframe or the engine that would have precluded normal operation. The pilot further reported that he did not initiate a go-around due to the airstrip being “narrow” and both the tall trees and the hangar “being in the way.”
Probable cause
The pilot’s failure to maintain directional control during the rollout, which resulted in a runway excursion, and a collision with a building. Contributing to the accident were the obstacles at the airstrip that prevented the pilot from performing a go-around.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN23LA265
- Event ID
- 20230626192459
- Case number
- CEN23LA265
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, cause areas. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: bf22e4a504932d0b2002569b10a2146fdc6240dc13f8148755d3743f1d357446; retrieved 2026-09-16T17:46:27.198Z.