Zone

Crash of a Canadair CRJ-701ER in Washington DC: 64 killed

Date & Time: Jan 29, 2025 at 2048 LT
Operator:
Registration:
N709PS
Survivors:
No
Schedule:
Wichita - Washington DC
MSN:
10165
YOM:
2004
Flight number:
AA5342
Crew on board:
4
Crew fatalities:
Pax on board:
60
Pax fatalities:
Other fatalities:
Total fatalities:
64
Captain / Total flying hours:
3950
Captain / Total hours on type:
3024.00
Copilot / Total flying hours:
2469
Copilot / Total hours on type:
965
Circumstances:
On January 29, 2025, about 2048 eastern standard time (EST), a Sikorsky UH-60L, operated by the US Army under the callsign PAT25 (Priority Air Transport Flight 25), and an MHI (Mitsubishi Heavy Industries) RJ Aviation (formerly Bombardier) CL-600-2C10 (CRJ700), N709PS, operated by PSA Airlines as American Airlines flight 5342, collided in flight about 0.5 miles southeast of Ronald Reagan Washington National Airport (DCA), Arlington, Virginia, and impacted the Potomac River in southwest Washington, DC. The 2 pilots, 2 flight attendants, and 60 passengers on board the airplane and all 3 crew members on board the helicopter died. Both aircraft were destroyed as a result of the accident. Flight 5342 was operating under the provisions of Title 14 Code of Federal Regulations Part 121 as a scheduled domestic passenger flight from Wichita Dwight D. Eisenhower National Airport, Wichita, Kansas, to DCA. PAT25 originated from Davison Army Airfield (DAA), Fort Belvoir, Virginia, for the purpose of the pilot’s annual standardization evaluation flight with the use of night vision goggles (NVGs). Night visual meteorological conditions prevailed in the area of DCA at the time of the accident. PAT25 departed DAA and landed at sites in Virginia and Maryland before the crew turned south toward Washington, DC, and was cleared by the DCA tower controller (who was working combined local control and helicopter control positions) to transition the DCA airspace via helicopter Routes 1 and 4 before proceeding back to DAA. The helicopter joined Route 1 near Cabin John, Maryland, and followed the Potomac River southbound at low altitude, passing the Key Bridge, Memorial Bridge, Tidal Basin, and Hains Point before continuing onto Route 4. At the same time, flight 5342 was approaching DCA on an instrument flight rules flight that had been uneventful during departure, cruise, and initial descent. The airplane was inbound from the south on a visual approach to runway 1 when the DCA tower controller asked the flight crew if they could accept runway 33 instead. After confirming landing performance, the crew accepted a circling approach to runway 33 and maneuvered the airplane to align with the runway 33 final approach path. While PAT25 was transitioning from Route 1 to Route 4 and flight 5342 was circling to land, the controller issued a traffic advisory to the helicopter crew about the airplane, which was south of the Woodrow Wilson Bridge. At this time, the airplane was about 6.5 nautical miles (about 7.5 statute miles) south of the helicopter’s position, and its exterior lights would have been visible in the dark among those of several other airplanes, which were on approach to runway 1 from the south. The instructor pilot onboard PAT25 stated that they had the traffic in sight and requested visual separation, which the controller approved. As the aircraft flightpaths converged near the runway 33 approach corridor about 1 1/2 minutes later (20 seconds before impact), the controller asked the helicopter crew whether they had the airplane in sight and instructed PAT25 to pass behind it; however, one of the helicopter pilots pressed the radio push-to-talk switch for 0.8 seconds while the controller was speaking, and this brief radio transmission blocked the helicopter crew from receiving the “pass behind” portion of the controller’s instruction. The instructor pilot onboard PAT25 again indicated that they had the airplane in sight and requested visual separation, which the controller approved. PAT25 continued southbound along Route 4 while flight 5342 descended on final approach for runway 33, and the aircraft collided over the Potomac River at an altitude about 278 ft above mean sea level (msl).
Probable cause:
We determined that the probable cause of this accident was the FAA’s placement of a helicopter route in close proximity to a runway approach path; their failure to regularly review and evaluate helicopter routes and available data, and their failure to act on recommendations to mitigate the risk of a midair collision near Ronald Reagan Washington National Airport; as well as the air traffic system’s overreliance on visual separation in order to promote efficient traffic flow without consideration for the limitations of the see-and-avoid concept. Also causal was the lack of effective pilot-applied visual separation by the helicopter crew, which resulted in a midair collision. Additional causal factors were the tower team’s loss of situation awareness and degraded performance due to the high workload of the combined helicopter and local control positions and the absence of a risk assessment process to identify and mitigate real-time operational risk factors, which resulted in misprioritization of duties, inadequate traffic advisories, and the lack of safety alerts to both flight crews. Also causal was the Army’s failure to ensure pilots were aware of the effects of error tolerances on barometric altimeters in their helicopters, which resulted in the crew flying above the maximum published helicopter route altitude. Contributing factors included:
• the limitations of the traffic awareness and collision alerting systems on both aircraft, which precluded effective alerting of the impending collision to the flight crews;
• an unsustainable airport arrival rate, increasing traffic volume with a changing fleet mix, and airline scheduling practices at DCA, which regularly strained the DCA ATCT workforce and degraded safety over time;
• the Army’s lack of a fully implemented safety management system, which should have identified and addressed hazards associated with altitude exceedances on the Washington, DC, helicopter routes;
• the FAA’s failure across multiple organizations to implement previous NTSB recommendations, including ADS-B In, and to follow and fully integrate its established safety management system, which should have led to several organizational and operational changes based on previously identified risks that were known to management; and
• the absence of effective data sharing and analysis among the FAA, aircraft operators, and other relevant organizations.
Final Report:

