This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages) This article needs more citations. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. Find sources: "Execuflight Flight 1526" – news · newspapers · books · scholar · JSTOR (June 2024) (Learn how and when to remove this message) This article includes a list of general references but lacks sufficient corresponding inline citations. Please help improve this article by introducing more precise citations. (June 2024) (Learn how and when to remove this message) (Learn how and when to remove this message)

Execuflight Flight 1526

Wreckage of the aircraft
Accident
Date	November 10, 2015 (2015-11-10)
Summary	Stalled on approach due to pilot error
Site	Akron, Ohio, United States 41°03′17″N 81°25′24″W / 41.05472°N 81.42333°W / 41.05472; -81.42333
Aircraft
N237WR, the aircraft involved in the accident, pictured in 2013
Aircraft type	British Aerospace BAe-125-700A
Operator	Execuflight
Call sign	ZIPLINE 1526
Registration	N237WR[1]
Flight origin	Dayton-Wright Brothers Airport, Ohio
Destination	Akron Executive Airport, Ohio
Occupants	9
Passengers	7
Crew	2
Fatalities	9
Survivors	0

Execuflight Flight 1526 was a regularly scheduled charter flight from Dayton–Wright Brothers Airport to Akron Executive Airport in Ohio.^[2] On November 10, 2015, the aircraft operating the flight crashed into an apartment building while on approach into Akron, killing all 9 occupants onboard.^[2] The investigation found that the crew performed an unstabilized approach, unknowingly letting the aircraft descend too fast and letting the airspeed gradually decrease until it entered a stall from which the crew did not recover.^[3]

Background

Accident

During approach the pilots noticed that the weather conditions were much worse than anticipated. The first officer, whose job it should have been to conduct the approach briefing, asked the captain to do so.^[2] The pilots then discussed an approach to runway 25.^[2] Indianapolis Air Traffic Control instructed the aircraft to fly over the "HUUVR" crossing at an altitude of 9,000 feet (2,700 m) and contact air traffic control in Cleveland.^[2] The pilots then continued to discuss the approach to runway 25.^[2]

As the business jet approached Akron, its pilots were instructed to slow down the approach, as a small Piper PA-28-161 aircraft was supposed to land on the same runway.^[2] The crew of the BAe-125 was instructed to change course, slow down, and remain at an altitude of 3,000 feet (900 m).^[2] After landing, the Piper's crew reported that the cloud cover had broken in the conditions of minimal visibility.^[2] The crew was instructed to descend further by ATC, but failed to do so.^[2] Noticing that they had not descended, the first officer increased the descent rate (reaching up to 2,000 feet per minute which was twice the normal descent rate), and at the same time slowing the plane, almost 20 knots (37 km/h) below the normal airspeed.^[2] The captain voiced his concerns on these matters but did not take action.^[2]

About 14 seconds after the minimum altitude of 500 feet (150 m) was reached, the airspeed had already decayed to 98 knots (181 km/h).^[2] The aircraft entered a stall and banked sharply to the left before crashing into an apartment building 2 miles (3.2 km) from the runway threshold, exploding on impact and destroying the building.^[2] The crash was captured on video by a neighbouring resident in an adjacent apartment and was also captured on CCTV cameras nearby.^[7][8] The aircraft was completely destroyed by the impact and fire.^[5] All seven passengers and two crew members died in the crash.^[5] No one on the ground was injured or killed.^[9][10][11]

Investigation

The National Transportation Safety Board (NTSB) was assigned to investigate the cause of the accident.^[5] A review of the two pilots' training records revealed that the captain had been fired by his previous employer after failing to show up for training.^[5] The first officer had also been fired by his last employer for poor performance in training.^[5] The president of Execuflight was aware of the shortcomings of the two pilots but had decided to hire them.^[5] The captain had been hired because of his extensive experience with the BAe-125 with the president of the airline company unaware of the captain's poor performance during flight training.^[5] The first officer was hired on the basis of a recommendation from an airline pilot and also flew a test flight to assess his flight performance.^[5] No effort was made to contact the pilots' previous employers and inquire about their specific deficits, leading to both being hired by Execuflight soon after.^[5][12]

The NTSB determined that the probable cause of the accident was:^[5]

The flight crew's mismanagement of the approach and multiple deviations from company SOPs, which placed the airplane in an unsafe situation and led to an unstabilized approach, a descent below MDA without visual contact with the runway environment, and an aerodynamic stall. Contributing to the accident were Execuflight's casual attitude toward compliance with standards; its inadequate hiring, training, and operational oversight of the flight crew; the company's lack of a formal safety program; and the FAA's insufficient oversight of the company's training program and flight operations.^[5]

In popular culture

The accident was featured in season 21 of the Canadian television series, Mayday (known as Air Crash Investigation in the UK) titled "Playing Catch Up".^[13]

See also

• 2017 Teterboro Learjet crash – Also stalled and crashed on approach with violations of standard operating procedures

References