# NTSB SEA08CA126: Cessna 172M, N20406, Dixie, ID, May 3, 2008 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: May 3, 2008, 06:00 local (13:00 UTC) - Place: Dixie, ID - Coordinates: 45.405555, -115.483329 - Nearby events: https://openairdocs.org/map.md?lat=45.4056&lon=-115.4833&mi=10 - Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping) - Defining event: [Initial climb: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report June 30, 2008 - Report: Approved by Office Director - Parties: Federal Aviation Administration - NTSB case key (mKey): 67960 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=SEA08CA126 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/67960/pdf - Page: https://openairdocs.org/ntsb/SEA08CA126 ## Probable cause The pilot's failure to maintain adequate clearance from the vegetation during takeoff. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Object/animal/substance: tree(s)](https://openairdocs.org/ntsb-findings/03022020): Environmental issues › Physical environment · Not specified; cases with it: [Cessna 172M, 16 cases](https://openairdocs.org/ntsb-findings/03022020/cases.md?model=2072418), [All aircraft, 933 cases](https://openairdocs.org/ntsb-findings/03022020/cases.md) - [Airport facilities/design: runway/landing area condition](https://openairdocs.org/ntsb-findings/03017035): Environmental issues › Operating environment · Decision related to condition; cases with it: [Cessna 172M, 3 cases](https://openairdocs.org/ntsb-findings/03017035/cases.md?model=2072418), [All aircraft, 61 cases](https://openairdocs.org/ntsb-findings/03017035/cases.md) - [Info processing/decision: identification/recognition](https://openairdocs.org/ntsb-findings/02041510): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cessna 172M, 8 cases](https://openairdocs.org/ntsb-findings/02041510/cases.md?model=2072418), [All aircraft, 559 cases](https://openairdocs.org/ntsb-findings/02041510/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Initial climb: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) (defining event); cases with it: [Cessna 172M, 15 cases](https://openairdocs.org/ntsb-events/490/sequence.md?model=2072418), [All aircraft, 1,309 cases](https://openairdocs.org/ntsb-events/490/sequence.md) ## Analysis The pilot was departing from an unimproved, mountain airstrip. During the takeoff ground roll, he moved the airplane to the right in order to miss some rocks that were on the airstrip. In the initial climb, the outboard portion of the right wing then collided with brush-like vegetation that had grown into the departure path. The pilot then flew the airplane to an airport where maintenance personnel examined the airplane. The pilot did not report any mechanical anomalies. The Federal Aviation Administration inspector reported structural damage to the right wing. ## Factual narrative The pilot was departing from an unimproved, mountain airstrip. During the takeoff ground roll, he moved the airplane to the right in order to miss some rocks that were on the airstrip. In the initial climb, the outboard portion of the right wing then collided with brush-like vegetation that had grown into the departure path. The pilot then flew the airplane to an airport where maintenance personnel examined the airplane. The pilot did not report any mechanical anomalies. The Federal Aviation Administration inspector reported structural damage to the right wing. ## Aircraft - Registration: [N20406](https://openairdocs.org/aircraft/N20406), registered now, S/N 17261265 (OpenAirDocs) - Reported make and model: Cessna 172M - Registry model: [Cessna 172M](https://openairdocs.org/model/cessna-172m) (registry code 2072418) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17261265 - Engines: Textron Lycoming O-320 reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Anthony Maniglia - Registered owner: Chewela Flyers Inc. - Airworthiness certificate: Standard, Normal - Departed: ID76, Wilson Bar, ID - Destination: 169, Chewela, WA - Airport: ID76, Wilson Bar, runway 6, 1,500 × 50 ft, grass/turf ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 57; private; airplane ratings: single-engine land; medical: class 3; flight hours: 152 total, 84 in this make and model, 22 in the last 90 days, 11 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: 11,000 ft broken - Temperature: 28 °F, dew point 25 °F - Altimeter: 30.04 inHg - Observed at: KMYL, 40 nm away ## 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 20080503833559A](https://openairdocs.org/incident/20080503833559A), May 3, 2008: Cessna 172M, Dixie, ID, Substantial damage. (-23) On Saturday 5/3/2008 at 6:00 a.m. PDT time, the pilot [privacy data omitted] was acting as pilot in command of Cessna 172M N20406. While departing Wilson… ## Other investigations on N20406 (1) 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. - [NTSB WPR21LA230](https://openairdocs.org/ntsb/WPR21LA230), Jun 12, 2021: Cessna 172 (N20406), Fields, OR, substantial damage. Probable cause: The pilot’s failure to maintain directional control during landing on a highway, which resulted in an impact with terrain and subsequent nose over. 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.