A Lufthansa A350's frustrating Oakland diversion
A delayed Lufthansa A350 flight into San Francisco was forced to divert to Oakland after the crew, bound by company rules, refused a night-time visual approach and insisted on an ILS (instrument) landing that local controllers could not immediately accommodate in heavy parallel-approach traffic. Commenters examine how fuel-planning rules and diversion procedures work, whether the pilots or air traffic control mishandled communication and expectations, and how much discretion controllers should have when one aircraft’s needs conflict with a tightly packed arrival stream. The incident becomes a case study in the trade-offs between safety margins and runway throughput, differences between U.S. and European operating norms, and broader concerns over FAA policy, controller staffing, and near-miss trends in U.S. airspace.
Context of the incident
- Lufthansa A350 to SFO arrived late into an extremely busy nighttime arrival bank.
- SFO was running simultaneous visual approaches on closely spaced parallels to maximize throughput.
- Lufthansa’s company SOP prohibits night visual approaches with visual separation; they requested an ILS approach instead.
- NorCal Approach could not easily create an ILS “gap” without disrupting a pre‑sequenced chain of 20–30 aircraft, so Lufthansa was held, then diverted to Oakland.
Fuel, holding, and diversion
- Several pilots in the thread explain fuel planning: enough to fly to destination, then to an alternate, plus “final reserve” (30–45 min).
- Consensus among pilots: you divert when approaching “minimum fuel”; you only declare a fuel emergency when you expect to land with less than reserve. Declaring early just to jump the queue is career‑risking.
- Many argue the Lufthansa crew were not yet close to true fuel emergency; they had a valid alternate (OAK) minutes away.
- Others counter that repeated 10‑minute “estimates” from ATC that slipped by 30+ minutes erode safety margins and decision‑making.
Visual vs ILS approaches & SFO specifics
- Many note US practice: visual approaches are heavily used at busy hubs; Europe relies more on instrument approaches.
- At SFO, visual parallel approaches allow roughly double the arrival rate vs ILS, due to different separation rules and pilot‑maintained separation.
- Lufthansa and some other non‑US carriers have policies limiting night visuals, partly influenced by incidents at SFO (Asiana 214, Air Canada 759) and FAA advisories to foreign carriers.
- Some see Lufthansa’s policy as prudent extra safety; others call it over‑cautious and misaligned with SFO’s “normal” operations.
ATC vs airline responsibility and professionalism
- One camp: ATC did what they could in saturated airspace; they warned of “extended delays,” offered holding or diversion, and correctly refused to be pressured by a hinted fuel emergency.
- Another camp: ATC mismanaged expectations (repeated optimistic ETAs, long periods with no update), then responded curtly (“this conversation is over”), which is viewed as unprofessional and potentially safety‑eroding.
Broader systemic issues
- Multiple comments tie this to wider FAA/ATC problems: controller shortages, overwork, outdated procedures, and SFO’s constrained, “troublesome” runway layout.
- Some argue FAA leadership and Congress have underfunded and over‑constrained ATC; others point to hiring rules, union issues, and safety regulations “written in blood.”
- Overall sense: the outcome was safe but exposed brittle interfaces between company SOPs, local ATC practices, and an overstressed US air traffic system.