Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Night Procedures topic
No spam. Unsubscribe anytime.
Working group weighs night‑hush and 050 bay routing; 050 is feasible but traffic‑dependent and slow to mandate
Summary
Panelists reviewed the night‑hush program (1–5 a.m.) and the 050 heading, noting that 050 can route traffic over the center of the bay but is traffic‑dependent and airlines resist longer routings; the group discussed incentivizing pilot requests and asking ATC for compliance checks.
At the June 11 technical working group meeting, experts and community representatives discussed night‑time routing options — the existing night‑hush agreement and the 050 heading that can route departures over the middle of the bay — and whether the fly‑quiet program can incentivize their broader adoption.
Marie Joe Fremont of the Aviation Impacted Communities Alliance said the air traffic side could do more: "I think there is room for improvement on the air traffic side on this one," she told the group, pointing to occasions when controllers do not prioritize allowed 050 headings even when traffic conditions make them feasible.
Why it matters: the night‑hush routing (the 'true night' path) keeps aircraft farther offshore and reduces community noise but adds distance and fuel burn; airlines generally oppose the longer path. The 050 heading is allowed and can cut across the bay but is traffic‑dependent — controllers will deny it when arrivals or conflicts make it unsafe — and some controllers do not always work to secure it for pilots even when it could be used.
Panelists discussed possible near‑term measures: encouraging pilots to request 050, asking ATC (the TCON) to treat the 050 more proactively when conditions allow, and requesting targeted compliance reporting so the airport can measure instances when 050 was possible but not used. Dan noted practical limits: "the FAA doesn't have any way of tracking what a pilot requests if they're not given it," so the group may need to rely on controller logs and targeted checks to measure pilot requests and denials.
The working group debated whether to include night‑hush as a scored metric in the fly‑quiet program. Some members urged tracking and public reporting but cautioned that incentives tied to night‑hush would be difficult to administer because airlines resist long routings and the procedure is viable only under light traffic conditions.
Next steps: members recommended adding 050 usage and center‑line compliance to follow‑up questions for ATC and asked staff to investigate whether controller logs or targeted compliance checks could capture pilot requests and denials.
