ASN Wikibase Occurrence # 44052
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Friday 4 August 2006 |
| Time: | 11:00 |
| Type: |  Cessna 182P Skylane |
| Owner/operator: | Zero Four Echo, Inc. |
| Registration: | N9904E |
| MSN: | 18263964 |
| Year of manufacture: | 1975 |
| Total airframe hrs: | 4206 hours |
| Fatalities: | Fatalities: 2 / Occupants: 2 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | Whitethorn, CA -
 United States of America
|
| Phase: | Take off |
| Nature: | Private |
| Departure airport: | Whitethorn, CA (0Q5) |
| Ukiah, CA (UKI) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
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.
Accident investigation:
 |
|
Sources:
NTSB: https://www.ntsb.gov/_layouts/ntsb.aviation/brief.aspx?ev_id=20060814X01161&key=1
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 28-Oct-2008 00:45 | ASN archive | Added |
| 21-Dec-2016 19:24 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 05-Dec-2017 09:19 | ASN Update Bot | Updated [Operator, Other fatalities, Source, Narrative] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation