# NTSB CEN09LA182: Cessna 172N, N734WD, Johnson County Exec Airport, KS, February 25, 2009 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: February 25, 2009, 16:17 local (22:17 UTC) - Place: Johnson County Exec Airport, KS - Coordinates: 38.840278, -94.736389 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=38.8403&lon=-94.7364&mi=10 - Phase of flight: [Prior to flight](https://openairdocs.org/ntsb-phases/100) (OpenAirDocs' grouping) - Defining events: [Prior to flight: Ground collision](https://openairdocs.org/ntsb-events/200); [Prior to flight: Ground collision](https://openairdocs.org/ntsb-events/200) - Highest injury: No injuries - Injuries: 3 uninjured - Status: Completed, report August 13, 2009 - Report: Approved by Office Director - NTSB office: Central Region - Parties: FAA - NTSB case key (mKey): 73412 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CEN09LA182 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/73412/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=73412 - Page: https://openairdocs.org/ntsb/CEN09LA182 ## Probable cause (aircraft 2) 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. ## Probable cause (aircraft 1) 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. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Action: forgotten action/omission](https://openairdocs.org/ntsb-findings/02041035): Personnel issues › Action/decision · Student/instructed pilot (probable cause), aircraft 1; cases with it: [Cessna 172N, 4 cases](https://openairdocs.org/ntsb-findings/02041035/cases.md?model=2072434), [All aircraft, 440 cases](https://openairdocs.org/ntsb-findings/02041035/cases.md) - [Communication (personnel): lack of communication](https://openairdocs.org/ntsb-findings/02063510): Personnel issues › Task performance · Student/instructed pilot (probable cause), aircraft 1; cases with it: [Cessna 172N, 4 cases](https://openairdocs.org/ntsb-findings/02063510/cases.md?model=2072434), [All aircraft, 84 cases](https://openairdocs.org/ntsb-findings/02063510/cases.md) - [Attention/monitoring: monitoring other aircraft](https://openairdocs.org/ntsb-findings/02021540): Personnel issues › Psychological · Pilot of other aircraft (probable cause), aircraft 1; cases with it: [Cessna 172N, 9 cases](https://openairdocs.org/ntsb-findings/02021540/cases.md?model=2072434), [All aircraft, 231 cases](https://openairdocs.org/ntsb-findings/02021540/cases.md) - [Action: forgotten action/omission](https://openairdocs.org/ntsb-findings/02041035): Personnel issues › Action/decision · Pilot of other aircraft (probable cause), aircraft 2; cases with it: [Cessna 172S, 4 cases](https://openairdocs.org/ntsb-findings/02041035/cases.md?model=2072439), [All aircraft, 440 cases](https://openairdocs.org/ntsb-findings/02041035/cases.md) - [Communication (personnel): lack of communication](https://openairdocs.org/ntsb-findings/02063510): Personnel issues › Task performance · Pilot of other aircraft (probable cause), aircraft 2; cases with it: [Cessna 172S, 4 cases](https://openairdocs.org/ntsb-findings/02063510/cases.md?model=2072439), [All aircraft, 84 cases](https://openairdocs.org/ntsb-findings/02063510/cases.md) - [Attention/monitoring: monitoring other aircraft](https://openairdocs.org/ntsb-findings/02021540): Personnel issues › Psychological · Pilot (probable cause), aircraft 2; cases with it: [Cessna 172S, 12 cases](https://openairdocs.org/ntsb-findings/02021540/cases.md?model=2072439), [All aircraft, 231 cases](https://openairdocs.org/ntsb-findings/02021540/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Prior to flight: Miscellaneous/other](https://openairdocs.org/ntsb-events/900), aircraft 1; cases with it: [Cessna 172N, 15 cases](https://openairdocs.org/ntsb-events/900/sequence.md?model=2072434), [All aircraft, 1,556 cases](https://openairdocs.org/ntsb-events/900/sequence.md) - [Prior to flight: Ground collision](https://openairdocs.org/ntsb-events/200) (defining event), aircraft 1; cases with it: [Cessna 172N, 16 cases](https://openairdocs.org/ntsb-events/200/sequence.md?model=2072434), [All aircraft, 618 cases](https://openairdocs.org/ntsb-events/200/sequence.md) - [Prior to flight: Miscellaneous/other](https://openairdocs.org/ntsb-events/900), aircraft 2; cases with it: [Cessna 172S, 28 cases](https://openairdocs.org/ntsb-events/900/sequence.md?model=2072439), [All aircraft, 1,556 cases](https://openairdocs.org/ntsb-events/900/sequence.md) - [Prior to flight: Ground collision](https://openairdocs.org/ntsb-events/200) (defining event), aircraft 2; cases with it: [Cessna 172S, 23 cases](https://openairdocs.org/ntsb-events/200/sequence.md?model=2072439), [All aircraft, 618 cases](https://openairdocs.org/ntsb-events/200/sequence.md) ## Analysis (aircraft 2) 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. ## Analysis (aircraft 1) 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. ## Factual narrative (aircraft 2) 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. ## Factual narrative (aircraft 1) 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. ## Aircraft 1 - Registration: [N734WD](https://openairdocs.org/deregistered/N734WD-2014-05-09), registration cancelled 2014-05-09, S/N 17269165, built 1977 (OpenAirDocs) - Reported make and model: CESSNA 172N - Registry model: [Cessna 172N](https://openairdocs.org/model/cessna-172n) (registry code 2072434) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17269165 - Engines: LYCOMING O-320 SERIES 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Registration Pending - Registered owner: Registration Pending - Airworthiness certificate: Standard, Normal - Departed: OJC, Johnson County Exec Airport, KS - Destination: OJC, Johnson County Exec Airport, KS - Flight plan: Unknown - Airport: OJC, Johnson County Executive Airpo, runway 36, 4,098 × 75 ft, concrete ## Aircraft 2 - Registration: [N5258Y](https://openairdocs.org/aircraft/N5258Y), registered now, S/N 172S9141, built 2002 (OpenAirDocs) - Reported make and model: CESSNA 172S - Registry model: [Cessna 172S](https://openairdocs.org/model/cessna-172s) (registry code 2072439) (OpenAirDocs) - Registry engine: [Lycoming IO-360-L2A](https://openairdocs.org/engine/lycoming-io-360-l2a) (registry code 41597, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 172S9141 - Airframe hours: 3437 - Engines: LYCOMING IO-360-L2A 180 horsepower reciprocating - Damage: Minor damage - Flight: Personal, Part 91 - Operator: T&C Aviation Enterprises Inc DBA, doing business as Air Associates of Kansas - Registered owner: T&C Aviation Enterprises Inc DBA - Airworthiness certificate: Standard, Normal - Last inspection: Annual, December 31, 2008 - Departed: OJC, Johnson County Exec Airport, KS - Destination: OJC, Johnson County Exec Airport, KS - Airport: OJC, Johnson County Executive Airpo, runway 36, 4,098 × 75 ft, concrete ## Flight crew As NTSB recorded them. NTSB leaves out names. - Student pilot, aircraft N734WD; age 18; injuries: none; student; medical: class 3, with waivers/limitations; seat: left; flight hours: 20 total, 20 in this make and model - Pilot, aircraft N5258Y; age 66; injuries: none; private; airplane ratings: single-engine land; medical: class 3, without waivers/limitations; last flight review February 20, 2008; seat: left; flight hours: 478 total, 303 in this make and model ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 66 °F, dew point 39 °F - Altimeter: 29.98 inHg - Observed at: OJC ## FAA reports on this event (2) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20090225004329A](https://openairdocs.org/incident/20090225004329A), Feb 25, 2009: Cessna 172N, Olathe, KS, Substantial damage. (-23) Prior to the student pilot's second supervised solo, she taxied N734WD to Kansas city aviation center FBO to let her instructor off on the ramp. The… - [Accident 20090225004399A](https://openairdocs.org/incident/20090225004399A), Feb 25, 2009: Cessna 172S, Olathe, KS, Minor damage. (-23) Prior to the accident, the PIC of N5258Y received an ATC clearance to runway 36 via taxiway b. he held short of the active runway awaiting a clearance to… ## Other investigations on N734WD (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB CHI00LA254](https://openairdocs.org/ntsb/CHI00LA254), Aug 12, 2000: Cessna 172N (N734WD), North Platte, NE, substantial damage. Probable cause: the pilot of the other airplane not maintaining clearance while taxiing. A factor was the dark night. ## Docket (8 files) The files NTSB released with the investigation on June 15, 2009, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=73412. 4.1 MB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 - N734WD Pilot (item 1, .PDF, 700 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40314128&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1%20-%20N734WD%20Pilot-Redacted.PDF - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 - N5258Y Pilot (item 2, .PDF, 633 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40314129&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1%20-%20N5258Y%20Pilot-Redacted.PDF - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 - N5258Y Owner (item 3, .PDF, 551 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40314131&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1%20-%20N5258Y%20Owner-Master.PDF - Witness Statement - Tower Controller (item 4, .PDF, 59 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40314136&FileExtension=.PDF&FileName=Witness%20Statement%20-%20Tower%20Controller-Redacted.PDF - Transcript of Radio Communications (item 5, .PDF, 22 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40314137&FileExtension=.PDF&FileName=Transcript%20of%20Radio%20Communications-Master.PDF - Photo - 734WD 1 (item 6, .PDF, 674 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40314139&FileExtension=.PDF&FileName=Photo%20-%20734WD%201-Master.PDF - Photo - 734WD 2 (item 7, .PDF, 876 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40314140&FileExtension=.PDF&FileName=Photo%20-%20734WD%202-Master.PDF - Photo - 734WD 3 (item 8, .PDF, 575 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40314141&FileExtension=.PDF&FileName=Photo%20-%20734WD%203-Master.PDF From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.