# NTSB CHI07CA136: Cessna 182P, N52621, Traer, IA, May 10, 2007 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: May 10, 2007, 14:20 local (19:20 UTC) - Place: Traer, IA - Coordinates: 42.199165, -92.458053 - Nearby events: https://openairdocs.org/map.md?lat=42.1992&lon=-92.4581&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report June 27, 2007 - Report: Approved by Office Director - Parties: FAA-Des Moines FSDO - NTSB case key (mKey): 65989 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CHI07CA136 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/65989/pdf - Page: https://openairdocs.org/ntsb/CHI07CA136 ## Probable cause The pilot's failure to maintain control of the airplane during landing on the grass airstrip. A contributing factor was the pilot's limited experience operating on grass runways. Additional factors were the runway cone struck during landing and the irrigation ditch encountered during the runway excursion. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of control - on ground/water, landing - roll - aircraft control - not maintained, pilot in command (cause) - lack of experience, pilot in command (contributing factor) - became lost/disoriented - inadvertent, pilot in command - terrain condition - grass (contributing factor) - On ground/water collision with object, landing - roll - object - airport sign/marker (contributing factor) - On ground/water encounter with terrain/water, landing - roll - terrain condition - ditch (contributing factor) ## Analysis The airplane was substantially damaged when it departed the runway (2,555 feet by 100 feet, turf) during landing and encountered an irrigation ditch. The pilot reported that after takeoff he intended to track a Very-High-Frequency Omni Range (VOR) navigation station to an intermediate fuel stop before continuing to his final destination. About 4 hours into the flight he attempted to contact air traffic control in order to verify his position; however, he was unable to establish contact. At that point, he began "to lose confidence in [his] present position" and decided to establish a heading he believed was toward his intermediate fuel stop. After an additional hour of flight, he became concerned about his remaining fuel and contacted a Flight Service Station (FSS). He informed them that he was "lost and short on fuel." The FSS located the flight and provided vectors to a nearby alternate airport. Upon landing at the alternate airport "the aircraft went into a skid, hit a runway cone and came to a stop across from the end of the runway. Just a few feet beyond [an] irrigation ditch." The pilot noted that he did not have experience landing on grass runways. The pilot did not indicate any failures or malfunctions associated with the aircraft's flight control system or engine. He did note the possibility of an "intermittent radio transmission failure" as a possible factor contributing to his becoming lost prior to the accident. ## Factual narrative The airplane was substantially damaged when it departed runway 17 (2,555 feet by 100 feet, turf) during landing and encountered an irrigation ditch. The pilot reported that after takeoff he intended to track a Very-High-Frequency Omni Range (VOR) navigation station to an intermediate fuel stop before continuing to his final destination. About 4 hours into the flight he attempted to contact air traffic control in order to verify his position; however, he was unable to establish contact. At that point, he began "to lose confidence in [his] present position" and decided to establish a heading he believed was toward his intermediate fuel stop. After an additional hour of flight, he became concerned about his remaining fuel and contacted a Flight Service Station (FSS). He informed them that he was "lost and short on fuel." The FSS located the flight and provided vectors to a nearby alternate airport. Upon landing at the alternate airport "the aircraft went into a skid, hit a runway cone and came to a stop across from the end of the runway. Just a few feet beyond [an] irrigation ditch." The pilot noted that he did not have experience landing on grass runways. The pilot did not indicate any failures or malfunctions associated with the aircraft's flight control system or engine. He did note the possibility of an "intermittent radio transmission failure" as a possible factor contributing to his becoming lost prior to the accident. ## Aircraft - Registration: [N52621](https://openairdocs.org/aircraft/N52621), registered now, S/N 18262719, built 1973 (OpenAirDocs) - Reported make and model: Cessna 182P - Registry model: [Cessna 182P](https://openairdocs.org/model/cessna-182p) (registry code 2075816) (OpenAirDocs) - Registry engine: [Continental O-470 series](https://openairdocs.org/engine/continental-o-470-series) (registry code 17026, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 18262719 - Engines: Continental O-470 reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Samuel L. White - Registered owner: Ray F Inc - Airworthiness certificate: Standard, Utility; Standard, Normal - Departed: RAP, Rapid City, SD - Destination: OTG, Worthington, MN ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 66; injuries: none; private; airplane ratings: single-engine land; medical: class 2, with waivers/limitations; last flight review November 1, 2006; seat: left; flight hours: 680 total, 680 in this make and model ## Weather - Conditions: Visual (VMC), Day - Wind: 20° at 10 knots, gusting 15 - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 82 °F, dew point 46 °F - Altimeter: 30.05 inHg - Observed at: ALO 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.