# NTSB GAA18CA017: Young David E Pitts S1 C, N25YD, Farmville, VA, October 20, 2017 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Data collection · Final report - Date: October 20, 2017, 10:30 local (14:30 UTC) - Place: Farmville, VA - Coordinates: 37.356109, -78.438613 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=37.3561&lon=-78.4386&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Defining events: [Landing-landing roll: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490); [Landing-landing roll: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) - Highest injury: Serious injuries - Injuries: 1 serious, 1 minor - Status: Completed, report June 14, 2018 - Report: Approved by Office Director - NTSB office: General Aviation Accidents - Parties: FAA - NTSB case key (mKey): 96219 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=GAA18CA017 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/96219/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=96219 - Page: https://openairdocs.org/ntsb/GAA18CA017 ## Probable cause (aircraft 2) 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. ## Probable cause (aircraft 1) 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. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [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: [Young David E PITTS S1-C, 1 case](https://openairdocs.org/ntsb-findings/02021540/cases.md?model=05615QC), [All aircraft, 231 cases](https://openairdocs.org/ntsb-findings/02021540/cases.md) - [Communication (personnel): accuracy of communication](https://openairdocs.org/ntsb-findings/02063515): Personnel issues › Task performance · Pilot of other aircraft (probable cause), aircraft 1; cases with it: [Young David E PITTS S1-C, 1 case](https://openairdocs.org/ntsb-findings/02063515/cases.md?model=05615QC), [All aircraft, 25 cases](https://openairdocs.org/ntsb-findings/02063515/cases.md) - [Object/animal/substance: aircraft](https://openairdocs.org/ntsb-findings/03022040): Environmental issues › Physical environment · Effect on operation (probable cause), aircraft 1; cases with it: [Young David E PITTS S1-C, 1 case](https://openairdocs.org/ntsb-findings/03022040/cases.md?model=05615QC), [All aircraft, 116 cases](https://openairdocs.org/ntsb-findings/03022040/cases.md) - [Attention/monitoring: monitoring other aircraft](https://openairdocs.org/ntsb-findings/02021540): Personnel issues › Psychological · Pilot (probable cause), aircraft 2; cases with it: [Staudacher Jon S-600F, 1 case](https://openairdocs.org/ntsb-findings/02021540/cases.md?model=056197Z), [All aircraft, 231 cases](https://openairdocs.org/ntsb-findings/02021540/cases.md) - [Communication (personnel): accuracy of communication](https://openairdocs.org/ntsb-findings/02063515): Personnel issues › Task performance · Pilot (probable cause), aircraft 2; cases with it: [Staudacher Jon S-600F, 1 case](https://openairdocs.org/ntsb-findings/02063515/cases.md?model=056197Z), [All aircraft, 25 cases](https://openairdocs.org/ntsb-findings/02063515/cases.md) - [Object/animal/substance: aircraft](https://openairdocs.org/ntsb-findings/03022040): Environmental issues › Physical environment · Effect on operation (probable cause), aircraft 2; cases with it: [Staudacher Jon S-600F, 1 case](https://openairdocs.org/ntsb-findings/03022040/cases.md?model=056197Z), [All aircraft, 116 cases](https://openairdocs.org/ntsb-findings/03022040/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Landing-landing roll: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) (defining event), aircraft 1; cases with it: [Young David E PITTS S1-C, 1 case](https://openairdocs.org/ntsb-events/490/sequence.md?model=05615QC), [All aircraft, 1,309 cases](https://openairdocs.org/ntsb-events/490/sequence.md) - [Landing-landing roll: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) (defining event), aircraft 2; cases with it: [Staudacher Jon S-600F, 1 case](https://openairdocs.org/ntsb-events/490/sequence.md?model=056197Z), [All aircraft, 1,309 cases](https://openairdocs.org/ntsb-events/490/sequence.md) ## Analysis (aircraft 2) 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. ## Analysis (aircraft 1) 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. ## Factual narrative (aircraft 2) 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 the 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. ## Factual narrative (aircraft 1) 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. ## Aircraft 1 - Registration: [N25YD](https://openairdocs.org/deregistered/N25YD-2019-11-04), registration cancelled 2019-11-04, S/N 625369829, built 2004 (OpenAirDocs) - Reported make and model: YOUNG DAVID E PITTS S1 C (NO SERIES) - Registry model: [Young David E PITTS S1-C](https://openairdocs.org/model/young-david-e-pitts-s1-c) (registry code 05615QC) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane, amateur-built - Serial number: 625369829 - Year built: 2004 - Airframe hours: 230 - Engines: Lycoming IO-320 150 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Standard, Aerobatic; Special, Experimental (Special) - Last inspection: Condition, April 29, 2017 - Departed: FVX, Farmville, VA - Destination: FVX, Farmville, VA - Airport: FVX, Farmville Rgnl, runway 03, 4,400 × 75 ft, asphalt - Equipment: Unknown ## Aircraft 2 - Registration: [N27KJ](https://openairdocs.org/deregistered/N27KJ-2018-10-02), registration cancelled 2018-10-02, S/N 32, built 2005 (OpenAirDocs) - Reported make and model: STAUDACHER JON S 600F (NO SERIES) - Registry model: [Staudacher Jon S-600F](https://openairdocs.org/model/staudacher-jon-s-600f) (registry code 056197Z) (OpenAirDocs) - Registry engine: [Lycoming IO-540 series](https://openairdocs.org/engine/lycoming-io-540-series) (registry code 41530, reciprocating) (OpenAirDocs) - Category: Airplane, amateur-built - Serial number: 32 - Year built: 2005 - Airframe hours: 730 - Engines: Lycoming AEIO-540-EXP 300 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Airworthiness certificate: Special, Experimental (Special) - Last inspection: Continuous airworthiness, May 3, 2017 - Departed: FVX, Farmville, VA - Destination: FVX, Farmville, VA - Airport: FVX, Farmville Rgnl, runway 21, 4,400 × 75 ft, asphalt - Equipment: Handheld GPS ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot, aircraft N25YD; age 49; injuries: serious; private; airplane ratings: single-engine land; medical: class 3, with waivers/limitations; last flight review February 4, 2017; seat: single; restraint: 5-point; flight hours: 272 total, 97 in this make and model, 218 as pilot in command, 35 in the last 90 days, 10 in the last 30 days - Pilot, aircraft N27KJ; age 58; injuries: minor; commercial; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: basicmed, without waivers/limitations; last flight review November 1, 2015; seat: rear; restraint: 5-point; flight hours: 4,100 total, 282 in this make and model, 4,100 as pilot in command, 38 in the last 90 days, 15 in the last 30 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: calm - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 64 °F, dew point 54 °F - Altimeter: 30.27 inHg - Observed at: KFVX ## 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 20171020020932A](https://openairdocs.org/incident/20171020020932A), Oct 20, 2017: Young David E PITTS S1-C, Farmville, VA, Substantial damage. The accident involved two experimental aircraft, N25YD (pitts S1-C) and N27KJ (staudacher S-600F). The pilot of N25YD had just completed his practice session… - [Accident 20171020020952A](https://openairdocs.org/incident/20171020020952A), Oct 20, 2017: Staudacher Jon S-600F, Farmville, VA, Substantial damage. The accident involved two experimental aircraft, N25YD (pitts S1-C) and N27KJ (Staudacher S-600F). The pilot of N25YD had just completed his practice session… ## Docket (4 files) The files NTSB released with the investigation on April 24, 2018, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=96219. 8.4 MB in all. - (N25YD) Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 3.3 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40462341&FileExtension=.PDF&FileName=(N25YD)%20Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - (N27KJ) Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 2, .PDF, 4.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40462342&FileExtension=.PDF&FileName=(N27KJ)%20Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - FAA Memo (item 3, .PDF, 101 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40462344&FileExtension=.PDF&FileName=FAA%20Memo-Master.PDF - Accident Photos (item 4, .PDF, 911 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40462345&FileExtension=.PDF&FileName=Accident%20Photos-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.