Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Program Scope topic
No spam. Unsubscribe anytime.
Technical working group narrows Fly Quiet focus; moves ATC-controlled items to work plan
Summary
The SFO Fly Quiet technical working group agreed to prioritize pilot- and airline-controlled elements for the program and to reclassify several ATC-controlled procedures (Oceanic/Woodside, certain sequencing) as work-plan or monitoring items to be pursued separately.
The Fly Quiet Technical Working Group met to decide which airport procedures should be included in SFO's Fly Quiet program and which should be tracked as separate work-plan or Noise Abatement Procedure (NAP) items. Moderator (speaker 1) opened the meeting by saying the group would focus "much more on the fly quiet program" and move items that do not fit into two other buckets into later work-plan discussions.
The group repeatedly returned to a single organizing distinction: whether an element is under pilot/airline control and thus a candidate for Fly Quiet incentives, or under air-traffic-control (ATC) control and therefore better handled as a work-plan or monitoring item. As Moderator summarized, "This is under ATC control, so it's not the fly quiet program, and it is something that could be considered for a future work plan item." Several technical panelists said ATC control made some topics unsuitable for immediate Fly Quiet scoring but worth tracking so staff could present firm recommendations to the full roundtable.
Why it matters: the distinction determines what the program can realistically influence through incentives and recognition. For ATC-determined behaviors the group recommended tracking and staff-level follow-up; for pilot- or airline-controllable elements (FMS loading, certain climb behaviors, airline engagement) the panel favored including those in Fly Quiet 2.0.
Looking ahead: the TWG agreed to a four-week sprint to package elements, scoring and incentives for the Roundtable meeting in August, with an initial beta year (offline scoring and staff review) before a public rollout.
