Minneapolis/St. Paul International Airport (MSP)

Noise Oversight Committee (NOC) Meeting Agenda

September 15, 2010 1:30 P.M.

Lindbergh Conference Room MAC General Office Building

6040 28th Avenue South Minneapolis, MN 55450

(Mary Loeffelholz, Delta Air Lines & NOC Co-Chair, will be the acting Chairperson for the meeting)

*Note: 1:00 to 1:30 – Committee Agenda Review Session (NOC members only in the Coleman Conference Room)

1. 1:30 to 1:45 – Public Comment Period

2. 1:45 to 1:50 – Review and Approval of July 21, 2010 NOC Meeting

Minutes 3. 1:50 to 1:55 – Review of Operations Report Summary

4. 1:55 to 2:15 – Delta Air Lines Performance Based Navigation (PBN)

Efforts

5. 2:15 to 2:25 – MSP Airspace-Wide RNAV Implementation a. Runways 12L and 12R RNAV Departure

Procedures and Runway 35 Optimized Profile Descent (OPD) Procedure Deferrals

6. 2:25 to 2:40 – Internet Real-Time Flight Tracker Demonstration

7. 2:40 to 2:50 – Review of Draft Crossing-in-the-Corridor Report Format

8. 2:50 to 3:00 – Runway 35 River Visual Approach Procedure

9. 3:00 to 3:15 – Review Items for Possible Inclusion in the 2011 MSP

NOC Work Plan

10. 3:25 to 3:30 – Third Quarter 2010 Public Input Meeting Comments

11. 3:30 – Adjourn

MEMORANDUM TO: MSP Noise Oversight Committee (NOC) FROM: Chad E. Leqve, Manager – Aviation Noise and Satellite Programs SUBJECT: DELTA AIR LINES PERFORMANCE BASED NAVIGATION

(PBN) EFFORTS DATE: September 1, 2010 At the September 15, 2010 NOC meeting Mr. Grady Boyce, Technical Pilot, Delta Air Lines, will be addressing the Committee on Delta Air Lines’ efforts in the area of Performance Based Navigation (PBN). We are extremely fortunate to have Mr. Boyce’s attendance at the September 15th NOC meeting. Please come prepared to ask any questions you might have related to Delta Air Lines’ aircraft navigation technologies and plans as they relate to Minneapolis-St. Paul International Airport (MSP).

ITEM 4

MEMORANDUM TO: MSP Noise Oversight Committee (NOC) FROM: Chad E. Leqve, Manager – Aviation Noise and Satellite Programs SUBJECT: MSP AIRSPACE-WIDE RNAV IMPLEMENTATION

a. Runway 12L and 12R RNAV Departure Procedures and Runway 35 Optimized Profile Descent (OPD) Procedure Deferrals

DATE: September 1, 2010 On August 30, 2010 the MSP Performance Based Navigation (PBN) Task Force met to discuss the Runway 35 Optimized Profile Descent (OPD) Procedure. As was discussed at the July 21, 2010 NOC meeting, Federal Aviation Administration (FAA) was considering the development and implementation of this procedure using RNAV, as well as the implementation of RNAV technology airspace-wide at MSP. After consultation with the FAA RNAV Project Office in Washington D.C., it was determined that MSP is an excellent airport for airspace-wide RNAV implementation given the present airspace design and the lack of conflicts with other airport airspaces. At the August 30th Task Force meeting it was determined that the most effective and efficient way to develop and implement Crossing-in-the-Corridor RNAV tracks, as well as OPD procedures, was through the airspace-wide RNAV procedures development and implementation initiative. Based on the interdependency that Runways 12L and 12R Corridor compliant RNAV tracks could have with Crossing-in-the-Corridor RNAV tracks, and the OPD considerations that could flow from implementation on all runways at MSP, it is recommended that the Runways 12L and 12R Crossing-in-the-Corridor RNAV procedures and OPD procedure design and implementation be rolled into the airspace-wide RNAV procedures development and implementation initiative. The MSP airspace-wide RNAV procedures development and implementation initiative will begin with a coordination meeting in October; an official kick-off meeting is planned for November 2010. The NOC will be kept updated on the developments and specifics related to this major effort as the activities move forward. Staff will provide a presentation on this topic at the September 15, 2010 NOC meeting. COMMITTEE ACTION RECOMMEND THAT THE METROPOLITAN AIRPORTS COMMISSION ENDORSE DEFERRAL OF THE RUNWAYS 12L AND 12R RNAV DEPARTURE PROCEDURES SO THE PROCEDURES CAN BE CONSIDERED IN FAA’S AIRSPACE-WIDE RNAV PROCEDURE DESIGN AND IMPLEMENTATION EFFORT.

