A reported close approach between FedEx Flight 710 (FDX710) and British Airways Flight 49 (BAW49) near Seattle-Tacoma International Airport on May 12, 2026, at approximately 01:14 UTC — roughly 6:14 PM Pacific Daylight Time on May 11 — has attracted attention in aviation communities following apparent flight-tracking data or video circulating on social media. The pairing involves two distinctly different operations: FDX710 is a FedEx Express cargo service, almost certainly operating a wide-body freighter such as a 767-300F or MD-11F, while BAW49 is a British Airways scheduled transatlantic passenger service, typically operated by a 787-9 or 777-200ER between London Heathrow and Seattle-Tacoma. The convergence of a major cargo carrier and a flag-carrier long-haul jet in the terminal environment or arrival/departure corridors near a large hub warrants scrutiny, though the full details — including whether any TCAS resolution advisory (RA) was triggered or ATC separation was formally lost — remain unconfirmed from available sourcing.
Seattle-Tacoma International (KSEA) presents a complex traffic environment, particularly in the early evening departure push and during mixed cargo and passenger arrival flows. The airport operates two closely spaced parallel runways (16L/34R and 16C/34C) with a third runway (16R/34L) on the east side, and its approach corridors frequently overlap with traffic transitioning through the Seattle TRACON and Oakland ARTCC handoffs for transoceanic departures and arrivals. British Airways 49 inbound from Heathrow would typically be handed off to Seattle Approach from high altitude over the Pacific Northwest, while a FedEx cargo departure or arrival could be operating on a tighter, lower-altitude profile within the terminal area. Any reduction in standard IFR separation — 3 nautical miles laterally or 1,000 feet vertically in terminal airspace — constitutes a reportable event requiring investigation by the FAA's Air Traffic Safety Action Program (ATSAP) and potentially the Aviation Safety Hotline.
For working pilots, this type of incident underscores the continued relevance of TCAS II as a last-resort safety net and the importance of crew adherence to RA commands without delay or deviation. Under current FAA and ICAO standards, flight crews are required to respond immediately to RAs and must not maneuver contrary to an RA even if an ATC instruction conflicts. In mixed cargo and passenger environments near Class B airports, situational awareness demands are compounded by differing performance profiles — a heavy freighter on a shallow climb and a fully loaded widebody on a long-haul descent occupy similar altitude bands and speeds in ways that can challenge ATC sequencing, particularly during late-afternoon traffic compression. The precise circumstances of this reported event, including whether it was a genuine loss of separation or a visually dramatic but legally separated encounter rendered alarming by tracking app perspective, will be critical to any formal assessment.
The incident, if confirmed as a separation event, fits a pattern of increased scrutiny on near-miss reports that has intensified across U.S. aviation since the January 2023 Austin (KAUS) runway incursion involving a FedEx 767 and a Southwest 737, and the February 2023 near-collision at JFK involving a Delta A321 and an American 777. Congress, the FAA, and the NTSB have all elevated attention to proximity events involving major cargo carriers and scheduled passenger airlines, particularly at hub airports. Operators and chief pilots monitoring this event should note that social media and flight-tracking platforms now routinely surface such encounters before formal ASRS or ATSAP reports are filed, creating a need for proactive internal review and crew debrief processes when unusual proximity is indicated by ADS-B data — regardless of whether a formal investigation follows.