Accident Beechcraft 19A Musketeer Sport N6974Q,
ASN logo
ASN Wikibase Occurrence # 43992
 
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 9 October 2006
Time:07:35
Type:Beechcraft 19A Musketeer Sport
Owner/operator:Private
Registration: N6974Q
MSN: MB-321
Total airframe hrs:6328 hours
Engine model:Lycoming O-320-E2C
Fatalities:Fatalities: 1 / Occupants: 1
Aircraft damage: Destroyed
Category:Accident
Location:Gunthertown, AL -   United States of America
Phase: En route
Nature:Private
Departure airport:Auburn, AL (AUO)
Destination airport:Murfreesboro, TN (MBT)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
About 24 minutes before departure, the pilot received a weather briefing from a flight service station that informed him that overcast conditions at 1200 feet could be expected along his route of flight. The briefer also informed the pilot that flight under visual flight rules (VFR) was not recommended; however, the pilot elected to depart under VFR. Although no radar data exists for the flight, the location of the accident site was consistent with the pilot having flown the airplane toward the Talladega National Forest, an area where the pilot frequently flew. After the pilot failed to arrive at his destination, a search was initiated, and the wreckage was located on October 11, 2006, at 1340, on Burgess Peak, at an elevation of 1,787 feet mean sea level. The airplane first impacted the top of a tree on the south side of Burgess Peak on a 300-degree heading. This heading coincides with the heading the pilot would have been flying when he departed the Auburn-Opelika Airport, indicating the pilot was on his intended heading and had control of the airplane at the time of the first tree impact. A review of the weather briefing the pilot received from Flight Service prior to his departure, revealed that the airplane likely encountered instrument meteorological conditions and near zero visibility at the altitude of the accident site. Examination of the airplane found no preimpact mechanical failure or malfunctions that would have prevented the airplane from operating properly.
Probable Cause: The pilot's continued flight from VMC into IMC conditions which resulted in an in-flight collision with rising terrain.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: ATL07FA005
Status: Investigation completed
Duration:
Download report: Final report

Sources:

NTSB: https://www.ntsb.gov/_layouts/ntsb.aviation/brief.aspx?ev_id=20061017X01525&key=1

Location

Revision history:

Date/timeContributorUpdates
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:26 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:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org