MIA90FA060 · Piper J-3
Piper J-3 · Accident: loss of control in flight
Event
- NTSB case
- MIA90FA060
- 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
- 2 · 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
Piper J-3
- Aircraft type
- Piper J-3
- 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
- N88125
- Operator
- Nesbitt, James K. · private individual
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 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
- Unknown
- 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 › Aircraft preflight, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING UNK PHASE OF FLT, PLT LOST CONTROL OF THE ACFT. IT DESCENDED WINGS LEVEL, 45 DEG NOSE LOW, IMPACTED TERRAIN, & WAS DESTROYED BY FIRE. EXAM OF ACFT REVEALED THE REAR SEAT (PLT) CONTROL STICK WAS LYING IN THE WRECKAGE. EXAM OF IT REVEALED NO IMPACT DAMAGE NOR WAS THERE EVIDENCE THAT A BOLT & NUT, USED TO SECURE IT, WAS INSTALLED. PLT REPORTEDLY REMOVED THE NUT & BOLT & SANDED THE INSIDE OF THE STICK TO FACILITATE REMOVAL. THE FLIGHT CONTROLS OPERATIONALLY CHECKED GOOD. THE FRONT SEAT CONTROL STICK WAS INSTALLED BUT NOT SECURED. ENG & PROP WERE REMOVED FOR FURTHER EXAM. EXAM OF THE ENG REVEALED VALVE CONTINUITY & COMPRESSION SUFFICIENT TO SUSTAIN ENG OPERATION. FIRE DAMAGED THE MAGS, IGNITION HARNESSES, & CARB. SPARK PLUGS WERE OPERATIONALLY TESTED, ONLY 1 TESTED GOOD. ACFT & ENG LOGBOOKS NOT LOCATED. FUEL QUANTITY WAS SUFFICIENT.
Probable cause
FAILURE OF THE PILOT TO SECURE THE FLIGHT CONTROL STICK (INADEQUATE PREFLIGHT) BEFORE TAKEOFF.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA90FA060
- Event ID
- 20001212X22450
- Case number
- MIA90FA060
- 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: e2a794fd5b146818e0f2da3a0a63bb81ebd481e79a01dddcf869452a6ab95d6d; retrieved 2026-09-21T03:01:07.383Z.