ITEM 5

MEMORANDUM TO: MSP Noise Oversight Committee (NOC) FROM: Chad E. Leqve, Manager – Aviation Noise & Satellite Programs SUBJECT: INTERNET REAL-TIME FLIGHT TRACKER DEMONSTRATION DATE: September 1, 2010 At the July 15, 2009 Noise Oversight Committee (NOC) meeting, staff reported that the development and integration of Harris, Miller, Miller and Hanson’s (HMMH) In-Flight flight track and noise data processing system was complete and operating as a central part of the Metropolitan Airports Commission Noise and Operations Monitoring System (MACNOMS). Additionally, the discussion focused on initial planning for the Committee’s development of a MACNOMS System Enhancement Plan. Committee members were informed that MAC staff was in the final phases of negotiating a contract with HMMH for a real-time flight tracking application on the macnoise.com website. Staff requested that Committee members go back to their respective airport advisory commissions and constituencies and conduct a review of the reports and interactive capabilities provided on the macnoise.com website. Members were asked to come to the September 16, 2009 NOC meeting prepared to discuss their desired enhancements to the reports and interactive capabilities provided on the website. At the September 16, 2009 NOC meeting staff provided a live demonstration of the reports and interactive functionality available on the macnoise.com website. The intent of this discussion was to provide staff with clear expectations and priorities in the context of new and/or enhanced reports and interactive functionality to be used as staff’s MACNOMS System Enhancement Plan moving forward. MAC staff received no feedback from NOC members regarding desired enhancements prior to the NOC meeting. At the September 16, 2009 NOC meeting the Committee determined that the highest priority system enhancement related to flight track and operations data timeliness. Specifically the NOC determined that next day operations data availability and real-time flight tracks on the macnoise.com website were the highest system development priorities. For the past year staff has been focusing on the development of these MACNOMS elements. With the integration of multilateration flight track data collection in the MACNOMS, the interactive reporting and mapping applications on the macnoise.com website now provided access to data with only a 24-hour delay. Additionally, staff has completed the development of the Real-Time Flight Tracker. This web-based application allows for animated viewing of flight track data with as little as a 10-minute delay, or the replay of historic flight track data. This application provides aircraft type, altitude, speed, and source/destination airports (when available) for each operation. Staff will provide a live demonstration of the Real-Time Flight Tracker at the September 15, 2010 NOC meeting.

ITEM 6

MEMORANDUM TO: MSP Noise Oversight Committee (NOC) FROM: Chad E. Leqve, Manager – Aviation Noise & Satellite Programs SUBJECT: REVIEW OF DRAFT CROSSING – IN –THE – CORRIDOR

