Summary Reagan National Airport Community Working Group Regular Meeting (13) May 25, 2017

Size: px

Start display at page:

Download "Summary Reagan National Airport Community Working Group Regular Meeting (13) May 25, 2017"

Roger Norton
6 years ago
Views:

1 Summary Reagan National Airport Community Working Group Regular Meeting (13) May 25, 2017 Date: May 25, 2017 Time: 6:00 P.M. 8:00 P.M. Location: Metropolitan Washington Airports Authority (MWAA) Terminal A Historic Lobby Conference Center Agenda: February 16, 2017 Meeting Summary, FAA Update, Working Group Discussion Working Group Members Present: Dick DeiTos Metropolitan Washington Airlines Committee Marcio Duffles District of Columbia - Ward 3 Ken Hartman Montgomery County Paul Janes Montgomery County - Inside Beltway John Mitchell Prince George s County - Accokeek Ron Montague Arlington County Mike Rioux Fairfax County Mount Vernon Susan Shipp Montgomery County - Outside Beltway Brian Stout Arlington County Steve Thayer City of Alexandria Wayne Tonkins, Sr. Prince George s County - Ft. Washington Alternates: Don Crockett District of Columbia - Ward 2 William Liebman Montgomery County Don Minnis Fairfax County - Mount Vernon William Noonan Montgomery County - Inside Beltway Richard Sternberg Montgomery County - Outside Beltway Agenda Item 1 Welcome and Updates: Margaret McKeough, MWAA Chief Operating Officer Welcomed Working Group and updated committee on membership changes: o Arlington County: Ron Montague will replace Dean Arkema o District of Columbia - Ward 2: Rick Murphy will replace Bob vom Eigen MWAA will contact information for current Working Group Voting Members 1A) April 27, 2017, Meeting Summary: o Discussion: John Mitchell: Requested edit on Page 3, Jurisdiction Updates: Accokeek is across the Potomac River from Mount Vernon; the community includes the Piscataway National Park, a public/private partnership that includes the first federal scenic easement over private lands, intended to protect the sph/kg Pg 1/12

2 viewshed from Mount Vernon so that Mount Vernon visitors may enjoy a view similar to what George Washington would have experienced. o April 27, 2017 Meeting Summary Approved with noted edit. 1B) Updates: o Complaint webform reconfiguration should be available by next Working Group meeting: Selection of Multiple Disturbance Types o Raw Complaint Data: Complaint data will be aggregated by zip code on a quarterly basis, i.e. no personal information will be released. o Cell Phone App: Phone App is in development by MWAA s Noise Information Office vendor, Bruel & Kjaer. It s expected to be available within a couple of months. Agenda Item 2 General Working Group Discussion: 2A) Jurisdiction Updates (City of Alexandria, Arlington, District of Columbia, Fairfax, Montgomery, Prince George s): o Arlington County: Ron Montague: New to Working Group; currently a Rosslyn, Virginia, resident (21 years), Retired FAA employee with air traffic control experience (34 years), and previous Maryland resident (Bethesda-Montgomery County, River Bend- Prince George s County). o Working Group members who deferred to Fairfax County member: Steve Thayer, Marcio Duffles, Ken Hartman, Wayne Tonkins o Mike Rioux: Fairfax County Update: South Flow Alliance community members and elected officials met on May 10 th to discuss the significant impact of South Flow flight path changes on Virginia neighborhoods south of DCA from Alexandria to Mt. Vernon. South Flow Alliance is focused on political activity to get action implemented. Working Group members presented a proposal intended to improve the group s effectiveness and progress. Current Working Group meeting process is informative but meetings are too infrequent and not producing desired results. Working Group members feel there s an opportunity to change the process and restructure similar to other airport Working Groups, i.e. Boston, San Francisco, Chicago and Baltimore. o Ken Hartman: In December 2016, the Working Group introduced a 6-Point Plan that has not been implemented. Working Group needs to package recommendations into a coherent format that is useful to the FAA. sph/kg Pg 2/12

Working Group also needs to improve its technical interface with the FAA by exploring/preparing concepts and vetting options, i.e.: Boston Logan Working Group is chaired by a community member and technically supported by MIT.

San Francisco Working Group has a technical panel that works with FAA.

deliverables for the full Working Group s consideration. 1. Noise Assessment/Footprints 2. Procedures 3. Fly Quiet Program 4.

