Regulations & Safety
CommuteAir Flight 4339 Runway Excursion and NTSB Preliminary Findings
NTSB preliminary report on CommuteAir Flight 4339 runway overrun at Roanoke highlights crew decisions and EMAS safety role.
CommuteAir Flight 4339 Runway Excursion: A Breakdown of the NTSB Preliminary Report
On the night of September 24, 2025, CommuteAir flight 4339, operating as a United Express service, ended its journey from Washington Dulles not at the terminal, but in an engineered materials arresting system (EMAS) at Roanoke-Blacksburg Regional Airport (ROA). The Embraer EMB-145XR, carrying 50 passengers and 3 crew members, overran runway 34 during a rainy landing. Fortunately, the incident resulted in no injuries and only minor damage to the aircraft, a testament to the effectiveness of modern runway safety technology. However, the events leading up to this runway excursion, as detailed in the National Transportation Safety Board’s (NTSB) preliminary report, raise important questions about crew coordination, decision-making under pressure, and adapting to rapidly changing weather.
The flight was already under a degree of stress before it even left the ground. It was the second leg of the fourth day of a long rotation for the crew. Passengers had been deplaned twice due to maintenance issues, leading to a departure approximately two and a half hours behind schedule. While pre-flight delays are not uncommon, they can contribute to a cascading series of events. This incident serves as a critical case study for the aviation industry, highlighting the razor-thin margins that separate a routine landing from a serious incident and the layers of safety that are in place to mitigate the consequences when things go wrong.
The NTSB’s investigation is ongoing, and this initial report provides a factual, unvarnished look at the sequence of events. It lays the groundwork for a deeper analysis of operational factors, human performance, and air traffic control communications. As we dissect the available information, we get a clearer picture of the dynamic challenges the flight crew faced and the critical decisions made in the final moments of the flight. The data from the cockpit voice recorder and flight data recorder will be crucial in piecing together the complete narrative.
From Clear Skies to a Rainy Approach
The flight’s journey from Washington to Roanoke began with a weather forecast that suggested a routine arrival. The initial Automatic Terminal Information Service (ATIS) report for ROA indicated calm winds, no rain, and runway 6 in use. Based on this, the captain, who was the pilot flying, briefed for a localizer approach to that runway. The first officer, acting as pilot monitoring, proactively suggested reviewing landing performance for a wet runway, but the captain declined, citing the clear conditions reported by ATIS. This initial interaction sets the stage for a developing situation where crew communication and differing perspectives on risk would become a central theme.
As the aircraft began its descent, the weather picture changed dramatically. Approach control alerted the crew to precipitation near the airport and advised that other aircraft were now using runway 34 for landing. This prompted a change in plan. The captain requested the first officer set up and brief the ILS (Instrument Landing System) approach for runway 34, a more precise approach suitable for deteriorating weather. The crew was now actively adapting to a new set of circumstances, a standard procedure in the dynamic environment of aviation.
The situation continued to evolve rapidly on the final approach. The crew overheard a report from a preceding aircraft that mentioned marginal visibility and bumpy conditions. The rain intensified, leading the first officer to perform a landing calculation for a wet runway. The calculation showed a safety margin of about 200 feet more than required, even without the use of thrust reversers. This data point suggested the landing was feasible, but the conditions were far from the calm, dry scenario anticipated at the start of the flight.
The Final Moments: Go-Around Calls and a Captain’s Decision
The intensity of the rain increased to “heavy” on the short final, prompting the captain to request the windshield wipers be set to high speed. As the aircraft descended below 500 feet, a critical phase of flight, the first officer noted they were high on the precision approach path indicator (PAPI), a visual aid that helps pilots maintain the correct glidepath. A high indication means the aircraft is above the ideal descent profile, which can lead to touching down too far down the runway and not having enough distance to stop.
Recognizing the unstable nature of the approach, the first officer made a critical callout: “go-around.” This is a standard call for discontinuing a landing approach that is not proceeding as planned. The call was made as the aircraft crossed the runway threshold, but the captain continued with the landing. The first officer repeated the “go-around” call about halfway down the runway, but again, the captain continued the landing attempt. This divergence in crew action is a significant point of interest for the NTSB’s human factors investigation.
The NTSB report states, “After crossing the runway markings, the FO called for a go-around, but the captain continued. About halfway down the runway, the FO called for a go-around a second time, but the captain continued.”
After touchdown, the crew applied maximum braking and deployed the engine thrust reversers. Despite these actions, the aircraft could not be stopped on the remaining runway. It overran the pavement and came to a safe stop in the EMAS. The successful deployment and function of the EMAS bed prevented a potentially far more serious outcome, containing the aircraft and protecting everyone on board. Following the event, airport rescue and firefighting personnel boarded the aircraft and assisted passengers in evacuating via a ladder.
The Investigation and the Role of Safety Systems
The NTSB is leading a comprehensive investigation into the incident, with participation from the Federal Aviation Administration (FAA), CommuteAir, the Air Line Pilots Association (ALPA), and Brazilian authorities, as the aircraft was manufactured by Embraer. Specialists in various fields, including flight recorders, meteorology, air traffic control, and human factors, have been assigned to the case. The cockpit voice and flight data recorders were recovered and sent to the NTSB’s lab in Washington, D.C., for detailed analysis. The data from these recorders will provide investigators with precise details about the aircraft’s parameters, crew conversations, and actions throughout the flight.
A key takeaway from this incident is the undeniable success of the Engineered Materials Arresting System (EMAS). This technology, installed at the end of runways where safety areas are limited, is designed to crush under the weight of an aircraft, decelerating it safely. The images from the report show the aircraft’s main landing gear embedded in the EMAS, illustrating exactly how the system is designed to work. This event serves as a powerful, real-world example of how investment in runway safety infrastructure pays dividends by preventing injuries and major aircraft damage.
The investigation will undoubtedly focus heavily on Crew Resource Management (CRM). CRM is the practice of using all available resources, both human and technological, to ensure safe and efficient flight operations. The differing actions of the captain and first officer in the final moments of the landing will be scrutinized. Investigators will seek to understand the decision-making process, communication dynamics, and any potential factors that may have influenced the captain’s choice to continue the landing despite the first officer’s calls to go around. The findings will likely contribute to ongoing training and procedural refinements across the airline industry.
Concluding Thoughts
The runway excursion of CommuteAir flight 4339 is a stark reminder of the complexities of commercial aviation. It underscores how quickly a routine flight can encounter unforeseen challenges, demanding rapid and accurate decision-making from the flight crew. The preliminary NTSB report provides a factual, dispassionate account of the events, laying the groundwork for a thorough investigation that will ultimately aim to enhance aviation safety for everyone.
While the absence of injuries is a relief, the incident highlights critical areas for review, particularly concerning crew coordination in unstabilized approaches and the persistent challenge of landing in rapidly deteriorating weather. The successful outcome, in terms of passenger and crew safety, can be directly attributed to the effectiveness of the EMAS, reinforcing the importance of such safety systems. The final NTSB report will provide the industry with valuable lessons to prevent similar occurrences in the future.
FAQ
Question: What is a runway excursion?
Answer: A runway excursion is an incident where an aircraft veers off or overruns the runway surface. This can occur during takeoff or landing and can be caused by various factors, including unstable approaches, contaminated runways (with water, ice, or snow), mechanical issues, or pilot error.
Question: What is an EMAS?
Answer: EMAS stands for Engineered Materials Arresting System. It is a bed of crushable, energy-absorbing material placed at the end of a runway. When an aircraft overruns the runway, the EMAS collapses under the weight of the aircraft’s tires, safely decelerating it and preventing it from causing more significant damage or injuries.
Question: Why did the first officer call for a “go-around”?
Answer: A “go-around” is a standard procedure where a landing is aborted. Pilots are trained to initiate a go-around if the approach is not “stabilized”, meaning the aircraft is not at the correct speed, descent rate, or on the correct flight path. In this case, the first officer observed the aircraft was too high on the approach path and called for a go-around to discontinue the unstable landing attempt.
Sources
Photo Credit: X
Regulations & Safety
NTSB: Thermal Plugs Caused AA Flight 3023 Tire Failure
NTSB determines melted thermal relief plugs caused tire failure on American Airlines 737-8 at Denver, triggering emergency evacuation.
The National Transportation Safety Board (NTSB) has determined that melted thermal relief plugs caused the left main landing gear tires to fail on an American Airlines Boeing 737-8 during a July 2025 takeoff roll at Denver International Airport (DEN), prompting a high-speed rejected takeoff and emergency evacuation.
The final aviation investigation report, published on August 26, 2026, officially closes the inquiry into American Airlines Flight 3023. The document details the mechanical sequence that led to the tire failure while highlighting significant passenger noncompliance during the subsequent evacuation, as travelers ignored crew commands and retrieved carry-on baggage.
Mechanical sequence and rejected takeoff
The incident occurred on July 26, 2025, involving a Boeing 737-8, registration N306SW, equipped with CFM International LEAP-1B28 engines. According to the NTSB, the flight experienced an approximate 25-minute delay while awaiting departure at runway 34L.
During the subsequent takeoff roll, as the aircraft reached an indicated airspeed between 90 and 100 knots, the captain reported hearing a loud pop accompanied by a noticeable bump. The flight crew initiated a rejected takeoff at speeds above 80 knots.
The NTSB determined the probable cause of the incident was the melting of thermal relief plugs in the left main landing gear. This melting released tire pressure and caused the tires and wheels to fail during the takeoff roll. The agency noted that this failure resulted in abnormal airplane handling characteristics, which prompted the flight crew to reject the takeoff. Debris from the fractured wheels caused minor damage to the aircraft, including a three-inch dent on the lower skin of the left wing.
Emergency evacuation and passenger behavior
Following the rejected takeoff, the flight crew initially instructed the cabin to remain seated. Between 30 and 45 seconds later, after identifying smoke and fire originating from the left main landing gear, the crew ordered an emergency evacuation.
The aircraft carried 175 occupants, comprising 169 passengers and six crew members. The NTSB final report confirms that zero injuries occurred during the event. This official casualty figure supersedes preliminary media reports from July 2025 that had indicated minor injuries and hospital evaluations.
The investigation report draws specific attention to passenger behavior during the emergency egress. The NTSB stated that the cabin crew described the evacuation as rapid but hindered by significant passenger confusion and noncompliance. Despite flight attendants repeatedly commanding passengers to leave their belongings behind, multiple individuals retrieved their carry-on baggage. The NTSB concluded that this noncompliance directly slowed the flow of egress from the aircraft.
AirPro News analysis
The NTSB findings regarding American Airlines Flight 3023 add to a well-documented and growing safety concern within the commercial aviation sector. Passenger retrieval of carry-on baggage during emergency evacuations is a recurring issue that compromises the 90-second evacuation standard mandated by the Federal Aviation Administration (FAA).
When passengers stop to open overhead bins and carry luggage down escape slides, they not only slow the egress rate for those behind them but also introduce the risk of puncturing the evacuation slides or injuring fellow passengers. We continue to see official accident reports cite passenger noncompliance as a negative factor in evacuation efficiency. This recurring behavioral pattern has prompted safety advocates and lawmakers to question whether current FAA evacuation certification tests, which rely on compliant participants, accurately reflect real-world human behavior during an emergency.
Sources: National Transportation Safety Board
Photo Credit: National Transportation Safety Board
Regulations & Safety
Marine One Loss of Separation at DCA: NTSB Preliminary Report
NTSB cites radio line-of-sight failure after Marine One and Envoy Air E-170 came within 0.82 NM at Reagan National.
This is a developing story. Information may change as official details are released.
This is original reporting and analysis by AirPro News.
A loss of separation occurred on August 4, 2026, between a Sikorsky VH-3D operating as Marine One and an Envoy Air Embraer E-170 departing Ronald Reagan Washington National Airport (DCA). The incident took place approximately two miles north of the airport at 14:34 EDT and prompted an immediate Federal Aviation Administration (FAA) relocation of radio equipment after investigators identified a communication failure.
According to a preliminary report released on August 27, 2026, by the National Transportation Safety Board (NTSB), air traffic controllers at DCA did not receive a required three-minute pre-departure warning from the helicopter. The event triggered a review of strict Safety protocols implemented following a fatal midair collision in the same airspace in January 2025.
Incident timeline and separation data
The loss of separation occurred when Marine One departed The Ellipse simultaneously with Envoy Air flight 3742 departing runway 1 at DCA. Preliminary FAA estimates indicate the aircraft came within 0.82 nautical miles (NM) laterally and 700 feet vertically. The NTSB is currently analyzing surveillance data to establish the exact closest point of approach.
President Donald Trump was on board the Sikorsky VH-3D at the time of the incident. In a statement provided to CBS News, White House spokesman Kush Desai confirmed the President was never in danger.
Marine One flights are piloted by the finest aviators in the world, and the White House maintains the utmost confidence in these patriots and other security officials who are responsible for ensuring the President’s safety.
No injuries were reported among the occupants of either aircraft, and both flights continued to their respective destinations without further incident.
Communication failure and FAA response
The NTSB preliminary report points to inadequate radio line-of-sight coverage between The Ellipse and the DCA tower as the primary factor in the missed pre-departure warning. A DCA tower controller reported that the transmission attempt from the helicopter was “broken and unreadable,” according to CBS News.
Following the August 4 incident, FAA technicians evaluated the infrastructure and confirmed the line-of-sight deficiency. To resolve the issue, the agency relocated the helicopter-control radio equipment to the top of the DCA control tower. Subsequent communication checks were successful.
CBS News also reported that recent construction at the White House may have contributed to the radio line-of-sight degradation, though the NTSB has not yet issued a final determination on the cause.
Regulatory context and prior airspace changes
The airspace surrounding DCA operates under highly specific procedural rules designed to deconflict fixed-wing airline traffic from frequent VIP helicopter movements. These procedures were significantly tightened following a fatal midair collision on January 29, 2025, involving an airliner and an Army Black Hawk helicopter near the airport.
Following the 2025 accident, regulators instituted a requirement for a ground stop at DCA anytime a Helicopters passes on a conflicting route. The failure of the three-minute warning on August 4 prevented controllers from initiating this required ground stop for the Envoy Air departure.
Air traffic controllers and Marine One pilots had previously met on July 28, 2026, exactly one week prior to the incident, to discuss ongoing communication challenges in the sector.
AirPro News analysis
The August 4 loss of separation highlights the fragility of procedural deconfliction in the Washington, D.C. airspace. While the FAA characterized the event as a momentary loss of separation, the failure of a critical communication link reveals a single point of failure in the safety protocols established after the 2025 collision. We note that the rapid relocation of the radio equipment by the FAA demonstrates an acknowledgment of the infrastructure gap. As the NTSB continues its Investigation, we will monitor the docket for potential systemic recommendations regarding how VIP helicopter movements integrate with high-volume Commercial-Aircraft traffic at DCA, particularly concerning redundant communication systems.
Sources: National Transportation Safety Board
Photo Credit: National Transportation Safety Board
Regulations & Safety
FAA Moves to Fire Two LaGuardia Controllers After Fatal Collision
FAA initiates termination proceedings against two LaGuardia controllers for early shift departures on the night of the March 22, 2026 runway collision.
This is a developing story. Information may change as official details are released.
This article summarizes reporting by Reuters by David Shepardson and Doyinsola Oladipo.
The FAA has initiated termination proceedings against two air traffic controllers accused of leaving their shifts early on the night of a fatal runway collision at LaGuardia Airport (LGA) in March 2026. The agency is classifying the unauthorized early departures as timecard fraud amid a broader national crackdown on the practice.
The disciplinary action follows the March 22, 2026, accident in which Air Canada Express Flight 8646, operated by Jazz Aviation LP, collided with an aircraft rescue firefighting (ARFF) vehicle while landing on Runway 4. According to Reuters, the two controllers allegedly departed the facility approximately one hour before their scheduled shifts ended, a practice colloquially known as an “early shove.”
Disciplinary actions and union response
The FAA stated its commitment to holding employees accountable, emphasizing that it will not compromise the safety or efficiency of the national airspace system. U.S. Secretary of Transportation Sean Duffy condemned the practice, stating that while most controllers complete their full shifts, the department will not tolerate fraud from individuals who unfairly burden their colleagues and impact the airspace.
The National Air Traffic Controllers Association (NATCA) confirmed it is actively discussing the allegations with FAA leadership. The union indicated that these internal discussions are the appropriate forum for addressing the matter. Reuters reports that the FAA is currently conducting a nationwide enforcement effort targeting employees who leave on break at the end of their shifts and fail to return.
The March 22 collision and investigation
The NTSB continues to investigate the March 22 collision under investigation ID DCA26MA161. The official cause of the accident remains undetermined. The aircraft involved was an MHI RJ Aviation CRJ-900, and the ground equipment was an Oshkosh Striker 1500 ARFF vehicle.
Official NTSB figures confirm that 76 people were on board the aircraft, including 72 passengers, two flight attendants, and two pilots. The captain and first officer sustained fatal injuries. Thirty-nine individuals were transported to local hospitals, with six reported to have serious injuries.
It remains unverified whether the controllers’ early departure directly influenced the events leading to the collision. Speaking in March 2026, NTSB Chair Jennifer Homendy noted that operating with two controllers in the tower cab during a midnight shift is common practice across the national airspace system, suggesting the facility may have been operating at standard staffing levels at the time of the accident.
Regulatory response to surface safety
Following the LaGuardia accident, the FAA accelerated initiatives to improve surface visibility at airports. On May 13, 2026, the agency announced a $16.5 million investment to equip all airport vehicles with transponders.
These vehicle movement area transponders (VMATs) are designed to provide ATC with better situational awareness of ground equipment operating on runways and taxiways.
AirPro News analysis
We note that the FAA’s decision to pursue termination for timecard fraud rather than operational errors highlights a strict administrative approach to facility management. By focusing on the unauthorized absence, the agency addresses the “early shove” culture directly without preempting the NTSB’s ongoing safety investigation into the collision’s root causes. The distinction between administrative violations and operational fault will likely remain a focal point as NATCA engages with FAA leadership.
Photo Credit: Mike Segar – Reuters
-
Technology & Innovation6 days agoSkyband Systems M100 LRU Validates GNSS Jamming Protection
-
MRO & Manufacturing6 days agoBoeing SPEEA Engineers Reject Contract, Authorize Strike
-
Military Technology6 days agoSaab Unveils A3-001 Supersonic Stealth Drone Concept
-
Business Aviation6 days agoFTAI Aviation Closes $2B Warehouse Financing for 2026 SPV
-
Business Aviation6 days agoSyberJet SJ30-2 Sets Transcontinental Speed Record