NTSB CAROL · Event
Event SEA04LA072
Registry · N8252A
FAA Aircraft Registry record.
Make / Model
CESSNA 170B
Year of manufacture
1952 · 52 years old at event
Engine
CONT MOTOR C145 SERIES (145 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
19560526
ADS-B equipped
Yes — Mode-S AB460D
Registrant of record
DUANE PETERS
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
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.
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. 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. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2004_SEA04LA072.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.