Skip to content

Atlas / NTSB / GAA17CA223

NTSB CAROL · Event

Event GAA17CA223

2017-04-08 New Carlisle, Ohio, United States Airport · 3OH0 None 1 aircraft Status: Completed

Aircraft involved

Probable cause & findings

The pilot’s decision to land on an occupied runway and his failure to see and avoid the other airplane.

Factual narrative

The pilot of the tailwheel-equipped Piper, reported that his airplane was not equipped with a radio, and that the forward visibility is not good when taxiing, while piloting the airplane from the rear seat. He entered a left downwind for the runway, saw no other aircraft while on final, and continued to land. He added that during the landing roll, as he turned to clear the runway, his airplane collided with a Cessna airplane that was taxiing on the runway after having landed on the same runway, from the opposite direction. He reported that he did not see the Cessna prior to the collision. The Piper sustained substantial damage to the right wing's front spar. The pilot of the Cessna reported that while flying local in the traffic pattern he announced his position and intent to land on the airport's Common traffic advisory frequency (CTAF) during all landings, while at the same time visually checking right and left for traffic. He added that as he was taxiing on the runway toward the exit after landing, he saw the Piper land in the opposite direction on the same runway. Subsequently, the Piper turned diagonally across the runway toward the Cessna, and the two airplanes collided. The Cessna sustained substantial damage to its right wing. Both pilots reported that there were no pre-accident mechanical failures or malfunctions with either airplane that would have precluded normal operation. The pilot of the tailwheel-equipped Piper reported that his airplane was not equipped with a radio and that the forward visibility was not good when taxiing while piloting the airplane from the rear seat. He entered a left downwind for the runway, saw no other aircraft while on final, and continued to land. He added that, during the landing roll, as he turned to clear the runway, his airplane collided with a Cessna airplane that was taxiing on the same runway after having landed on it from the opposite direction. He reported that he did not see the Cessna before the collision. The Piper sustained substantial damage to the right wing's front spar. The pilot of the Cessna reported that, while flying local in the traffic pattern, he announced his position and intent to land on the airport's common traffic advisory frequency during all landings while simultaneously visually checking right and left for traffic. He added that, as he was taxiing on the runway toward the exit after landing, he saw the Piper land in the opposite direction on the same runway. Subsequently, the Piper turned diagonally across the runway toward the Cessna, and the two airplanes collided. The Cessna sustained substantial damage to its right wing. Both pilots reported that there were no preaccident mechanical failures or malfunctions with either airplane that would have precluded normal operation. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12

NTSB Findings

Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).

  • C Personnel issues-Psychological-Attention/monitoring-Monitoring other aircraft-Pilot - C
  • C Environmental issues-Physical environment-Object/animal/substance-Aircraft-Effect on operation - C
  • Environmental issues-Task environment-Physical workspace-Visibility-Effect on personnel
  • C Personnel issues-Psychological-Attention/monitoring-Monitoring other aircraft-Pilot of other aircraft - C
  • C Environmental issues-Physical environment-Object/animal/substance-Aircraft-Effect on operation - C

Verbatim from NTSB's published report. Source file NTSB_2017_GAA17CA223.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.