Crash of a Cessna 208B Super Cargomaster in La Crosse: 1 killed

Date & Time: Mar 17, 2020 at 0919 LT
Type of aircraft:
Operator:
Registration:
N274PM
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Wichita - Hays
MSN:
208B-0705
YOM:
1998
Flight number:
PMS1670
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
9900
Circumstances:
The pilot was conducting a Part 135 on-demand cargo flight in instrument meteorological conditions. After executing a second missed approach, he informed air traffic control (ATC) of his intentions to divert to an airport located about 36 miles to the southeast. About 7 minutes after executing the second missed approach, the pilot began making unintelligible radio communications that ATC characterized as very garbled and difficult to understand, “almost hypoxic.” ATC then instructed the pilot to utilize oxygen. About 19 minutes after the second missed approach, ATC informed the pilot that the airplane had descended 1,600 ft, not following assigned course vectors or instructions and asked if everything was alright, to which no response was received. After attempting to relay communications through other airplanes in the area, an unintelligible response was received from the accident airplane. ATC then made numerous transmissions to the accident pilot urging him to utilize oxygen and open a window. No further communications were received from the accident airplane. A witness reported that he saw the airplane descend out of a low overcast cloud layer at a high rate of descent. The airplane then abruptly transitioned into a steep climb before re-entering the clouds. A few seconds later, he heard the airplane impact terrain and responded to the accident site. The sudden change in communications from the pilot indicates a possible impairment. When combined with the ATC data, the witness account, and the lack of any mechanical irregularities or malfunctions with the airplane, it is likely the pilot experienced difficulty controlling the airplane due to impairment. While the pilot was at an increased risk for an acute cardiovascular event, the extremely limited available medical evidence leaves no way to quantify that risk and no evidence regarding whether such an event occurred. As a result, whether the pilot was incapacitated by an acute medical event cannot be determined from the available medical information.
Probable cause:
An infight loss of control as a result of pilot impairment, the cause of which could not be determined.
Final Report:

Crash of a Beechcraft B200 Super King Air in Wichita: 4 killed

