ASN Wikibase Occurrence # 202796
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: | Sunday 10 December 2017 |
| Time: | 11:05 |
| Type: |  Cessna U206G Stationair |
| Owner/operator: | Private |
| Registration: | N732DF |
| MSN: | U206-04662 |
| Year of manufacture: | 1978 |
| Engine model: | Continental IO-520-F27B |
| Fatalities: | Fatalities: 2 / Occupants: 2 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | West of Molokai Airport, Molokai, HI -
 United States of America
|
| Phase: | Approach |
| Nature: | Private |
| Departure airport: | Honolulu-Daniel K. Inouye International Airport, HI (HNL/PHNL) |
| Molokai/Kaunakakai Airport, HI (MKK/PHMK) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The instrument-rated private pilot was conducting a personal flight under visual flight rules (VFR) from one island to the airplane's home base on another island with one passenger onboard. The airport's automated weather observation system reported marginal VFR (MVFR) conditions throughout the morning of the accident, and an AIRMET Sierra was valid for the area of the accident site for mountain obscuration, widespread MVFR ceilings, and scattered rain showers. However, there was no evidence to suggest that the pilot had obtained a weather briefing from an official, access-controlled source before departing on the flight. While en route and receiving VFR flight following services from air traffic control, the pilot requested an instrument (VOR-A) approach to the destination airport. The pilot also reported having the most recent ATIS weather information Juliet, issued at 1055. The ATIS reported 4 miles of visibility with light rain and mist, along with a ceiling of 1,400 ft broken with a broken cloud layer at 3,300 ft. The controller provided the pilot with vectors to initiate the approach and advised him to maintain VFR, which the pilot acknowledged. Two minutes later, the controller issued a frequency change to the destination airport control tower. About 4 minutes after that, the tower controller advised the pilot that the airplane was south of the final approach course. The pilot indicated that he was correcting and was "right at the edge of VFR," but that he had "pretty good visibility." There were no further communications from the accident airplane and radar contact was lost shortly thereafter. The airplane impacted remote mountainous terrain about 1,285 ft msl and about 3.35 miles southwest of the runway threshold at the destination airport; the airplane was destroyed by a postimpact fire. Postaccident examination of the airframe and engine revealed no evidence of preimpact mechanical anomalies that would have precluded normal operation. A photo taken by first responders about 1.5 hours after the accident showed a low cloud layer at the accident site.
Damage to 20-ft-tall trees indicated that the airplane impacted them and then struck a second set of trees that were about 15 ft tall. Multiple tree branches with propeller cut marks were found along the wreckage path. The wreckage was located on the western side of a ridge with dirt and low growth vegetation that crested about 100 ft above the surrounding area, with about a 50° incline. It is likely that, during the approach, the pilot continued visual fight into an area of instrument meteorological conditions consisting of clouds and showers, which resulted in a loss of visual reference and subsequent controlled flight into terrain.
The pilot's logbook was not available for review, and neither his recency of experience nor instrument experience could be determined. The flight instructor who conducted his most recent flight review, about 8 months before the accident, did not endorse the pilot for instrument flight. Autopsy of the pilot identified severe heart disease, which placed the pilot at risk of sudden acute symptoms such as chest pain, palpitations, shortness of breath, or fainting. Flight track information and the pilot's communication with air traffic control indicate that he was actively maneuvering the airplane, likely to avoid clouds and attempt to remain in visual conditions, until it impacted terrain. Thus, it is unlikely that symptoms from the heart disease contributed to the accident.
Probable Cause: The pilot's decision to continue visual flight into an area of instrument meteorological conditions while conducting an instrument approach, which resulted in a loss of visual reference and subsequent controlled flight into terrain.
Accident investigation:
 |
|
Sources:
NTSB
FAA register: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=732DF
Location
Images:
Photo: NTSB
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 11-Dec-2017 03:41 | Geno | Added |
| 11-Dec-2017 11:04 | Iceman 29 | Updated [Time, Embed code] |
| 11-Dec-2017 18:58 | harro | Updated [Aircraft type, Registration, Cn, Operator, Source, Embed code] |
| 11-Dec-2017 23:08 | Geno | Updated [Aircraft type, Source] |
| 23-Apr-2020 09:37 | ASN Update Bot | Updated [Time, Nature, Departure airport, Destination airport, Source, Embed code, Damage, Narrative, Accident report, ] |
| 23-Apr-2020 19:39 | harro | Updated [Source, Embed code, Narrative, Photo, Accident report, ] |
| 09-Jun-2023 05:12 | Ron Averes | Updated [[Source, Embed code, Narrative, Photo, Accident report, ]] |
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