Regulations & Safety
FAA Safety Alert Highlights Risks of Carry On Bags in Emergencies
FAA warns that retrieving carry on baggage during emergency evacuations delays exits and increases injury risks worldwide.

FAA Issues Critical Safety Alert on Passenger Baggage Retrieval During Emergency Aircraft Evacuations
In September 2025, the Federal Aviation Administration (FAA) released a Safety Alert for Operators (SAFO) addressing a persistent and dangerous risk in commercial aviation: passenger non-compliance with crew instructions regarding carry-on baggage during emergency evacuations. This alert is the result of decades of research, incident analysis, and regulatory debate. It highlights how attempts to retrieve personal belongings during emergencies can transform manageable situations into life-threatening events, undermining the 90-second evacuation standard that underpins commercial aviation safety.
The issue is not isolated to the United States. Globally, incidents and accident investigations have repeatedly shown that passengers’ instinctive desire to grab their belongings during emergencies can delay evacuations, increase injury rates, and sometimes contribute to fatalities. The FAA’s alert is both a response to these realities and a call to action for airlines, regulators, and passengers alike.
This article examines the historical context, recent developments, incident data, expert opinions, and economic impacts related to passenger baggage retrieval during emergency evacuations, providing a comprehensive, fact-based overview of the issue and the industry’s evolving response.
Historical Context and Regulatory Foundation
The regulatory foundation for emergency evacuations in commercial aviation was established in 1967, when the FAA introduced the 90-second evacuation demonstration requirement. This rule, prompted by a fatal 1965 accident in Salt Lake City, mandates that aircraft manufacturers prove their planes can be evacuated in 90 seconds or less, using only half of the available exits and under challenging conditions (e.g., darkened cabins, simulated obstructions).
The 90-second standard is not arbitrary. It is based on survivability studies indicating that, in the event of fire or smoke, conditions inside an aircraft can become unsurvivable in less than two minutes. The regulation has been tested repeatedly in certification trials, such as the Airbus A380’s evacuation of more than 800 volunteers in 77 seconds.
Yet, the assumptions underlying the standard, particularly regarding passenger behavior, have come under scrutiny. The National Transportation Safety Board (NTSB) highlighted this gap in 2000, urging the FAA to address problems associated with carry-on luggage during evacuations. Subsequent research found that emergency evacuations, on average, occurred every 11 days in the 1990s, with injuries and delays often linked to passengers retrieving baggage.
Evacuation Incidents and Recurring Patterns
Despite regulatory advances, the challenge of passenger baggage retrieval persists. The 2016 American Airlines Flight 383 incident at Chicago O’Hare is a case in point. Video footage showed passengers evacuating with bags in hand, even as smoke and fire threatened the aircraft. NTSB investigators found that flight attendants attempted to stop passengers from taking their bags, but ultimately had to prioritize the flow of evacuation over enforcement.
Internationally, the 2019 Aeroflot Superjet 100 fire at Moscow Sheremetyevo Airport was particularly tragic. Investigators concluded that passengers retrieving luggage created an “impassable blockage” in the aisle, possibly preventing others from reaching safety. Of the 78 people onboard, 41 died, many found in the aisle, overcome by smoke.
More recently, a July 2024 American Airlines evacuation in Denver again saw passengers sliding down emergency slides with bags in tow. This incident raised concerns in Congress and among regulators about the adequacy of current procedures and the effectiveness of passenger briefings.
“Any delay caused by retrieval of baggage can significantly affect survival rates in rapidly deteriorating conditions.” —FAA SAFO 25003
Quantitative Analysis: Safety and Economic Impact
The consequences of baggage-related evacuation delays are not only measured in lives, but also in substantial economic costs. In the late 1990s, the direct costs of precautionary evacuations exceeded $11 million annually, with passenger injury claims averaging over $550,000 per incident. Airlines also incurred significant expenses for replacing damaged evacuation equipment, particularly slides, and for lost revenue due to aircraft downtime.
Injury data from the same period showed that about 17% of evacuations resulted in injuries, with the majority requiring medical attention. Most injuries involved the back, neck, legs, and feet, and a notable portion were serious enough to require hospitalization.
Simulation studies have further demonstrated that when even a portion of passengers attempt to evacuate with bags, overall evacuation times increase, sometimes beyond the survivability threshold. The FAA’s December 2024 report to Congress acknowledged that, while not every incident could be conclusively linked to baggage delays, the risk is significant enough to warrant industry-wide action.
Global and Industry Perspectives
The problem is not unique to the United States. Canadian authorities issued a safety alert in 2018, and the European Union’s aviation safety agency has also addressed evacuation standards, though it has not changed certification requirements. The International Air Transport Association (IATA) reported that non-compliance incidents, including those involving baggage, increased in frequency globally in 2022.
International incidents, from Russia to the UK and Canada, have revealed similar patterns of passenger behavior. This consistency points to fundamental psychological drivers, such as normalcy bias and attachment to personal belongings, that transcend cultural and regulatory differences.
The challenge of standardizing procedures and messaging across different regulatory jurisdictions, languages, and cultural contexts remains significant. Universally recognizable symbols and pictograms, as recommended by the FAA, are one approach to bridging these gaps.
Expert Opinions and Industry Recommendations
The FAA’s SAFO 25003 recommends a multi-layered approach: leveraging Safety Management Systems (SMS) to assess and mitigate risks, improving safety briefings with clear and standardized messaging, and conducting ongoing passenger outreach and education campaigns.
Experts, including Captain Chesley Sullenberger, have called for updates to evacuation standards to reflect real-world conditions and passenger demographics. As aircraft cabins become denser and passenger populations age, evacuation procedures and training must adapt accordingly.
Some industry stakeholders have proposed technological solutions, such as locking overhead bins during emergencies. However, these ideas raise concerns about crew access to emergency equipment and the potential for unintended consequences.
“Changes are long overdue, as the current standards do not reflect actual conditions.” —Captain Chesley Sullenberger
Behavioral and Training Considerations
Research into evacuation behavior suggests that psychological factors, such as normalcy bias and emotional attachment to belongings, play a significant role in non-compliance. Passengers may not fully process the urgency of an emergency, or may prioritize items like medication, passports, or electronics.
Crew training is critical. Flight attendants must be prepared to enforce baggage policies while making real-time decisions about when to prioritize evacuation flow over confrontation. Short, clear commands have been shown to be most effective in high-stress situations.
Passenger education remains a challenge. Traditional safety briefings are often ignored or forgotten, prompting calls for more engaging and memorable methods, such as visual displays in airports and messaging that appeals to collective responsibility (“Help everyone get out safely—leave your bags.”).
Conclusion
The FAA’s recent Safety Alert underscores the urgency of addressing passenger baggage retrieval during emergency evacuations. The evidence from decades of incidents, research, and regulatory review is clear: even brief delays caused by retrieving carry-on items can have catastrophic consequences in time-critical situations.
Moving forward, the aviation industry will need to implement a combination of regulatory, technological, procedural, and educational strategies to change passenger behavior and ensure compliance. International coordination and standardization, as well as ongoing research into human factors, will be essential for improving evacuation outcomes and maintaining the high safety standards that have defined commercial aviation.
FAQ
Why is it dangerous to take bags during an emergency evacuation?
Retrieving bags can block aisles and exits, delay evacuation times, and increase the risk of injury or death, especially in situations involving fire or smoke.
What does the 90-second evacuation rule mean?
Aircraft must be designed and certified to allow all passengers and crew to evacuate within 90 seconds, using only half of the available exits, under simulated emergency conditions.
What are airlines doing to address this problem?
Airlines are updating safety briefings, using clear and standardized messaging, leveraging Safety Management Systems, and launching education campaigns to encourage passengers to leave belongings behind during emergencies.
Have any technological solutions been proposed?
Some have suggested locking overhead bins during emergencies, but this raises concerns about access to emergency equipment and unintended safety risks.
Is this problem unique to the United States?
No. Incidents and regulatory responses have occurred worldwide, and similar passenger behaviors have been observed in many countries.
Sources
Photo Credit: Avgeek
Regulations & Safety
FAA Investigates Southwest Airlines Near Miss at Nashville
Two Southwest Boeing 737s came within 500 vertical feet near Nashville on April 18, 2026, after an ATC error during a go-around.

