Summary Reagan National Airport Community Working Group Regular Meeting (17) October 26, 2017

Transcription

1 Summary Reagan National Airport Community Working Group Regular Meeting (17) October 26, 2017 Date: October 26, 2017 Time: 6:00 P.M. 8:00 P.M. Location: Metropolitan Washington Airports Authority (MWAA) Terminal A Historic Lobby Conference Center Agenda: September 28, 2017 and August 18, 2017 Summaries, Working Group Discussion, FAA Update 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 Mike Metcalf District of Columbia - Ward 6 John Mitchell Prince George s County - Accokeek Ron Montague Arlington County Tracy Montross American Airlines Rick Murphy District of Columbia - Ward 2 Jim Phelps Fairfax County - Dranesville Mike Rioux Fairfax County - Mount Vernon Susan Shipp Montgomery County - Outside Beltway Brian Stout Arlington County Steve Thayer City of Alexandria Edward Williams Prince George s County - Ft. Washington Alternates: Don Crockett District of Columbia - Ward 2 Carol Hawn Fairfax County At-Large William Liebman Montgomery County Don Minnis Fairfax County - Mount Vernon William Noonan Montgomery County - Inside Beltway Janelle Wright Montgomery County - Outside Beltway Agenda Item 1 Welcome and Updates: Margaret McKeough, MWAA Chief Operating Officer: Welcomed Working Group and new Montgomery County Alternate, Janelle Wright. Facilitated the introduction of staff representing Maryland elected officials for U.S. Senator VanHollen and Montgomery County Council President Roger Berliner. 1A) Approval of September 28, 2017 and August 18, 2017 (conf. call) Meeting Summaries: o Approved. sph/ry Pg 1/7

2 1B) Draft Working Group By-Laws and Procedures Discussion: o Brian Stout: Reported that Working Group By-laws have been drafted. Highlights: Goal: Submit recommendations to FAA via MWAA, on behalf of the region, to address aircraft noise issues experienced in our communities. Working Group Officers: Establish Chair and Vice Chair. Purpose and Objective Structure and Organization Funding and Budget Recommended an ad-hoc Sub-committee (DC-MD-VA-Airlines) to finalize By-laws then distribute to the Working Group 2 weeks prior to November meeting. Motion with 2 nd : Motion: Establish a Working Group ad-hoc Sub-committee (DC-MD-VA-Airlines) to review and finalize By-laws two weeks prior to November meeting. Members: Dick DeiTos (Airlines) Marcio Duffles (DC) Ken Hartman (MD) Mike Rioux (VA) Working Group Voting Member Results: o Yay (15): Dick DeiTos, Marcio Duffles, Ken Hartman, Paul Janes, Mike Metcalf, John Mitchell, Ron Montague, Tracy Montross, Jim Phelps, Mike Rioux, Susan Shipp, Brian Stout, Steve Thayer, Edward Williams. o Nay (0): None o Abstain (0): None Agenda Item 2 General Working Group Discussion: 2A) WebTrak Accuracy/B&K App and Complaint Portal Update Simon Heath / Bruel & Kjaer, Manager of Products Alex Fluken / Bruel &Kjaer, Account Manager o David Mould / MWAA VP Communications: o B&K: Introduced Bruel & Kjaer (B&K) guests representing MWAA s Noise & Track Monitoring System vendor from Australia and California. B&K invited to address concerns related to WebTrak data accuracy, as well as, demo prototypes of MWAA s new Mobile App and Community Complaint Dashboard to be released in early WebTrak Data Accuracy: o Compared aircraft photo provided by homeowner with WebTrak flight track video to demonstrate variability of ground experience. sph/ry Pg 2/7

