CEN23FA369 · Piper J5A
Piper J5A · Accident: loss of control on ground during landing
From Escanaba, MI to an unrecorded destination
Event
- NTSB case
- CEN23FA369
- 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
Piper J5A
- Aircraft type
- Piper J5
- 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
- N35417
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Escanaba, MITo not recorded
- Aircraft age
- About 82 years (built 1941)
- 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
- Landing · landing roll
- Defining eventThe 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 on ground
- 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
- Aircraft › Aircraft oper/perf/capability
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The 78-year-old pilot had flown his airplane to the destination airport where an annual inspection was to be performed. The airplane did not have a current annual inspection and did not have a ferry permit for the accident flight. No record of a current flight review for the pilot was found. In addition, the pilot did not possess current FAA medical certification or BasicMed qualifications. Recorded GPS device data showed the airplane made several turns around the airport and then proceeded in the direction of and onto a grass taxiway with a prevailing tailwind, where it was found nosed over. There were no witnesses to the accident. There were no indications of ground scars or rotational features on the propeller and spinner indicative of engine power production. Although the airplane’s right front brake master cylinder arm had a bungee cord tied around it that connected to the pilot seat frame, the brakes actuated and released without anomaly. Examination of the airplane revealed no useable fuel aboard; however, the airplane’s flight path indicated that it circled the airport multiple times before landing, indicating that the flight had adequate fuel to reach and land at the airport. No mechanical anomalies were found that would have precluded normal operation. Although the pilot’s cardiovascular disease placed him at increased risk of an impairing or incapacitating medical event such as heart attack, arrhythmia, or stroke, there was no autopsy evidence that such an event occurred, and such an event does not reliably leave autopsy evidence if it occurs just before death. Toxicology results indicated that the pilot had used the opioid pain medication tramadol and likely was experiencing some effects of tramadol at the time of the accident. Although details of the pilot’s tramadol use are unknown, there is no specific evidence that this use was significantly different from the pilot’s baseline use of tramadol, which had begun years previously. Toxicology results also indicated that the pilot had used venlafaxine and a cannabis product. The measured postmortem levels of the substances in the pilot’s system at the time of the accident neither exclude nor specifically predict any impairing effects, especially in combination with one another and considering the pilot’s age and medical conditions. Based on the evidence, the pilot likely did not maintain control of the airplane after landing on a grass taxiway with a tailwind. Whether the impairing effects of the pilot’s substance use and medical conditions contributed to the accident could not be determined.
Probable cause
The pilot’s failure to maintain control of the airplane after landing on a grass taxiway with a tailwind, which resulted in a nose over.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN23FA369
- Event ID
- 20230819192898
- Case number
- CEN23FA369
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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, cause areas. 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: 0d744583847be93ba407b2926164706b70ff2a9774c0618279b07fa7f1e2c4f5; retrieved 2026-09-15T08:04:56.919Z.