CHI04LA002 · Goldman Dragonfly
Goldman Dragonfly · Accident: partial loss of engine power (non-mechanical) en route
From Kenosha Regional Airport (ENW) to General Wayne A. Downing Peoria International Airport (PIA)
Event
- NTSB case
- CHI04LA002
- 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
- Visual Meteorological Cond
Goldman Dragonfly
- Aircraft type
- Goldman DRAGONFLY
- 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
- N222TH
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Kenosha Regional Airport (ENW), Kenosha, WITo General Wayne A. Downing Peoria International Airport (PIA), Peoria, IL
- 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 · descent
- 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
- Partial 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
- Stall/mush
- 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 › Airspeed, not maintained
- Pilot in command › Proper descent rate, not maintained
- Pilot in command › Stall/mush, inadvertent
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The amateur-built experimental airplane was substantially damaged during a forced landing following a partial loss of engine power. The pilot reported that he was in an en route descent when he advanced the throttle in order to level off. However, the engine did not respond and remained at idle power. His attempts to restore useful power were not successful. He set up for a forced landing. As he turned final, about 50 feet above ground level, he "felt the canard stall with its characteristic nose down bob." He reportedly pushed the nose down and "felt the canard resume flying." The pilot pulled back, raising the nose as the aircraft "pancaked into the ground." The aircraft slid approximately 300 feet on the grass before coming to rest. After the aircraft came to a stop, the pilot noted the engine was "still ticking over smoothly as it had been throughout this experience." He reported that he advanced the throttle once again to see if the engine would respond, however, it did not. A post-accident inspection was conducted. The aircraft was powered by an electronic fuel injected, rotary engine. Control continuity from the cockpit to the engine was verified and no anomalies were noted. Internal engine continuity was verified by propeller shaft/crankshaft rotation. Fuel was present at the inlet and outlet to the filter and the filter itself was clean. Fuel was present in the fuel tanks and appeared to be uncontaminated. The throttle body was intact and appeared fully functional. The manifold pressure orifices at the throttle body and the tubing from each orifice to the manifold pressure sensor was intact and unobstructed. The wiring harness between the sensor and electronic control unit (ECU), including the connectors and connector pins, appeared undamaged. The manifold pressure sensors were tested and functioned properly. The ECU controlled ignition and fuel metering to the engine. According to the manufacturer, a sensor reads manifold pressure at the throttle body. This is provided to the ECU in order to control fuel metering.
Probable cause
The loss of power for undetermined reasons and the inadvertent stall of the canard by the pilot on the turn to final during the forced landing, as well as the excessive descent rate causing the aircraft to "pancake" into the ground.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI04LA002
- Event ID
- 20031010X01707
- Case number
- CHI04LA002
- 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, coordinates. 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: f8fd008531004d0f237b7ce22901e202ef40eefb62ed8f78397585381798ac41; retrieved 2026-09-21T19:21:08.399Z.