18 Apr 2015: BEECH F33A — CLARK DANIEL W

18 Apr 2015: BEECH F33A (N84MD) — CLARK DANIEL W

No fatalities • Puyallup, WA, United States

Probable cause

A total loss of engine power due to fuel starvation as a result of a mechanic’s failure to properly tighten the B-nut to the fuel pump inlet during a recent annual inspection. Contributing to the accident was the pilot's decision to take off despite indications that the engine was not operating normally.

— NTSB Determination

Accident narrative

On April 18, 2015 about 1100 Pacific daylight time, a Beech F33A, N84MD, experienced a total loss of engine power shortly after takeoff from Pierce County Airport – Thun Field (PLU) in Puyallup, Washington. The pilot (sole occupant) sustained no injuries, and the airplane sustained substantial damage to the engine mounting structure. The airplane was registered to, and operated by, the pilot under provisions of 14 Code of Federal Regulations Part 91 as a personal flight. Visual meteorological conditions prevailed for the flight, and no flight plan was filed.

The pilot reported that after an uneventful run-up he took off from the runway. About 350 feet above the ground the engine stopped. There were no abnormal sounds, but instead it sounded as if the mixture had been pulled to cut off. The pilot found a safe place to land and landed in a field. The airplane rolled in the field and down an embankment before the nose wheel collapsed and the airplane came to rest nose down.

A mechanic reported that this was the first flight after an annual inspection dated April 17, 2015. The morning of the accident, the pilot came to pick up the airplane; he filled it with fuel and taxied toward the runway. The pilot was conducting a run-up when the engine died. The airplane was towed back to the maintenance shop and a mechanic visually inspected, and ran, the engine. Since nothing was found the mechanic suggested the pilot wait until Monday to have it further examined. The pilot downloaded the data from the airplane's engine data monitor and took it home to examine. Later that day the pilot returned to the airport and he informed the mechanic he found nothing abnormal on the data. The pilot got back into the airplane and taxied it to the runway. A different mechanic observed the pilot conduct a few high speed taxi tests before he took off. After the takeoff, about 200 feet above the ground, the engine lost power and the airplane glided to a field.

After a postaccident external examination and the installation of an undamaged propeller, an engine run was performed. The engine started without hesitation, however, when the fuel boost pump was turned off the engine shut down shortly thereafter. Upon further examination, the B-nut to the fuel pump inlet was noted to be loose. The fuel line B-nut was tightened and another engine run was attempted. The engine started and it operated normally, even after the boost pump was turned off. The engine was run for about five minutes and the engine RPM was slowly increased to about 2,100 RPM. All engine gauges indicated normal operation.

The airplane's engine data management system was removed from the airframe and sent to the National Transportation Safety Board Recorders Laboratory. On the day of the accident there were seven sessions of data recorded. The accident sequence occurred during the seventh session. The first six sessions occurred during a time span of about 1 hour and 18 minutes. There was an about 1 hour and 14 minutes break between the sixth and seventh sessions. The data revealed that during the seventh session, the engine speed was increased to mid power for approximately one minute. About 2 minutes later the engine RPM was increased to 2,727 RPM followed by 2,462 RPM, 6 seconds later. The engine speed briefly increased to 2,628 for 12 seconds before falling below 1,000 RPM.

Contributing factors

  • cause Maintenance personnel
  • cause Incorrect service/maintenance
  • cause Fluid level
  • factor Pilot

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.