Regulations & Safety
Alaska Airlines Wingtip Collision at Sea-Tac Prompts FAA Safety Review
Two Alaska Airlines aircraft clipped wings at Seattle-Tacoma Airport, sparking an FAA investigation into ground safety protocols and operational challenges.

Alaska Airlines Wingtip Collision at Seattle-Tacoma Airport: A Wake-Up Call for Ground Safety
On May 17, 2025, two Alaska Airlines aircraft clipped wings during pushback at Seattle-Tacoma International Airport (Sea-Tac), prompting an official investigation by the Federal Aviation Administration (FAA). While no injuries were reported, the incident has drawn attention to the complexities and risks associated with ground operations at busy airports. With increasing air traffic and limited gate space, the margin for error in apron areas is narrowing.
This event is more than an isolated occurrence; it reflects systemic challenges in ground coordination and safety protocols. As airports grow busier and fleets expand, ensuring the safety of aircraft movements on the ground becomes as critical as managing them in the air. The FAA’s investigation into the Sea-Tac incident may uncover broader implications for how ground operations are managed nationwide.
In this article, we explore the details of the Alaska Airlines incident, examine historical data on similar events, and evaluate the broader implications for airport safety and airline operations.
Understanding the Incident at Sea-Tac
What Happened on May 17, 2025?
At approximately 12:15 p.m. local time, Alaska Airlines Flights 1190 and 1094 were being pushed back from adjacent gates at Sea-Tac when their winglets made contact. Both aircraft involved were Boeing 737-900ER models. According to Alaska Airlines, the ground-service tugs were maneuvering the planes when the contact occurred. No passengers or crew members were injured, and all passengers were safely deplaned and rebooked on other flights.
Alaska Airlines issued a public apology, acknowledging the inconvenience caused to passengers. The FAA confirmed that it had launched an investigation into the incident. Importantly, the FAA clarified that air traffic control is not responsible for aircraft movements in the gate area, placing the focus squarely on ground operations and airline procedures.
While the damage appeared to be limited to the winglets, even minor structural contact can lead to significant delays, aircraft inspections, and potential financial costs. The incident underscores the delicate choreography required to manage aircraft on the ground, especially at high-traffic airports.
“We sincerely apologize to our guests for the delay and inconvenience,” Alaska Airlines spokesperson
Operational Disruptions and Immediate Response
Following the collision, both aircraft were taken out of service for inspection. Passengers were transferred to alternate flights, and operations resumed later the same day. However, the incident caused delays and logistical challenges, particularly in a tightly scheduled airport environment like Sea-Tac.
Sea-Tac is one of the busiest airports on the West Coast, handling over 50 million passengers annually. With limited gate availability and high aircraft turnover, even a minor incident can ripple through the schedule, affecting not only Alaska Airlines but also other carriers operating in adjacent gates.
Alaska Airlines, which operates a major hub at Sea-Tac, has not disclosed the estimated repair costs or the timeline for returning the affected aircraft to service. However, the airline’s prompt response and coordination with the FAA suggest a proactive approach to incident management.
Broader Context: Ground Safety in Aviation
Historical Trends in Ground Collisions
While mid-air collisions are rare due to advanced avionics and strict regulations, ground collisions remain a persistent issue. According to FAA data, there are dozens of ground incidents reported annually, ranging from minor scrapes to more serious collisions involving injuries or substantial aircraft damage.
Most ground incidents occur during pushback, taxiing, or gate arrival—phases of flight where multiple ground personnel and vehicles are involved. The complexity of these operations, combined with tight schedules and congested ramp areas, increases the likelihood of human error or miscommunication.
Notable past incidents include the 2019 collision between two American Airlines jets at Chicago O’Hare and the 2021 wingtip contact between Delta and Southwest planes at Atlanta. These events, like the Sea-Tac incident, often lead to FAA investigations and internal airline reviews.
Challenges in Ground Operations
Ground operations involve a network of personnel, including tug drivers, ground control, ramp agents, and airline dispatchers. Coordination among these roles is essential but often hindered by outdated communication systems and inconsistent training standards across airports.
Additionally, the physical layout of airports can contribute to ground safety risks. Sea-Tac, for example, has limited space between gates, which increases the risk of incidents during pushback. Weather conditions, visibility, and human fatigue also play a role in operational safety.
Experts have long called for standardized training, better equipment, and real-time monitoring systems to improve situational awareness. Some airports have begun implementing advanced ground radar and automated tug systems, but these technologies are not yet widespread.
“The apron area is one of the most complex and dynamic parts of an airport. It’s where most near-misses and minor collisions occur,” Aviation Safety Analyst, FlightGlobal
Regulatory Oversight and Industry Response
The FAA’s role is primarily regulatory, focusing on setting safety standards and investigating incidents. However, the responsibility for implementing those standards lies with airlines and airport authorities. In the wake of the Sea-Tac incident, the FAA may issue new guidance or recommendations for ground operations.
Airlines like Alaska are also revisiting their internal protocols. This includes reviewing tug operator training, gate assignment procedures, and communication protocols between ground crews and flight decks. Many carriers have adopted Safety Management Systems (SMS) to proactively identify and mitigate risks.
Industry groups such as the International Air Transport Association (IATA) have also emphasized the need for global standards in ground handling. Their Ground Operations Manual outlines best practices, but adherence varies by region and carrier.
Conclusion
The Alaska Airlines wingtip collision at Sea-Tac serves as a reminder of the complexities and risks inherent in ground operations. While the incident did not result in injuries, it highlights vulnerabilities in current airport procedures and the need for enhanced safety measures. With air travel rebounding post-pandemic, the pressure on airport infrastructure and personnel is only increasing.
Looking ahead, airlines, regulators, and airport authorities must collaborate to improve ground safety through better training, technology adoption, and standardized procedures. As the FAA continues its investigation, the findings may shape future policy and operational norms across the aviation industry.
FAQ
What caused the Alaska Airlines planes to clip wings?
The incident occurred during pushback from adjacent gates when the winglets of two Alaska Airlines aircraft made contact. Ground-service tugs were maneuvering the planes at the time.
Were there any injuries reported?
No injuries were reported. All passengers were safely deplaned and rebooked on other flights.
Who is responsible for aircraft movements at the gate?
The FAA clarified that air traffic control is not responsible for aircraft movements in the gate area. This responsibility typically falls on the airline and ground service personnel.
What actions are being taken?
The FAA has launched an investigation into the incident. Alaska Airlines is also reviewing internal procedures and training protocols.
How common are ground collisions at airports?
Ground collisions are relatively uncommon but not rare. According to FAA data, dozens of such incidents occur annually in the U.S., often during taxiing or pushback operations.
Sources: Fox Business, FAA, FlightGlobal, IATA
Photo Credit: FoxBusiness
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
Regulations & Safety
NTSB Final Report: Southwest Flight 4273 Turbulence Encounter
NTSB cites ATC communication delays and sector overload in Southwest Airlines turbulence event over Gulf of Mexico.