Dulles Matters Rules of engagement need to be established to ensure appropriate subcommittee composition and protocols.

3 Working Group also needs to improve its technical interface with the FAA by exploring/preparing concepts and vetting options, i.e.: Boston Logan Working Group is chaired by a community member and technically supported by MIT. Baltimore Working Group is also chaired by a community member and technically supported by a consultant. San Francisco Working Group has a technical panel that works with FAA. o Mike Rioux: Working Group members recommend using their 6-Point Plan to categorize issues and create 6 subcommittees to develop deliverables for the full Working Group s consideration. 1. Noise Assessment/Footprints 2. Procedures 3. Fly Quiet Program 4. Permanent Advisory Group 5. Residential Sound Insulation Program RSIP 6. Dulles Matters Rules of engagement need to be established to ensure appropriate subcommittee composition and protocols. External technical expertise with funding needed for Noise and Procedure subcommittees. o Working Group Presentation - Community Report Mike Rioux, Fairfax County Mt. Vernon sph/kg Pg 3/12

4 sph/kg Pg 4/12

Noise Subcommittee 1: Subcommittee would require

Concern is the noise footprint under flight tracks,

Noise impact (grid map, footprint) is needed prior to

o Example: After FAA implemented NextGen procedure

SIDs for westbound turns, consequently, noise impacts

5 Noise Subcommittee 1: Subcommittee would require external, technical support. Concern is the noise footprint under flight tracks, not the DNL contours. Noise impact (grid map, footprint) is needed prior to FAA implementing procedure changes. o Example: After FAA implemented NextGen procedure changes, MWAA noise monitors are not under South Flow SIDs for westbound turns, consequently, noise impacts are not quantifiable from MWAA noise monitor data. Marcio Duffles: DC Noise Study is evaluating noise monitoring locations. sph/kg Pg 5/12

6 Ken Hartman: North of DCA, communities are also concerned about environmental impacts of South Flow arrival flight path changes. Unable to obtain results of the Environmental Impact Study conducted by the FAA for South Flow changes. Communities need baseline noise data to evaluate the impacts of proposed flight path changes. William Noonan: Communities need access to flight track and noise data. Cell phone noise apps are notoriously inaccurate. Nighttime Noise and Procedures also need to be addressed, i.e. schedules, flight corridors and altitudes. Example: o AAL154, ORD-DCA, May 22, 11:19:06 pm, 1631ft AGL o Why can t FAA Air Traffic position aircraft at higher altitudes until they turn onto the river at 5,000 feet, then descend? o In addition to noise levels, the frequency of flights is a contributing annoyance factor over a specific location. o Working Group members discussed presenting a Nighttime Noise Resolution but agreed that the Procedures Subcommittee would be the appropriate subcommittee to address Nighttime Noise and Procedures as a top priority. Procedures Subcommittee 2: Subcommittee would require external, technical support. Need two Procedures subcommittees, North and South, to develop recommendations to FAA: o Procedures Subcommittee 1: North Flow Departures / South Flow Arrivals o Procedures Subcommittee 2: South Flow Departures / North Flow Arrivals Departure noise (full thrust) and approach noise (airframe) are both important concerns to communities on the ground. Fly Quite Program Subcommittee 3: Recommended incorporating the best practice from other Fly Quiet Programs with MWAA s proposed Fly Quiet program. Permanent Working Group Subcommittee 4: MWAA previously stated that the Working Group will continue. Subcommittee 4 may be a subset of the Fly Quiet Program Subcommittee 3. Residential Sound Insulation Program Subcommittee 5: Working Group understands that DCA is currently ineligible to receive federal sound insulation funding since there are no households inside the Part DNL contour. Subcommittee 5 would provide research support in the event that federal eligibility laws change. sph/kg Pg 6/12

