NYC03LA090 · Starnes Quickie Q-200
Starnes Quickie Q-200 · Accident: loss of control in flight during takeoff
From Henderson City County Airport (EHR) to EHR
Event
- NTSB case
- NYC03LA090
- 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
- 1 · 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
Starnes Quickie Q-200
- Aircraft type
- Starnes QUICKIE Q-200
- 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
- N1V
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Henderson City County Airport (EHR), Henderson, KYTo EHR
- 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
- Takeoff · rejected takeoff
- 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
- Loss of control in flight
- 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 › Directional control, not maintained
- Pilot in command › Recovery from bounced landing, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The accident flight was the first flight for the airplane. As the airplane departed, it climbed to an altitude of about 30 feet, and began to porpoise. It then descended towards the runway, touched down hard, and the propeller struck the asphalt. The airplane bounced back into the air, and traveled for a short distance, before touching down hard again. It then veered off the left side of the runway, rolled over on it's left side, and came to rest inverted. A post crash fire ensued and consumed the wreckage. According to witnesses, the pilot had performed several hours of high-speed taxi runs with the accident airplane before the day of the accident. On the day of the accident, the pilot again performed high-speed taxi tests, and determined that the engine "sounded good and the airplane handled steady." Inspection of the wreckage revealed no abnormalities with the engine or airframe.
Probable cause
The pilot's improper recovery from a bounced landing and his failure to maintain directional control, after experiencing an in-flight loss of control for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC03LA090
- Event ID
- 20030514X00658
- Case number
- NYC03LA090
- 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: 56f3000a5fb0937ceeae38f257991d0c0168e128b9544cc5347baf5f8ff43fce; retrieved 2026-09-20T19:16:14.134Z.