20 Oct 2017: YOUNG DAVID E PITTS S1 C NO SERIES

20 Oct 2017: YOUNG DAVID E PITTS S1 C NO SERIES — Unknown operator

No fatalities • Farmville, VA, United States

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.

— NTSB Determination

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

Contributing factors

  • cause Pilot of other aircraft
  • factor Pilot of other aircraft
  • cause Effect on operation
  • cause Pilot
  • factor Pilot
  • cause Effect on operation

Conditions

Weather
VMC, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.