7 Dulles Matters Subcommittee 6: Working Group would like to contribute to MWAA s program to drive business and opportunity to Dulles. Subcommittee could collect information and meet with elected officials to share ideas. Mike Jeck / MWAA Noise Information Office: Loudoun County and Fairfax County are both evaluating potential changes to existing land use zoning around Dulles that would introduce residential properties potentially affected by low altitude arrivals and departures. It would be helpful if the Working Group would work with MWAA to oppose rezoning that could expose future residential property to overflights and restrict growth of Dulles flight operations. Documentation and Reporting: What, Who When format needed for subcommittee documentation. Written and oral presentations needed at each Working Group meeting. Summary: Reduce full Working Group meetings to 4-6 times per year. Use other technology resources for supplemental subcommittee meetings, i.e. GoToMeeting. o Discussion: After rules of engagement have been established, subcommittee chairs may need to coordinate joint subcommittee discussions to decouple important issues such as flight procedures and noise impacts. Susan Shipp: The noise isn t going away. Consequently, a common understanding of Working Group s goal needs to be established to ensure subcommittee success. Working Group needs a baseline understanding of how equitably people are willing to sharing the pain. Margaret McKeough: MWAA will follow Working Group s lead regarding committee structure. For fiduciary reasons, technical resources funded by MWAA will need to be managed by MWAA. Request for technical support needs consideration to prioritize resources and financial responsibilities. MOTION: Resolution #1 - Working Group consensus to review the committee s governing structure to include subcommittees aligned with their 6-Point Plan and present as a June action Item. Working Group Voting Member Results: Yay (12): Dick DeiTos, Marcio Duffles, Ken Hartman, Paul Janes, John Mitchell, Ron Montague, Mike Rioux, Susan Shipp, Brian Stout, Steve Thayer, Wayne Tonkins, Jr., Don Crockett (DC Ward 2 Alternate) Nay (0) sph/kg Pg 7/12

assigned to meet project timelines. Ken Hartman / Mike Rioux: Working Group confirms previous recommendations and endorses FAA s effort to continue development of solutions.

8 Abstain(0) Resolution #1 was approved. Lynn Ray / FAA VP, Mission Support Services for the Air Traffic Organization: FAA needs the Working Group to re-affirm previous committee recommendations to ensure appropriate FAA resources are assigned to meet project timelines. Ken Hartman / Mike Rioux: Working Group confirms previous recommendations and endorses FAA s effort to continue development of solutions. Agenda Item 3 FAA Update: 3A) Revised Notional North Flow Graphics: o FAA Presentation Conceptual West & East RNAV SIDs - Update Bennie Hutto / FAA NACTA Representative Presented updated DCA Runway 01 and 33 graphics for Conceptual West & East RNAV SIDs: Prohibited Airspace P-56A/B (red) Conventional 328 radial (white dotted line) Current published procedure (yellow-brown) Notional procedure (green) Aircraft would depart northwest off Runways 01 and 33, avoid P-56, then align with the center of the Potomac River: o ADAXE waypoint would be replaced with WP395 o Current BEBLE waypoint would remain o COVTO waypoint would be replaced by WP173 Westbound traffic: o New WP398 waypoint where aircraft will disperse west and southwest Eastbound traffic: o ALEEX moved very slightly to northeast o DCA eastbound traffic sequenced with other eastbound traffic, including Dulles, to get into flows headed to New York, Boston etc.; some may turn early to be sequenced into flow. o FAA has limited options regarding eastbound traffic. sph/kg Pg 8/12

9 sph/kg Pg 9/12

o FAA Presentation DCA Conceptual SIDs_Land vs Water Bennie Hutto / FAA NACTA Representative Presented DCA percentage time over water analysis for current and notional procedures: Prohibited Airspace

Time over Water: Westbound: Improves over water time by 27% Eastbound: Improves over water time by 15% FAA will provide North Flow percentages for eastbound and westbound departures.

10 o FAA Presentation DCA Conceptual SIDs_Land vs Water Bennie Hutto / FAA NACTA Representative Presented DCA percentage time over water analysis for current and notional procedures: Prohibited Airspace P-56A/B (red) Conventional 328 radial (orange dotted line) Timing Start-Stop line (green) Current published procedure (gray) Notional/Conceptual procedure (blue) Notional/Conceptual Percentage of Time over Water: Westbound: Improves over water time by 27% Eastbound: Improves over water time by 15% FAA will provide North Flow percentages for eastbound and westbound departures. o FAA Video DCA Notional and Current SIDs Bennie Hutto / FAA NACTA Representative Presented video of aircraft flying notional procedure (aircraft 1 and 2) and current procedure (aircraft 3 and 4): Prohibited Airspace P-56A/B (red) Conventional 328 radial (yellow dotted line) Current published procedure (red) Projected path of notional/conceptual procedure (light blue) Target aircraft (white circle) Departure lag: 70s between aircraft Approximate notional/conceptual altitudes at waypoints: WP395: 2, ft BEBLE: 3,400 ft COVTO: 4,800 ft WP173: Above 5,000 ft o Discussion: Ron Montague: From a Rosslyn perspective, concerned the notional procedure has shifted back over Rosslyn and Arlington National Cemetery. sph/kg Pg 10/12

