Beechcraft 350 Super King Air

Historical safety data and incident record for the Beechcraft 350 Super King Air aircraft.

Safety Rating

9.4/10

Total Incidents

18

Total Fatalities

102

Incident History

February 6, 2025 4 Fatalities

Air Tindi

Thunder Bay Ontario

Following an uneventful flight from RCAF Trenton on behalf of the RCAF, the twin engine aircraft apparently landed hard at Thunder Bay Airport. After touchdown on runway 25, it went out of control and veered off runway into a snow covered area. All three crew members evacuated safely while the aircraft suffered severe damages to wings and tail. The fuselage also broke in two.

May 21, 2021 11 Fatalities

Nigerian Air Force

Kaduna-Intl Kaduna

On final approach to Kaduna Airport in poor weather conditions, the twin engine aircraft crashed, bursting into flames. The aircraft was totally destroyed by impact forces and a post crash fire. All 11 occupants were killed, among them General Ibrahim Attahiru, Chief of Staff of the Nigerian Army. He was returning to Kaduna with a delegation of six other Army officers, among them three Brigadier General. Crew: F/Lt T. Asaniyi, F/Lt A. Olufade, Sgt Adesina, Acm Oyedepo. Passengers: Lt General Ibrahim Attahiru, Br/Gen M. Abdulkadir, Br/Gen Olayinka, Br/Gen Kuliya, Maj Lawal Hayat, Maj Hamza, Sgt Umar.

March 1, 2021 5 Fatalities

Beidahuang General Airlines

Ganzhou Jiangxi

The twin engine aircraft departed Ganzhou Airport at 1440LT on a cloud seeding mission over the Jiangxi Region. While flying in clouds, the aircraft entered an uncontrolled descent, entered a spin and eventually crashed in a residential area. All five occupants were killed and one people on the ground was slightly injured.

February 21, 2021 7 Fatalities

Nigerian Air Force

Abuja Abuja Federal Capital Territory

After takeoff from Abuja-Nnamdi Azikiwe Airport, while climbing, the crew informed ATC about an engine failure and was cleared for an immediate return. On final approach to runway 22, the aircraft went out of control and crashed in an open field, bursting into flames. The aircraft was destroyed and all 7 occupants were killed, among them two pilots, four ATOS specialists (Airborne Tactical Observation System) and one technician.

July 15, 2020 7 Fatalities

Turkish Police - Türk Polis

Mt Artos Eastern Anatolia Region (Dogu Anadolu Bölgesi)

The twin engine aircraft departed Van-Ferit Melen Airport at 1834LT on a survey/reconnaissance mission over the province of Hakkari and Van, carrying five passengers and two pilots. At 2232LT, the crew informed ATC about his position vertical to Baskale on approach to Van-Ferit Melen Airport. Thirteen minutes later, the aircraft struck the slope of Mt Artos located 30 km southwest of runway 03 threshold. The aircraft was destroyed upon impact and all seven occupants were killed.

September 1, 2019 9 Fatalities

INAEC Aviation Corporation

Pansol Laguna

The twin engine airplane was completing an ambulance flight from Dipolog and Manila, carrying seven passengers and a crew of two. While cruising in marginal weather conditions, the airplane went out of control and crashed into several houses located in the city of Pansol, about 40 km southeast of Manila-Ninoy Aquino Airport. The aircraft was destroyed and all nine people on board were killed. There were apparently no injuries on the ground.

July 30, 2019 19 Fatalities

Pakistan Air Force - Pakistan Fiza'ya

Islamabad Islamabad Capital Territory (<U+0648><U+0641><U+0627><U+0642><U+06CC> <U+062F><U+0627><U+0631><U+0627><U+0644><U+062D><U+06A9><U+0648><U+0645><U+062A>)

The twin engine airplane departed Chaklala-Nur Khan AFB with five crew members on board for a local training flight. In flight, it went out of control and crashed onto several houses located in the suburb of Mora Kalu, about 10 km south of Chaklala-Nur Khan AFB, Islamabad, bursting into flames. The aircraft and several houses were destroyed. All five crew members as well as 14 people on the ground were killed.

