Accident Beechcraft B55 Baron N128VB,
ASN logo
ASN Wikibase Occurrence # 189245
 
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:Friday 12 August 2016
Time:12:22
Type:Silhouette image of generic BE55 model; specific model in this crash may look slightly different    
Beechcraft B55 Baron
Owner/operator:Ross & Company
Registration: N128VB
MSN: TC-1211
Year of manufacture:1969
Total airframe hrs:4224 hours
Engine model:Continental IO-470
Fatalities:Fatalities: 6 / Occupants: 6
Aircraft damage: Substantial
Category:Accident
Location:near Shannon Airport, Fredericksburg, VA -   United States of America
Phase: Initial climb
Nature:Private
Departure airport:Shelbyville, IN (GEZ)
Destination airport:Fredericksburg-Shannon Airport, VA (EZF)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The private pilot, who was seated in the left front seat, was making a cross-country flight in the twin-engine airplane with five passengers on board; the passenger seated in the right front seat was a commercial pilot. Shortly after departing, the pilot contacted air traffic control and requested visual flight rules flight following services to the destination airport. A variable quartering headwind prevailed about the time the airplane approached the destination airport's 2,999-ft-long runway, with an approximate headwind component of about 8 knots. Given the airplane's estimated landing weight and the prevailing weather conditions, the airplane's calculated landing distance was between 1,280 and 1,850 feet.

Review of recorded data showed that the airplane crossed the runway threshold for landing at an altitude about 40 ft above the ground and at an estimated airspeed of 95 knots, about 9 knots faster than the airframe manufacturer's recommended final approach speed for its estimated weight. Witness interviews, surveillance video, and recorded data showed that the airplane touched down and bounced several times near the mid-point of the runway. The airplane then started to climb at an estimated airspeed of 68 knots, which was well below the balked landing climb speed of 90 knots, and near the published stall speed of 73 knots with the landing gear and flaps extended. The airplane made a shallow left turn and climbed to an altitude of about 100 ft above ground level. During the climbing turn, airplane's speed further decreased to an estimated 62 knots before it entered an aerodynamic stall and descended to impact terrain.

Examination of the airframe and engines did not reveal any evidence of preimpact mechanical malfunctions that would have precluded normal operation. Postaccident weight and balance calculations indicated that the airplane was below its maximum gross landing weight and that the center of gravity was within limits.

The pilot did not hold a valid Federal Aviation Administration medical certificate and had a history of significant medical issues, including hypertension, high cholesterol, diabetes, and heart disease; however, it is unlikely that the pilot's hypertension or high cholesterol contributed to the accident. Toxicology testing identified zolpidem, a prescription sleep aid, at below-therapeutic levels; because zolpidem undergoes postmortem redistribution and the tested blood came from the heart, the antemortem level was likely lower than the measured level. As a result, it is unlikely that the sedative effects from the zolpidem contributed to the accident. The pilot's diabetes could have contributed to the accident if he experienced acutely low blood sugar, which causes psychomotor slowing and eventually loss of consciousness, or had difficulty operating the airplane due to diabetic neuropathy. Further, an acute cardiac event in either the pilot or the pilot-rated passenger, who also had significant heart disease, could have contributed to the accident; however, the investigation was unable to determine whether any of the pilots' medical issues contributed the accident, and it is unlikely that both suffered an acute medical event at the time of the landing and subsequent loss of control during the go-around attempt.

It could not be determined which of the two pilots was manipulating the controls and flying the airplane during the landing approach and subsequent go-around, as both the pilot (airplane owner) and the pilot-rated passenger were seated at a fully functional set of flight controls.

Probable Cause: The pilot(s) failure to maintain adequate airspeed during an attempted go-around, which resulted in an exceedance of the airplane's critical angle of attack and an aerodynamic stall.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: ERA16FA288
Status: Investigation completed
Duration: 2 years 1 month
Download report: Final report

Sources:

NTSB

FAA register: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=128VB

https://flightaware.com/photos/view/283489-575fe7a1a4c98dc6e0451a34700ca6c9572324d8

Location

Images:


Photo: NTSB

Media:

Revision history:

Date/timeContributorUpdates
12-Aug-2016 22:23 Geno Added
13-Aug-2016 11:32 Aerossurance Updated [Time, Aircraft type, Operator, Location, Phase, Nature, Source, Embed code, Damage, Narrative]
13-Aug-2016 14:52 Iceman 29 Updated [Embed code]
13-Aug-2016 16:02 Geno Updated [Aircraft type, Registration, Cn, Operator, Source]
13-Aug-2016 16:10 harro Updated [Aircraft type]
13-Aug-2016 23:07 Geno Updated [Departure airport]
14-Aug-2016 06:47 Anon. Updated [Source]
14-Aug-2016 14:09 Iceman 29 Updated [Source, Narrative]
15-Aug-2016 04:14 Glass-man Updated [Source, Narrative]
17-Aug-2016 10:11 Glass-man Updated [Narrative]
08-Oct-2018 16:42 ASN Update Bot Updated [Time, Operator, Departure airport, Destination airport, Source, Embed code, Damage, Narrative, Accident report, ]
08-Oct-2018 17:04 harro Updated [Operator, Source, Embed code, Narrative, Photo]
08-Oct-2018 17:23 harro Updated [Destination airport, Embed code]
05-Jun-2023 21:16 Ron Averes Updated [[Destination airport, Embed code]]

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