11 William Liebman: Notional procedure doesn t provide much relief to residents under eastbound procedure. Bennie Hutto: Majority of aircraft currently fly the RNAV versus the legacy conventional 328 radial that flew over Arlington National Cemetery; FAA will avoid designing a new procedure that results in Arlington National Cemetery overflights. That s why Runway 33 departures vector northeast after departure. Legacy noise abatement procedure and engine settings were designed for older, louder stage 2 aircraft. Modern aircraft perform better, so the goal is to climb them faster to a higher altitude which impacts fewer people on the ground. Criteria will ultimately determine the position of WP395 based on P-56 avoidance, aircraft separation, climb rates, distance between waypoints, etc. After the onboard Flight Management System engages at 500 ft AGL, 95% of the time the aircraft will be less than 1 mile laterally from the procedure centerline. FMS should constantly correct to centerline if an aircraft deviates from the centerline. Changes generate cascading impacts on other procedures. FAA can provide a graphic with 10 DME arc, legacy noise abatement procedure and notional procedure. FAA is committed to investigating possible modifications to the eastbound procedure but there are operational and safety factors that limit those options. Based on the Working Group s previous suggestion, the notional concept was presented to provide relief to the Georgetown/Foxhall and Montgomery County communities. FAA can t chase relief for every community; Working Group needs to decide what is equitable for the overall region. FAA needs a Working Group recommendation to continue development of the notional procedure. 3B) South Flow SID Schedule: o Lynn Ray: FAA will kick-off their formal working group in August. Local outreach will begin in about 6 weeks. Goal is to achieve an month publication date. 3C) IFP Gateway Procedures: o Margaret McKeough: MWAA received several Working Group inquiries regarding the relevance of an FAA approach procedure change published on the FAA website. o Bennie Hutto: LDA-Y (formally LDA-Rosslyn) and LDA-Z serve as approach procedures to Runway 19. Approach procedures have a missed approach component for when an aircraft approaches the airport, aborts the landing and needs to go around to re-enter the approach pattern. sph/kg Pg 11/12

12 When the aircraft aborts the approach, the aircraft is vectored to a navigational fix called BADDN which is intersection of a DCA radial and the Nottingham VORTAC. Two reasons for the published change: Nottingham VORTAC is being decommissioned and taken off the approach procedure. Glideslope does not work below a certain altitude so it is being removed for LDA-Y. There are no lateral or vertical changes associated with the LDA-Y and LDA-Z procedures. River Visual is the primary approach procedure when weather ceiling is 3,500 ft and 3 miles visibility. LDA-Y is not issued very often, because it has higher minimums than LDA-Z, which means aircraft have to change to another approach procedure when the weather conditions worsen. LDA-Z is more efficient. 3D) Minimum Altitudes on Procedures: o FAA will address Minimum Altitude on Procedures at a future meeting. 3E) LAZIR-B Public Comments: o FAA delivered a CD with LAZIR-B Public Comments to MWAA during meeting. o MWAA will identify a distribution method and send to the LAZIR-B Public Comments Working Group. Agenda Item 4 Other Business/Next Meeting Agenda: 2017 Meeting Dates (4 th Thursday) o Margaret McKeough: Future meeting dates were established for the Working Group. MWAA will take the Working Group s lead on which dates work with the Proposed 6- Point Plan under consideration. Action Items Prior to Next Meeting or Future Meeting: FAA: FAA will provide North Flow percentages for eastbound and westbound departures. FAA can provide a graphic with 10 DME arc, legacy noise abatement procedure and notional procedure. FAA will address Minimum Altitude on Procedures at a future meeting. MWAA: MWAA will contact information for current Working Group Voting. MWAA will identify a distribution method and send to the LAZIR-B Public Comments Working Group. Working Group: MOTION: Resolution #1 - Working Group consensus to review the committee s governing structure to include subcommittees aligned with their 6-Point Plan and present as a June Action Item. sph/kg Pg 12/12

Summary Reagan National Airport Community Working Group Regular Meeting (24) July 26, 2018

Summary Reagan National Airport Community Working Group Regular Meeting (24) July 26, 2018 Date: July 26, 2018 Time: 6:00 P.M. 8:00 P.M. Location: Metropolitan Washington Airports Authority (MWAA) Terminal