REPORT FORMAT DATE: September 1, 2010 At the July 21, 2010 Noise Oversight Committee (NOC) Meeting the Committee reviewed a Draft Monthly Crossing – in – the – Corridor Report format. As part of the discussion it was determined that Mendota Heights would like the opportunity to discuss the format with its Airport Relations Commission (ARC). Additionally, it was determined that the time periods reported previously (2300-0600 and Sat. 1500 – Sun. 1300) in past Crossing – in – the – Corridor analyses may no longer be appropriate given the introduction of Runway 17/35 at Minneapolis-St. Paul International Airport (MSP) and hourly operation concentrations related to the one-local controller requirement for procedure execution. Mendota Heights was going to go back and confer on the report format and staff agreed to engage Federal Aviation Administration (FAA) staff on the appropriate procedure use expectations considering the procedure’s one-local controller requirement in the context of Runway 17/35 operations and hourly operation concentrations. As a result of staff’s discussion with the FAA it was determined that the 2300 to 0600 hours represent the only time period at MSP when circumstances are likely to support the use of the Crossing – in – the – Corridor procedure. Staff conducted an independent analysis of the hourly operations at MSP which also supported this conclusion. As such, the attached updated Draft Monthly Crossing – in – the – Corridor Report removes the weekend analysis (Sat. 1500 – Sun. 1300). However, the updated Draft provides an analysis of the 0600 to 2300 timeframe to see if there are instances throughout the month when Air Traffic Control uses the Crossing – in – the – Corridor procedure outside of the core nighttime hours. An important distinction moving forward is that the probability of crossing operations in the non-core nighttime hours is very low and should not be expected. Staff will provide a presentation on this topic at the September 15, 2010 NOC meeting. COMMITTEE ACTION APPROVE THE ATTACHED CROSSING – IN – THE – CORRIDOR REPORT FORMAT, REQUEST STAFF TO PRODUCE A MONTHLY REPORT, AND TO PUBLISH THE REPORT ON THE WWW.MACNOISE.COM WEBSITE.

ITEM 7

Draft Crossing in the Corridor Analysis

Draft Report Generated: 8/30/2010 12:50 PM -1-

Crossing in the Corridor Analysis

May 2010

Draft Copy

Draft Report – not intended for public reporting purposes.

Draft Crossing in the Corridor Analysis

Draft Report Generated: 8/30/2010 12:50 PM -2-

May 2010

Carrier Jet Departure Operations Runways 12L & 12R (23:00 – 06:00)

468 Carrier Jets Departed Runways 12L & 12R between the hours of 23:00 and 06:00

Draft Crossing in the Corridor Analysis

Draft Report Generated: 8/30/2010 12:50 PM -3-

May 2010

Carrier Jet Departure Operations Performing the Crossing Procedure off Runways 12L &12R

(23:00 – 06:00)

113 (24.1%) Carrier Jets Crossed After Departing Runways 12L & 12R between the hours of 23:00 and 06:00

Draft Crossing in the Corridor Analysis

Draft Report Generated: 8/30/2010 12:50 PM -4-

May 2010

Carrier Jet Departure Operations Runways 12L & 12R (06:01 – 22:59)

4,077 Carrier Jets Departed Runways 12L & 12R between 06:01 and 22:56

Draft Crossing in the Corridor Analysis

Draft Report Generated: 8/30/2010 12:50 PM -5-

May 2010

Carrier Jet Departure Operations Performing the Crossing Procedure off Runways 12L &12R

(06:01 – 22:59)

810 (19.9%) Carrier Jets Crossed After Departing Runways 12L & 12R between 06:01 and 22:59

MEMORANDUM TO: MSP Noise Oversight Committee (NOC) FROM: Chad E. Leqve, Manager – Aviation Noise & Satellite Programs SUBJECT: RUNWAY 35 RIVER VISUAL APPROACH PROCEDURE DATE: September 1, 2010 A review of the Runway 35 River Visual Approach Procedure was discussed in 2009 by the NOC and was carried forward in the 2010 NOC Work Plan at the request of the City of Eagan. The procedure was outlined in the November 2004 Minneapolis/St. Paul International Airport (MSP) Part 150 Update Document as Noise Abatement Measure 16. The intent of this measure in the Part 150 Update was to consider a visual river approach to Runway 35 that routes arriving aircraft over the Minnesota River Valley. The purpose of this procedure would be to reduce aircraft arrival overflights of residential areas south of MSP.

Aircraft using this procedure would approach from the southwest, flying a 65o heading over the river. As the aircraft nears the airport, it would turn on to final approach and align with Runway 35.

As detailed in the November 2004 Part 150 Update document, several issues need to be resolved prior to possible implementation of this procedure, including airspace design, Flight Standards District Office (FSDO) concurrence and flight testing. Also, additional analysis would

be required to determine if the procedure could be safely used at night.