Date & Time: Oct 30, 2014 at 0948 LT
Registration:
N52SZ
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Wichita – Mena
MSN:
BB-1686
YOM:
1999
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
4
Captain / Total flying hours:
3139
Aircraft flight hours:
6314
Aircraft flight cycles:
7257
Circumstances:
The airline transport pilot was departing for a repositioning flight. During the initial climb, the pilot declared an emergency and stated that the airplane "lost the left engine." The airplane climbed to about 120 ft above ground level, and witnesses reported seeing it in a left turn with the landing gear extended. The airplane continued turning left and descended into a building on the airfield. A postimpact fired ensued and consumed a majority of the airplane. Postaccident examinations of the airplane, engines, and propellers did not reveal any anomalies that would have precluded normal operation. Neither propeller was feathered before impact. Both engines exhibited multiple internal damage signatures consistent with engine operation at impact. Engine performance calculations using the preimpact propeller blade angles (derived from witness marks on the preload plates) and sound spectrum analysis revealed that the left engine was likely producing low to moderate power and that the right engine was likely producing moderate to high power when the airplane struck the building. A sudden, uncommanded engine power loss without flameout can result from a fuel control unit failure or a loose compressor discharge pressure (P3) line; thermal damage prevented a full assessment of the fuel control units and P3 lines. Although the left engine was producing some power at the time of the accident, the investigation could not rule out the possibility that a sudden left engine power loss, consistent with the pilot's report, occurred. A sideslip thrust and rudder study determined that, during the last second of the flight, the airplane had a nose-left sideslip angle of 29°. It is likely that the pilot applied substantial left rudder input at the end of the flight. Because the airplane's rudder boost system was destroyed, the investigation could not determine if the system was on or working properly during the accident flight. Based on the available evidence, it is likely that the pilot failed to maintain lateral control of the airplane after he reported a problem with the left engine. The evidence also indicates that the pilot did not follow the emergency procedures for an engine failure during takeoff, which included retracting the landing gear and feathering the propeller. Although the pilot had a history of anxiety and depression, which he was treating with medication that he had not reported to the Federal Aviation Administration, analysis of the pilot's autopsy and medical records found no evidence suggesting that either his medical conditions or the drugs he was taking to treat them contributed to his inability to safely control the airplane in an emergency situation.
Probable cause:
The pilot's failure to maintain lateral control of the airplane after a reduction in left engine power and his application of inappropriate rudder input. Contributing to the accident was the pilot's failure to follow the emergency procedures for an engine failure during takeoff. Also contributing to the accident was the left engine power reduction for reasons that could not be determined because a postaccident examination did not reveal any anomalies that would have precluded normal operation and thermal damage precluded a complete examination.
Final Report:

Crash of a Cessna 500 Citation in Derby: 2 killed

Date & Time: Oct 18, 2013 at 1017 LT
Type of aircraft:
Operator:
Registration:
N610ED
Flight Phase:
Survivors:
No
Schedule:
Wichita - New Braunfels
MSN:
500-0241
YOM:
1975
Location:
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
2605
Captain / Total hours on type:
1172.00
Aircraft flight hours:
7560
Circumstances:
After climbing to and leveling at 15,000 feet, the airplane departed controlled flight, descended rapidly in a nose-down vertical dive, and impacted terrain; an explosion and postaccident fire occurred. Evidence at the accident site revealed that most of the wreckage was located in or near a single impact crater; however, the outer portion of the left wing impacted the ground about 1/2 mile from the main wreckage. Following the previous flight, the pilot reported to a maintenance person in another state that he had several malfunctioning flight instruments, including the autopilot, the horizontal situation indicator, and the artificial horizon gyros. The pilot, who was not a mechanic, had maintenance personnel replace the right side artificial horizon gyro but did not have any other maintenance performed at that time. The pilot was approved under an FAA exemption to operate the airplane as a single pilot; however, the exemption required that all equipment must be operational, including a fully functioning autopilot, flight director, and gyroscopic flight instruments. Despite the malfunctioning instruments, the pilot chose to take off and fly in instrument meteorological conditions. At the time of the loss of control, the airplane had just entered an area with supercooled large water droplets and severe icing, which would have affected the airplane's flying characteristics. At the same time, the air traffic controller provided the pilot with a radio frequency change, a change in assigned altitude, and a slight routing change. It is likely that these instructions increased the pilot's workload as the airplane began to rapidly accumulate structural icing. Because of the malfunctioning instruments, it is likely that the pilot became disoriented while attempting to maneuver and maintain control of the airplane as the ice accumulated, which led to a loss of control.
Probable cause:
The airplane's encounter with severe icing conditions, which resulted in structural icing, and the pilot's increased workload and subsequent disorientation while maneuvering in instrument flight rules (IFR) conditions with malfunctioning flight instruments, which led to the subsequent loss of airplane control. Contributing to the accident was the pilot's decision to takeoff in IFR conditions and fly a single-pilot operation without a functioning autopilot and with malfunctioning flight instruments.
Final Report:

