# NTSB GAA18CA513: Cessna 172, N53051, Winchester, VA, August 27, 2018 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: August 27, 2018, 11:30 local (15:30 UTC) - Place: Winchester, VA - Coordinates: 39.143611, -78.144447 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=39.1436&lon=-78.1444&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report June 10, 2019 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FAA - NTSB case key (mKey): 98169 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA18CA513 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/98169/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=98169 - Page: https://openairdocs.org/ntsb/GAA18CA513 ## Probable cause The student pilot's failure to maintain directional control during the takeoff roll. ## 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 · Student/instructed pilot (probable cause); cases with it: [Cessna 172P, 76 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md?model=2072436), [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) - [Performance/control parameters: directional control](https://openairdocs.org/ntsb-findings/01062020): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Cessna 172P, 28 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=2072436), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md) - [Object/animal/substance](https://openairdocs.org/ntsb-findings/03022000): Environmental issues › Physical environment · Contributed to outcome; cases with it: [Cessna 172P, 2 cases](https://openairdocs.org/ntsb-findings/03022000/cases.md?model=2072436), [All aircraft, 224 cases](https://openairdocs.org/ntsb-findings/03022000/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [Cessna 172P, 37 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=2072436), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Landing-landing roll: Attempted remediation/recovery](https://openairdocs.org/ntsb-events/060); cases with it: [Cessna 172P, 13 cases](https://openairdocs.org/ntsb-events/060/sequence.md?model=2072436), [All aircraft, 1,422 cases](https://openairdocs.org/ntsb-events/060/sequence.md) - [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Cessna 172P, 29 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2072436), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) - [Landing-landing roll: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Cessna 172P, 45 cases](https://openairdocs.org/ntsb-events/470/sequence.md?model=2072436), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) - [Landing-landing roll: Nose over/nose down](https://openairdocs.org/ntsb-events/096); cases with it: [Cessna 172P, 18 cases](https://openairdocs.org/ntsb-events/096/sequence.md?model=2072436), [All aircraft, 2,287 cases](https://openairdocs.org/ntsb-events/096/sequence.md) ## Analysis The student pilot reported that he completed a touch-and-go landing and applied full power to increase the airplane's ground speed. During the takeoff roll, the engine power increased, and the airplane drifted to the left side of the runway. The student applied full right rudder, but it was ineffective. He then reduced the engine power to idle and applied brakes, but the airplane exited the left side of the runway, collided with a drainage culvert, and then came to rest inverted. The airplane sustained substantial damage to the right wing lift strut, the vertical stabilizer, and the rudder. The student reported that he thought that a mechanical malfunction of the rudder system might have occurred before the accident sequence. However, Federal Aviation Administration aviation safety inspectors reported that, during a postaccident airplane examination, the rudder system was operational, and rudder control continuity was established. ## Factual narrative The student pilot reported that he completed a touch-and-go landing and applied full power to increase the airplane's ground speed. During the takeoff roll, the engine power increased, and the airplane drifted to the left side of the runway. The student pilot's full deflection right rudder application was ineffective, and the he reduced the engine power to idle. He applied brakes, but the airplane exited the left side of the runway, collided with a drainage culvert, and the airplane came to rest inverted. The airplane sustained substantial damage to the right wing lift strut, the vertical stabilizer, and the rudder. The student pilot suspected that a mechanical malfunction of the airplane's rudder system may have occurred prior to the accident sequence. However, Federal Aviation Administration, Aviation Safety Inspectors reported that during a post-accident airplane examination, the airplane's rudder system was operational and rudder control continuity was attained. ## Aircraft - Registration: [N53051](https://openairdocs.org/deregistered/N53051-2019-02-23), registration cancelled 2019-02-23, S/N 17274673, built 1981 (OpenAirDocs) - Reported make and model: Cessna 172 (P) - Registry model: [Cessna 172P](https://openairdocs.org/model/cessna-172p) (registry code 2072436) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17274673 - Year built: 1981 - Airframe hours: 12049.7 - Engines: Lycoming O-320 160 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: AV-ED Flight School- Winchester, LLC - Registered owner: Archer Associates Llc. - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, July 27, 2018 - Departed: OKV, Winchester, VA - Destination: OKV, Winchester, VA - Airport: OKV, Winchester Rgnl, runway 32, 5,498 × 100 ft, asphalt - Equipment: None ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 60; injuries: none; student; medical: class 3; seat: left; restraint: 3-point; flight hours: 17 total, 17 in this make and model, 2 as pilot in command, 9 in the last 90 days, 5 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 220° at 5 knots - Visibility: 10 statute miles - Lowest ceiling: 7,500 ft broken - Temperature: 81 °F, dew point 72 °F - Altimeter: 30.20 inHg - Observed at: KOKV ## 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 20180827012399A](https://openairdocs.org/incident/20180827012399A), Aug 27, 2018: Cessna 172P, Winchester, VA, Substantial damage. The student pilot was conducting his third solo flight. While performing a touch and go on runway 32, the aircraft veered to the left as the power was applied… ## Docket (3 files) The files NTSB released with the investigation on April 17, 2019, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=98169. 4.7 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 4.4 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40471935&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Memorandum for Record (item 2, .PDF, 130 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40471936&FileExtension=.PDF&FileName=Memorandum%20for%20Record-Master.PDF - Photo (item 3, .PDF, 1 photo, 133 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40471937&FileExtension=.PDF&FileName=Photo-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.