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

September 28, 2002 · Piper PA-28-161 · N132ND

Spokane, WA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
September 28, 2002
Injury Outcomes
No injuries (2 uninjured)
Location
Spokane, WA
Aircraft
Piper PA-28-161
Tail Number
N132ND
Injuries
None
Aircraft Damage
Substantial
NTSB Number
SEA02LA186

The flight instructor told his student to make his landing on the second centerline stripe of the runway. After turning final, the student established a stabilized approach at the correct airspeed, but with a glideslope that would take him past the desired second stripe touchdown point. Because runway length was not a critical factor, the instructor decided to let the student continue on the higher than desired glideslope so that he would learn that it would take him past the desired point of touchdown. Reportedly, when the aircraft was still about 20 feet above the runway surface, the student reduced the power to idle and started to flare prematurely, and the aircraft ultimately leveled off about 10 feet above the runway. The instructor then advised the student that they were too high, and that if they landed from that height "...it would be rough." The student therefore added power (about one-quarter throttle) and lowered the nose in order to descend to a point closer to the runway. Soon after starting to make this adjustment, the student flared a second time, and the aircraft fell to the runway surface from an altitude that was still too high. As the aircraft began to fall toward the runway, the instructor reached for the throttle in order to initiate a go-around, but just as he made contact with it, the aircraft impacted the runway with sufficient force to result in substantial damage. At that point, the instructor took control of the aircraft, completed the landing sequence, and then taxied to an area where the aircraft could be checked for damage. According to the instructor, there was no indication of any problem with the engine or flight control system that would have contributed to the accident, and the FAA Inspector who looked at the aircraft did not find evidence of any such anomaly.

NTSB Probable Cause

The flight instructor's delay of the remedial action necessary to correct for the student pilot's error during the landing flare. Factors include the student pilot's misjudgment of the aircraft's height above the runway when he initiated the flare.

Full Narrative

On September 28, 2002, approximately 1525 Pacific daylight time, a Piper PA-28-161, N132ND, experienced a hard landing at Spokane International Airport, Spokane, Washington. The flight instructor and his student were not injured, but the aircraft, which is owned and operated by the University of North Dakota, sustained substantial damage. The 14 CFR Part 91 instructional flight, which departed the same location about 25 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 flight instructor, he told his student to make his landing on the second centerline stripe of the runway. After turning final, the student established a stabilized approach at the correct airspeed, but with a glideslope that would take him passed the desired second stripe touchdown point. Because runway length was not a critical factor, the instructor decided to let the student continue on the higher than desired glideslope so that he would learn that it would take him past the desired point of touchdown. Reportedly, when the aircraft was still about 20 feet above the runway surface, the student reduced the power to idle and started to flare prematurely, and the aircraft ultimately leveled off about 10 feet above the runway. The instructor then advised the student that they were too high, and that if they landed from that height "...it would be rough." The student therefore added power (about one-quarter throttle) and lowered the nose in order to descend to a point closer to the runway. Soon after starting to make this adjustment, the student flared a second time, and the aircraft fell to the runway surface from an altitude that was still too high. As the aircraft began to fall toward the runway, the instructor reached for the throttle in order to initiate a go-around, but just as he made contact with it, the aircraft impacted the runway with sufficient force to result in substantial damage. At that point, the instructor took control of the aircraft, completed the landing sequence, and then taxied to an area where the aircraft could be checked for damage. According to the instructor, there was no indication of any problem with the engine or flight control system that would have contributed to the accident, and the FAA Inspector who looked at the aircraft did not find evidence of any such anomaly.

Flight

Event TypeAccident
Event Time15:25 PDT
Nearest AirportSpokane International (0nm)
Runway25
Runway Length8199 ft
Runway Width150 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-28-161
Tail NumberN132ND
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320-D3G · Reciprocating · 160
Seats4

People & Injuries

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

Conditions

ConditionsVMC
LightDaylight
Wind7 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point63 F / 0 C
Altimeter29.84 inHg
Weather SourcePILO

Appendix: Source Data