Crash of a Cessna 208B Super Cargomaster in Wichita: 1 killed

Date & Time: Nov 6, 2012 at 0745 LT
Type of aircraft:
Operator:
Registration:
N793FE
Flight Type:
Survivors:
No
Schedule:
Wichita - Garden City
MSN:
208B-0291
YOM:
1991
Flight number:
FDX8588
Crew on board:
1
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
1
Captain / Total flying hours:
15200
Aircraft flight hours:
10852
Circumstances:
The aircraft was substantially damaged when it collided with a hedgerow during a forced landing following a loss of engine power near Wichita, Kansas. The loss of engine power occurred about 4-1/2 minutes after departing Wichita Mid-Continent Airport (ICT), Wichita, Kansas. The commercial pilot, who was the sole occupant, was fatally injured. The airplane was registered to the Federal Express Corporation and operated by Baron Aviation Services Incorporated, under the provisions of 14 Code of Federal Regulations Part 135 while on an instrument flight plan. Day visual meteorological conditions prevailed for the cargo flight that had the intended destination of Garden City Regional Airport (GCK), Garden City, Kansas. According to air traffic control transmissions, at 0734:35 (hhmm:ss), the pilot requested an instrument flight rules clearance from ICT to GCK. Radar track data indicated that the airplane departed runway 19R approximately 0737:45. At 0738:18, the tower controller told the pilot to change to the departure control frequency. The departure controller then cleared the flight to proceed direct to GCK and to climb to 8,000 ft mean sea level (msl). The airplane continued to climb on a westerly heading until 0742:02, at which time the airplane began a left 180-degree turn back toward the departure airport. According to radar data, the airplane had reached 4,700 ft msl when it began the left turn. At 0742:13, the pilot transmitted that his airplane had experienced a loss of engine power and that he was attempting to return to the departure airport. At 0742:31, the pilot asked if there were any nearby airports because he was unable to reach ICT. The departure controller provided vectors toward an airstrip that was approximately 2.5 miles southeast of the airplane's position. At 0743:46, the pilot advised that he could not see the airstrip because the airplane's windshield was contaminated with oil. At 0744:57, the pilot's final transmission was that he was landing in a grass field. The airplane was located about 2.2 miles south of ICT at 1,600 feet msl, about 300 feet above ground level (agl) at the time of the last transmission. The radar data continued northeast another 1/2 mile before radar contact was lost at 0745:15. A witness to the accident reported that he was outside his residence when he observed the accident airplane overfly his position. He recalled that the airplane's propeller was not rotating and that he did not hear the sound of the engine operating. He stated that the airplane landed in a nearby agricultural field on a northeast heading. He reported that during the landing rollout the airplane impacted a hedgerow located at the northern edge of the field. The witness indicated that the pilot was unresponsive when he arrived at the accident site and that there was a small grass fire located 8 to 10 feet in front of the main wreckage.
Probable cause:
The total loss of engine power as a result of a fractured compressor turbine blade due to high-cycle fatigue.
Final Report:

