ERA10CA093 · Rockwell International 114
Staples Investment Group Rockwell International 114 · Accident: ground collision during landing
From Monroe Walton County Airport (D73) to Shelby County Airport (EET)
Event
- NTSB case
- ERA10CA093
- 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
- 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
- Instrument Meteorological Cond
Rockwell International 114
- Aircraft type
- Rockwell 114
- 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
- N5872N
- Operator
- Staples Investment Group
- Onboard fatalities
- Unknown
- Route
- From Monroe Walton County Airport (D73), Monroe, GATo Shelby County Airport (EET), Alabaster, AL
- 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
- Landing
- 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
- Ground collision
- 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 › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that he was conducting an instrument-flight-rules flight with an estimated flight time of 1 hour and 33 minutes. He encountered unanticipated headwinds along the route of flight, and as he neared his destination airport he learned that weather conditions had deteriorated below minimums. The pilot diverted to a nearby airport, but was unable to complete the approach due to a windshear encounter. He then diverted to a third airport and reported that he was concerned about the airplane's available fuel. The pilot again aborted his first approach due to a windshear encounter and during a subsequent approach the airplane experienced a total loss of engine power due to fuel exhaustion. The pilot performed a forced landing to a field prior to the runway. The airplane's nose and left main landing gears collapsed upon contact with a ditch, which resulted in substantial damage to the left wing.
Probable cause
A total loss of engine power due to fuel exhaustion as a result of the pilot’s inadequate preflight fuel planning.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA10CA093
- Event ID
- 20091209X22636
- Case number
- ERA10CA093
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2009-12-09.
- API snapshot SHA-256: e9b72d3b8311ad88cb16e51da60d2fb2234ff3c855aa7a40f10ca8530bf1449d; retrieved 2026-09-15T13:33:41.557Z.