15 May 2008: CESSNA 182P — Gregory S. Anderson

15 May 2008: CESSNA 182P (N4660K) — Gregory S. Anderson

No fatalities • Santa Maria, CA, United States

Probable cause

The pilot's impairment from alcohol and his improper flare, which resulted in a bounced landing. Contributing to the accident was the FAA's failure to obtain additional information about the pilot's alcohol use history to verify that he met the requirements and standards for medical certification.

— NTSB Determination

Accident narrative

"THIS CASE WAS MODIFIED MAY 15, 2009."

On May 14, 2008, approximately 1815 Pacific daylight time, a Cessna 182P, N4660K, sustained substantial damage following a hard landing at Santa Maria Public Airport (SMX), Santa Maria, California. The private pilot, the sole occupant, was not injured. The pilot/owner was operating the airplane under the provisions of 14 Code of Federal Regulations Part 91. Visual meteorological conditions prevailed for the local, personal flight, which had originated approximately 55 minutes before the accident. No flight plan had been filed.

The pilot reported that after returning from a local area flight, he informed the tower controller of his intentions for a left downwind, full stop landing. The pilot was given clearance and instructed that he was number two for landing. The pilot reported that the airplane touched down on the mains and bounced. The pilot added power to stabilize the landing, however, the nose gear collapsed.

Witnesses to the accident reported that the airplane landed on runway 30 and bounced repeatedly until the nose landing gear collapsed.

Inspection of the airplane found that the engine firewall was wrinkled and the fuselage structure around the nose landing gear was damaged.

First responders to the accident site called for the on-airport law enforcement officer to respond to the accident site as they suspected that the pilot was intoxicated. Shortly thereafter, the Santa Maria Police Department tested the pilot for alcohol intoxication. The first breath test was conducted at 1933, and resulted in a .24 percent blood alcohol content (BAC); a second breath test was performed at 1937, and resulted in a .23 percent BAC. The pilot was subsequently taken into custody.

The pilot initially reported to law enforcement that he had a bad cold and had taken Vicks Cold Medicine that morning. In the pilot's statement to the National Transporation Safety Board, the pilot reported that he had been taking a cold medicine that had been given to him as a Christmas gift, and he did not know the ingredients. He reported that it was a homemade mixture that came from Tennessee.

A review of the pilot's medical records maintained by the Federal Aviation Administration (FAA) Aerospace Medical Certification Division indicated that the pilot reported to the FAA a DUI with license suspension on August 21, 2006. No records were found indicating that any details of the license suspension were provided by the pilot or that such details were pursued by the FAA prior to the aircraft accident. No FAA action was noted in response to the reported DUI. The arrest report for that DUI was obtained by the NTSB and indicated a blood alcohol content of 0.10 and the possession of cocaine at the time of arrest.

The pilot's most recent medical certificate dated April 14, 2008, indicates that on that application, the pilot indicated, "yes" in response to item 18.v. "history of any conviction(s) involving driving while intoxicated by, while impaired by, or while under the influence of alcohol or a drug...." He gave no further explanations.

There is no further information dated prior to the accident in the FAA medical records regarding the pilot's prior history of driving while intoxicated, and no indications that the FAA requested any additional information.

Contributing factors

  • cause Pilot
  • factor FAA/Regulator
  • cause Landing flare — Not attained/maintained
  • cause Pilot

Conditions

Weather
VMC, wind 340/05kt, vis 9sm

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.