The U.S. aircraft register, updated daily
Accidents · NTSB GAA18CA017 · Final report

Amateur-built PITTS S1 C and Staudacher Jon S 600F accident near Farmville, Virginia, October 20, 2017

On October 20, 2017 at about 2:30 pm local time, 2 aircraft, amateur-built PITTS S1 C (N25YD) and Staudacher Jon S 600F (N27KJ), were involved in the same accident near Farmville, Virginia (Farmville Rgnl airport). 1 person was seriously injured and 1 person had minor injuries. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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.
The pilot’s failure to see and avoid the other airplane landing in the opposite direction on the runway. Contributing to the accident was the pilot’s failure to use the correct runway call sign in his radio communications.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
October 20, 2017 · about 2:30 pm local time
Place
Farmville, Virginia · Farmville Rgnl · map
Type
Accident · collision on the ground
Injuries
1 person was seriously injured and 1 person had minor injuries.
Weather
visual conditions (good weather)
Aircraft 1
Amateur-built PITTS S1 C NO SERIES, built 2004
Registration
N25YD · no longer on the register · serial 625369829
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)
Aircraft 2
Staudacher Jon S 600F NO SERIES, built 2005, amateur-built
Registration
N27KJ · no longer on the register · serial 32
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative for the amateur-built PITTS S1 C final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The NTSB's narrative for the Staudacher Jon S 600F final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record for the amateur-built PITTS S1 C from the NTSB's investigation tables, in plain English

What happened, in order

  1. Collision during takeoff/land during landing (landing roll) defining event

The NTSB's findings

  • cause Personnel issues › Psychological › Attention/monitoring › Monitoring other aircraft › Pilot of other aircraft
  • factor Personnel issues › Task performance › Communication (personnel) › Accuracy of communication › Pilot of other aircraft
  • cause Environmental issues › Physical environment › Object/animal/substance › Aircraft › Effect on operation

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 272 hours in all; 97 in this make and model; 35 in the last 90 days; 10 in the last 30 days; 218 as pilot in command
  • Last flight review: February 4, 2017
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: sngl
  • Injury: serious injuries

The aircraft

  • Airframe total time: 230 hours
  • Last inspection: condition inspection, April 29, 2017
  • Seats: 1
  • Landing gear: fixed
  • Engine: Lycoming IO-320 (piston); 4,000 hours total

The flight

  • Departed from: FVX Farmville VA at 2:05 pm
  • Destination: FVX Farmville VA
  • Flight plan: none
  • Runway 03, 4,400 ft by 75 ft

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 64°F (18°C), dew point 54°F (12°C)
  • Altimeter: 30.27 inHg
  • Observation at 2:15 pm from KFVX

Injuries

FatalSeriousMinorNone
Flight crew1

The factual record for the Staudacher Jon S 600F from the NTSB's investigation tables, in plain English

What happened, in order

  1. Collision during takeoff/land during landing (landing roll) defining event

The NTSB's findings

  • cause Personnel issues › Psychological › Attention/monitoring › Monitoring other aircraft › Pilot
  • factor Personnel issues › Task performance › Communication (personnel) › Accuracy of communication › Pilot
  • cause Environmental issues › Physical environment › Object/animal/substance › Aircraft › Effect on operation

Pilot

  • Certificate: commercial pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 4,100 hours in all; 282 in this make and model; 38 in the last 90 days; 15 in the last 30 days; 4,100 as pilot in command; 1,000 on instruments
  • Last flight review: November 1, 2015
  • Medical certificate: BasicMed (without waivers/limitations)
  • Seat: rear
  • Injury: minor injuries

The aircraft

  • Airframe total time: 730 hours
  • Last inspection: continuous airworthiness programme, May 3, 2017
  • Maximum gross weight: 2,100 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Lycoming AEIO-540-EXP (piston); 300 hours total

The flight

  • Departed from: FVX Farmville VA at 2:30 pm
  • Destination: FVX Farmville VA
  • Flight plan: none
  • Runway 21, 4,400 ft by 75 ft

Injuries

FatalSeriousMinorNone
Flight crew1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.