- Date
- March 24, 2010, 08:15 local (15:15 UTC)
- Place
- Kingman, AZ
- Injuries
- 2 uninjured
- Damage
- Substantial damage
- Phase of flight
- Landing
- Aircraft
- N4200VCessna 170
- Defining event
- Landing-landing roll: Loss of control on ground
- Weather
- Visual (VMC) · Day
- Status
- Completed · report July 1, 2010
- Report
- Approved by Office Director
- NTSB office
- Western Pacific Region
- Parties
- Federal Aviation Administration
- FAA report
- 20100324030019A
- Case key
- 75580
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 failure to maintain directional control during landing rollout. Contributing to the accident was flight control interference by the passenger.
Findings · 4
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 he was landing the tailwheel-equipped airplane when he lost control and veered off the runway. He stated that the three-point landing was “textbook” and on the runway centerline; however, during the rollout the airplane veered to the left. The pilot attempted to regain control of the airplane by applying rudder inputs but was not successful. The airplane exited the runway; the right main landing gear separated and the right wing then impacted the ground. The pilot reported that after the accident the passenger told him that he applied rudder during the landing to help the pilot. The pilot stated that in the future he would be more assertive whenever there was someone with access to controls as to who is the actual manipulator of the controls.
Factual narrative
The pilot reported that he was landing a tail wheel equipped airplane when he lost control and veered off the runway. He stated the three-point landing was “textbook” and on the runway centerline; however, during the roll-out the airplane veered to the left. The pilot attempted to regain control of the airplane by applying rudder inputs but was not successful. The airplane exited the runway and the right main landing gear separated and the right wing impacted the ground. The pilot reported that after the accident the passenger told him that he applied rudder during the landing to help the pilot. The pilot stated that in the future he would be more assertive whenever there was someone with access to controls as to who is the actual manipulator of the controls.
Aircraft
- Registration
- N4200V
- Reported as
- Cessna 170
- Category
- Airplane
- Serial number
- 18556
- Engine
- Cont Motor C145 SERIES, 145 horsepower, reciprocating
- Damage
- Substantial damage
- Flight
- Personal · Part 91
- Airworthiness certificate
- Standard, Normal
- Departed
- 2AZ1 · Solome, AZ
- Destination
- IGM · Kingman, AZ
- Airport
- IGM · Kingman Airport, runway 21, 6,827 × 150 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
- 51
- Injuries
- None
- Certificate
- Private
- Airplane ratings
- Single-engine land
- Medical
- Class 3, With waivers/limitations
- Last flight review
- January 14, 2010
- Seat
- Left
- Flight hours
- 528 total · 38 in this make and model · 469 as pilot in command · 30 in the last 90 days · 16 in the last 30 days · 1 in the last 24 hours
Weather
- Conditions
- Visual (VMC) · Day
- Wind
- 110° at 4 knots
- Visibility
- 10 statute miles
- Lowest ceiling
- None
- Temperature
- 43 °F, dew point 21 °F
- Altimeter
- 30.14 inHg
- Observed at
- IGM
Docket · 1
The files NTSB released with the investigation on April 22, 2010, on NTSB’s docket system: statements, records, photos and specialists’ reports. 243 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.