CHI94DCJ01 · Mustari DRAGONFLY MARK II DRAGONFLY
Mustari DRAGONFLY MARK II DRAGONFLY · Accident: in flight collision with object en route
From an unrecorded airport to Hastings Municipal Airport (HSI)
Event
- NTSB case
- CHI94DCJ01
- 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
Mustari DRAGONFLY MARK II DRAGONFLY
- Aircraft type
- Mustari DRAGONFLY MARK
- 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
- N3147B
- Operator
- Fowler, Kevin A. · private individual
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Hastings Municipal Airport (HSI), Hastings, NE
- 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 · climb to 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
- In flight collision with object
- 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
- Wire, transmission
- 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 › Preflight planning/preparation, inadequate
Approximate · Estimated position: the centre of Scottsbluff, NE, the place the record names. Not the accident site.
NTSB narrative
THE PILOT REPORTED DURING DEPARTURE THE HOMEBUILT AIRPLANE REACHED ABOUT 150 TO 200 FEET ABOVE THE GROUND, AND WOULDN'T CLIMB ANY FURTHER. HE ATTEMPTED TO RETURN TO THE AIRPORT, BUT THE AIRPLANE STRUCK POWER LINES AND CAME TO REST IN A SOYBEAN FIELD. THE PILOT REPORTED THE TEMPERATURE WAS 92 DEGREES FAHRENHEIT AT THE TIME OF THE ACCIDENT, AND THE AIRPORT ELEVATION IS 3,965 FEET. HE STATED HE COULD HAVE AVOIDED THE ACCIDENT 'BY RESTRICTING MY FLIGHTS TO LOWER ELEVATION AIRPORTS WHEN TEMP. IS ABOVE 90 DEGREES.'
Probable cause
the private pilot's inadequate preflight planning/preparation. A related factor is the high density altitude.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI94DCJ01
- Event ID
- 20001206X01480
- Case number
- CHI94DCJ01
- 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: 72f25e984d477a6e6335d3329e91c0b9378403f2f44f25f6ae8ccc2df400493a; retrieved 2026-09-21T13:50:28.778Z.