3 o Explained that personal perception of overhead is not restricted to 90 perpendicular to the ground. People experience a much wider field of view that is perceived to be overhead. o WebTrak flight track video demonstrated that the visual perception of an aircraft can be deceptive without a visible reference to actual ground track radar points, i.e. curtain. o Aircraft position is determined by fusing data from multiple sources to synthesize a flight track. Goal is to generate the most accurate representation of a flight track based on its noise profile. FAA provides industry with different raw track point data sets along the flight track. B&K uses the most accurate data source as it builds tracks from raw points. Given that aircraft are big objects, raw track points are scattered based on the part of the aircraft that the radar was reflected (wing tip, nose, tail, belly etc.) Smoothing algorithm is applied to the scattered raw points to identify a flight envelope used to filter track points that best represent the physics of the actual flight track position. Data sources: Ground radar, Terminal Area Radar (ATC), Long Range Radar, Aircraft transponder (ADS-B) etc. Data sources become available at different times which limits the ability to build real-time flight tracks. MWAA has placed a high priority on data accuracy versus time track reporting, consequently, tracks are typically available to view on WebTrak within 1 hour of the flight. Flight track margin of error is within 200 ft. Altitudes are reported to the nearest 100 ft; smoothing algorithm may interpolate between raw points during track synthesizing. Altitude is most challenging dimension to measure, e.g. - ground radar does not provide altitude; aircraft broadcast their flight level, which is air pressure related, but aircraft equipment may have different calibration parameters; uncertainty of Terminal Area Radar etc. However, aircraft noise is very traceable to height. As an aircraft flies over a noise monitor, sound pressure is very consistent with an altitude. Ground radar data is available every 1 second, Terminal Area Radar data is available every 4 seconds. Flight validation tests are periodically conducted to ensure flight track accuracy. Military and helicopters are the most difficult tracks to build because they are less predictable. sph/ry Pg 3/7

4 Mobile App - Prototype Demo: o B&K Mobile App creates a compatible interface to incorporate mobile complaints with other B&K products versus community-designed apps that are difficult to incorporate into the complaint database. o Started with a simple approach that allows a person to submit a complaint with or without using a social media login. o If a person chooses to use a social media account, the social login only provides access to the person s first/last name and ; App only records the social media unique identifier associated with the Facebook, Google, LinkedIn or Microsoft account to validate the person s account. o User completes the profile page, selects Compose to write a complaint, then selects NOW feature which will correlate date, time and location with available flight track data. o User s complaint history is only available on their phone; data is not stored in the Cloud. Community Complaint Dashboard Prototype Demo: o Dynamic, online reporting using Microsoft Power BI technology that allows self-investigation of complaint statistics from present: Disturbance Type, Date/Time, Zip Code, Households/Individuals etc. Goal is to effectively engage individuals, aggregate data and identify trends. MWAA will release Complaint Mobile App and Community Complaint Dashboard in early Additional Discussion: o 2017 Annual Aircraft Noise Report: MWAA will work with Fly-Quiet Sub-committee to review Annual Aircraft Noise Report format and possibly incorporate additional data available in the Community Complaint Dashboard. o Noise Monitoring Data Accuracy: Noise monitors are a Class I Type, i.e. most accurate, calibrated instrument available. Instrument contains a piston phone which confirms noise level accuracy, between calibrations, that is traceable to a national laboratory standard guaranteeing that period of time was valid. o William Liebman: See Addendum #1 Asked Mr. Heath whether the collection and presentation of noise data is merely an academic exercise if the FAA, MWAA and the airlines ignore these data and do not use them in furtherance of developing noise-abatement strategies. Simon Heath replied, Yes. sph/ry Pg 4/7

