ASN Wikibase Occurrence # 176222
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: | Monday 18 May 2015 |
| Time: | 12:38 |
| Type: |  Beechcraft B55 Baron |
| Owner/operator: | Private |
| Registration: | N5816S |
| MSN: | TC-941 |
| Year of manufacture: | 1965 |
| Total airframe hrs: | 4119 hours |
| Engine model: | Continental IO-470 |
| Fatalities: | Fatalities: 2 / Occupants: 2 |
| Aircraft damage: | Destroyed |
| Category: | Accident |
| Location: | Flat Top Mountain, E of Saltville, VA -
 United States of America
|
| Phase: | En route |
| Nature: | Private |
| Departure airport: | Daytona Beach, FL (7FL6) |
| Mansfield-Lahm Municipal Airport, OH (MFD/KMFD) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
The airplane departed on an instrument flight rules flight; it was equipped with a weather receiver and was capable of displaying XM Weather information through a subscription service. It was not equipped with weather radar in the nose cone of the airplane. The airplane was in cruise flight about 9,000 ft mean sea level (msl) when the pilot contacted an air traffic approach controller who issued the altimeter setting. The controller then asked the pilot his on-course heading, and the pilot responded 356 degrees. The controller advised the pilot of “areas of weather, ah 12 o’clock and ah about four zero miles, just scattered areas, type and intensity unknown.” The pilot stated he would “like to deviate east if we could,” and the controller approved deviations left and right as necessary; he also told the pilot to maintain 9,000 ft. The controller switched the pilot to an Air Route Traffic Control Center (ARTCC) and the pilot acknowledged. The pilot never contacted the ARTCC, and there were no further communications between the accident airplane and air traffic control. Radar data depicted an easterly deviation off course and a gradual descent before the radar target disappeared. A search was initiated, and the airplane wreckage was discovered in heavily wooded, mountainous terrain on the following day.
The pilot obtained preflight weather briefings, but only reviewed the information for the southern half of his route, and not for the northern half, which included the accident site. The briefings included forecasts for thunderstorm activity. A significant meteorological information (SIGMET) for thunderstorms was issued for the area surrounding the accident site 10 minutes after the accident.
An NTSB Weather Study also depicted the weather images that were likely available before the accident time. The XM Weather radar images just before the accident displayed light echoes to the west and north of the accident site with only very light echoes approaching the southwest corner of the accident site region at the time of the accident; the majority of the moderate-to-heavy rain showers and thunderstorms were depicted north and west of the accident flight track. It is likely that the accident airplane flew into a developing rain shower and updraft around the accident time. Given that the rain shower development right near the accident site occurred right at the accident time, it would be very difficult for either XM Weather or FIS-B regional NEXRAD data to pick up the newest rain shower development because of the inherent delay in the image depiction.
Probable Cause: The pilot’s flight into developing rain showers and updrafts, which resulted in a loss of airplane control and collision with terrain. Contributing to the accident were the pilot’s continued flight into forecast adverse weather conditions, and his reliance on weather technologies with known limitations and processing delays.
Accident investigation:
 |
|
Sources:
NTSB
FAA register: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=5816S
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 19-May-2015 16:36 | Geno | Added |
| 19-May-2015 19:56 | gerard57 | Updated [Registration, Operator, Other fatalities, Location, Source, Damage, Narrative] |
| 19-May-2015 23:56 | Geno | Updated [Aircraft type, Cn, Operator, Total fatalities, Total occupants, Location, Source, Narrative] |
| 20-May-2015 02:08 | Geno | Updated [Nature, Source] |
| 20-May-2015 09:42 | Alpine Flight | Updated [Time, Aircraft type] |
| 21-Dec-2016 19:30 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 01-Dec-2017 13:07 | ASN Update Bot | Updated [Operator, Other fatalities, Departure airport, Destination airport, Source, Narrative] |
| 08-Jun-2023 12:14 | Ron Averes | Updated [[Operator, Other fatalities, Departure airport, Destination airport, 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