GAA18CA017
2017-10-20 · Farmville, Virginia, United States · Serious · 1 aircraft · Status: Completed
Airport FVX
Aircraft involved
Probable cause & findings
The other pilot’s failure to see and avoid the other airplane landing in the opposite direction on the runway. Contributing to the accident was the other pilot’s failure to use the correct runway call sign in his radio communications.
Factual narrative
The pilot of the tailwheel equipped Pitts reported that he had departed from runway 3, flew out to the aerobatic practice box, completed his practice, and returned to the airport. He added that, he entered a downwind for runway 3, and announced his location relative to the traffic pattern throughout the landing. He heard another aircraft making calls in the traffic pattern but nothing he was concerned about. After he landed, during the rollout, about midfield, he heard someone announce on the radio that there was an airplane on the runway. This was the last thing the pilot remembered prior to the impact with the S600. The pilot of the tailwheel equipped S600 reported that while he was en route to the designated aerobatic box, he decided that he needed to return to the airport and land. He added that because the winds were calm he elected to land on runway 21. He made a right base call and did not hear anyone else on the radio. He touched down about 300-500 ft down the runway about 75 miles per hour. He further reported that the impact with the Pitts came without warning. According to the Federal Aviation Administration (FAA) Inspector the pilot of the S600 had taken off from runway 3 en route to the practice box. While en route, the pilot noticed a loose water bottle inside the cockpit and returned to the airport to drop it off. The pilot flew a tight right steep approach for runway 21. The inspector noted that all the S600 radio traffic calls were for runway 3. During the landing roll the two airplanes collided. A postaccident examination revealed substantial damage to both airplanes. Both pilots reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation. The pilot of the tailwheel-equipped Pitts reported that he had departed from runway 3, flew out to the aerobatic practice box, completed his practice, and returned to the airport. He added that he entered a downwind for runway 3 and announced his location relative to the traffic pattern throughout the landing. He heard another aircraft making calls in the traffic pattern but nothing he was concerned about. After he landed, during the rollout, about midfield, he heard someone announce on the radio that there was an airplane on the runway. This was the last thing the pilot remembered before impacting the S600. The pilot of the tailwheel-equipped S600 reported that, while he was en route to the designated aerobatic box, he decided that he needed to return to the airport and land. He added that, because the winds were calm, he chose to land on runway 21. He made a right base call and did not hear anyone else on the radio. He touched down about 300 to 500 ft down the runway about 75 mph. He further reported that the impact with the Pitts came without warning. According to the Federal Aviation Administration inspector, the pilot of the S600 had taken off from runway 3 en route to the practice box. While en route, the pilot noticed a loose water bottle inside the cockpit and returned to the airport to drop it off. The pilot flew a tight right steep approach for runway 21. The inspector noted that all the S600 radio traffic calls were for runway 3. During the landing roll, the two airplanes collided. Postaccident examination revealed substantial damage to the forward fuselage. Both pilots reported that there were no preaccident mechanical failures or malfunctions with their airplanes that would have precluded normal operation. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
FAA avdata. C = Cause, F = Factor.
- C Personnel issues-Psychological-Attention/monitoring-Monitoring other aircraft-Pilot of other aircraft - C
- F Personnel issues-Task performance-Communication (personnel)-Accuracy of communication-Pilot of other aircraft - F
- C Environmental issues-Physical environment-Object/animal/substance-Aircraft-Effect on operation - C
- C Personnel issues-Psychological-Attention/monitoring-Monitoring other aircraft-Pilot - C
- F Personnel issues-Task performance-Communication (personnel)-Accuracy of communication-Pilot - F
- C Environmental issues-Physical environment-Object/animal/substance-Aircraft-Effect on operation - C
Verbatim from NTSB's published report. Source file
NTSB_2017_GAA18CA017.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