FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN14LA086 · Piper PA-22-108

11 Dec 2013 · Oscoda, MI, United States

Piper PA-22-108 · Accident: loss of control on ground during landing

From Oscoda Wurtsmith Airport (OSC) to Oscoda Wurtsmith Airport (OSC)

Report a problem

Event

NTSB case
CEN14LA086
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
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 PA-22-108

Aircraft type
Piper PA-22
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
N5386Z
Operator
Unknown
Onboard fatalities
Unknown
Route
From Oscoda Wurtsmith Airport (OSC), Oscoda, MITo Oscoda Wurtsmith Airport (OSC), Oscoda, MI
Aircraft age
About 52 years (built 1961)
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
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
  • Personnel issues › Action/decision
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The student pilot was conducting a second supervised solo flight after his flight instructor had checked the weather and released him for the flight. The student pilot reported that, during his first approach for a solo landing, the touchdown was normal, but that, a second or two after touchdown, the right wing lifted up. The airplane then veered left, and the student pilot applied right rudder. The airplane continued to veer left and began to nose over. The student applied full right aileron, but the airplane continued to nose over and subsequently impacted the runway surface. Recorded wind exceeded 10 knots gusting to above 20 knots about the time of the accident.

Probable cause

The student pilot’s loss of control during landing in gusting wind conditions. Contributing to the accident was the pilot’s decision to land with gusting wind.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN14LA086
Event ID
20131216X43530
Case number
CEN14LA086
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. 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: 54ef7f7aeb87573fa8000fc7c572e1b672e1db98406f8344c7e328d283992ff9; retrieved 2026-09-15T23:11:25.330Z.