10 Aug 2014: JACKSON JEREMIAH D VANS RV6A

10 Aug 2014: JACKSON JEREMIAH D VANS RV6A (N214MJ) — Unknown operator

No fatalities • West Palm Beach, FL, United States

Probable cause

The pilot’s excessive landing speed, which resulted in a runway excursion and noseover. Contributing to the accident was a partial loss of engine power during an attempted go-around for reasons that could not be determined because no anomalies were identified during postaccident examination.

— NTSB Determination

Accident narrative

On August 10, 2014, about 1123 eastern daylight time, a Jackson Van's RV6A, N214MJ, was substantially damaged following a partial loss of engine power and precautionary landing at Palm Beach County Park Airport (LNA), West Palm Beach, Florida. The private pilot received minor injuries. The airplane was operated by the pilot under the provisions of 14 CFR Part 91 and no flight plan was filed. Day, visual meteorological conditions prevailed for the personal flight that originated at Kissimmee Airport (ISM), Kissimmee, Florida and was destined for North Perry Airport (HWO), Pembroke Pines, Florida.

According to the pilot, the ground operations, takeoff, and departure were normal. About 20 minutes into the flight, at 5,500 feet above mean sea level, the engine began "missing," but continued to run. This occurred about every minute, and lasted about one second each time. He reported the engine issue to air traffic control, and alternate airport information was provided along with flight following. He climbed to 10,000 feet and assessed the situation. He switched fuel tanks, checked the magnetos, adjusted the mixture, and cycled the propeller. After scanning his engine instruments, he noted that engine rpm was 1,300 with 22" manifold pressure.

After discussing his situation with ATC, he elected to divert into LNA, about 13 miles to the south-southeast. He set up for an approach to runway 27. He crossed the runway threshold about 25 feet above the ground and at 110 knots. Unable to slow the airplane to a safe landing speed, he attempted a go-around. The engine "appeared to rev up" but there was little power observed. He discontinued the go-around and landed straight ahead. The airplane departed the runway at the departure end and the pilot applied rudder and aileron controls to avoid striking the perimeter fence. The airplane flipped over and came to rest, inverted.

An inspector with the Federal Aviation Administration responded to the accident site and examined the wreckage. He confirmed substantial damage to both wings and extensive damage to the fuselage.

The airplane was equipped with a Dynon EFIS-D6 (D6) uncertified electronic flight information system (EFIS). The D6 was removed by aircraft recovery personal and sent to the NTSB Vehicle Recorders Laboratory, Washington, DC for possible flight and engine data retrieval.

The D6 incorporated a 3.8" display for mounting in the cockpit of non-type certificated aircraft. The instrument integrated multiple flight instruments including attitude, airspeed, altitude, magnetic compass, turn rate, slip/skid ball, bank angle, pitch angle, and vertical speed. The unit contained an Air Data, Attitude and Heading Reference System (ADAHRS) to provide air data, attitude, and heading to the display.

There was no log file capability on the D6 which meant that no parameters are recorded or stored. Based upon discussions with Dynon technical support representatives, there was no logging capability planned for future firmware releases. The only information available from the device is the last input altimeter setting (30.08").

The wreckage was examined by a NTSB Senior Air Safety Investigator at the wreckage storage facility. A review of the cockpit revealed that the fuel selector was positioned to the right main fuel tank. The mixture and propeller levers were full forward and the throttle lever was retarded. The mixture and throttle linkages remained attached to the fuel metering unit. No obstructions were observed in the air intake. The top spark plugs were removed; their electrodes were intact and exhibited color consistent with a rich mixture. The valve covers were removed and oil was noted throughout the engine. When the propeller was rotated by hand, camshaft, crankshaft, and valve train continuity were confirmed and thumb compression was attained on all cylinders. Several drops of fuel were recovered from the fuel line to the fuel metering unit. The fuel was clear and consistent with 100 low lead aviation gasoline. Additionally, the fuel screen in the fuel metering unit was absent of contamination. Approximately 10 gallons of fuel had been drained from the wreckage and retained at the recovery facility; the fuel was clear, blue, and absent of moisture when tested with water finding paste.

Contributing factors

  • cause Airspeed — Not attained/maintained
  • cause Pilot

Conditions

Weather
VMC, wind 220/04kt, 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.