CHI90DEX02 · Johnson QUICKIE 299 QUICKIE 29
Johnson QUICKIE 299 QUICKIE 29 · Accident: airframe, component or system failure during takeoff
From 1L9 · Delphi, IN to an unrecorded destination
Event
- NTSB case
- CHI90DEX02
- 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
Johnson QUICKIE 299 QUICKIE 29
- Aircraft type
- Johnson QUICKIE 299
- 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
- N42LQ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 1L9 · Delphi, INTo not recorded
- 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
- 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
- Airframe, component or system failure
- 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 › Maintenance, installation, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT REPORTED THAT IMMEDIATELY AFTER TAKEOFF THE AIRPLANE TENDED TO ROLL INVERTED. WITH AN INCREASE IN AIRSPEED, THE PILOT WAS ABLE TO CONTROL THE ROLL TENDENCY, BUT STATED A HEAVY RIGHT YAW EXISTED. APRX 3/4 OF A MILE FROM THE AIRPORT, THE ENGINE BEGAN RUNNING ROUGH, SO THE PILOT RETURNED TO THE AIRPORT. A GO-AROUND WAS MADE DURING THE FIRST APPROACH DUE TO EXCESSIVE AIRSPEED. THE PILOT SHUT DOWN THE ENGINE ON SHORT FINAL OF THE SECOND APPROACH. ON TOUCHDOWN, THE AIRPLANE TRAVELED (BOUNCING) OFF THE RIGHT SIDE OF THE RUNWAY INTO THE GRASS AND CORN CROP. POST-ACCIDENT INSPECTION REVEALED THE RIGHT RUDDER CABLE WAS DISCONNECTED AT THE MODIFIED TURNBUCKLE INSTALLATION. THE PILOT, ALSO THE MECHANIC, REPORTED THE COTTER PIN WAS LEFT OUT ALLOWING THE BOLT AND NUT CONNECTOR TO BACK OUT.
Probable cause
PILOT/MECHANIC'S IMPROPER INSTALLATION OF THE RUDDER CABLE TURNBUCKLES.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI90DEX02
- Event ID
- 20001212X23923
- Case number
- CHI90DEX02
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1990-08-26.
- API snapshot SHA-256: c157ac4d36e97a8eb2e2888e2534bdb4271582fedb187ed43eb9a9d218fd678a; retrieved 2026-09-23T05:22:49.658Z.