GAA18CA017

NTSB accident investigation · Young David E Pitts S1 C · Farmville, VA · October 20, 2017

Accident · Serious injuriesData collectionFinal report
Date
October 20, 2017, 10:30 local (14:30 UTC)
Place
Farmville, VA
Injuries
1 serious, 1 minor
Phase of flight
Landing
Aircraft
N25YDYoung David E Pitts S1 CN27KJStaudacher Jon S 600F
Defining events
Landing-landing roll: Collision during takeoff/landLanding-landing roll: Collision during takeoff/land
Weather
Visual (VMC) · Day
Status
Completed · report June 14, 2018
Report
Approved by Office Director
NTSB office
General Aviation Accidents
Parties
FAA
Case key
96219

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

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.

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 · 6

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

N25YD · Young David E Pitts S1 C

Attention/monitoring: monitoring other aircraftPersonnel issues › Psychological · Pilot of other aircraftYoung David E PITTS S1-C: 1 caseAll aircraft: 231 casesProbable cause
Communication (personnel): accuracy of communicationPersonnel issues › Task performance · Pilot of other aircraftYoung David E PITTS S1-C: 1 caseAll aircraft: 25 casesProbable cause
Object/animal/substance: aircraftEnvironmental issues › Physical environment · Effect on operationYoung David E PITTS S1-C: 1 caseAll aircraft: 116 casesProbable cause

N27KJ · Staudacher Jon S 600F

Object/animal/substance: aircraftEnvironmental issues › Physical environment · Effect on operationStaudacher Jon S-600F: 1 caseAll aircraft: 116 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

N25YD · Young David E Pitts S1 C

N27KJ · Staudacher Jon S 600F

Analysis

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

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.

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 · 2

Registration
N25YD
Reported as
Young David E Pitts S1 C (NO SERIES)
Category
Airplane, amateur-built
Serial number
625369829
Built
2004
Airframe hours
230
Engine
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

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Registration
N27KJ
Reported as
Staudacher Jon S 600F (NO SERIES)
Category
Airplane, amateur-built
Serial number
32
Built
2005
Airframe hours
730
Engine
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

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew · 2

As NTSB recorded them. NTSB leaves out names.

Role
Pilot, aircraft N25YD
Age
49
Injuries
Serious
Certificate
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
Role
Pilot, aircraft N27KJ
Age
58
Injuries
Minor
Certificate
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

Docket · 4

The files NTSB released with the investigation on April 24, 2018, on NTSB’s docket system: statements, records, photos and specialists’ reports. 8.4 MB in all.

FAA reports on this event · 2

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.