SAN DIEGO- A complex operational challenge unfolded at San Diego International Airport (SAN) on February 7, 2025, highlighting the inherent limitations of the facility’s single-runway design.
The airport’s unique configuration, featuring operational areas on both sides of the runway, requires aircraft to frequently cross the active runway, creating intricate traffic patterns.
Photo: By Anna Zvereva from Tallinn, Estonia – JetBlue Airways, N950JT, Airbus A321-231, CC BY-SA 2.0, https://commons.wikimedia.org/w/index.php?curid=41996019Lufthansa Nose to Nose with JetBlue
Severe weather conditions compounded the airport’s logistical constraints that day. Dense fog blanketed the area while shifting wind patterns complicated aircraft movements.
The airport’s single runway, designated as either Runway 9 or Runway 27 depending on the direction of operation, became a focal point of these challenges.
Weather conditions forced a split operational pattern, with arriving aircraft using Runway 9 for eastbound landings. However, departing aircraft faced restrictions as wind conditions exceeded safety parameters for Runway 9 departures.
Simultaneously, poor visibility initially prevented the use of Runway 27 for westbound departures, creating a bottleneck as aircraft awaited improved conditions.
The situation reached a critical point when a Lufthansa (LH) Airbus A350, arriving from Munich, and a JetBlue (B6) Airbus A321, scheduled for departure to Boston, encountered each other nose-to-nose on a taxiway.
This unusual predicament emerged as the Lufthansa aircraft completed its landing on Runway 9 while the JetBlue flight positioned itself for an eventual Runway 27 departure. The resulting gridlock paralyzed a section of the taxiway for approximately one hour, OMAAT reported.
Photo: Clément AlloingGrid Lock
The gridlock between the Lufthansa A350 and JetBlue A321 escalated when spatial miscalculations prevented the aircraft from passing each other on the taxiway.
The situation created significant operational challenges, as modern commercial aircraft lack self-powered reverse capabilities, necessitating the deployment of a tug vehicle for repositioning.
Radio communications during the incident revealed notable interactions between air traffic control and flight crews. The air traffic controller maintained professional composure despite audible frustration in their voice.
A particularly telling moment occurred when American Airlines flight 1049’s pilot commented on the congestion, suggesting that continued aircraft movements would worsen the situation. The controller’s response, following a prolonged pause, acknowledged this obvious observation with barely concealed exasperation.
The incident severely impacted flight schedules. The Lufthansa A350 experienced substantial delays reaching its assigned terminal. The situation proved more detrimental for the JetBlue A321, which federal tarmac delay regulations forced to return to the gate.
This resulted in the Boston-bound flight arriving at 4:12 AM the following morning, nearly eight hours behind its scheduled 8:35 PM arrival.
While some observers criticized the air traffic controller’s decision-making, the circumstances reveal complex operational priorities. The controller’s primary objective focused on clearing the active runway quickly, with reasonable expectations that the taxiway would accommodate both aircraft.
The A350’s wider fuselage likely contributed to the miscalculation, as a narrow-body aircraft might have successfully navigated the space.
Stay tuned with us. Further, follow us on social media for the latest updates.
Join us on Telegram Group for the Latest Aviation Updates. Subsequently, follow us on Google News
Lufthansa Pilot Incapacitated on Miami to Frankfurt Flight
The post Lufthansa A350 Came Nose-to-Nose with JetBlue A321 at San Diego appeared first on Aviation A2Z.
