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

February 25, 2009 · Cessna 172N · N734WD

Johnson County Exec Airport, KS

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
February 25, 2009
Injury Outcomes
No injuries (3 uninjured)
Location
Johnson County Exec Airport, KS
Aircraft
Cessna 172N
Tail Number
N734WD
Operator
Registration Pending
Injuries
None
Aircraft Damage
Substantial
NTSB Number
CEN09LA182

Two airplanes were taxiing to the run up area of the airfield. A Cessna 172N, piloted by a student pilot, had departed a terminal ramp without obtaining proper clearance and was taxiing down the parallel taxiway. A Cessna 172S, piloted by a private pilot, had been cleared to taxi and crossed the active runway. The private pilot had his attention diverted to the run up area to his left, did not look right as he approached the parallel taxiway, and did not see the 172N. The student pilot saw the 172S as she taxied, but thought the other plane would stop and did not take any action to avoid the other airplane. The 172S collided with the 172N resulting in substantial damage to the 172N. The tower controller was monitoring a different area of the airfield and did not see the converging airplanes.

NTSB Probable Cause

The failure of the private pilot to see and avoid the student pilot's airplane, and the failure of the student pilot to avoid the approaching airplane. Contributing to the accident was the failure of the student pilot to obtain taxi clearance.

Full Narrative

On February 25, 2009, about 1617 central standard time, a Cessna 172S airplane, N5258Y, piloted by a private pilot, and a Cessna 172N, N734WD, piloted by a student pilot, collided during taxi operations at Johnson County Executive Airport (OJC), Olathe, Kansas. Neither the private pilot or passenger in the 172S or the student pilot in the 172N were injured. The 172S received minor damage and the 172N was substantially damaged. Both personal flights were being conducted under the provisions of Title 14 Code of Federal Regulations Part 91 without flight plans. Visual meteorological conditions prevailed at the time of the accident. Both local flights were originating at the time of the accident. The 172S airplane was occupied by a private pilot and a non-rated passenger. The private pilot received clearance to taxi from the tower controller and proceeded from the east parking ramp south on taxiway Bravo to taxiway Juliet. Taxiway Juliet crossed runway 18/36 and connected to taxiway Alpha. At taxiway Juliet, the private pilot was instructed to hold short of runway 36 for arriving traffic. After receiving clearance, the private pilot crossed the runway. When the 172S was approaching the intersection of taxiway Juliet and Alpha, the pilot diverted his attention to the run-up area of runway 36 to observe how many airplanes were performing run-ups. As he started the turn, the 172S impacted the left side of 172N. Neither the private pilot or his passenger reported seeing the 172N prior to impact. The 172N was occupied by a solo student pilot. The student pilot had completed a dual instruction ride and landed on Runway 36. She taxied clear of the runway on a midfield taxiway, where air traffic control (ATC) transcripts show she requested and received clearence to taxi to Runway 36 via Taxiway A. She then stopped on the taxiway and her certified flight instructor (CFI) got out of the airplane to allow her to continue for a solo flight. The tower controller contacted her and informed her the CFI could not exit the airplane on the taxiway. The CFI returned to the airplane and the 172N was cleared by the tower controller to taxi to the parking ramp. The student pilot then taxied north on Taxiway A to the west parking ramp. The student pilot reported that her CFI informed her that she "was clear to continue up the taxiway." The CFI deplaned and the student pilot taxied south on taxiway Alpha without obtaining a new taxi clearence from the tower controller. She said she saw 172S on the connecting taxiway prior to impact, but thought it was going to stop. According to FAA investigators, there was a single tower controller on duty at the time of the accident. He was not aware the 172N was taxiing south on taxiway Alpha and was following aircraft activity on a different area of the airfield at the time of the accident. Examination of the 172N revealed a propeller strike to the left wing spar, a bent left horizontal stabilizer, and a bent fuselage tail cone.

Flight

Event TypeAccident
Event Time16:17 CST
Nearest AirportJohnson County Executive Airpo (0nm)
Runway36
Runway Length4098 ft
Runway Width75 ft
Flight Plan FiledUnknown
Flight Plan ActivatedUnknown
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftCessna 172N
Tail NumberN734WD
Aircraft CategoryAir
DamageSubstantial
OperatorRegistration Pending
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsLycoming · O-320 SERIES · Reciprocating · 180 | Lycoming · IO-360-L2A · Reciprocating · 180
Seats4

People & Injuries

Injury SummaryNo injuries (3 uninjured)
Fatal0
Serious0
Minor0
Uninjured3
Total3
Crew 1Age 18 · Third Class · None
Crew 2Age 66 · Third Class · None

Conditions

ConditionsVMC
LightDaylight
WindCalm
Visibility10 sm
CeilingNone
Temperature / Dew Point66 F / 39 C
Altimeter29.98 inHg
Observation Time22:53
Weather SourceWFAC

Appendix: Source Data