Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

October 3, 2003 · Goldman Dragonfly · N222TH

Peoria, IL

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
October 3, 2003
Injury Outcomes
1 injury (1 minor injury)
Location
Peoria, IL
Aircraft
Goldman Dragonfly
Tail Number
N222TH
Injuries
Minor
Aircraft Damage
Substantial
NTSB Number
CHI04LA002

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.

NTSB 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.

Full Narrative

On October 3, 2003, at 1045 central daylight time, an amateur-built Goldman Dragonfly, N222TH, piloted by a private pilot, was substantially damaged during a forced landing following a partial loss of engine power 7 miles north of the Greater Peoria Regional Airport (PIA), in Peoria, Illinois. The personal flight was conducted under 14 CFR Part 91 and was not on a flight plan. Visual meteorological conditions prevailed at the time of the accident. The pilot reported minor injuries. The flight departed the Kenosha Regional Airport, Kenosha, Wisconsin, at 0900, with an intended destination of PIA. In the pilot's written statement, he 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. The pilot stated that he was in contact with PIA approach control at the time and was given a vector to Mt. Hawley airport approximately 1-1/2 miles from his present position. However, he judged that he would not be able to make that airport so he selected an apparently smooth field within gliding distance. He noted that as he turned final for this field, 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." At this point, the pilot stated he 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. According to the pilot, throughout the event fuel pressure indications were normal. Application of alternate heated induction air and resetting the engine's Electronic Control Unit (ECU) had no effect. The ECU did not present any fault indications during or after the accident sequence. 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 sensors and 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, the sensor reads manifold pressure at the throttle body. This is provided to the ECU in order to control fuel metering.

Flight

Event TypeAccident
Event Time10:45 CDT
Nearest Airport0nm
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftGoldman Dragonfly
Tail NumberN222TH
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsMid-West Engines · AE-110-R · Reciprocating · 105
Seats2

People & Injuries

Injury Summary1 injury (1 minor injury)
Fatal0
Serious0
Minor1
Uninjured0
Total1
Crew 1Age 59 · Second Class · Minor

Conditions

ConditionsVMC
LightDaylight
Wind210° @ 15 kt
Visibility10 sm
CeilingBroken clouds 5000 ft
Temperature / Dew Point48 / 37 C
Altimeter29.86 inHg
Observation Time15:54
Weather SourceWFAC

Appendix: Source Data