FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

GAA18CA017 · Young David E PITTS S1 C

20 Oct 2017 · Farmville, VA, United States

Young David E PITTS S1 C and Staudacher JON S 600F · Accident: collision during takeoff/landing

Report a problem

Event

NTSB case
GAA18CA017
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Aircraft 1 · Young David E PITTS S1 C

Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N25YD
Operator
Unknown
Onboard fatalities
Unknown
Route
From Farmville Regional Airport (FVX), Farmville, VATo Farmville Regional Airport (FVX), Farmville, VA
Aircraft age
About 13 years (built 2004)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing · landing roll
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Collision during takeoff/landing
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Aircraft 2 · Staudacher JON S 600F

Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N27KJ
Operator
Unknown
Onboard fatalities
Unknown
Route
From Farmville Regional Airport (FVX), Farmville, VATo Farmville Regional Airport (FVX), Farmville, VA
Aircraft age
About 12 years (built 2005)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing · landing roll
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Collision during takeoff/landing
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Environmental issues › Physical environment
  • Personnel issues › Psychological

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

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

Probable cause

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record GAA18CA017
Event ID
20171020X15857
Case number
GAA18CA017
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 108505117ab19fe8d69848d962210bcd78ec036649f3e19e6a5831e61d049818; retrieved 2026-09-13T18:27:59.589Z.