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 20, 2022 · Piper PA-28-140 · N267PC

Saint Joseph, MO

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
November 20, 2022
Injury Outcomes
1 injury (1 serious injury)
Location
Saint Joseph, MO
Aircraft
Piper PA-28-140 (1973)
Tail Number
N267PC
Injuries
Serious
Aircraft Damage
Substantial
NTSB Number
CEN23LA041

The pilot recalled communicating with air traffic control (ATC) for his taxi clearance and did not recall any events after acknowledging the taxi clearance. An ATC controller issued taxi instructions and observed the airplane taxi to the run-up area. After completing the run-up, the pilot was instructed to contact the ATC tower. After no communications were received from the pilot, the controller attempted to initiate contact but there was no reply. Several attempts to contact the pilot via radio were unsuccessful, and the tower controller noticed the airplane had turned around in the run-up area. Based on the airplane’s repositioning, the controller assumed the pilot was looking for a light signal and issued a green light. When the airplane did not move, the controller made several more attempts to contact the pilot but there was no response. The controller then noticed that the airplane appeared to be taxiing back to the general aviation ramp; however, the airplane accelerated, departed the movement area into the grass, and impacted a perimeter fence. Postaccident examination of the airplane revealed no evidence of any preimpact mechanical malfunction or failures that would have precluded normal operation. The airplane sustained substantial damage to the fuselage and both wings. Based on the witnessed circumstances of the accident, it is likely the accident was the result of the pilot’s temporary incapacitation. Postaccident medical care of the pilot revealed the pilot had an undiagnosed brain tumor. The incapacitation was possible due to a seizure trigged by the tumor, and it was also possible that the brain tumor was an incidental finding unrelated to incapacitation. The cause of the pilot’s incapacitation could not be definitively determined from available medical evidence.

NTSB Probable Cause

Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Directional control-Not attained/maintained

Full Narrative

On November 20, 2022, about 1149 central standard time, a Piper PA-28-140 airplane, N267PC, sustained substantial damage when it was involved in an accident near Saint Joseph, Missouri. The pilot sustained serious injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. According to the pilot, he recalled communicating with ATC for his taxi clearance to runway 17. The pilot did not recall any events after acknowledging the taxi clearance. An ATC controller issued taxi instructions to the pilot for a visual flight rules departure and observed the airplane taxi to the run-up area near runway 17. After completing the run-up, the pilot was instructed to contact the ATC tower. After no communications were received from the pilot, the controller attempted to initiate contact but there was no reply. Several attempts to contact the pilot via radio were unsuccessful and the tower controller noticed the airplane had turned around in the run-up area. Based on the airplane’s repositioning, the controller assumed the pilot was looking for a light signal and issued a green light. When the airplane did not move, the controller made several more attempts to contact the pilot but there was no response. The controller then noticed that the airplane appeared to be taxiing back to the general aviation ramp; however, the airplane accelerated, departed the movement area into the grass and impacted a perimeter fence. Postaccident examination of the airplane revealed no evidence of any preimpact mechanical malfunction or failures that would have precluded normal operation. The airplane sustained substantial damage to the fuselage and both wings. According to hospital records, the pilot was taken to the emergency room by emergency medical services following the accident. The pilot reported not remembering the events leading up to the accident. The pilot had a small forehead abrasion without acute injury findings on head/brain imaging. The pilot underwent additional imaging to evaluate for injuries. According to the pilot’s neurosurgery consultation notes, magnetic resonance imaging (MRI) of his brain identified a brain tumor in the left posterior cranial fossa. The neurosurgeon discussed with the pilot the possibility that the tumor may have been connected with the symptoms the pilot described before the accident. The neurosurgeon noted that a complex seizure could not be excluded, particularly with the pilot’s reported prior history of visual problems. A routine electroencephalogram (EEG) performed at the hospital did not show any seizure activity, but was nonspecifically abnormal, with mild diffuse slowing and mild slowing in the left occipital leads compared to the right. The pilot was discharged with a plan for outpatient follow up and instructions not to drive or fly. He was diagnosed with a brain mass and injuries including closed head injury. Hospital records documented that the pilot reported a history of headaches and sometimes used over-the-counter medication on an as-needed basis. The Federal Aviation Administration Forensic Sciences Laboratory performed toxicology testing of blood and urine specimens collected during the initial postaccident medical care. No alcohol or controlled substances were detected, and no substances that were generally considered impairing were detected in the pilot’s blood.

Flight

Event TypeAccident
Event Time11:49 CST
Nearest AirportRosecrans Meml (0nm NNE)
Runway17
Runway Length8061 ft
Runway Width150 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-28-140
Tail NumberN267PC
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320-E3D · Reciprocating · 150
Seats4

People & Injuries

Injury Summary1 injury (1 serious injury)
Fatal0
Serious1
Minor0
Uninjured0
Total1
Crew 1Age 49 · First Class · Serious

Conditions

ConditionsVMC
LightDaylight
Wind210° @ 14 kt, gusting 20 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point39 F / 18 F
Altimeter30.34 inHg
Observation Time16:53
Weather SourceWFAC

Appendix: Source Data