This is original reporting and analysis by AirPro News.
The National Transportation Safety Board (NTSB) has released its final report on a severe turbulence encounter involving a Southwest Airlines Boeing 737-700, detailing how rapidly developing convective weather and air traffic control communication delays factored into an event that seriously injured two people.
The April 3, 2024, incident aboard Southwest Airlines Flight 4273 over the Gulf of Mexico highlights the operational risks when severe weather systems intersect with technical limitations at air traffic control facilities. According to the NTSB investigation, the aircraft was navigating complex weather en route from New Orleans to Orlando when the encounter occurred, resulting in serious injuries to one flight attendant and one passenger, alongside minor injuries to a second flight attendant.
Weather conditions and the turbulence encounter
Flight 4273, operated by a Boeing 737-700 (registration N567WN) with 140 passengers and five crew members on board, was traveling from Louis Armstrong New Orleans International Airport (MSY) to Orlando International Airport (MCO).
At 11:55 UTC, a Convective Significant Meteorological Information (SIGMET) advisory was issued for the region, warning of cloud tops exceeding 45,000 feet.
At approximately 08:20 Eastern Daylight Time, the aircraft encountered severe turbulence over the Gulf of Mexico. The NTSB confirmed the aircraft itself sustained no damage during the event and the flight crew was able to continue the flight.
Air traffic control workload and technical limitations
The NTSB report outlines compounding factors at the Jacksonville Air Route Traffic Control Center (JAX ARTCC) that affected the flight routing through the weather system.
During the incident, the specific JAX ARTCC sector was managing a traffic volume that exceeded its target capacity of 20 aircraft.
This high workload was exacerbated by a technical limitation involving the facility communication infrastructure. The primary VHF antenna at JAX ARTCC had been rendered inoperative following a fire in October 2023. As a result, controllers were utilizing a temporary satellite relay connection to communicate with aircraft in the sector.
The NTSB determined this satellite relay introduced a 600-millisecond round-trip transmission delay, complicating timely communication between controllers and flight crews navigating the dynamic weather environment.
AirPro News analysis
We note that the findings in this final report underscore a critical vulnerability in the National Airspace System. When primary communication infrastructure fails, the fallback systems must be robust enough to handle high-stress, time-critical scenarios like severe convective weather deviation. A 600-millisecond delay might seem negligible in routine operations, but in a saturated sector where controllers are issuing rapid heading changes to keep aircraft clear of building storm cells, that latency degrades situational awareness and increases the risk of weather encounters. The NTSB documentation of this technical shortfall will likely prompt further scrutiny of contingency communication systems at major en route centers.
Photo Credit: NTSB
-
Technology & Innovation2 days agoAirbus Vision Landing Application Enables AI Autoland
-
Route Development5 days agoDubai International Airport to Close in 2035 for Al Maktoum
-
Commercial Aviation5 days agoIATA 2026 Airline Profit Forecast Cut in Half by Fuel Costs
-
Defense & Military6 days agoWhisper Aero Launches Collaborative Logistics Aircraft for US Military
-
MRO & Manufacturing5 days agoGE Aerospace Q1 2026: LEAP Deliveries Up 60%, $170B Backlog