MAC staff again reviewed the procedure with local Federal Aviation Administration (FAA) representatives, as was done in 2009. As was the case previously, several issues remain regarding the implementation of this procedure at the present time. Some of the issues include safety, efficiency, and established final approach segment length. Both MAC and FAA staff agree that such procedures are better suited to be considered in the context of Performance Based Navigation (PBN), possibly utilizing Area Navigation (RNAV) and/or Global Positioning System (GPS)-based navigation technologies in the future. Although this position does not provide a future date-certain implementation of this procedure, it provides further support for the present RNAV efforts underway at MSP. Moreover, this procedure framework provides a possible focus for follow-on RNAV and/or GPS/GBAS procedure development at MSP in the future once more aircraft are appropriately equipped and airspace redesign opportunities exist as part of the FAA’s NEXT-GEN program.

Staff will provide a presentation on this topic at the September 15, 2010 NOC meeting.

ITEM 8

MEMORANDUM TO: MSP Noise Oversight Committee (NOC) FROM: Chad E. Leqve, Manager – Aviation Noise & Satellite Programs SUBJECT: REVIEW ITEMS FOR POSSIBLE INCLUSIONS IN THE 2011

MSP NOC WORK PLAN DATE: September 1, 2010 At the September 15, 2010 NOC meeting discussions will begin regarding possible elements of the 2011 NOC Work Plan. Final member comments and ideas will be sought at the November 17, 2010 NOC meeting in an effort to finalize the 2011 NOC Work Plan. MAC staff provides the following for consideration as possible 2011 NOC efforts: Residential Noise Mitigation Program

• Review Residential Noise Mitigation Program Implementation Status MSP Noise Program Specific Efforts

• 2010 Actual Noise Contour Report • Annual Scheduled Nighttime Operations Assessment • Implementation of Runway 35 Optimized Profile Descent (OPD) Procedure • Runways 17, 12R and 12L RNAV Departure Procedure Use Analysis • Noise Analysis – Minneapolis-St. Paul International Airport (MSP) 2020

Environmental Assessment (EA) • Review of Aircraft Fleet-mix Trends at MSP • Development of Performance Based Navigation (PBN) Procedure Design

Noise Criteria for Procedure Development/Implementation at MSP • Nighttime Runway Use Analysis • Review Status of FAA Center of Excellence/PARTNER, TRB and FICAN

Initiatives • Macnoise.com Website Redesign and Enhancement

Continued Review of Public Input

• Continue to Review Input Received from the Public Input Meetings as Possible Agenda Items

Please consider the above efforts in preparation for a preliminary 2011 NOC Work Plan discussion at the September 15, 2010 NOC meeting. Final discussion and consideration of work plan elements will occur at the November 17, 2010 NOC meeting when the 2011 NOC Work Plan is finalized.

ITEM 9

MEMORANDUM TO: MSP Noise Oversight Committee (NOC) FROM: Chad E. Leqve, Manager – Aviation Noise & Satellite Programs SUBJECT: THIRD QUARTER 2010 PUBLIC INPUT MEETING COMMENTS DATE: September 1, 2010 One of the elements of the Metropolitan Airports Commission’s (MAC) approved framework for the MSP Airport Noise Oversight Committee (NOC) requires MAC staff to conduct quarterly public input meetings. The intent is to ensure residents’ concerns are considered as part of the ongoing effort by the MAC and the NOC to address noise issues around Minneapolis-St. Paul International Airport (MSP). This memorandum provides a summary of the comments received at the last public input meeting. The NOC may also review these topics as possible future action items if the members so desire.

On July 27, 2010 MAC Aviation Noise and Satellite Program staff conducted the third quarter 2010 public input meeting – two people attended the meeting and one individual made comments. MAC staff responded to questions at the meeting and is also providing a written response to the questions. The comments and associated responses can be found on the MAC Noise Program’s website accessible on the Internet at www.macnoise.com when they are completed.

In summary, questions raised at the meeting focused on nighttime Runway 35 aircraft arrival impacts in the City of Apple Valley. The questions also focused on Runway 35 arrival data, Optimized Profile Descent (OPD), a Runway 35 river arrival procedure, Runway 17 departure fanning away from runway heading and anticipated future Runway 17/35 operation levels.

The above topics are provided to MAC Commissioners for informational purposes and to NOC members for consideration as possible future discussion items if the Committee members so desire.

The next quarterly public input meeting is planned for September 28, 2010.

ITEM 10