11 Oct 2008: CESSNA 210 — MICHAEL TAYLOR

11 Oct 2008: CESSNA 210 (N7418E) — MICHAEL TAYLOR

No fatalities • Placerville, CA, United States

Probable cause

The loss of engine power for undetermined reasons.

— NTSB Determination

Accident narrative

On October 10, 2008, at 1715 Pacific daylight time, a Cessna 210, N7418E, landed hard following a loss of engine power while on approach to runway 23 at the Placerville Airport (PVF), Placerville, California. The private pilot/owner operated the airplane under the provisions of Title 14 Code of Federal Regulations Part 91 as a personal cross-country flight. The airplane sustained substantial damage to the left wing. The pilot and one passenger were not injured. Visual meteorological conditions prevailed for the flight that departed the Corona Municipal Airport (AJO), Corona, California, about 1440, for Placerville. No flight plan had been filed.

According to the pilot, he attempted to contact the common traffic advisory frequency (CTAF) for traffic advisories to the airport at 10 miles out, and again at 5 miles out, with no response. Upon arriving at PVF, he overflew the airport at 4,000 feet to check the wind direction. He made a right-hand entry to the traffic pattern for runway 23. On downwind he lowered the gear and set up for landing. He was on a mile final with flaps at 30 degrees and the airspeed at 85 knots. He thought his approach was high about 1/2 mile out, so he initiated a forward slip to lose altitude; he returned to level flight about 200 feet above the ground. The pilot stated that he was still high and close to the runway threshold. He decided to go around and pushed the throttle full in; however, the engine did not respond. He checked the settings, reduced the throttle, and then pushed the throttle in again with no response.

The pilot reported that due to obstacles off the end of the runway, he decided to make a forced landing on the remaining last half of the runway. He told his passenger to brace for a hard landing and then pointed the nose toward the runway. He stated at that point the airplane's altitude was about 50 feet above the ground. When they were about 10 to 15 feet above the ground, he pitched up and landed flat on all three landing gear. The nose landing gear tire popped, and after applying brakes, collapsed. The propeller struck the ground stopping the engine. The pilot lifted his foot off the left brake, and the airplane slid off the runway to the right. The airplane slid about 40 feet before coming to a stop. The pilot noted damage to the front engine cowling, the nose landing gear, and the left wing spar.

A witness to the accident reported that he was standing at the opposite end of the runway when he saw the airplane enter the traffic pattern for runway 23 from the east. The witness indicated that the airplane was landing with a tailwind of about 8 to 10 knots. The airplane appeared to be too high on the approach, and appeared to be in a slip in an effort to lose altitude on final. The witness was able to hear the engine for a short period of time and it did not sound abnormal. From his position, the airplane appeared to touch down about halfway down the runway, and bounced 2 times. The next thing he saw was a large cloud of dust; when it finally cleared he saw the accident airplane’s tail in the air.

A Federal Aviation Administration (FAA) inspector examined the airplane at Placerville Aviation. A visual examination of the airplane revealed that the fuel tanks had not been breached during the accident. Maintenance personnel reported that they drained 9.6 gallons of fuel from the left fuel tank, and 15 gallons from the right fuel tank. Visual examination revealed no mechanical anomalies. Maintenance personnel removed the spark plugs, which appeared to be good condition, and fuel was found in the gascolator. An engine ground run was performed; the engine started normally, the magneto check was performed at 1,700 revolutions per minute (rpm) and a normal magneto drop was observed. The engine was then run at full power with no "hesitation or missing experienced."

Contributing factors

  • Aircraft power plant — Failure

Conditions

Weather
VMC, wind 020/07kt, 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.