NTSB News Talk – Aviation Accidents, Safety Investigations & Pilot Lessons

Reagan National Midair NTSB Hearing Day 3: Collision Avoidance & Safety Culture

On this episode of NTSB News Talk, Max Trescott covers the third and final day of the NTSB’s investigative hearing into the January 2024 midair collision near Washington’s Reagan National Airport between a PSA Airlines CRJ-700 and a U.S. Army UH-60L Black Hawk. Day 3 featured Panel 4: Collision Avoidance Technology and Panel 5: Safety Data and Safety Management Systems.The hearing opened with spatial disorientation testimony and interviews with Army pilots about Route 4 altitude protections they incorrectly believed would keep them clear of Runway 33 arrivals. NASA’s Dr. Stephen Casner explained that cockpit traffic displays can help pilots spot targets up to eight times faster than by visual scan alone.Experts detailed ADS-B system complexities — including the two incompatible broadcast frequencies (UAT and 1090ES) — and reviewed the limits of pre-ADS-B collision avoidance technology. The UH-60L Black Hawk lacks integrated traffic displays, relying instead on iPads with Stratus receivers, which Army policy prohibits the flying pilot from using. Portable ADS-B In devices provide only partial traffic pictures unless paired with ADS-B Out, limiting situational awareness.Discussions turned to TCAS: its nuisance alert problem, differences for helicopter operations, and why the CRJ-700 lacks a certified ADS-B In solution. The NTSB Chairwoman confronted the FAA over its 17-year refusal to mandate ADS-B In, despite repeated post-collision recommendations. The Army is now procuring 1,685 Stratus/iPad sets for priority units, but operational use will still be limited at low level.FAA data revealed 366 TCAS resolution advisories within 10 nm of DCA from 2023–2025. Testimony noted that crews involved in RAs are typically not notified unless a deviation occurs. Panelists debated safety culture, just culture, and leadership removals at DCA Tower after the accident. A controller supervisor described the pre-accident culture as “robust,” but post-accident changes removed key institutional knowledge.The hearing also exposed gaps in PSA pilot special-qualification training for DCA — including no information on helicopter routes or operations — and examined simulator results showing that circling to Runway 33 can double or triple pilot workload compared to a straight-in to Runway 1.Closing testimony on future ACAS XR technology indicated it could have alerted the Black Hawk crew 73 seconds before impact, with potential nationwide deployment by 2027. Max weaves these details into a narrative showing how technological shortfalls, flawed assumptions, procedural gaps, and cultural challenges all converged in this tragic midair — and what reforms could prevent a repeat.NTSB Docket on Reagan National midair collisionCheck out our other Aviation News Talk Network podcasts:UAV News Talk Podcast Rotary Wing Show PodcastAviation News Talk

Reagan National Midair NTSB Hearing Day 2: Army Black Hawk & CRJ-700 Testimony

