# NTSB WPR10LA421: Cessna U206, N29100, Grangeville, ID, August 23, 2010

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: August 23, 2010, 09:45 local (16:45 UTC)
- Place: Grangeville, ID
- Coordinates: 45.942501, -116.123611 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=45.9425&lon=-116.1236&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing-landing roll: Sys/Comp malf/fail (non-power)](https://openairdocs.org/ntsb-events/330)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report March 20, 2012
- Report: Approved by Office Director
- NTSB office: Western Pacific Region
- Parties: FAA Spokane FSDO
- NTSB case key (mKey): 77049
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=WPR10LA421
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/77049/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=77049
- Page: https://openairdocs.org/ntsb/WPR10LA421

## Probable cause

The pilot’s decision to fly with a known defective nosewheel assembly, which resulted in a loss of directional control and nose-over on landing after the assembly shifted out of alignment during the flight.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Landing gear system: nose/tail landing gear](https://openairdocs.org/ntsb-findings/01023220): Aircraft › Aircraft systems · Malfunction (probable cause); cases with it: [Cessna U206C, 1 case](https://openairdocs.org/ntsb-findings/01023220/cases.md?model=2073332), [All aircraft, 185 cases](https://openairdocs.org/ntsb-findings/01023220/cases.md)
- [Performance/control parameters: directional control](https://openairdocs.org/ntsb-findings/01062020): Aircraft › Aircraft oper/perf/capability · Attain/maintain not possible (probable cause); cases with it: [Cessna U206C, 1 case](https://openairdocs.org/ntsb-findings/01062020/cases.md?model=2073332), [All aircraft, 3,958 cases](https://openairdocs.org/ntsb-findings/01062020/cases.md)
- [Info processing/decision: decision making/judgment](https://openairdocs.org/ntsb-findings/02041520): Personnel issues › Action/decision · Pilot (probable cause); cases with it: [Cessna U206C, 3 cases](https://openairdocs.org/ntsb-findings/02041520/cases.md?model=2073332), [All aircraft, 3,098 cases](https://openairdocs.org/ntsb-findings/02041520/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: Sys/Comp malf/fail (non-power)](https://openairdocs.org/ntsb-events/330) (defining event); cases with it: [Cessna U206C, 1 case](https://openairdocs.org/ntsb-events/330/sequence.md?model=2073332), [All aircraft, 994 cases](https://openairdocs.org/ntsb-events/330/sequence.md)
- [Landing-landing roll: Loss of control on ground](https://openairdocs.org/ntsb-events/230); cases with it: [Cessna U206C, 2 cases](https://openairdocs.org/ntsb-events/230/sequence.md?model=2073332), [All aircraft, 4,585 cases](https://openairdocs.org/ntsb-events/230/sequence.md)
- [Landing-landing roll: Runway excursion](https://openairdocs.org/ntsb-events/300); cases with it: [Cessna U206C, 2 cases](https://openairdocs.org/ntsb-events/300/sequence.md?model=2073332), [All aircraft, 3,643 cases](https://openairdocs.org/ntsb-events/300/sequence.md)
- [Landing-landing roll: Nose over/nose down](https://openairdocs.org/ntsb-events/096); cases with it: [Cessna U206C, 3 cases](https://openairdocs.org/ntsb-events/096/sequence.md?model=2073332), [All aircraft, 2,287 cases](https://openairdocs.org/ntsb-events/096/sequence.md)

## Analysis

The pilot reported that, during the landing roll on a turf airstrip, he noticed rattling and shaking after the nosewheel touched down, but had no problem holding a straight line. After taxiing to the tie-down area and parking the airplane, the pilot inspected the nose gear and found that the upper end of the nose gear scissor had separated from the casting and was lying on the tire. The pilot reported that he walked out to where he touched down and observed tire tracks on the grass, and it appeared that the nosewheel track began after a large ground squirrel hole. The pilot contacted his mechanic, who informed him that he should be able to fly home if he tied the nose gear scissor up. Before departing, the pilot taxied about 1,000 feet on the runway and made two 180-degree turns with no problems encountered. During the landing at his destination, the pilot held the nose gear off of the ground for about 1,500 feet. When the nosewheel contacted the ground, the airplane made a hard left turn that the pilot could not stop with right rudder and brake. When the airplane reached the edge of the runway, it nosed over. The pilot indicated that the nosewheel had evidently cocked 90 degrees prior to the landing.

## Factual narrative

On August 23, 2010, about 0945 Pacific daylight time, a Cessna U206C, N29100, nosed over during landing at Idaho County Airport, Grangeville, Idaho. The pilot/owner was operating the airplane under the provisions of 14 Code of Federal Regulations (CFR) Part 91 as a positioning flight. The commercial pilot was not injured; the airplane sustained substantial damage to the fuselage, wings, and empennage. The airplane departed Concord airstrip (25 miles southeast of Idaho County Airport) at 0930, en route to Grangeville. Visual meteorological conditions prevailed, and no flight plan had been filed. The pilot reported that he began the day at Grangeville at 0615, for a 14 CFR Part 135 flight to Campbell’s Ferry on the Main Salmon River. After landing and unloading his passenger, he departed for the airstrip at Concord. The pilot stated that during the landing he noticed that the airplane was rattling and shaking, but he had no problem maintaining a straight line on roll out. He taxied back to the tie down area, and parked the airplane. The pilot inspected the landing gear and observed the nose gear scissor lying on the tire; the upper end had snapped off (separated from the casting). He walked out to where he touched down, and observed good tracks on the grass in the morning dew. He saw that the nose wheel track first appeared after a large ground squirrel hole. The pilot reported that earlier in the summer he had filled in some of the holes. The pilot contacted his mechanic, who informed him that he should be able to fly home if he tied the nose gear scissor up. After doing that, the pilot taxied about 1,000 feet on the runway, and made two 180-degree turns with no problems encountered. The pilot then departed for Grangeville. During the landing, the pilot held the nose off for about 1,500 feet, and then eased the nose down. The airplane made a hard left turn that he could not stop with right rudder and brake. When the airplane reached the edge of the runway, it nosed over. The pilot indicated that the nose wheel had evidently cocked 90 degrees prior to the landing.

## Aircraft

- Registration: [N29100](https://openairdocs.org/deregistered/N29100-2013-10-29), registration cancelled 2013-10-29, S/N U206-1072, built 1968 (OpenAirDocs)
- Reported make and model: CESSNA U206 (C)
- Registry model: [Cessna U206C](https://openairdocs.org/model/cessna-u206c) (registry code 2073332) (OpenAirDocs)
- Registry engine: [Continental IO-520 series](https://openairdocs.org/engine/continental-io-520-series) (registry code 17032, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: U206-1072
- Airframe hours: 6146
- Engines: Teledyne Continental Motors IO-520-F4B 300 horsepower reciprocating
- Damage: Substantial damage
- Flight: Positioning, Part 91
- Operator: Karl E. Urquhart
- Registered owner: Karl E. Urquhart
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, November 1, 2009, 54 hours before
- Departed: Concord, ID
- Destination: S80, Granville, ID
- Airport: S80, Grangeville Idaho County, runway 07, 5,101 × 75 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 53; injuries: none; private, commercial; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 2, with waivers/limitations; last flight review August 1, 2009; seat: left; flight hours: 2,770 total, 955 in this make and model, 2,700 as pilot in command, 54 in the last 90 days, 6 in the last 30 days

## Weather

- Conditions: Visual (VMC), Day
- Wind: 30° at 4 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 72 °F, dew point 34 °F
- Altimeter: 29.75 inHg
- Observed at: KLWS, 48 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 20100823041909A](https://openairdocs.org/incident/20100823041909A), Aug 23, 2010: Cessna U206C, Grangeville, ID, Substantial damage. Pilot departed airstrip in concord, Idaho with broken nose landing gear casting at upper scissor link attach point. Upon landing at Idaho County Airport (S80)…

## Other investigations on N29100 (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 LAX07CA132](https://openairdocs.org/ntsb/LAX07CA132), Apr 22, 2007: Cessna U206-C (N29100), Cottonwood, ID, substantial damage. Probable cause: The pilot's misjudgment of distance/speed, which resulted in a overshoot of the runway in tailwind conditions and subsequent nose over. Factors in the accident were the tail wind condition and the…

## Docket (1 files)

The files NTSB released with the investigation on February 1, 2012, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=77049. 506 KB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 506 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40338071&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.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.
