25 Feb 2009: CESSNA 172N — REGISTRATION PENDING

25 Feb 2009: CESSNA 172N (N5258Y) — REGISTRATION PENDING

No fatalities • Johnson County Exec Airport, KS, United States

Probable cause

Failure of the pilot of the Cessna 172S to ensure the taxiway was clear prior to initiating the turn. Contributing to the accident was the failure of the pilot of the Cessna 172N to obtain taxi clearance prior to entering the movement area.

— NTSB Determination

Accident 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.

Contributing factors

  • factor Student pilot
  • factor Student pilot
  • cause Pilot of other aircraft
  • factor Pilot of other aircraft
  • factor Pilot of other aircraft
  • cause Pilot

Conditions

Weather
VMC, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.