FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN13CA202 · Cessna 172L

17 Mar 2013 · Pontiac, MI, United States

Cessna 172L · Accident: loss of control on ground while taxiing

From Oakland County International Airport (PTK) to Oakland County International Airport (PTK)

Report a problem

Event

NTSB case
CEN13CA202
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

Cessna 172L

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
N7282Q
Operator
Unknown
Onboard fatalities
Unknown
Route
From Oakland County International Airport (PTK), Pontiac, MITo Oakland County International Airport (PTK), Pontiac, 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
Taxi · to runway
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

  • Not determined › Not determined
  • 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 private pilot said she was taxiing her single-engine airplane to the active runway when the engine suddenly went to full power. She did not recall any related engine instrument indications and tried to reduce power by moving the throttle control to its idle position, pulling the mixture control aft, and applying the brakes. During this time, the airplane veered off the taxiway, impacted a snow bank, and nosed over, coming to rest on its back, which resulted in substantial damage to the airframe. Examination of the engine found no mechanical anomalies that would explain the sudden increase in engine power. The pilot had 2,000 feet of taxiway remaining from where the airplane departed the runway.

Probable cause

The pilot's failure to maintain airplane control after an unexplained increase in engine power while taxiing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN13CA202
Event ID
20130321X72747
Case number
CEN13CA202
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: 4889dccd439ce183d89623428670b4bfc03f9c09f97a672b382656595e9b6089; retrieved 2026-09-15T21:09:17.569Z.