ASN Wikibase Occurrence # 43057
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 13 February 2000 |
Time: | 12:45 |
Type: | Beechcraft P35 Bonanza |
Owner/operator: | Private |
Registration: | N9796Y |
MSN: | D-7168 |
Engine model: | Continental IO-470N |
Fatalities: | Fatalities: 1 / Occupants: 1 |
Aircraft damage: | Destroyed |
Category: | Accident |
Location: | Dayton, TN -
United States of America
|
Phase: | En route |
Nature: | Private |
Departure airport: | 2A0 |
Destination airport: | Fort Worth, TX |
Investigating agency: | NTSB |
Confidence Rating: | Accident investigation report completed and information captured |
Narrative:The pilot of N9796Y called the Air Traffic Control Specialist at the Automated Flight Service Station (AFSS), for a weather briefing from Dayton, Tennessee, to the Fort Worth, Texas area, for a proposed flight that afternoon. The specialist's issued him a detailed synopsis with emphasis on forecast thunderstorms and IFR conditions. There were AIRMETS (Airman's Meteorological Information) for IFR conditions along the route of flight until 1800 UTC (1400). The specialist told the pilot that the system would take about 24 to 36 hours to clear, and the phone call ended. The pilot again called the AFSS, and he told the specialist that the flight would have to be 'VFR only......I'm...v f r I need to go v f r....' The pilot was issued the AIRMETS, conditions, and forecast information showing IFR conditions, and given a forecast for continued IFR. The specialist told the pilot that it was '...highly improbable (VFR).' According to a witness at the departure airport, who saw the airplane take off, and watched it disappear into the clouds, '...the ceiling appeared to be about 600 to 900 feet high.' Another witness about 3 miles from the crash site said when she saw the airplane it was flying 'low' as it came out of the clouds. She said the engine seemed to 'sound normal,' and the airplane was heading in a southwest direction. The witness said that at the time the weather was, '...overcast, foggy, misting rain.' A police officer that had responded to the reported crash site at 1311, said, 'due to the fog, the visibility was approximately 20 to 30 feet. According to local police records the airplane was found by a ground search at 1649. FAA records indicated that the pilot did not possess an instrument rating at the time of the accident. The pilot's personal logbook listing his flight hours was not recovered. Based on his last application for insurance, dated April 20, 1999, it was estimated that the pilot had about 1,207 hours of total flight time in all aircraft, and 36 hours in this make and model airplane, at the time of the application. The airplane impacted in a heavily wooded area, in rising terrain. The elevation at the crash site was about 1,910 feet mean sea level. The elevation at the departure airport was 855 feet.
Probable Cause: the non-instrumented rated pilot elected to takeoff into known adverse weather conditions, which resulted in impact with rising terrain. Factors in this accident were, clouds and low ceilings.
Accident investigation:
|
| |
Investigating agency: | NTSB |
Report number: | MIA00FA090 |
Status: | Investigation completed |
Duration: | |
Download report: | Final report |
|
Sources:
NTSB:
https://www.ntsb.gov/_layouts/ntsb.aviation/brief.aspx?ev_id=20001212X20529&key=1 Revision history:
Date/time | Contributor | Updates |
24-Oct-2008 10:30 |
ASN archive |
Added |
21-Dec-2016 19:24 |
ASN Update Bot |
Updated [Time, Damage, Category, Investigating agency] |
12-Dec-2017 18:25 |
ASN Update Bot |
Updated [Operator, Departure airport, Source, Narrative] |
The Aviation Safety Network is an exclusive service provided by:
CONNECT WITH US:
©2024 Flight Safety Foundation