June 30, 2019 10 Fatalities

EE Operations

Addison Texas

The pilot, co-pilot, and eight passengers departed on a cross-country flight in the twin-engine airplane. One witness located on the ramp at the airport reported that the airplane sounded underpowered immediately after takeoff “like it was at a reduced power setting.” Another witness stated that the airplane sounded like it did not have sufficient power to takeoff. A third witness described the rotation as “steep,” and other witnesses reported thinking that the airplane was performing aerobatics. Digital video from multiple cameras both on and off the airport showed the airplane roll to its left before reaching a maximum altitude of 100 ft above ground level; it then descended and impacted an airport hangar in an inverted attitude about 17 seconds after takeoff and an explosion immediately followed. After breaching a closed roll-up garage door, the airplane came to rest on its right side outside of the hangar and was immediately involved in a postimpact fire. Sound spectrum analysis of data from the airplane’s cockpit voice recorder (CVR) estimated that the propeller speeds were at takeoff power (1,714 to 1,728 rpm) at liftoff. About 7 seconds later, the propeller speeds diverged, with the left propeller speed decreasing to about 1,688 rpm and the right propeller speed decreasing to 1,707 rpm. Based on the airplane’s estimated calibrated airspeed of about 110 knots and the propeller rpm when the speeds diverged, the estimated thrust in the left engine decreased to near 0 while the right engine continued operating at slightly less than maximum takeoff power. Analysis of available data estimated that, 2 seconds after the propeller speed deviation, the airplane’s sideslip angle was nearly 20°. During the first 5 seconds after the propeller speed deviation, the airplane’s roll rate was about 5° per second to the left; its roll rate then rapidly increased to more than 60° per second before the airplane rolled inverted. Witness marks on the left engine and propeller, the reduction in propeller speed, and the airplane’s roll to the left suggest that the airplane most likely experienced a loss of thrust in the left engine shortly after takeoff. The airplane manufacturer’s engine-out procedure during takeoff instructed that the landing gear should be retracted once a positive rate of climb is established, and the propeller of the inoperative engine should be feathered. Right rudder should also be applied to balance the yawing moment imparted by a thrust reduction in the left engine. Examination of the wreckage found both main landing gear in a position consistent with being extended and the left propeller was unfeathered. The condition of the wreckage precluded determining whether the autofeather system was armed or activated during the accident flight. Thus, the pilot failed to properly configure the airplane once the left engine thrust was reduced. Calculations based on the airplane’s sideslip angle shortly after the propeller speed deviation determined that the thrust asymmetry alone was insufficient to produce the sideslip angle. Based on an evaluation of thrust estimates provided by the propeller manufacturer and performance data provided by the airplane manufacturer, it is likely that the pilot applied left rudder, the opposite input needed to maintain lateral control, before applying right rudder seconds later. However, by then, the airplane’s roll rate was increasing too rapidly, and its altitude was too low to recover. The data support that it would have been possible to maintain directional and lateral control of the airplane after the thrust reduction in the left engine if the pilot had commanded right rudder initially rather than left rudder. The pilot’s confused reaction to the airplane’s performance shortly after takeoff supports the possibility that he was startled by the stall warning that followed the propeller speed divergence, which may have prompted his initial, improper rudder input. In addition, the NTSB’s investigation estimated that rotation occurred before the airplane had attained Vr (rotation speed), which decreased the margin to the minimum controllable airspeed and likely lessened the amount of time available for the pilot to properly react to the reduction in thrust and maintain airplane control. Although the airplane was slightly over its maximum takeoff weight at departure, its rate of climb was near what would be expected at maximum weight in the weather conditions on the day of the accident (even with the extended landing gear adding drag); therefore, the weight exceedance likely was not a factor in the accident. Engine and propeller examinations and functional evaluations of the engine and propeller controls found no condition that would have prevented normal operation; evidence of operation in both engines at impact was found. Absent evidence of an engine malfunction, the investigation considered whether the left engine’s thrust reduction was caused by other means, such as uncommanded throttle movement due to an insufficient friction setting of the airplane’s power lever friction locks. Given the lack of callouts for checklists on the CVR and the pilot’s consistently reported history of not using checklists, it is possible that he did not check or adjust the setting of the power lever friction locks before the accident flight, which led to uncommanded movement of the throttle. Although the co-pilot reportedly had flown with the pilot many times previously and was familiar with the B-300, he was not type rated in the airplane and was not allowed by the pilot to operate the flight controls when passengers were on board. Therefore, the co-pilot may not have checked or adjusted the friction setting before the flight’s departure. Although the investigation considered inadequate friction setting the most likely cause of the thrust reduction in the left engine, other circumstances, such as a malfunction within the throttle control system, could also result in loss of engine thrust. However, heavy fire and impact damage to the throttle control system components, including the power quadrant and cockpit control lever friction components, precluded determining the position of the throttle levers at the time of the loss of thrust or the friction setting during the accident flight. Thus, the reason for the reduction in thrust could not be determined definitively. In addition to a lack of callouts for checklists on the CVR, the pilots did not discuss any emergency procedures. As a result, they did not have a shared understanding of how to respond to the emergency of losing thrust in an engine during takeoff. Although the co-pilot verbally identified the loss of the left engine in response to the pilot’s confused reaction to the airplane’s performance shortly after takeoff, it is likely the co-pilot did not initiate any corrective flight control inputs, possibly due to the pilot’s established practice of being the sole operator of flight controls when passengers were on board. The investigation considered whether fatigue from inadequately treated obstructive sleep apnea contributed to the pilot’s response to the emergency; however, the extent of any fatigue could not be determined from the available evidence. In addition, no evidence indicates that the pilot’s medical conditions or their treatment were factors in the accident. In summary, the available evidence indicates that the pilot improperly responded to the loss of thrust in the left engine by initially commanding a left rudder input and did not retract the landing gear or feather the left propeller, which was not consistent with the airplane manufacturer’s engine out procedure during takeoff. It would have been possible to maintain directional and lateral control of the airplane after the thrust reduction in the left engine if right rudder had been commanded initially rather than left rudder. It is possible that the pilot’s reported habit of not using checklists resulted in his not checking or adjusting the power lever friction locks as specified in the airplane manufacturer’s checklists. However, fire and impact damage precluded determining the position of the power levers or friction setting during the flight.

