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

December 25, 2001 · Piper PA-32-300 · N666DE

Olathe, KS

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
December 25, 2001
Injury Outcomes
No injuries (2 uninjured)
Location
Olathe, KS
Aircraft
Piper PA-32-300
Tail Number
N666DE
Injuries
None
Aircraft Damage
Substantial
NTSB Number
CHI02LA056

The airplane was damaged when it went off of the left side of the runway, crossed a parallel taxiway and went down an embankment during landing. The pilot stated that when he applied the brakes during the landing, "...it felt like the left brake 'grabbed' and jerked me to the left. While still on the runway I applied power and right rudder to try to straighten me out. I immediately [went] left very quickly on to the grass." Subsequent to the accident, the nose landing gear fork was found fractured in two places near the attachment to the strut portion of the landing gear. No other anomalies were found with respect to the airplane, or its systems that were determined to have existed prior to impact. The nose landing gear fork was examined by the National Transportation Safety Board's Materials Laboratory. The fork was found to have deformation consistent with excessive lateral loading. The fracture surfaces were examined and both fractures exhibited signatures consistent with overstress. No evidence of fatigue or preexisting damage was found.

NTSB Probable Cause

The pilot's failure to maintain directional control during landing resulting in the overload of the nose gear fork. The overload failure of the nose landing gear fork, the embankment, and the remedial action not possible were contributing factors.

Full Narrative

On December 25, 2001, at 1016 central standard time, a Piper PA-32-300, N666DE, piloted by a private pilot, sustained substantial damage during landing on runway 18 (4,099 feet by 75 feet, concrete) at the Johnson County Executive Airport (OJC), Olathe, Kansas. The airplane went off of the left side of the runway, crossed a parallel taxiway and went down an embankment. The 14 CFR Part 91 personal flight was not on a flight plan and was operating in visual meteorological conditions. The pilot and his one pasasenger were not injured. The local flight originated at an undetermined time. In a written statement, the pilot said that he landed on the centerline of runway 18 at OJC and when he applied the brakes, "...it felt like the left brake 'grabbed' and jerked me to the left. While still on the runway I applied power and right rudder to try to straighten me out. I immediately [went] left very quickly on to the grass." The airplane crossed a taxiway, down an embankment and impacted in a creek. A postaccident examination of the airplane was conducted. The nose landing gear fork was found fractured in two places near the attachment to the strut portion of the landing gear. No other anomalies were found with respect to the airplane, or its systems that were determined to have existed prior to impact. The nose landing gear fork was examined by the National Transportation Safety Board's Materials Laboratory. The fork was found to have deformation consistent with excessive lateral loading. The fracture surfaces were examined and both fractures exhibited signatures consistent with overstress. No evidence of fatigue or preexisting damage was found.

Flight

Event TypeAccident
Event Time10:16 CST
Nearest AirportJohnson County Executive (0nm N)
Runway18
Runway Length4099 ft
Runway Width75 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftPiper PA-32-300
Tail NumberN666DE
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · IO-540 · Reciprocating · 300
Seats6

People & Injuries

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

Conditions

ConditionsVMC
LightDaylight
Wind260° @ 10 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point27 C / 18 C
Altimeter30.14 inHg
Observation Time16:53
Weather SourceWFAC

Appendix: Source Data