This is a developing story. Information may change as official details are released.
This article summarizes reporting by CNN, Fox News, and The Washington Post.
Two Southwest Airlines (WN) Boeing 737 aircraft passed within 500 vertical feet of each other near Nashville International Airport (BNA) on April 18, 2026, after air traffic control instructions placed an aborting arrival into the path of a departing flight.
The incident, which occurred at approximately 5:30 p.m. local time, prompted both flight crews to execute evasive maneuvers following onboard Traffic Collision Avoidance System (TCAS) alerts. The Federal Aviation Administration (FAA) has launched an investigation into the airspace separation loss, which highlights ongoing scrutiny over air traffic control protocols and collision avoidance effectiveness.
Sequence of events and evasive maneuvers
According to statements provided to CNN and Fox News, Southwest Airlines Flight 507 was arriving from Myrtle Beach, South Carolina, when the flight crew initiated a precautionary go-around due to gusty wind conditions at BNA. During this maneuver, air traffic controllers instructed the crew to turn right.
The FAA confirmed in a statement that these instructions placed Flight 507 directly into the departure path of Southwest Airlines Flight 1152, which was taking off from a parallel runway bound for Knoxville, Tennessee. As the aircraft converged, TCAS resolution advisories activated in both cockpits. Flight tracking data from Flightradar24 indicates the two Boeing 737s came within 500 vertical feet of one another before the crews successfully altered their trajectories.
Both aircraft continued to safe landings without further incident. Flight 507 completed its arrival into Nashville on a subsequent approach, while Flight 1152 proceeded to its destination in Knoxville.
Regulatory investigation and safety context
The FAA is currently investigating the circumstances that led to the loss of separation. Southwest Airlines issued a statement emphasizing that the pilots of Flight 507 were complying with air traffic control directives when the conflict occurred, and that the crews responded professionally to the onboard traffic alerts to maintain safety.
The Nashville incident occurs against a backdrop of heightened national attention on mid-air collision risks. The Washington Post notes that aviation safety systems have faced intense public and regulatory scrutiny following a January 29, 2025, collision between an American Airlines aircraft and a military helicopter near Washington, D.C., which resulted in 67 fatalities. While the circumstances of the two events differ, the 2025 accident has amplified focus on the reliability of TCAS and air traffic control coordination in congested airspace.
AirPro News analysis
The activation of TCAS resolution advisories in this incident demonstrates the critical role of automated safety nets when procedural separation fails. While the FAA investigation will ultimately determine the root cause of the controller instructions, the event underscores the vulnerability of the go-around phase. Go-arounds are dynamic maneuvers that rapidly alter an aircraft’s energy state and expected flight path. These maneuvers require immediate and precise coordination between the flight deck and air traffic control, particularly when parallel runway operations are active.
Sources: CNN (via KESQ)
Photo Credit: Flightradar24 – Google Earth via CNN Newsource
Regulations & Safety
FAA Investigates Southwest Airlines Ground Collision at PVD
Two Southwest Boeing 737s collided during pushback at Rhode Island T.F. Green Airport on June 11, 2026. FAA investigation opened.

