DFW05FA170 · Beech E90
Beech E90 · Accident: loss of control in flight on approach
From Jonesboro Municipal Airport (KJBR) to False River Regional Airport (KHZR)
Event
- NTSB case
- DFW05FA170
- 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
- 5 · all aircraft and ground
- Ground fatalities
- Unknown
- 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
Beech E90
- Aircraft type
- Beechcraft 90
- 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
- N62BL
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Jonesboro Municipal Airport (KJBR), Jonesboro, ARTo False River Regional Airport (KHZR), New Roads, LA
- Aircraft age
- Not recorded
- 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
- Approach · VFR go-around
- First occurrenceThe 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 in flight
- 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
- Stall
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Airspeed, not maintained
- Pilot in command › Stall, inadvertent
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
A 4,000-hour multi-engine private pilot lost control of the airplane while performing a go-around maneuver. The airplane subsequently pitched up, stalled and impacted a corn field in a nose low attitude where a post-impact fire ensued. Communications data and radar data compatible with the Radar Audio Playback Terminal Operations Recording (RAPTOR) program was used to plot the airplane's flight path on a topographical map. The plots appeared to indicate the airplane was on final, left of the extended runway 36 centerline. Detailed post-accident examinations of the airframe, engines and propellers were conducted and no anomalies were noted.
Probable cause
The pilot's failure to maintain airspeed and subsequent loss of control during a go-around maneuver.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record DFW05FA170
- Event ID
- 20050706X00940
- Case number
- DFW05FA170
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2005-06-24.
- API snapshot SHA-256: 1d14afcea7e62af216431dca0e9732c46750c7d1d763609b0d9393f0164c7e8b; retrieved 2026-09-20T18:00:27.341Z.