Southwest planes clip at BWI airport

Two Southwest jets bumping wings at the gate sounds minor compared with a runway collision or a crash. But that’s exactly why people in aviation pay attention to it. These are the kinds of events that expose where the system gets thin — not just in the air, but on the ground, in the handoffs, and in the parts of the airport where pilots are mostly on their own. At Baltimore/Washington International this week, two Southwest planes clipped each other during pushback. The FAA opened an investigation, and the details matter. (cbsnews.com) ### What actually happened at BWI? Southwest flights 1048 and 562 clipped wings while pushing back from their gates at BWI around 10:30 p.m. local time on Monday, May 4. One flight was headed to Connecticut and the other to Houston. Nobody was injured, but both aircraft were taken out of service and passengers had to switch planes. (cbsnews.com)during pushback” the key detail? Because pushback is one of those awkward airport phases where the airplane is moving, space is tight, and the margin for error is tiny. The aircraft is being backed away from the gate and lined up to taxi, often with help from ramp crews rather than tower instructions. If two jets are moving in close q(cbsnews.com)s this happened in an area where controllers do not communicate with flight crews. (faa.gov) ### So was air traffic control involved? Not in the usual way people mean when they think about ATC. The important distinction is between movement areas controlled by the tower and ramp areas where airlines, tug operators, and flight crews handle the choreography more directly. That doesn’t make the area unregulated — it just means the safety net is different. At BWI, the pi(faa.gov)hit and asked to taxi straight ahead back to Alpha 7. (cbsnews.com) ### Why does a wingtip strike matter if nobody got hurt? Because modern airline safety is built on catching weak signals early. A wingtip strike on the ramp usually lands in the “minor damage” bucket, but it still means two large aircraft ended up occupying the same space. That can point to problems with gate spacing, ramp procedures, crew coordi(cbsnews.com) bigger incidents start. (cbsnews.com) ### Is this connected to the JFK near-miss story? Only loosely. The JFK event was a different kind of problem — an aircraft on final approach and another crossing to a parallel runway. The FAA said required separation was maintained there after controllers gave traffic advisories and both pilots reported the other aircraft in sight. So the two ev(cbsnews.com) producing moments that look too close for comfort. (faa.gov) ### Where does staffing fit into this? Staffing is the bigger backdrop, even if it did not directly cause the BWI ramp strike. FAA controller staffing is still below where it was a decade ago. GAO said the agency had 13,164 controllers at the end of fiscal 2025 — about 6% fewer than in 2015 — even though flight activity had risen about 10% from 2015 to 2024. A separate DOT w(faa.gov)nderstaffed as of April 2025. (files.gao.gov) ### Why does that matter before summer? Because summer is when the system gets less forgiving. More flights, more weather disruptions, more congestion, and more pressure on every handoff. A ramp incident at BWI does not prove a nationwide safety breakdown. But it does show how easily a routine operation can go sideways when the choreography gets tight. ### Bottom line? Th(files.gao.gov)uched wings in a part of the airport where crews don’t have direct controller guidance, and that is exactly the kind of small failure investigators study hard before peak travel season. (faa.gov)