Crash of a Beechcraft B90 King Air in Dodge City: 3 killed

Date & Time: Feb 17, 2004 at 0257 LT
Type of aircraft:
Operator:
Registration:
N777KU
Flight Type:
Survivors:
No
Schedule:
Wichita - Dodge City
MSN:
LJ-377
YOM:
1968
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
3066
Captain / Total hours on type:
666.00
Aircraft flight hours:
9005
Circumstances:
The emergency medical services (EMS) airplane was destroyed by terrain impact and post impact fire about 7 nautical miles (nm) west of its destination airport, Dodge City Regional Airport (DDC), Dodge City, Kansas. The 14 Code of Federal Regulations Part 91 positioning flight departed the Wichita Mid-Continental Airport (ICT), Wichita, Kansas, about 0215 central standard time and was en route to DDC. Night visual meteorological conditions prevailed when the accident occurred about 0257 central standard time. The flight had been on an instrument flight rules (IFR) flight plan, but the pilot cancelled the IFR flight plan about 34 nm east of DDC and initiated a descent under visual flight rules. Radar track data indicated that the airplane maintained a magnetic course of about 265 degrees during the flight from ICT to DDC. The rate of descent was about 850 to 950 feet per minute. During the descent, the airplane flew past the airport on a 270 degree course. Witnesses in the area reported hearing the engine noise of a low-flying airplane followed by the sound of impact. One of the witnesses described the engine noise as sounding like the engines were at "full throttle." The on-site inspection revealed that the airplane impacted the terrain in a gear-up, wings-level attitude. The inspection of the airplane revealed no anomalies to the airframe or engines. A review of the pilot's 72-hour history before the accident revealed that it had been 14 hours and 32 minutes from the time the pilot reported for duty about 1225 central standard time until the time of the accident. It had been 20 hours 57 minutes from the time the pilot awoke (0600) on the morning before the accident until the time of the accident. No evidence of pilot impairment due to carbon monoxide, drugs, or medical incapacitation was found. The accident occurred during a time of day that was well past the pilot's normal bedtime and also at a time of day when the physiological need to sleep is especially strong. The findings from a Safety Board's human performance analysis indicates that the pilot was likely fatigued. A review of 14 CFR 135.267 indicated that the pilot had adhered to the flight time limitations and rest requirements specified in the regulation.
Probable cause:
The pilot failed to maintain clearance with terrain due to pilot fatigue (lack of sleep).
Final Report:

Crash of a Canadair CL-604-2B16 Challenger in Wichita: 3 killed

Date & Time: Oct 10, 2000 at 1452 LT
Type of aircraft:
Operator:
Registration:
C-FTBZ
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Wichita - Wichita
MSN:
5991
YOM:
1994
Crew on board:
3
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
6159
Captain / Total hours on type:
189.00
Copilot / Total flying hours:
6540
Copilot / Total hours on type:
1
Aircraft flight hours:
1226
Circumstances:
On October 10, 2000, at 1452 central daylight time, a Canadair Challenger CL-600-2B16 (CL604) (Canadian registration C-FTBZ and operated by Bombardier Incorporated) was destroyed on impact with terrain and postimpact fire during initial climb from runway 19R at Wichita Mid-Continent Airport (ICT), Wichita, Kansas. The flight was operating under the provisions of 14 Code of Federal Regulations (CFR) Part 91 as an experimental test flight. The pilot and flight test engineer were killed. The copilot was seriously injured and died 36 days later.
Probable cause:
The pilot’s excessive takeoff rotation, during an aft center of gravity (c.g.) takeoff, a rearward migration of fuel during acceleration and takeoff and consequent shift in the airplane’s aft c.g. to aft of the aft c.g. limit, which caused the airplane to stall at an altitude too low for recovery. Contributing to the accident were Bombardier’s inadequate flight planning procedures for the Challenger flight test program and the lack of direct, on-site operational oversight by Transport Canada and the Federal Aviation Administration.
Final Report: