22 Feb 2009: PIPER PA-28C-235 — 9487W LLC

22 Feb 2009: PIPER PA-28C-235 (N9487W) — 9487W LLC

No fatalities • Falcon, CO, United States

Probable cause

A loss of engine power due to fuel starvation as a result of the pilot's inadequate fuel management.

— NTSB Determination

Accident narrative

On February 22, 2009, approximately 1300 mountain standard time, a Piper PA-28C-235, N9487W, piloted by a private pilot, was substantially damaged when it struck a barbed wire fence following a loss of engine power during a landing approach at Meadow Lake Airport (00V), Falcon, Colorado. Visual meteorological conditions prevailed at the time of the accident. The personal flight was being conducted under the provisions of Title 14 Code of Federal Regulations (CFR) Part 91 without a flight plan. The pilot and a passenger on board the airplane were not injured. The local flight originated at 00V approximately 1130.

The pilot said he preflighted the airplane and noted the following fuel gauge indications:

Left tip tank, 6 gallons (17 gallon capacity) Left main tank, 12 to 15 gallons (25 gallon capacity) Right main tank, 5 to 10 gallons (25 gallon capacity) Right tip tank, empty (17 gallon capacity)

The pilot and a friend took off and flew to Fremont County Airport (1V6) in Canon City, and return to Meadow Lake after about a 1.5 hour flight. While at 500 feet and on short final approach to runway 15 in the landing configuration (carburetor heat, fuel pump on; flaps 20 degrees), the engine lost power. The airplane touched down in a field 200 to 300 feet short of the runway and struck a barbed wire fence. The airplane sustained leading edge damage to both wings and damage to the left main tank.

A witness standing next to fixed base operator Classic Air, just east of the A2 intersection, observed the airplane on final approach to runway 15. He watched as the pilot made a go-around. He said that as the airplane passed his position, the engine "didn't sound like it was running perfect. There was a slight roughness to the exhaust sound." The airplane continued around in the traffic pattern. The witness again saw the airplane on final approach, but "he was much lower than expected. His rate of descent also was higher than normal. He continued down until he contacted the ground far short of the runway. I observed a large puff of dust. The airplane continued forward at a high rate of speed. The plane jumped a few times and swerved left and right. As the aircraft came closer to the threshold of the runway it swerved left and crossed into taxiway alpha. As soon as he got on the taxiway he regained all control. At this point I could see his engine was out and I observed two large holes in the leading edge of the wings with fuel pouring out. He rolled right past me and stopped about 300 feet beyond me. I called him on my handheld to let him know about the fuel leak. He exited the plane with his friend. We went to see if they were ok and if they needed any help. The pilot stated when he turned final the engine just quit."

On March 3, 2009, an FAA inspector examined the airplane and reported finding the fuel selector positioned on the left main fuel tank. He found fuel in the fuel selector drain and in the left main fuel tank drain. There was a negligible amount of fuel in the right main tank fuel drain. The left wing tip tank contained approximately 3 to 5 gallons, and the right wing tip tank contained approximately 2 to 4 gallons.

With the fuel selector positioned on the left main tank, the engine was started and allowed to run for approximately 5 minutes. The fuel selector was then positioned on the left wing tip tank and the engine was allowed to run for another 5 minutes. The fuel selector was then positioned on the right wing tip tank, and the engine continued to run. The fuel selector was positioned on the right main tank and approximately one to two minutes later the engine stopped running.

The pilot did not submit an accident report. According to a Piper Aircraft Company spokesman, the airplane's engine, operating at 7000 feet msl (mean sea level) and 75 percent power, will consume about 14 gallons per hour.

Contributing factors

  • cause Fluid management
  • cause Incorrect use/operation
  • cause Pilot

Conditions

Weather
VMC, wind 170/09kt, 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.