Max Trescott plays audio clips from Day 2 of the NTSB investigative hearing on the midair collision near Washington’s Reagan National Airport between a PSA Airlines CRJ-700 and a U.S. Army UH-60L Black Hawk. This day focused exclusively on Panel 3: Training, Guidance, and Procedures Applicable to DCA Air Traffic Control, revealing systemic issues that shaped the events leading to the accident.A major theme was visual separation. Testimony explored the difference between pilot-applied and tower-applied visual separation in Class B airspace and the operational norm at DCA where helicopter pilots almost reflexively request pilot-applied visual separation. Experts explained how the unique combination of restricted airspace, helicopter routes, and runway configurations makes visual separation “paramount” for traffic flow, though it shifts collision avoidance responsibility to pilots. A U.S. Army pilot described the difficulty of spotting Runway 33 arrivals at low altitude, highlighting how these challenges contributed to the accident sequence.Staffing emerged as a critical factor. The DCA tower had 19 fully operational controllers to cover 16 shifts a day, forcing position combinations such as merging tower and helicopter frequencies. Witnesses described high workload and a culture summed up by the phrase “just make it work,” raising questions about whether safety margins were being eroded. A management-level request to reduce arrival rates from 32 to 28 per hour due to safety concerns was denied, reportedly over political timing related to FAA reauthorization.The hearing also examined miles-in-trail spacing, revealing inconsistent agreements between Potomac TRACON and DCA Tower and noting that arrivals were being fed at less than four miles apart before the accident. Conflict alert systems were scrutinized, with testimony that up to 50% of alerts are “nuisance alerts,” that could lead to controller desensitization. The Black Hawk’s lack of ADS-B Out was discussed, though radar coverage mitigated its effect on conflict alerting in this case.Additional revelations included confusion over helicopter route altitudes, the tower’s downgrade from Level 10 to Level 9 (which resulted in new controllers being paid at a lower level than existing controllers), and an external compliance audit that found 33 areas of non-compliance—so severe the audit was halted and converted into an internal corrective action. The episode also covers the failure to conduct alcohol testing at all of controllers after the accident, contrary to the DOT’s two-hour requirement.Max weaves over an hour of testimony into a narrative that exposes the intersection of human factors, training gaps, and systemic pressures inside one of the nation’s most complex airspace environments. The episode underscores how a combination of cultural norms, operational constraints, and safety oversight gaps set the stage for this tragic collision—and what must change to prevent future accidents.NTSB Docket on Reagan National midair collisionCheck out our other Aviation News Talk Network podcasts:UAV News Talk Podcast Rotary Wing Show PodcastAviation News Talk

Reagan National Midair NTSB Hearing Day 1: Army Black Hawk & Regional Jet Crash Testimony

Max Trescott takes listeners deep inside Day 1 of the NTSB’s investigative hearing into the tragic midair collision near Washington’s Reagan National Airport between a PSA Airlines CRJ-700 and a U.S. Army UH-60L Black Hawk helicopter. The accident claimed the lives of 67 people, including the crew of both aircraft, and has become one of the most scrutinized airspace safety failures in recent history. In this episode of NTSB News Talk, Max distills over ten hours of testimony into 18 critical clips, delivering more than an hour of compelling audio that reveals surprising findings, heated exchanges, and systemic safety issues.The day opened with an animated reconstruction of the collision showing the helicopter at 280 feet MSL—80 feet above the 200-foot altitude depicted for that segment of the published helicopter route—and the CRJ-700 at 290 feet on short final to DCA’s Runway 33. Panel 1, “Overview of Accident Helicopter’s Air Data Systems and Altimeters,” uncovered a significant problem with UH-60L altimeter accuracy. Test flights conducted after the accident revealed rotor downwash caused barometric altimeters to read 80–130 feet lower than true altitude at hover and cruise. Compounding the issue, transponder encoders legally transmit in 100-foot increments and can be off by up to 90 feet while still being “in spec.” The testimony underscored how cumulative tolerances could create a 100-foot discrepancy between left and right seat altimeters, even with properly maintained systems.The hearing also exposed a fundamental difference in altitude standards between Army and civilian pilots. Army witnesses stated their standard is to maintain altitude within ±100 feet, meaning 300 feet would still be considered acceptable when targeting 200 feet MSL. Civilian operators, including medevac pilots accustomed to the DCA corridor, testified that in this airspace 200 feet is treated as a hard ceiling, not a target with a tolerance band. This cultural gap framed much of the day’s discussion.Panel 2, “Overview of the DCA Class B Airspace and Helicopter Routes,” shifted focus to the unique and congested structure of Washington’s helicopter corridors. FAA representatives confirmed a startling fact: the altitudes on the published helicopter charts are “recommended” for VFR operations and are not regulatory unless specifically assigned by ATC. Likewise, drifting off the depicted route or exceeding the published altitude is not a violation unless ATC imposes a hard restriction. Yet multiple witnesses testified that in practice, both Army and civilian pilots, as well as controllers, treat the published routes and altitudes as mandatory. The disconnect between policy and operational understanding drew pointed questioning from the Board.A recurring theme was the vulnerability of the route structure due to lack of consistent oversight. FAA orders require an annual review of the Baltimore-Washington helicopter route chart, but testimony revealed that DCA Tower has cycled through ten air traffic managers since 2013, with five in the last five years, making continuity of safety evaluations nearly impossible. A working group identified Route 4—the exact route used by the Black Hawk—as hazardous and attempted to mitigate risk by designating charted hotspots. FAA’s Aeronautical Information Services rejected the request on the grounds that “hotspot” symbology is limited to surface charts. NTSB members expressed frustration that bureaucratic charting standards overrode a direct safety recommendation from front-line controllers in the nation’s most complex helicopter environment.One surprising revelation involved ADS-B compliance. The Army testified that less than 20% of its flights in the region flew with ADS-B Out enabled. Even worse, the investigation discovered that seven of eight Lima-model Black Hawks at Davison Army Airfield were misconfigured and not broadcasting ADS-B Out at all due to maintenance documentation errors during equipment installation. Although the Army issued an immediate safety action message once the problem was discovered, the finding highlights a significant blind spot in surveillance and collision avoidance in one of the busiest mixed-use airspaces in the country.MedStar’s chief pilot, Rick Dressler, raised another critical point: pilot experience in the National Capital Region. Civilian medevac crews often log thousands of hours flying the DCA corridors over decades, developing an intimate understanding of priorities and flow in the Class B environment. By contrast, Army pilots rotate frequently, often with only a few hundred hours of experience in the airspace, and sometimes exhibit unfamiliarity with medevac priority protocols and heliport coordination. Dressler cited incidents where military helicopters blocked hospital pads, preventing civilian medevac landings with critically ill patients—a chilling illustration of cultural and procedural gaps.The NTSB also explored training and proficiency, uncovering that aggregate flight hours among Army aviators have been declining for years. Where battalions once had “thousands and thousands” of collective cockpit hours, current totals are “hundreds and hundreds,” with many pilots flying just enough to meet minimum currency requirements rather than achieving deep proficiency. This trend, combined with complex airspace and limited local familiarity, creates layers of risk.The day concluded with a tense exchange between NTSB Chair Jennifer Homendy and FAA leadership over delays in providing data. Homendy blasted the agency for withholding critical information for six months, only delivering thousands of pages on the Friday before the hearing after intervention from the Secretary of Transportation. Her pointed “Do better” summed up the Board’s frustration with bureaucratic inertia in the face of a catastrophic loss of life.As Day 2 approaches, focusing on training, guidance, and collision avoidance technology, this episode sets the stage for a deeper understanding of how a confluence of small gaps and misunderstandings led to one of the most devastating midair collisions in recent U.S. aviation history.NTSB Docket on Reagan National midair collisionCheck out our other Aviation News Talk Network podcasts:UAV News Talk Podcast Rotary Wing Show PodcastAviation News Talk

