Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

May 10, 2004 · Cessna 172P · N54477

Battle Ground, WA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
May 10, 2004
Injury Outcomes
No injuries (2 uninjured)
Location
Battle Ground, WA
Aircraft
Cessna 172P
Tail Number
N54477
Injuries
None
Aircraft Damage
Substantial
NTSB Number
SEA04LA081

The dual student, who holds a private pilot certificate for helicopters, was working towards a fixed-wing add-on to his certificate. As per the lesson profile, the student planned a dual cross country flight, but while en route, the instructor told the student to divert to another field. After arrival at the field, they over-flew the runway and determined that there was a direct crosswind at what they estimated was about 10 knots. The student then entered a left pattern for a full-stop landing on the damp turf runway. During his first two approaches, the student allowed the aircraft to get too high on final, and in both instances a go-around was initiated. On the third approach the aircraft remained on the proper final approach path until it was approximately 50 feet above the ground. At that point the aircraft encountered a wind gust, and it ballooned upward to an extent that the pilot was not able to descend to a position where he felt comfortable initiating the landing flare until the aircraft was almost halfway down the 2,600 foot runway. Then the aircraft "floated for awhile in ground effect" before touching down approximately two-thirds of the way down the runway. During this sequence of events, the student did not attempt to initiate a go-around on his own, and the instructor did not direct him to do one. After the aircraft touched down, the student applied the wheel brakes while holding the yoke full back for aerodynamic braking. Then the instructor came on the controls and assisted with the braking effort. Ultimately the pilots were unable to get the aircraft stopped before it went off the end of the runway, down a steep embankment, and into a ditch. Upon impacting the ditch, the nose wheel folded back and the aircraft sustained substantial damage. The investigation did not find any evidence of problems with the aircraft's flight control or wheel braking systems.

NTSB Probable Cause

The student pilot's misjudgment of distance and his failure to do a go-around. Also causal was the instructor's inadequate supervision of the flight. Factors include gusty crosswinds, the dual student's failure to adequately compensate for those winds, a wet runway surface, and a ditch off the departure end of the runway.

Full Narrative

On May 10, 2004, approximately 1120 Pacific daylight time, a Cessna 172P, N54477, collided with the terrain during the landing roll at Goheen Field, Battle Ground, Washington. Neither the flight instructor or the dual student were injured, but the aircraft, which is owned and operated by Hillsboro Aviation, sustained substantial damage. The 14 CFR Part 91 instructional flight, which departed Hillsboro Airport, Hillsboro, Oregon, about 40 minutes earlier, was being operated in visual meteorological conditions. No flight plan had been filed. There was no report of an ELT activation. According to the instructor pilot, her student, who holds a private pilot certificate for helicopters, was working towards a fixed-wing add-on to his certificate. As per the lesson profile, the student planned a dual cross country flight to Toledo-Winlock, Washington (TDO), and then while en route, the instructor told the student to divert to Goheen Field. After arrival at the field, they over-flew the runway and determined that there was a direct crosswind at what they estimated was about 10 knots. The student then entered a left pattern for runway 15 for a full-stop landing on the damp turf runway. During his first two approaches, the student allowed the aircraft to get too high on final, and in both instances a go-around was initiated. According to both the instructor and the student, on the third approach the aircraft remained on the proper final approach path until it was approximately 50 feet above the ground. At that point the aircraft encountered a wind gust, and it ballooned upward to an extent that the student was not able to descend to a position where he felt comfortable initiating the landing flare until the aircraft was almost half way down the 2,600 foot runway. Then, according to the student, the aircraft "floated for awhile in ground effect" before touching down approximately two-thirds of the way down the runway. During this sequence of events, the student did not attempt to initiate a go-around on his own, and the instructor did not direct him to do one. After the aircraft touched down, the student applied the wheel brakes while holding the yoke full back for aerodynamic braking. Then, according to the student, the instructor came on the controls and assisted with the braking effort. Ultimately the pilots were unable to get the aircraft stopped before it went off the end of the runway, down a steep embankment, and into a ditch. Upon impacting the ditch, the nose wheel folded back and the aircraft sustained substantial damage. According to both the instructor pilot and the FAA Inspector that responded to the scene, there was no evidence of any problems with the aircraft's flight control or wheel braking systems.

Flight

Event TypeAccident
Event Time11:20 PDT
Nearest AirportGoheen Airfield (0nm)
Runway15
Runway Length2600 ft
Runway Width50 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172P
Tail NumberN54477
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320 · Reciprocating · 160
Seats4

People & Injuries

Injury SummaryNo injuries (2 uninjured)
Fatal0
Serious0
Minor0
Uninjured2
Total2
Crew 1Age 26 · Second Class · None
Crew 2None
Crew 3Age 29 · Second Class · None

Conditions

ConditionsVMC
LightDaylight
Wind260° @ 7 kt, gusting 12 kt
Visibility10 sm
CeilingOvercast 5000 ft
Temperature / Dew Point55 / 0 C
Altimeter0
Weather SourcePILO

Appendix: Source Data