2 Oct 2016: VOLAIRCRAFT 10A NO SERIES

2 Oct 2016: VOLAIRCRAFT 10A NO SERIES (N6666D) — Unknown operator

No fatalities • Mandan, ND, United States

Probable cause

The student pilot’s failure to maintain the proper approach path on landing, which resulted in impact with terrain short of the runway.

— NTSB Determination

Accident narrative

On October 2, 2016, about 1557 central daylight time, a Volaircraft 10A airplane, N6666D, registered to the student pilot, was destroyed by post impact fire after it landed short of runway 13 at the Mandan Municipal Airport (Y19), Mandan, North Dakota. The student pilot, who was the sole occupant, was not injured. The flight was being conducted under the provisions of Federal Code of Regulations Part 91. Visual meteorological conditions prevailed and a flight plan was not filed. The local flight had originated from Y19.

According to local respondent authorities, the airplane landed short of the runway and skidded to a stop beside the paved runway surface. After the student pilot exited uninjured, the airplane caught fire and was destroyed. The student pilot did not report any mechanical problems prior to the event and there were no witnesses. On NTSB Form 6120, the student pilot stated that he encountered turbulence on final approach and pushed the airplane downward. He stated that a fuel line ruptured upon impact and sparks ignited, resulting in a post-impact fire. There were three distinct ground impressions in a grassy area just prior to the paved runway threshold. The impressions correlated with the fixed landing gear of the aircraft.Visual inspection of the wreckage by an FAA inspector revealed that the fuel/gascolator line had ruptured during the impact.

The reported local weather at the time of the accident was: Wind 130 at 3 knots, 10 miles visibility, temperature 22 C, dew point 13 C, altimeter 29.92. Soon after the accident when the aircraft was still on fire, a photo was taken of the accident scene by first responders. The photo shows billowing smoke going straight up from the fire. the photo is included in the public docket for this case file.

According to the FAA and the pilot's submitted NTSB Form 6120, the student pilot reported a total of 20 hours of total flight time, all of which were flown in the accident airplane.

Contributing factors

  • cause Pilot
  • factor Pilot

Conditions

Weather
VMC, wind 130/03kt, 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.