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

November 11, 2016 · Piper PA 28R 200 · N9466K

Payallup, WA

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
November 11, 2016
Injury Outcomes
No injuries (2 uninjured)
Location
Payallup, WA
Aircraft
Piper PA 28R 200 (1976)
Tail Number
N9466K
Operator
Spanaflight
Injuries
None
Aircraft Damage
Substantial
NTSB Number
GAA17CA072

According to the pilot under examination, he was to accomplish a short-field landing to the runway 17 numbers during his single-engine airplane flight instructor practical examination. He reported that, during the transition from final to the flare, the bottom of the fuselage struck an aircraft traffic monitoring camera system. The camera system was located about 125 ft north of the runway 17 threshold and was about 8 inches high. After striking the camera, the pilot added power and landed the airplane on the runway 17 numbers. There were no NOTAMs regarding the use of the aircraft traffic monitoring camera system issued at the time of the accident. However, the next day, the airport manager issued a NOTAM regarding the deployment of the camera system. The airplane sustained substantial damage to the right wing spar. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

NTSB Probable Cause

The airport’s failure to issue a NOTAM regarding the deployment of the traffic monitoring camera system before the accident, which resulted in the airplane striking the camera system during a short-field approach and landing.

Full Narrative

According to the pilot under examination, he was to accomplish a short field landing to the runway 17 numbers, during his single engine airplane flight instructor practical examination. He reported that during the transition from final to the flare, the bottom of the fuselage struck an aircraft traffic monitoring camera system. The camera system was located about 125 ft. north of the runway 17 threshold, and stood about 8 inches in height. After striking the camera, the pilot added power and landed the airplane on the runway 17 numbers. There were no NOTAM's regarding the use of the aircraft traffic monitoring system issued at the time of the accident. However, the next day a NOTAM regarding the deployment of the camera system was issued by the airport manager. The airplane sustained substantial damage to the right wing spar. The pilot reported that there were no pre-accident mechanical malfunctions or failures with the airplane that would have precluded normal operation.

Flight

Event TypeAccident
Event Time12:30 PST
Nearest AirportPierce County - Thun Field (0nm SW)
Runway17
Runway Length3650 ft
Runway Width60 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA 28R 200
Tail NumberN9466K
Aircraft CategoryAir
DamageSubstantial
OperatorSpanaflight
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · IO-360 · Reciprocating · 200
Seats4

People & Injuries

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

Conditions

ConditionsVMC
LightDaylight
WindCalm
Visibility10 sm
CeilingNone
Temperature / Dew Point59 / 55
Altimeter29.90 inHg
Observation Time20:15
Weather SourceWFAC

Appendix: Source Data