# NTSB CEN13CA202: Cessna 172L, N7282Q, Pontiac, MI, March 17, 2013 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: March 17, 2013, 15:18 local (20:18 UTC) - Place: Pontiac, MI - Coordinates: 42.659442, -83.418891 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=42.6594&lon=-83.4189&mi=10 - Phase of flight: [Taxi](https://openairdocs.org/ntsb-phases/250) (OpenAirDocs' grouping) - Defining event: [Taxi-to runway: Loss of control on ground](https://openairdocs.org/ntsb-events/230) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report July 18, 2013 - Report: Approved by Office Director - NTSB office: Central Region - Parties: FAA/FSDO - NTSB case key (mKey): 86488 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN13CA202 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/86488/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=86488 - Page: https://openairdocs.org/ntsb/CEN13CA202 ## Probable cause The pilot's failure to maintain airplane control after an unexplained increase in engine power while taxiing. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [Cessna 172L, 24 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072432), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Not determined](https://openairdocs.org/ntsb-findings/05000000): Not determined › Not determined · Unknown/Not determined (probable cause); cases with it: [Cessna 172L, 1 case](https://openairdocs.org/ntsb-findings/05000000/cases.md?model=2072432), [All aircraft, 2,247 cases](https://openairdocs.org/ntsb-findings/05000000/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Taxi-to runway: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [Cessna 172L, 13 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=2072432), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Taxi-to runway: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 172L, 21 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072432), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis 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. ## Factual narrative The private pilot said she was taxing her single-engine airplane to the active runway when the engine suddenly went to full power. She did not recall any engine instrument indications and tried to reduce power by closing the throttle, pulling the mixture control, and applying the brakes. During this time, the airplane veered off the taxiway, impacted a snow bank, and flipped over on its back causing substantial damage to the airframe. Examination of the engine found no mechanical anomalies that would explain why there was a sudden increase in engine power. The pilot had 2,000 feet of taxiway remaining from where the airplane departed the runway. ## Aircraft - Registration: [N7282Q](https://openairdocs.org/deregistered/N7282Q-2018-02-08), registration cancelled 2018-02-08, S/N 17260582, built 1972 (OpenAirDocs) - Reported make and model: CESSNA 172L - Registry model: [Cessna 172L](https://openairdocs.org/model/cessna-172l) (registry code 2072432) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17260582 - Engines: Lycoming O-360 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Normal - Departed: PTK, Pontiac, MI - Destination: PTK, Pontiac, MI - Airport: PTK, Pontiac ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 55; injuries: none; private; airplane ratings: single-engine land; medical: class 3, unknown; flight hours: 620 total, 500 in this make and model ## Weather - Conditions: Visual (VMC), Day ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20130317003539A](https://openairdocs.org/incident/20130317003539A), Mar 17, 2013: Cessna 172L, Waterford, MI, Substantial damage. Pilot was taxiing west on taxiway c and experienced an increase in engine power that was described as "close to full power." No engine indications were… ## Docket (2 files) The files NTSB released with the investigation on April 29, 2013, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=86488. 584 KB in all. - Pilot and Passenger written statements (item 1, .PDF, 497 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40390261&FileExtension=.PDF&FileName=Pilot%20and%20Passenger%20written%20statements-Redacted.PDF - FAA Inspector written statement (item 2, .PDF, 87 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40390263&FileExtension=.PDF&FileName=FAA%20Inspector%20written%20statement-Master.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.