SEA04LA072

NTSB accident investigation · Cessna 170B · Nampa, ID · April 23, 2004

Accident · No injuriesLimited investigationFinal report
Date
April 23, 2004, 13:30 local (19:30 UTC)
Place
Nampa, ID
Injuries
2 uninjured
Damage
Substantial damage
Phase of flight
Landing
Aircraft
N8252ACessna 170B
Weather
Visual (VMC) · Day
Status
Completed · report December 28, 2004
Report
Approved by Office Director
Parties
Boise FSDO
FAA report
20040423005999A
Case key
59110

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 right seat pilot's failure to maintain directional control during the initial part of the landing roll, and his improper handling of the aircraft (excessive braking) as the aircraft departed the side of the runway. Factors include the pilot's lack of recent experience in this make and model aircraft.

Sequence of events

NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.

Loss of control - on ground/waterLanding - roll
Directional control - not maintainedPilot in commandCause
Lack of recent experience in type of aircraftPilot in commandFactor
Nose overLanding - roll
Aircraft handling - improperPilot in commandCause

Analysis

The pilot in the left seat, who had purchased the aircraft the day prior to the accident, started the flight by making two takeoffs and two full-stop landings. Both of his takeoff rolls were uneventful with no directional control difficulties, but because he was having trouble with directional control during landing, it was decided that the more experienced tail wheel pilot in the right seat would perform a takeoff and landing, during which the pilot in the left seat would keep his hands and feet on the controls in order to feel the control inputs made by the other pilot. The pilot in the right seat experienced "some difficulty" during the takeoff, but he was unsure if it was related to having the left seat pilot on the controls with him. He then made a landing, touching down near the centerline, and pulling the yoke to the "full back" position, while making sure the engine was at idle. Although the initial touchdown was uneventful, soon thereafter the aircraft veered to the right, and the pilot applied left rudder in an attempt to return it to the runway heading. Seeing that the application of rudder alone was not adequate, the pilot applied heavy left brake, but the aircraft continued to the right and exited the right side of the runway. As the aircraft exited the runway, the right seat pilot began applying right brake also, and soon thereafter the aircraft nosed over onto its back. Inspection and testing of the aircraft did not reveal any indication that there had been a brake malfunction or any anomaly in the rudder/tail wheel steering system that would have created an uncontrollable situation. In addition it was determined that although the right seat pilot had about 25 hours in this make and model airplane, it had been "many years" since he had flown one.

Factual narrative

On Friday, April 23, 2004, approximately 1330 mountain daylight time, a Cessna 170B, N8252A, nosed over after exiting the side of the runway during landing at Nampa Municipal Airport, Nampa, Idaho. Neither the private pilot/owner, who was in the left seat, nor the airline transport pilot, who was in the right seat, were injured. The aircraft, which is owned and operated by the pilot in the left seat, sustained substantial damage. The 14 CFR Part 91 personal pleasure flight, which had been in the pattern at Nampa for about 15 minutes, was being operated in visual meteorological conditions. No flight plan had been filed. There was no report of an ELT activation.

According to the pilot in the left seat, who had purchased the aircraft the day prior to the accident, prior to the purchase he had no experience in this make and model airplane. He started the flight by making two takeoffs and two full-stop landings. He said that both of his takeoff rolls were uneventful, with no directional control difficulties, but during both landings he had problems keeping the aircraft heading straight down the runway, and the pilot in the right seat had to take control of the aircraft and bring it to a full stop. After those two landings, it was decided that the more experienced tail wheel pilot in the right seat would perform a takeoff and landing, during which the pilot in the left seat would keep his hands and feet on the controls in order to feel the control inputs made by the other pilot. According to the pilot in the right seat, who's flight instructor's certificate had expired in 1991, during the takeoff he experienced "some difficulty," but he was not sure if it was related to having the left seat pilot on the controls with him. Once he got in the air, he tested the brakes a couple of times, but could find no fault, and confirmed each had "plenty of pressure." He then made a landing, touching down near the centerline, and pulling the yoke to the "full back" position, while making sure the engine was at idle. Although the initial touchdown was uneventful, soon thereafter the aircraft veered to the right, and the pilot applied left rudder in an attempt to return it to the runway heading. Seeing that the application of rudder alone was not adequate, the pilot applied heavy left brake, but the aircraft continued to the right and exited the right side of the runway. As the aircraft exited the runway, the right seat pilot began applying right brake also, and soon thereafter the aircraft nosed over onto its back.

The Federal Aviation Administration's post-accident inspection of the scene revealed a black skid mark on the runway surface created by the left main landing gear, and no indication of braking with right wheel until after the aircraft departed the runway surface. Inspection and testing of the aircraft did not reveal any indication that there had been a brake malfunction or any anomaly in the rudder/tail wheel steering system that would have created an uncontrollable situation.

In an interview with the NTSB Investigator-In-Charge (IIC), the right seat pilot said that although he had about 25 hours in this make and model airplane, it had been "many years" since he had flown one.

Aircraft

Registration
N8252A
Reported as
Cessna 170B
Category
Airplane
Serial number
25104
Airframe hours
3,347
Engine
Continental O-300, 145 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Registered owner
Dwight R. Magnuson
Airworthiness certificate
Standard, Normal
Last inspection
Annual · December 1, 2003 · 68 hours before
Departed
S67 · Nampa, ID
Destination
S67
Airport
S67 · Nampa Municipal, runway 11, 5,000 × 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 · 2

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
63
Injuries
None
Certificates
Flight instructor, Airline transport
Airplane ratings
Single-engine land, Multi-engine land, Single-engine sea
Instrument ratings
Airplane
Medical
Class 3, Valid Medical--w/ waivers/lim
Last flight review
March 22, 2003
Seat
Right
Flight hours
20,000 total · 25 in this make and model · 19,500 as pilot in command · 30 in the last 90 days · 10 in the last 30 days · 2 in the last 24 hours
Role
Pilot
Age
55
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, Valid Medical--w/ waivers/lim
Last flight review
August 9, 2003
Seat
Left
Flight hours
488 total · 2 in this make and model · 417 as pilot in command · 21 in the last 90 days · 6 in the last 30 days · 2 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Visibility
10 statute miles
Lowest ceiling
None
Temperature
64 °F

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 N8252A · 2

Matched to the same aircraft by N-number and date.