Casualties unknown

Airplane Impacts Mountain During Instrument Departure in Dense Fog (N9904E)

Whitethorn, CA, US

On August 4, 2006, a Cessna 182P (registration N9904E) was involved in an aviation accident near Whitethorn, CA. Investigators recorded the probable cause as: The pilot's loss of situational awareness with regard to the airplane's proximity to mountainous terrain, and her failure to maintain an adequate terrain clearance altitude or flight path, which resulted in an in-flight collision with the terrain. This summary draws on records from the U.S. National Transportation Safety Board (NTSB) historical archive.

Sourcesthe U.S. National Transportation Safety Board (NTSB) historical archivePrimary reportUpdated 2026-07-04Data APIEditorial standards

An airplane struck a mountain about 1 nautical mile from the departure airport during the en route climb phase of an instrument departure. Dense fog and unusual flight path preceded the accident.

Accident Overview

The airplane impacted a mountain approximately 1 nautical mile from the departure airport during the en route climb phase of an instrument departure. The airport is located on the coast next to the ocean, with mountains immediately adjacent to the east that rise to 3,000 feet mean sea level (msl).

Weather and Witness Observations

A witness observed the airplane depart to the south in dense fog, with ground visibility less than 1/4 mile. The airplane followed the coastline until entering the fog layer. The witness noted that the departure direction was unusual; typically, airplanes depart to the north, then turn left over the ocean to avoid the mountains. After entering the fog layer, the airplane climbed to about 500 to 700 feet above ground level (agl) and then made a 90-degree turn to the left toward the mountains.

Numerous residents around the airport reported dense fog surrounding the airport and cloaking the mountains. A witness stated that while driving an automobile up the mountain away from the coastline, he came out of the clouds at around 1,300 feet msl.

Pilot and Flight Information

The left-seated pilot held an instrument rating; the right-seated pilot did not. Both pilots had made flights together to this airport twice before, about 11 days and 2 days prior to the accident. The airspace overlying the airport is Class G, and there is no radar coverage in the area below 6,000 feet.

Communications and Flight Planning

Records maintained at the Automated Flight Service Station (AFSS) disclosed that the pilot contacted the facility twice for weather information. During the first call, about 3 hours prior to departure, she requested a weather briefing. The briefer advised that an AIRMET for instrument flight rule (IFR) conditions was current for the area. He then queried her, "how does it look outside?" The pilot responded, "It's foggy probably visibility is less than 2." During her second telephone call, about 1 hour 45 minutes later, she was again told about the AIRMET for IFR conditions in the coastal areas, and she filed an IFR flight plan requesting a direct routing and a 6,000-foot cruise altitude. She called the AFSS again and received her IFR clearance "as filed"; no heading or other departure instructions were requested by the pilot nor given in the clearance. The airport does not have a specified instrument departure.

Accident Site and Mechanical Examination

Examination of the accident site revealed that the left wing hit a tree first in a wings-level, slightly nose-high attitude. Post-accident examinations revealed no mechanical anomalies with the airframe or engine that would have precluded normal operation.

Air Traffic Control Actions

The AFSS specialist who read the IFR clearance to the pilot was given the IFR clearance by the Air Route Traffic Control Center (ARTCC) controller along with a clearance void time, but not a time check as required. When the pilot did not communicate with the radar controller on or before the void time, the controller transmitted "in the blind" and did not receive a reply. At that time, the controller should have considered the aircraft overdue and made appropriate notifications, including issuing an Alert Notice (ALNOT), which would have initiated search and rescue efforts. However, the controller, with approval from his supervisor, removed the flight plan from the system. This action deleted any record of the flight and adversely impacted search and rescue efforts. Although the actions of the ARTCC controllers did not cause or contribute to this accident, their performance hindered the timeliness of search and rescue efforts.

Frequently asked questions

What happened in the 4 Aug 2006 Cessna 182P accident near Whitethorn, CA?

An airplane struck a mountain about 1 nautical mile from the departure airport during the en route climb phase of an instrument departure. Dense fog and unusual flight path preceded the accident.

What aircraft was involved and where did it happen?

The accident on 4 Aug 2006 involved a Cessna 182P, registration N9904E, at Whitethorn, CA.

What was the probable cause of the accident?

The pilot's loss of situational awareness with regard to the airplane's proximity to mountainous terrain, and her failure to maintain an adequate terrain clearance altitude or flight path, which resulted in an in-flight collision with the terrain.

Investigation report by the U.S. National Transportation Safety Board (NTSB) historical archive. Original record: https://carol.ntsb.gov/event/20060814X01161. This page is a structured re-presentation; facts and quotes are in the National Transportation Safety Board (NTSB), United States.