May 15, 2017 4 Fatalities

Japan Air Self-Defense Force - Koku Jieitai

Assabu Hokkaido

The Beechcraft LR-2 Hayabusa (a version of the Beechcraft 350 Super King Air) departed Sapporo-Okadama Airport at 1123LT on a flight to Hakodate to evacuate a patient. On board were two doctors and two pilots. While descending to Hakodate at an altitude of 3,000 feet, the crew encountered poor weather conditions with low clouds and rain showers when the airplane registered 23057 (JG-3057) impacted the slope of a mountain located near Assabu, about 40 km northwest of Hakodate Airport. The aircraft disintegrated on impact and all four occupants were killed.

September 7, 2010 6 Fatalities

Colombian Air Force - Fuerza Aérea Colombiana

Uribe Meta

The twin engine aircraft was engaged in a reconnaissance and survey mission over the southern Colombia territory, carrying six crew members. At 2306LT, the last radio contact was recorded with the crew. In unknown circumstances, while cruising at an altitude of 10,600 feet, the aircraft impacted terrain near Uribe. The wreckage was found four days later, on September 11. The aircraft was totally destroyed and all six occupants were killed.

May 22, 2009 14 Fatalities

Santa Coloma Investimento e Participações

Porto Seguro-Terravista Golf Club Bahia

The twin engine aircraft departed São Paulo-Congonhas Airport at 1831LT on a private flight to Porto Seguro, carrying 12 passengers and two pilots, among them the Brazilian Businessman Roger Wright, his wife, children and grandchildren. On approach to Porto Seguro-Terravista Golf Club Airport, the crew encountered poor weather conditions and the visibility was low due to the night. On final approach to runway 15, the aircraft impacted trees located 900 metres from the runway threshold. The aircraft continued for about 700 metres then struck others trees and crashed 200 metres short of runway, bursting into flames. The aircraft was totally destroyed and all 14 occupants were killed.

