Beechcraft A36 N8283D
31 August 2016 · Bentonville, Arkansas, United States · Fatal
Summary
On 31 August 2016 at about 14:30 local time, a Beechcraft A36 registered N8283D was involved in an accident near Bentonville, Arkansas, United States. One person was on board and one died. The aircraft was destroyed. The NTSB has published a probable cause for this accident; it is quoted in full below.
The record
- Date
- at 14:30
- Classification
- Accident
- Location
- Bentonville, Arkansas, United States
- Nearest airport
- Bentonville Muni/Louise M Thad (VBT)
- Coordinates
- 36.3453, -94.2194
- Aircraft
- Beechcraft A36
- Registration
- N8283D
- Category
- Airplane
- Year built
- 1993
- Operator
- Not recorded
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Personal
- Phase of flight
- Not recorded
- Route
- Bentonville → Springdale
- Aircraft damage
- Destroyed
- Weather
- VMC
- Light
- Day
- NTSB number
- CEN16FA341
People
1 person died.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 1 | 1 | 0 | 0 | 0 |
Probable cause
The pilot's failure to monitor and/or transmit his position over the uncontrolled airport's common traffic advisory frequency, and his decision to continue the takeoff when he observed conflicting traffic on the runway.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
The private pilot was departing from an uncontrolled airport at the same time that another airplane was landing in the opposite direction. Surveillance video showed the accident airplane veer to the left during its takeoff roll, become airborne over a unpaved area between the runway and ramp area, and cross the ramp. The airplane subsequently impacted the top of a hangar and was destroyed by postcrash fire. The video evidence and propeller signatures suggest that the pilot did not reduce power and was attempting to continue the takeoff. An employee at the fixed base operator on the airport reported that she heard the pilot of the landing airplane announce over the airport's common traffic advisory frequency (CTAF) his airplane's position inbound to the airport and his intent to land the airplane at the accident airport; however, neither she nor the pilot of landing airplane heard the accident pilot transmit his position or intentions over the CTAF. The airplane was equipped with communication radios, suggesting that the pilot was not using the radios prior to his takeoff. Examination of the accident airplane did not reveal any preimpact failures or anomalies. Toxicology testing of the pilot revealed the presence of temazepam, a Schedule IV controlled substance of the benzodiazepine class, that is a sedative intended for the short-term treatment of insomnia. The pilot's blood concentration of temazepam was well below that considered to cause significant effects; therefore, it is unlikely the pilot was impaired by this medication at the time of the accident. Additionally, the pilot had atrial fibrillation treated with an anticoagulant and a history of a slow heart rate treated with an implanted pacemaker. The actions of the pilot indicate that he was awake and alert, and there is no evidence to suggest that he was impaired due to his cardiac conditions. It is unlikely that the pilot's atrial fibrillation, high blood pressure, elevated cholesterol, insomnia, or medications used to treat these conditions impaired him or contributed to the accident. It is also unlikely that the pilot's slow heart rhythm treated with a pacemaker contributed to the accident. It is likely that the pilot did not recognize that another airplane was landing in the opposite direction before he initiated the takeoff. When he did see the other airplane during his takeoff roll, rather than abort the takeoff, the pilot veered the airplane off the runway surface and attempted to continue the takeoff, which resulted in collision with the hangar. Federal Aviation Administration guidance states that, in order to achieve the greatest degree of safety, it is essential that all radio-equipped aircraft transmit/receive on a common frequency identified for the purpose of airport advisories. If the accident pilot had been monitoring and/or transmitting over the CTAF, he may have been alerted to the presence of the landing airplane and the accident could have been avoided. In addition, although radio communication is not required at uncontrolled airports, the pilot's failure to use radio communication resulted in his unawareness of the other landing airplane.
Quoted verbatim from the NTSB record.
Other Beechcraft A36 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 12 Dec 2016 | Beechcraft A36 | New Smyrna Beach, Florida, United States | - | Minor injuries | - |
| 11 Dec 2016 | Beechcraft A36 | Shoreham, New York, United States | - | No injuries | - |
| 17 Dec 2016 | Beechcraft A36 | Ormond Beach, Florida, United States | - | Serious injuries | - |
| 31 Aug 2016 | Beechcraft A36 | Sparks, Nevada, United States | Flying Start Aero | Fatal | 2 |
| 25 Oct 2016 | Beechcraft A36 | Pittsburg, California, United States | - | Fatal | 2 |
| 19 Feb 2016 | Beechcraft A36 | Marshville, North Carolina, United States | - | Fatal | 1 |
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 29 May 2016 | Cessna 177 | Pine Bluff, Arkansas, United States | - | Minor injuries | - |
| 13 May 2016 | Mooney M20 | Little Rock, Arkansas, United States | - | No injuries | - |
| 12 Jan 2016 | Mitsubishi MU 300 | Little Rock, Arkansas, United States | Central Flying Service Inc | No injuries | - |
| 7 Jul 2016 | Cessna 182 | Searcy, Arkansas, United States | - | No injuries | - |
| 11 Oct 2016 | Remos REMOS GX | Lowell, Arkansas, United States | Adventure Flight Aviation Inc | No injuries | - |
| 5 Jun 2016 | Cessna 172 | Henderson, Arkansas, United States | - | No injuries | - |