NTSB: Delta B-52 Close Call and Runway Incursion at Mexico City

Max and Rob bring listeners a packed episode of aviation safety lessons anchored by the NTSB. They begin with the Board’s announcement of a three-day investigative hearing into the Reagan National midair between a regional jet and a U.S. Army helicopter. Rob dives into a dramatic close call in North Dakota, where a Delta Regional Jet on final narrowly avoided a B-52 bomber crossing its flight path near Minot. The incident exposes communication gaps, contract tower limitations, and the critical need for radar and coordination between military and civilian traffic.In Mexico City, a Delta A320 rejected a high-speed takeoff to avoid an AeroMexico E-190 landing over the top of it on the same runway. The event raises red flags about ATC language use, as Spanish transmissions prevented the Delta crew from maintaining situational awareness. Max explores the Hollister RV-8/Cirrus collision, highlighting how a relocated runway threshold and lack of radio calls can set the stage for disaster. A video of the midair was posted on Facebook. AOPA's Sweepstakes Aviat A-1C-200 Husky was damaged in a landing incident, in which the pilot's left foot was misplaced an not on the rudder pedal.A Murphy Aircraft Manufacturing Limited Moose airplane, N250MK, was destroyed when it was involved in a takeoff accident near Montrose, CO. According to the Preliminary NTSB report, two pilots on board were killed. The Falcon 10 runway overrun in Panama City offers a textbook example of checklist discipline when thrust reversers failed due to switches left in the wrong position, turning deceleration into forward thrust. The AOPA Sweepstakes Husky mishap adds another cautionary tale about cockpit discipline and distractions.The episode’s most personal moment comes when Rob shares his experience flying rusty in a G1000-equipped Cessna 182. Fatigue, cockpit visibility issues, haze, and a failed trim system combined to erode his performance and highlight how ego can mask risk. Max underscores the I’M SAFE checklist—illness, medications, stress, alcohol, fatigue, emotion—and how self-awareness can prevent tragedies. Together, they emphasize that open discussion and honest reflection are vital to improving safety and preventing accidents.Check out our other Aviation News Talk Network podcasts:UAV News Talk Podcast Rotary Wing Show PodcastAviation News Talk