This is a developing story. Information may change as official details are released.
This article summarizes reporting by WPRI, NBC 10, Daily Voice, and CBS News Baltimore.
The Federal Aviation Administration (FAA) has opened an investigation after two Southwest Airlines Boeing 737 aircraft collided during pushback at Rhode Island T.F. Green International Airport (PVD) late on June 11, 2026.
The ground collision resulted in no reported injuries but forced the cancellation of both flights and the grounding of the involved aircraft for mandatory safety inspections. According to reporting by the Daily Voice and NBC 10, the incident highlights ongoing operational challenges on airport ramps, occurring just weeks after a similar event involving the same carrier at another East Coast facility.
Details of the ground collision
At approximately 10:45 p.m. local time, Southwest Airlines Flight 3515, bound for Ronald Reagan Washington National Airport (DCA), was pushing back from its gate. During the maneuver, the aircraft’s wing made contact with the tail of Southwest Airlines Flight 3409, which was scheduled to depart for Chicago Midway International Airport (MDW).
Both aircraft returned to their respective gates following the contact, allowing passengers to deplane normally. Southwest Airlines confirmed that no injuries occurred among passengers or crew members. The carrier subsequently canceled both flights and reaccommodated the affected travelers.
“Southwest Airlines is aware of an incident involving two of our aircraft at Rhode Island T. F. Green International Airport. We are investigating further and will be thoroughly inspecting the two aircraft,”
the airline stated in remarks provided to local media, adding that safety remains its highest priority.
Local media outlets, including NBC 10, reported passenger accounts suggesting that Flight 3515 continued to move briefly after the initial impact. These accounts claim passengers verbally alerted the flight crew to the collision. Neither Southwest Airlines nor the FAA has officially verified these specific passenger narratives, and the official sequence of events remains under investigation.
Regulatory response and recent precedent
The FAA confirmed on June 12, 2026, that it is investigating the circumstances surrounding the collision. Ground operations during pushback rely heavily on coordination between flight crews and ground personnel, particularly in ramp areas where air traffic controllers do not maintain direct communication with the aircraft.
This event follows a comparable occurrence on May 4, 2026, at Baltimore/Washington International Thurgood Marshall Airport (BWI). In that instance, two Southwest Airlines Boeing 737s clipped wings during pushback operations. The FAA investigated the BWI incident, noting the specific communication dynamics between ground crews and the flight deck in non-controlled ramp sectors.
AirPro News analysis
We note that while ground collisions during pushback rarely pose a severe threat to passenger safety, they represent a significant operational and financial burden for carriers. Ramp incidents require immediate grounding of the involved airframes, triggering mandatory structural inspections and potential repairs. The recurrence of pushback-related contact within a single airline’s network over a short period may prompt internal reviews of ground handling procedures, wingwalker positioning, and ramp communication protocols. Until the FAA concludes its investigation, the specific cause of the PVD collision remains undetermined.
Sources: WPRI
Photo Credit: Zachary Reis
Regulations & Safety
Turkish Airlines 777-300ER Wing Strike at Antalya Airport
A Turkish Airlines Boeing 777-300ER struck a radar antenna pole taxiing at Antalya Airport, prompting evacuation and a formal investigation.