January 12, 2006 2 Fatalities

Euroflug Frenzel

Freiburg im Breisgau Baden-Württemberg

After the crew dropped off passengers at Karlsruhe-Baden-Baden Airport, he was returning to his base in Freiburg im Breisgau. On final approach to runway 16 in marginal weather conditions (poor visibility due to night and fog), the crew descended too low when the aircraft collided with trees and crashed in a wooded area located 450 metres short of runway, bursting into flames. The aircraft was destroyed by a post crash fire and both pilots were killed.

May 24, 2005 2 Fatalities

Empresa Agroservicios Polar

El Junquito Caracas Federal District

The crew was performing a ferry flight from Caracas-Maiquetía-Simón Bolívar Airport to Charallave. While cruising in poor weather conditions, the twin engine aircraft struck the slope of a mountain located near El Junquito, about 35 km northwest of Charallave-Óscar Machado Zuloaga Airport. The aircraft was destroyed and both pilots were killed.

Wyngs Aviation

Punto Fijo Falcón

The twin engine aircraft completed a charter flight from La Carlota to Calabozo with four passengers and two pilots. At Calabozo Airport, the four passengers brandished guns and took over the airplane on an illegal flight to Punto Fijo. Upon arrival, the aircraft crashed under unknown circumstances. There were no casualties and the aircraft was destroyed.

Oso Rio

West Houston Texas

The aircraft overran the departure end of the runway while landing on Runway 33. The 5,200-hour pilot reported that while on the base leg, the annunciator light for the "low pitch stop" propeller system on the right side illuminated. The pilot pulled the circuit breaker and left it out, as per the pilot operating handbook (POH). During the landing-roll, the pilot encountered a severe yaw to the right. The pilot added power to the right engine and realigned the airplane down the centerline. He then applied brakes and reverse thrust. The pilot stated that " it felt like I had no braking action and then felt the right side grab and brake, but not the left." The combination of right side braking and the right low pitch system malfunction caused considerable adverse yaw, jerking the plane to the right. The pilot applied power again and straightened the nose of the airplane. He then made the decision to go around, but at this point did not have adequate airspeed or runway length to safely accomplish a go around. He applied the brakes again, and the airplane immediately yawed to the right again, at which time the pilot was unable to compensate before the airplane caught the edge of the runway. The airplane went into the grass, where the pilot attempted to control the direction of the airplane and bring it to a complete stop. Examination of the hydraulic brake hoses from the left and right main landing gears revealed that both hoses appeared to have been damaged with a hand tool.

Aerope 3S Aviation

Santiago de Compostela Galicia

While on approach to Santiago de Compostela Airport, around 0000LT, meteorological conditions were reported to be good, and the crew requested a visual approach to runway 17, even though the active runway was 35. Once cleared to land, the aircraft encountered a fog patch and from this moment it began a high rate descent (2,000 to 3,000 feet per minute). A minute after entering an unexpected and unforeseen fog patch, at 00:13:02 of June 7, the aircraft struck some trees, in level flight and with an airspeed of 148 knots. The wings and engines detached from the fuselage, and they dragged along a scrubland area until they came to a stop. The crew suffered minor injuries and the aircraft was completely destroyed.

December 5, 1998 2 Fatalities

Dogus Air

Istanbul-Atatürk Marmara Region (Marmara Bölgesi)

After takeoff from Istanbul-Atatürk Airport, on a positioning flight to Antalya, the crew reported technical problems and was cleared to return for an emergency landing. After touchdown, the twin engine aircraft went out of control, veered off runway and eventually collided with containers stored by the apron, bursting into flames. Both pilots were killed.

Safety Profile

Reliability

Reliable

This rating is based on historical incident data and may not reflect current operational safety.

Primary Operators (by incidents)

Nigerian Air Force2
1
Aerope 3S Aviation1
Air Tindi1
Beidahuang General Airlines1
Colombian Air Force - Fuerza Aérea Colombiana1
Dogus Air1
EE Operations1
Empresa Agroservicios Polar1
Euroflug Frenzel1