FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX06FA256 · Cessna 182P

4 Aug 2006 · Whitethorn, CA, United States

Cessna 182P · Accident: in flight collision with terrain/water en route

From Shelter Cove Airport (0Q5) to Ukiah Municipal Airport (UKI)

Report a problem

Event

NTSB case
LAX06FA256
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
2 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Instrument Meteorological Cond

Cessna 182P

Aircraft type
Cessna 182
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N9904E
Operator
Unknown
Onboard fatalities
Unknown
Route
From Shelter Cove Airport (0Q5), Whitethorn, CATo Ukiah Municipal Airport (UKI), Ukiah, CA
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
En route · climb to cruise
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
In flight collision with terrain/water
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Pilot in command › Altitude/clearance, not maintained

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane impacted a mountain about 1 nautical mile from the departure airport during the en route climb phase of an instrument departure. The airport is on the coast next to the ocean with mountains immediately adjacent to the east that rise to 3,000 feet msl. A witness saw the airplane depart to the south in dense fog with the ground visibility less than 1/4-mile and follow the coastline until entering the fog layer. The witness noted that the direction of flight was unusual; typically, airplanes depart to the north, then turn left over the ocean to avoid the mountains. After the airplane entered the fog layer it climbed to about 500 to 700 feet above ground level (agl) and then made a 90-degree turn to the left toward the mountains. The airspace overlying the airport is Class G and there is no radar coverage in the area below 6,000 feet. 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 prior to the accident and 2 days prior to the accident). Numerous residents around the airport reported that a dense fog surrounded the airport and cloaked the mountains. One witness stated that as he drove his automobile up the mountains away from the coastline, he came out of the clouds around 1,300 feet mean sea level (msl). 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 by saying, "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 was requested by the pilot nor given in the clearance. The airport does not have a specified instrument departure. 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. 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 the 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.

Probable cause

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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX06FA256
Event ID
20060814X01161
Case number
LAX06FA256
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 85a5193689d7ff3b1f64f2803e6f02934649e4a2bf94d046ce67b8c6cfd8cbbe; retrieved 2026-09-20T17:06:05.109Z.