This is a developing story. Information may change as official details are released.
This article summarizes reporting by Hürriyet.
A Turkish Airlines (TK) Boeing 777-300ER sustained damage and prompted a passenger evacuation after its right wing struck a ground radar antenna pole while taxiing at Antalya Airport (AYT) on June 11, 2026.
The incident, which occurred at approximately 20:00 local time following Flight TK2430 from Istanbul, resulted in minor injuries among the passengers. According to official statements reported by Hürriyet, the widebody aircraft was maneuvering toward its parking position on Apron-1 when the collision occurred, leading to an immediate evacuation on the tarmac.
Conflicting passenger and injury reports
Following the evacuation, official sources provided conflicting figures regarding the number of passengers on board and the extent of injuries. In a public statement, Turkish Airlines Senior Vice President of Communications Yahya Üstün confirmed the evacuation, stating that 267 passengers were safely removed from the aircraft. The airline reported that one passenger sustained minor injuries and was in good health.
Conversely, the Turkey Ministry of Transport released a separate statement indicating a higher passenger count. The ministry reported that the aircraft was carrying 284 adult passengers and four infants. Furthermore, the government authority stated that three passengers suffered minor injuries during the event. Both entities confirmed that the aircraft, registered as TC-LKD, was towed to a parking area after the necessary safety checks and passenger removal were completed.
Investigation into the ground collision
A technical investigation into the ground collision has been initiated by the Turkey Ministry of Transport and the General Directorate of State Airports Authority (DHMI). The official cause of the incident remains under investigation.
While the airline noted the aircraft was approaching its parking position, preliminary remarks from the Ministry of Transport suggested the Boeing 777-300ER made contact with the radar pole after entering an incorrect taxiway line. Final determinations regarding the aircraft routing, ground control instructions, and the sequence of events will be established by the investigating authorities.
AirPro News analysis
Ground collisions involving widebody aircraft like the Boeing 777-300ER often highlight the tight tolerances required when maneuvering large airframes around airport infrastructure. While we await the official investigation findings, safety reviews following such events typically examine airport taxiway markings, lighting, and the clarity of ground control communications. The discrepancy in passenger manifests between the operator and the regulator is a notable detail, though initial reporting conflicts frequently occur in the immediate aftermath of an evacuation before final reconciliations are completed.
Sources: X.com
Photo Credit: X
-
Technology & Innovation4 days agoAirbus Vision Landing Application Enables AI Autoland
-
Defense & Military2 days agoBoeing Withdraws T-7A Red Hawk from Navy UJTS Competition
-
Route Development7 days agoDubai International Airport to Close in 2035 for Al Maktoum
-
Commercial Aviation7 days agoIATA 2026 Airline Profit Forecast Cut in Half by Fuel Costs
-
Training & Certification5 days agoAirbus Overhauls Pilot Training With VR and CBTA Standards
