# NTSB CEN09CA141: Cessna 172S, N2465H, Emporia, KS, January 18, 2009 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: January 18, 2009, 11:00 local (17:00 UTC) - Place: Emporia, KS - Coordinates: 38.332221, -96.191108 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=38.3322&lon=-96.1911&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining event: [Landing: Loss of control on ground](https://openairdocs.org/ntsb-events/230) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report April 15, 2009 - Report: Approved by Office Director - NTSB office: Central Region - Parties: FAA FSDO - NTSB case key (mKey): 73277 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN09CA141 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/73277/pdf - Page: https://openairdocs.org/ntsb/CEN09CA141 ## Probable cause The pilot's inadequate compensation for the wind conditions during the touch-and-go. Contributing to the accident were the gusty crosswinds. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: directional control](https://openairdocs.org/ntsb-findings/01062020): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md) - [Wind: crosswind](https://openairdocs.org/ntsb-findings/03034040): Environmental issues › Conditions/weather/phenomena · Effect on operation (probable cause); cases with it: [All aircraft, 1,008 cases](https://openairdocs.org/ntsb-findings/03034040/cases.md) - [Wind](https://openairdocs.org/ntsb-findings/03034000): Environmental issues › Conditions/weather/phenomena · Response/compensation (probable cause); cases with it: [All aircraft, 110 cases](https://openairdocs.org/ntsb-findings/03034000/cases.md) - [Use of equip/info: aircraft control](https://openairdocs.org/ntsb-findings/02063040): Personnel issues › Task performance · Pilot (probable cause); cases with it: [All aircraft, 9,295 cases](https://openairdocs.org/ntsb-findings/02063040/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-flare/touchdown: Other weather encounter](https://openairdocs.org/ntsb-events/400); cases with it: [All aircraft, 1,127 cases](https://openairdocs.org/ntsb-events/400/sequence.md) - [Landing: Loss of control on ground](https://openairdocs.org/ntsb-events/230) (defining event); cases with it: [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md) - [Landing: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md) ## Analysis The solo student pilot was performing touch-and-gos to the 4,999-foot-long, 100-foot-wide asphalt runway in the single-engine, high-wing airplane. The winds were stronger than forecasted, yet the pilot elected to perform approaches to the airport anyway. On the second touch-and-go to runway 01, the student pilot stated that he encountered a gust of wind and lost control of the airplane. The airplane exited the right side of the runway and impacted terrain in a dirt field resulting in damage to the airplane's firewall. According to the airfield's automated weather report, winds at the time of the accident were estimated to be from 330 degrees at 14 knots, gusting to 22 knots. A review of the student pilot's logbook revealed that he was endorsed for the solo flight with a maximum crosswind component of 7 knots. ## Factual narrative The solo student pilot was performing touch-and-gos to the 4,999 foot long, 100-foot wide asphalt runway in the single-engine, high wing airplane. The winds were stronger than forecasted, yet the pilot elected to perform approaches to the airport anyway. On the second touch-and-go to runway 01, the student pilot stated he encountered a gust of wind and lost control of the airplane. The airplane exited the right side of the runway and impacted terrain in a dirt field resulting in damage to the airplane's firewall. According to the airfield's automated weather report, winds at the time of the accident were estimated to be from 330 degrees at 14 knots gusting to 22 knots. A review of the student pilot's logbook revealed that he was endorsed for the solo flight with a maximum crosswind component of 7 knots. ## Aircraft - Registration: N2465H (not matched to a registry record) - Reported make and model: CESSNA 172S - Category: Airplane - Serial number: 172S10056 - Engines: LYCOMING IO-360-L2A 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Hetrick Air Services Inc. - Registered owner: Ron-Air Systems Inc - Airworthiness certificate: Standard, Normal - Departed: LWC, LAWRENCE, KS - Destination: LWC, LAWRENCE, KS - Airport: EMP, Emporia Municipal, runway 01, 4,999 × 100 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Student pilot; age 43; injuries: none; student; medical: class 3, with waivers/limitations; seat: left; flight hours: 50 total, 30 in this make and model, 5 as pilot in command, 4 in the last 90 days, 4 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 330° at 14 knots, gusting 22 - Visibility: 10 statute miles - Temperature: 45 °F, dew point 27 °F - Altimeter: 30.10 inHg - Observed at: EMP ## 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 20090118000699A](https://openairdocs.org/incident/20090118000699A), Jan 18, 2009: Cessna 172S, Emporia, KS, Substantial damage. Student pilot was on a solo cross country flight from lawrence, KS airport (klwc) to Emporia, KS airport (kemp). Upon arriving at kemp he attempted a crosswind… 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.