27 Jul 2012: Joseph C. Andrews, Jr. Vans RV-4 — Joseph C. Andrews, Jr.

27 Jul 2012: Joseph C. Andrews, Jr. Vans RV-4 (N766HS) — Joseph C. Andrews, Jr.

1 fatality • Valentine, NE, United States

Probable cause

The RV-6 pilot's failure to monitor the location of the RV-4, resulting in the on-ground collision. Contributing to the accident was the RV-6 pilot not ensuring proper separation from the RV-4 and his expectation that the pilot of RV-4 would roll out to the end of the runway.

— NTSB Determination

Accident narrative

On July 27, 2012, about 1350 central daylight time, a Vans RV-6, N766HS, collided with a Vans RV-4, N122JA, after landing at Miller Field (KVTN), Valentine, Nebraska. The pilot of the RV-4 was seriously injured and succumbed to his injuries on August 17, 2012. The pilot of the RV-6 sustained minor injuries. Both airplanes were substantially damaged. Both airplanes were registered to and operated by their respective pilots under the provisions of 14 Code of Federal Regulations Part 91 as personal flights. Visual meteorological conditions prevailed at the time of the accident, and no flight plans had been filed. The cross-country flights originated from Jackson Municipal Airport (KMJQ), Jackson, Minnesota, about 1000.

According to the pilots involved, this was a flight of four airplanes, three Vans RV-4s and a Vans RV-6, that were en route from the 2012 Experimental Aircraft Association AirVenture in Oshkosh, Wisconsin, to their home bases in Washington State. They had landed for fuel at KMJQ and were landing at KVTN for fuel at the time of the accident.

According to the accident report submitted by the pilot of the RV-6, the first airplane, N49DB, an RV-4, landed on runway 14 and exited at the end of the runway. The pilot of the RV-6 said he was following the accident RV-4 (N122JA) and made S-turns on final approach for more separation. He said he also moved to the far left side of the runway in order to avoid wake turbulence over the runway threshold from N122JA. As the RV-6 crossed the runway threshold, he saw that N122JA had landed and was on rollout. The RV-6 pilot flared for landing in a 3-point conventional attitude but did not see that N122JA had moved to the left of the centerline. The collision followed. The pilot exited his airplane and went to the aid of the pilot of N122JA. He said when they landed at other airports, all the airplanes would roll out to the end of the runway, then back-taxi to the ramp together. This was what he had expected.

The pilot of the fourth airplane, N579MS, an RV-4, saw the RV-6 making S-turns for spacing behind the RV-4. He said N49DB, the lead aircraft, had landed and had rolled to the end of runway 14 and N122JA had landed on the first third of the runway. He said the RV-6 was close behind and lined up to the left of the centerline and was beginning to touch down. N122JA slowed and started turning left at a runway intersection. The RV-6 then struck the left side of the RV-4 and cartwheeled over the top of it, coming to rest close to the RV-4. The pilot of N579MS abandoned his approach, went around, and landed uneventfully. He also went to the aid of the injured pilot.

An employee of the airport's fixed base operator, who was in the shop, looked up and saw the RV-4 bounce up in the air. He said the RV-6 had already gone past the RV-4 and was sliding backwards. He said it appeared that the RV-6 had struck the RV-4 behind the pilot's seat with its propeller and landing gear, almost cutting it in half.

A Valentine police officer's report noted that he was dispatched to the airport at 1352. When he arrived, the pilot of the RV-6 told him he did not realize the RV-4 had slowed and had turned into his path.

The RV-4 was nearly cut in half. Both wings on the RV-6 bore leading edge damage, and the vertical stabilizer was twisted.

Contributing factors

  • factor Pilot of other aircraft
  • cause Pilot of other aircraft
  • factor Pilot
  • cause Pilot

Conditions

Weather
VMC, wind 080/07kt, 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.