CHI91DEX02 · Hagg STARDUSTER TOO STARDUSTER
Hagg STARDUSTER TOO STARDUSTER · Accident: total loss of engine power (non-mechanical) en route
From I52 · Indianapolis, IN to 35M · IN
Event
- NTSB case
- CHI91DEX02
- 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
Hagg STARDUSTER TOO STARDUSTER
- Aircraft type
- Hagg STARDUSTER TOO
- 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
- N224JH
- Operator
- Jeffery Hagg
- Onboard fatalities
- Unknown
- Route
- From I52 · Indianapolis, INTo 35M · IN
- 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
- En route · cruise
- 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
- Total loss of engine power (non-mechanical)
- 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
- Fuel exhaustion
- 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
- Pilot in command › Fuel consumption calculations, inaccurate
- Pilot in command › Preflight planning/preparation, inadequate
- Pilot in command › Refueling, not performed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
PILOT FUELED THE AIRCRAFT WITH 9 GALLONS OF FUEL, TOOK OFF, AND WENT SIGHTSEEING FOR ABOUT AN HOUR, AND LANDED AT ANOTHER FIELD. HE GAVE RIDES TO THREE PERSONS WHILE HE WAS THERE. PILOT THEN TOOK OFF TO RETURN TO HIS POINT OF ORIGIN. APPROXIMATELY 45 MINUTES LATER HE EXPERIENCED A TOTAL LOSS OF ENGINE POWER, AND ATTEMPTED TO MAKE A FORCED LANDING IN A PLOWED CORN FIELD PERPENDICULAR TO THE FURROWS. RIGHT MAIN LANDING GEAR DUG IN AND COLLAPSED ON LANDING ROLL. INVESTIGATION REVEALED NO FUEL IN AIRCRAFT. PILOT HAD FLOWN FOR 2.1 HOURS SINCE HIS ORIGINAL TAKEOFF, AND STATED THAT HE THOUGHT HE HAD FUEL FOR ANOTHER HOUR OF FLIGHT TIME WHEN THE MISHAP OCCURRED. FUEL WAS AVAILABLE AT BOTH AIRFIELDS HE WAS USING.
Probable cause
THE PILOT'S INADEQUATE PREFLIGHT PLANNING/PREPARATION, NOT REFUELING THE AIRCRAFT BEFORE TAKING OFF ON THIS FLIGHT, AND INACCURATE FUEL CONSUMPTION CALCULATIONS. A FACTOR RELATED TO THE ACCIDENT IS THE UNSUITABLE TERRAIN SELECTED BY THE PILOT FOR A FORCED LANDING.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI91DEX02
- Event ID
- 20001212X16417
- Case number
- CHI91DEX02
- 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: investigation status. 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: 20c2473fcf02d6412bb3bcdf5ba792ae40b4a690e09018c00f005bf0de890103; retrieved 2026-09-23T04:48:46.330Z.