- Date
- August 23, 2010, 09:45 local (16:45 UTC)
- Place
- Grangeville, ID
- Injuries
- 1 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N29100Cessna U206
- Defining event
- Landing-landing roll: Sys/Comp malf/fail (non-power)
- Weather
- Visual (VMC) · Day
- Status
- Completed · report March 20, 2012
- Report
- Approved by Office Director
- NTSB office
- Western Pacific Region
- Parties
- FAA Spokane FSDO
- FAA report
- 20100823041909A
- Case key
- 77049
From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.
On this page
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 · 3
NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.
Sequence of events
The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.
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
- Reported as
- Cessna U206 (C)
- Category
- Airplane
- Serial number
- U206-1072
- Airframe hours
- 6,146
- Engine
- 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
Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.
Flight crew
As NTSB recorded them. NTSB leaves out names.
- Role
- Pilot
- Age
- 53
- Injuries
- None
- Certificates
- 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
Docket · 1
The files NTSB released with the investigation on February 1, 2012, on NTSB’s docket system: statements, records, photos and specialists’ reports. 506 KB in all.
FAA reports on this event · 1
The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.
Other investigations on N29100 · 1
Matched to the same aircraft by N-number and date.