5 Agenda Item 3 FAA Update: 3A) Anacostia River Proposal Robert Owens / FAA Terminal Assistant District Manager, Donna Creasap / FAA Mission Support Services o Difficult for FAA to completely eliminate a viable procedure. o Procedure is challenging and not favored by ATC; procedure issued by ATC when requested by pilots and operationally feasible. o FAA has no plan to increase the use of the Anacostia River procedure. 3B) Update on Process Robert Owens / FAA Terminal Assistant District Manager, Donna Creasap / FAA Mission Support Services o FAA delivered a prepared statement on behalf of Jodi McCarthy, Acting VP of Mission Support Services: See Addendum #2. FAA accepted Recommendation #8 in its entirety; FAA Working Group meetings began in August Updates will be provided to BWI Roundtable on November 7, 2017 and DCA Roundtable on November 8, Recommendation #9 will be addressed only to the extent it supports completion of Recommendation #8; the portion of Recommendation #9 that may be supportive is the recommendation for North Flow SIDS. FAA previously explained that additional changes will delay the project and impede the ability of FAA to deliver on the original scope/commitment. Additional recommendations, including the Anacostia River proposal, will need to be addressed as separate activities from the current.41 process. FAA does not have the resources or budget to concurrently work on multiple recommendations. FAA has created a Community Engagement effort, attached to each PBN project, to meet/brief/engage airports and local officials on the design process of proposed changes to the airspace. o FAA extended an invitation to host a tour of the Potomac Consolidated TRACON: 3 Working Group members per jurisdiction. MWAA will poll Working Group members and coordinate with FAA to arrange a date/time for 3 members per jurisdiction to tour the Potomac Consolidated TRACON in Warrenton, VA. Agenda Item 4 Other Business/Next Meeting Agenda: Meeting Schedule: o Next meeting: November 30, 2017 sph/ry Pg 5/7

6 Action Items Prior to Next Meeting or Future Meeting: MWAA: MWAA will release Complaint Mobile App and Community Complaint Dashboard in early MWAA will poll Working Group members and coordinate with FAA to arrange a date/time for 3 members per jurisdiction to tour the Potomac Consolidated TRACON in Warrenton, VA. MWAA will work with Fly-Quiet Sub-committee to review Annual Aircraft Noise Report format and possibly incorporate additional data available in the Community Complaint Dashboard. Working Group: Motion: Establish a Working Group ad-hoc Sub-committee (DC-MD-VA-Airlines) to review and finalize By-laws two weeks prior to November meeting. Members: Dick DeiTos (Airlines) Marcio Duffles (DC) Ken Hartman (MD) Mike Rioux (VA) sph/ry Pg 6/7

7 Addendums Reagan National Airport Community Working Group Regular Meeting (17) October 26, 2017 Addendum #1 - October 26, 2017 Meeting Summary: Agenda Item 2A - WebTrak Accuracy/B&K App and Complaint Portal Update - Additional Discussion, Page 4: William Liebman submitted the following edit to be included in the meeting summary. The edit was approved by the Working Group on November 30, 2017: o Include: Asked Mr. Heath whether the collection and presentation of noise data is merely an academic exercise if the FAA, MWAA and the airlines ignore these data and do not use them in furtherance of developing noise-abatement strategies. Mr. Heath replied, Yes. Simon Heath s response to William Liebman s meeting summary edit: o Yes, as an engineer, I believe the outcome matters. o Within the safe operational choices set by the airspace regulator, our goal is to inform people that there may be choices that create a quieter environment for the community while allowing the airport to increase passenger loads. Addendum #2 - October 26, 2017 Meeting Summary: Agenda Item 3B - Update on Process, Page 5: John Mitchell submitted the following edit to be incorporated in the meeting summary. The edit was approved by the Working Group on November 30, 2017: o Original: FAA accepted Recommendation #8 o Change: FAA accepted Recommendation #8 in its entirety. Donna Creasap s response to John Mitchell s meeting summary edit: o I do not concur with the requested edit for the following reasons: Edit implies an extension beyond the acceptance of Recommendation #8 to indicate the FAA will address the entirety of the recommendation. The extent to which we are able to address the recommendation will be determined by the workgroup. It is inappropriate to anticipate the outcome of the workgroup in advance. When asked if we are working on the departures and arrivals, I responded affirmatively. However, that should not be interpreted that the outcome of the workgroup will be resolution of all areas (one possible outcome is that they worked on it and were not able to develop an acceptable resolution). I was simply affirming that departures and arrivals are part of the scope of the workgroup activities. sph/ry Pg 7/7