SR22 Electrical Failure Crash; Air India Fuel Switches, Cessna 240 Crashes into Pacific

Max Trescott and Rob Mark return for episode five of NTSB News Talk with a full slate of recent accidents and preliminary reports that highlight critical lessons in decision-making, mechanical failure, and situational awareness.They start with the tragic crash of a Cirrus SR22 in North Carolina that killed a family of four. The aircraft had experienced electrical issues early in the flight, and despite indications of ongoing problems, the pilot chose to continue to the destination rather than land. Max emphasizes how what may seem like a minor issue—such as an alternator failure—can escalate, especially if the pilot doesn’t fully understand the systems or how cascading failures can emerge.Next, they examine a mid-air collision in Steinbach, Manitoba between two Cessna training aircraft. Despite clear weather and an active pattern, both pilots were killed. Max reminds listeners that most mid-airs happen close to airports, often on final. Rob adds that see-and-avoid doesn’t always work, especially with sun glare or poor traffic sequencing.They then move to a bizarre and poorly documented case of a Cessna T240 that departed Ramona, California and flew 400 miles offshore before descending into the Pacific. With no radio contact and the aircraft failing to respond to repeated ATC calls, the case raises the possibility of a medical event or incapacitation. The plane was never recovered.A medical charter King Air crash in London, UK, is briefly discussed. The aircraft appeared to roll left and crash immediately after takeoff. Rob stresses the importance of immediate rudder input and pitch control following engine failure in twins.A major focus of the episode is the preliminary report on Air India Flight 171, a Boeing 787 that lost both engines seconds after rotation. Both fuel cutoff switches moved from RUN to CUTOFF, then briefly back. One pilot is heard asking, “Why did you cut the fuel?” The other responds, “I didn’t do anything.” Rob and Max explore the implications of this odd event, especially in light of a 2018 FAA bulletin about fuel control switch locking mechanisms. Despite the non-mandatory nature of the bulletin, it directly referenced the potential for disengagement of the locking feature. Rob explains how the switches require a deliberate lift-and-pull action to move into CUTOFF, making accidental movement unlikely. Suicide and sabotage are also deemed improbable.The discussion turns back to U.S. reports, including a crash in Montana where a Cessna 172 flew low and hit unmarked power lines. Max reiterates how hard it is to see wires until it's too late. Rob reflects on his own youthful low-level flying and how little awareness he had of such hazards at the time.They then discuss a helicopter crash in Alaska. A Robinson R66 pilot operating in flat, snow-covered terrain under a 500-foot overcast likely experienced whiteout conditions and lost situational awareness. Max explains how disorientation is common in visually featureless environments—recounting his own night flight in hazy conditions where city lights and stars blurred together.They also dissect a De Havilland Twin Otter crash in Tennessee during a skydiving flight. A left engine power loss forced a turnback attempt. The aircraft crashed into trees short of the runway, severely damaging the left wing and engine. Six people were seriously injured, though none killed. Rob questions the decision to add flaps during the emergency and notes the pilot’s inability to confirm if he secured the failed engine.Finally, the hosts cover the NTSB final report of a 2023 Cessna 172 crash near San Rafael, CA. The pilot failed to apply carb heat during descent at night and suffered an engine failure. The aircraft struck a power line and terrain. Max references carb ice charts and highlights how even VFR conditions can require IFR-like vigilance, especially during nighttime descents.The episode wraps with Rob pointing out a discrepancy between NTSB and FAA data on the aircraft’s engine model, and Max reminding pilots that modifying aircraft with STCs can create documentation mismatches.