CEN13FA364 · Cessna 172M
Flight 101 Cessna 172M · Accident: loss of control in flight during initial climb
From Oakland County International Airport (KPTK) to Oakland County International Airport (KPTK)
Event
- NTSB case
- CEN13FA364
- 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
- 4 · 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
Cessna 172M
- Aircraft type
- Cessna 172
- 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
- N9926Q
- Operator
- Flight 101
- Onboard fatalities
- Unknown
- Route
- From Oakland County International Airport (KPTK), Waterford, MITo Oakland County International Airport (KPTK), Waterford, MI
- 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
- Initial climb
- 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 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Action/decision
- Personnel issues › Experience/knowledge
Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.
NTSB narrative
Air traffic control tower personnel saw the airplane lift off the runway and attain an altitude of about 100 feet. A pilot approaching the runway for landing saw the airplane lift off and noticed it was not climbing. He saw the airplane "lagging" and "wallowing in the air with flaps extended." Shortly after, the accident pilot advised an air traffic controller that he was "a little overweight" and would need to return to the airport and land. The air traffic controller cleared the airplane to land on the parallel runway or the grass area surrounding the runways. The pilot did not respond. Several witnesses near the airport, including the pilot in the landing airplane, saw the accident airplane impact the ground and burst into flames. A postaccident examination revealed that the wing flaps were fully extended (40 degrees). Weight and balance calculations indicated the airplane was slightly under maximum gross weight. Postaccident examinations revealed no evidence of preimpact mechanical malfunctions or failures that would have precluded normal operation.
The pilot received his private pilot certificate almost 2 months before the accident and had flown a Cirrus SR20 almost exclusively. He reportedly had flown the Cessna 172, the accident airplane make and model, for a few hours, but this report could not be confirmed. Cirrus SR20 takeoffs are normally made using 50 percent flaps, whereas Cessna 172M takeoffs are normally made with the flaps up. The pilot most likely configured the airplane incorrectly for takeoff and the airplane was unable to climb due to his lack of familiarity with the airplane make and model.
Probable cause
The pilot's failure to retract the wing flaps before attempting to take off, due to his lack of familiarity with the airplane make and model, which prevented the airplane from maintaining adequate altitude for takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN13FA364
- Event ID
- 20130621X52631
- Case number
- CEN13FA364
- 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. 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: 5571325b3d623ac5efe4c34e1f8ab6d60eb81f4a702c0c274e67dd9ca66557ae; retrieved 2026-09-14T15:59:17.585Z.