14 Mar 2014: CESSNA 402B — Marlin Moudy

14 Mar 2014: CESSNA 402B (N419AR) — Marlin Moudy

No fatalities • Stuart, FL, United States

Probable cause

The pilot’s improper preflight planning and fuel management, which resulted in a total loss of power in both engines due to fuel exhaustion.

— NTSB Determination

Accident narrative

On March 14, 2014, about 1730 eastern daylight time, a Cessna 402B, N419AR, was substantially damaged when it collided with terrain while making a forced landing following loss of power in both engines while on short final approach to Witham Field Airport, Stuart, Florida. The commercial pilot sustained minor injuries. The airplane was registered to and operated by the commercial pilot under the provisions of 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed and no flight plan was filed for the personal flight. The flight departed from St. Lucie County International Airport (FPR), Fort Pierce Florida at 1705.

According to the pilot, prior to departing he checked the fuel gauges and determined that he had approximately 28 gallons of fuel onboard, which he calculated as 1 hour of flight time. He did not indicate that he visually checked the fuel level in the tanks before departure. As he approached his destination airport he was instructed by air traffic control (ATC) to enter a 2 mile left base. Approximately 3 miles from the airport, ATC advised him to intercept a 6 mile final. The pilot stated that, at the time, he wasn't aware he had a fuel shortage situation. After turning final, the pilot configured the airplane for landing, and approximately one and a half miles from the runway, the left engine "quit." The pilot elected not to feather the left propeller because it would take six seconds to complete. Instead, he turned the left fuel valve to the left inboard fuel tank and the left engine restarted successfully; however, the right engine then "quit." The pilot then attempted to turn the right fuel valve to the right inboard tank, but the left engine quit again. The pilot made a forced landing in a field and impacted a tree before colliding with the ground, which resulted in substantial damage to both wings and the fuselage. The pilot stated that, upon exiting the airplane, he saw that a section of the right wing was inverted and "fuel was coming out of the right vent."

The Federal Aviation Administration (FAA) inspector who responded to the scene about 3.5 hours after the accident reported that he did not detect any fuel odor at the scene and that examination of the airplane revealed no evidence of fuel leakage. The FAA inspector stated that a law enforcement officer on scene informed him that the fire department personnel who responded to the scene did not spray any foam on the airplane because there was no fuel leaking from it.

Examination of the engines by the FAA revealed that due to external damage, an engine run could not be performed on either engine. An examination of the engines revealed that both engines were rotated by hand and valve train continuity and cylinder compression was obtained. Further examination revealed that spark was obtained on all ignition leads. Examination of the aircraft systems did not revealed any anomalies that would have precluded normal operation. Examination of the left wing tanks revealed that they were void of fuel. The right wing was separated from the fuselage and, although they were breached, no evidence of fuel was noted in any of the right wing tank.

In the pilot's written statement submitted to the NTSB, he indicated that the airplane was topped off with fuel the night before the accident. His statement described that, on the day of the accident, he flew several short flights before the accident flight. He provided his fuel endurance calculation for the airplane with full fuel then subtracted the "flight time" for each of the previous flights from that total endurance time to determine that, before departing on the accident flight, the airplane should have had "2 hours 23 minutes fuel left, without takeoff and landing." The pilot explained the approaches for each of these flights and indicated that he taxied to the ramp to pick up and drop off friends at each destination.

Contributing factors

  • cause Fluid level
  • cause Pilot
  • cause Pilot

Conditions

Weather
VMC, wind 120/12kt, vis 7sm

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.