03/11/2014 - Airport Relations CommissionAGENDA
EAGAN AIRPORT RELATIONS COMMISSION
SPECIAL LOCATION: FARMINGTON FAA AIR ROUTE TRAFFIC CONTROL CENTER
512 DIVISION STREET
FARMINGTON, MN 55024
TUESDAY, MARCH 11, 2014
6:30 PM
I. ROLL CALL AND AGENDA ADOPTION
H. TOUR OF FAA AIR ROUTE TRAFFIC CONTROL CENTER IN FARMINGTON*
*This tour was originally scheduled in January 2014, but had to be postponed to March due
to weather.
III. STAFF UPDATES:
A. FAA DECISION NOT TO PURSUE USE OF RNAV FLIGHT TRACKS
B. ARC MEETING PLANS FOR MAY AND JULY 2014
IV. OTHER BUSINESS
V. VISITORS TO BE HEARD
VI. ADJOURNMENT
C M�mu
TO: THE EAGAN AIRPORT RELATIONS COMMISSION
FROM: DIANNE MILLER, ASSISTANT CITY ADMINISTRATOR
DATE: . MARCH 6, 2014
SUBJECT: AIRPORT RELATIONS COMMISSION MEETING / TUESDAY, MARCH 11, 2014
The Eagan Airport Relations Commission will meet on Tuesday, March 11 at 6:30 p.m. at the
Farmington FAA Control Center (512 Division Street, Farmington, MN 55024). To ensure
a quorum is present, please contact Executive Assistant Cheryl Stevenson at 651/675 -5005 or
cstevensongciiyofeagan.com if you are unable to attend the meeting.
I. ROLL CALL AND ADOPTION OF THE AGENDA
The agenda, as presented or modified, is in order for adoption by the Commission.
II. TOUR OF FAA AIR ROUTE TRAFFIC CONTROL CENTER IN FARMINGTON
Staff from the FAA will lead the Commission on a tour of the FAA Control Center in
Farmington. The tour will last approximately 45 minutes.
III. STAFF UPDATES
A. FAA DECISION NOT TO PURSUE USE OF RNAV FLIGHT TRACKS /.COMMUNITY
RESPONSES —On February 19, 2014, the FAA announced they will not implement a partial
use of Area Navigation (RNAV) for departure operations at MSP Airport. This means
departure operations will remain status quo. The FAA does plan to implement RNAV
arrival procedures, which includes use of Optimized Profile Descent (OPD).
Enclosed on pages I and 5 is a letter from the FAA to the Metropolitan Airports
Commission (MAC), summarizing their conclusions pertaining to the use of RNAV at MSP.. .
Z
AIRPORT RELATIONS COMMISSION MEET1NCr / TUESDAY, NOVEMBER 12, 2013
Page 2
n
Also enclosed on pages 6 and is a press release issued by the MAC highlighting the
FAA's findings.
In response to the FAA decision, the Noise Oversight Committee (NOC) considered the
resolution enclosed on pages 3— through LZ— at a special meeting on March 6, 2014. The
language is technical in nature as the FAA is the intended audience. In summary, the
resolution states: 1.) The unanimous support for the RNAV arrival procedures; 2.) Calls on
the FAA to present a case study of the successful implementation of RNAV at an airport
with similar challenges to MSP (including the airport's location adjacent to densely
populated residential areas) prior to RNAV implementation in the future; and, 3.)
Communicates that if the FAA introduces RNAV depar .ture tracks in the future at MSP, they
should be responsible for community outreach efforts related to the implementation.
Assistant City Administrator Miller will provide an update to the ARC on March 11 .
regarding the outcome of the NOC meeting since the ARC packet was prepared in advance
of the NOC meeting.
B. ARC MEETINGS PLANS FOR MAY 13, 2014 AND JULY 8, 2014 — Enclosed on pages
and j lis the revised 2014 ARC Work Plan, showing the changes made as a result of
the rescheduled tour, Previously, an open house was anticipated for March 2014 to focus
on the RNAV tracks; however, as noted above, there will not be any changes to the existing
departure tracks given the FAA's decision not to implement the partial RNAV procedures.
The Commission is encouraged to discuss their spring and summer meeting plans, and the
work plan can be adjusted accordingly.
III. VISITORS TO BE HEARD
The Eagan City Council and its Commissions set aside up to ten minutes at public meetings
to permit visitors to address items of interest that are not addressed on the regular agenda.
Items that will take more than ten minutes or that require specific action can be scheduled
for a future meeting agenda.
IX. ADJOURNMENT
Per the request of the Commission, the Eagan ARC meetings will go no later than 8:30 p.m.
unless agreed upon by the Commission.
./s /Dianne E. Miller
Assistant City Administrator
3
eft ,
U.S. Department
of,Transportatlon
Federal Aviation
Administration
FEB 19 2014
Jeff Hamiel
Executive Director /CEO
-Metropolitan Airports Commission
6040 28 " Avenue South
Minneapolis, MN 55450
Dear Mr. Hamiel;
The Federal Aviation Administration (FAA) and the Metropolitan Airports Commission
(MAC) have been working together to consider a proposal endorsed by the Noise Oversight
Committee regarding implementation of Area Navigation (RNAV) arrival and departure
procedures at Minneapolis —.St: Paul International Airport (MSP). On November 19, 2012, .
the MAC met and after considerable discussion and public comment, 'gave partial support of
the proposed RNAV deployment at MSP. In its motion, the MAC stated;
"Commissioner Foster moved and Commissioner Mencel seconded that the
Metropolitan Airports Commission supports implementation of the area navigation
(RNAV) procedures as designed by the Federal Aviation Administration with the
exception of RNAV departure procedures off runways 30L and 3 O at Minneapolis
St. Paul International Airport,"
I advised the MAC at this meeting that partial deployment of the full RNAV procedure
package would have to be evaluated for its compliance with the Safety Risk Management
(SRM) and Environmental requirements.
Subsequently, I received a letter dated February 1, 2013, which again outlined the MAC's
position for "partial implementation" of FAA proposed RNAV, Standard Terminal Arrivals
(STARS) and Standard Instrument Departures (SIDS), with the exception of Runway 30L
and 3 O RNAV SIDS. The MAC also suggested a collaborative framework for community
outreach for future RNAV development and deployment initiatives,
The FAA. recently completed a thorough review of the safety impacts of the MAC's partial
implementation proposal. The review, which is officially described as a SRM Document,
concluded that partial implementation of RNAV SIDs, as proposed by the MAC, introduces
unacceptable safety risks into the National Airspace System. FAA's recommended
mitigations, from a SRM perspective, are to either implement RNAV SIDS for all runways,
or use existing (legacy) SIDs for all runways, In summary, the FAA will not implement
RNAV SIDs.
4
The FAA has.also completed a thorough follow-on safety review of RNAV STARS for all.
MSP runways. In the MAC's motion from the November 19, 2012 meeting, the Commission
supported the implementation of the RNAV STARS, Accordingly, the FAA intends to move
forward with implementation and deployment of RNAV STARS at MSp,
If RNAV SIDS are reconsidered by FAA at any time in the future, we would welcome the
opportunity to work with you and the MSF Noise Oversight Committee on a community
outreach plan as outlined in your February 1, 2013 letter,
Sincerely,
Dennis E, Roberts
Director, Airspace Services
Enclosure
Safety Risk Management Document
,I In P0400
FOR IMMEDIATE RELEASE
Feb, 19, 2014
Patrick Hogan
612 - 726 -5335
Metropolitan Airports Commission Receives FAA
Decision Regarding RNAV Use at Minneapolis -St. Paul International Airport
MINNEAPOLIS -ST. PAUL —The Metropolitan Airports Commission (MAC) today
received a letter from the Federal Aviation Administration (FAA) indicating that the FAA .
will not implement Area Navigation (RNAV) departure routes at Minneapolis -St. Paul
International Airport (MSP) at this time.
The RNAV technology enables aircraft to consistently fly specific, predictable, pre -
determined routes, enhancing safety and efficiency while reducing fuel burn and
emissions. RNAV is a key part of the federal NextGen' program for addressing congestion
and improving safety and efficiency in the national airspace.
In September 2012, the FAA proposed a plan to implement RNAV procedures on all
runways at MSP. The Noise Oversight Committee (NOC), which advises the MAC on
noise issues around MSP, determined that the FAA had satisfied all the criteria the NOC
had established for RNAV development, and the FAA plan then went to the MAC board
for consideration in November 2012.
MAC board members heard from many area residents concerned about potential noise
impacts under the proposed. RNAV departure routes, Based on those concerns, the MAC
board voted to support only partial implementation of the FAA plan, withholding support
for RNAV departures off runways 30L and 30R, over the heavily populated areas north
and west of MSP. The FAA indicated it would need to study the safety implications of .
partially implementing the federal RNAV plan for the airport,
The letter received by the MAC today indicates the FAA is concerned that implementing
RNAV departures on some runways and not others could create "unacceptable safety
risks," Therefore, the FAA will not implement RNAV departures from any runways at
MSP at present.
-more-
RNAV /2222
The FAA will, however, move forward with the approved RNAV arrival procedures on a
timeline still to be determined. Currently, arriving aircraft perform a stepped descent,
reducing altitude and plateauing a number of times before landing. Under RNAV arrival
procedures, aircraft remain at a higher altitude longer and, once they begin descending,
continue to do so with the engines in an idle configuration until landing, Staying'higher
longer with the engines at an idle setting reduces noise impacts and emissions. Arriving
aircraft have to line up with runway headings whether or not they use RNAV, so flight
paths will not change under an RNAV approach process,
Jeff Hamiel, executive director and CEO of the Metropolitan Airports Commission, said
that safety must remain the top priority; "While we had initially hoped the FAA could
implement RNAV departures in areas to the south and east of the airport where there
were significant opportunities to reduce noise impacts, we obviously don't want them to
do so if they believe a partial implementation. would be unsafe," Hamiel said.,
The FAA letter provides no timeline for revisiting the issue of RNAV departures at MSP,
"If RNAV SIDs [departures] are reconsidered by FAA at any time in the future," the
letter states, "we would welcome the opportunity to work with you and the MSP Noise
Oversight Committee on a community outreach plan as outlined in your February 1, 2013
letter,"
That letter from MAC CEO Jeff Hamiel to FAA Airspace Service Director Dennis
Roberts recommended that any future effort by the FAA to implement RNAV departures
atMSP involve a robust FAA outreach program to affected communities, early
coordination with community leaders, investment of adequate resources to address local
expectations, and authorization for local air traffic control representatives to lead resource
allocation and community outreach efforts,
(Note; A copy of the FAA's decision letter is attached)
Attachment 3
MINNEAPOLIS- ST.PAUL INTERNATIONAL AIRPORT (MSP)
NOISE OVERSIGHT COMMITTEE (NOC)
c zXr.
RESOLUTION # 01 2C 1A.f P.1
REGARDING FUTURE FAA PERFORMANCErRS�D`9NAVIGATION (PBN) /AREA
NAVIGATION (RNAV) STANDARD DEPART RE PROCEDURE DESIGN AND
IMPLEMENTATION EFFORTS AT MINNEAPO `P-ST. PAUL INTERNATIONAL AIRPORT
WHEREAS, the NOC is the primary{ Viso
(MAC) on topics related`t� alr
w=
WHEREAS, NOC members have been offici
community-,, group and airport �u
WHEREAS, the NO °pis a bala rum fo
around MS Rdnoluding e iden
ry body toll
craft noise at
WHEREAS,Osln�oet2wQ07 th
existing vect6ted no
Airport (MSP�'Rac�d,
9etropolitan Airports Commission
and,
allj`saected to represent their respective
ser group eonstltuenciesand vote accordingly; and,
r khcJscussion'a` evaluation of noise impacts
tificon, study, and analysis of noise issues; and,
ated fo Implementation of Performance -Based
�$t} for of Area Navigation RNAV to enhance
end procedures at Minneapolis -St. Paul International
;_, >
WHEREAS, in�lalsea2010, amid' he ongaing NOC dialogue on RNAV noise abatement
t�R
procedures, the Federal Aviation Administration determined it was moving forward
with an ail pace vi'0 Performance -Based Navigation (PBN) procedure design and
implementAibmpro ss in .the form of Area Navigation (RNAV) Standard
� .,
Instrument Dep,��tures (SIDs) and Standard Terminal Arrival Routes (STARs).on
all runways at MSP; and,
WHEREAS, the NOC realized there were expanded considerations such as capacity, noise
mitigation, and operational efficiency, beyond just noise, that would factor into the
process as a result of the transition from a locally- focused noise procedure
enhancement initiative, to an FAA headquarter - driven airspace -wide effort; and,
WHEREAS, on March 22, 2011 the NOC sent a letter, and the MAC Commission sent a similar
letter on May 16, 2011, to the FAA requesting that the Agency's process include
I
various measures in the form of five noise related activities including noise impact
analyses, community engagement, information sharing, and noise - reduoing
procedure design considerations; and,
WHEREAS, following the March 2011 NOC letter, FAA representatives indicated that the project
scope did not.include the requested analyses and community
engagement /information sharing activities; and,
WHEREAS, the NOC structured a plan to attempt to provide the desired analyses and
community engagement/information sharing activities (planned to require
approximately six months to complete) following* r c 1pt of the FAA's final proposed
procedure tracks; and, h,r'
WHEREAS, in early September 2012 the MAC and th wleceived the FAA's final proposed
procedure tracks and shortly thereafter, Jan %ld- September 2012, the FAA
requested the MAC's support for tb procedures by the3_end of November 2012 to
avoid jeopardizing the pro cedurgTtnnplementation by de la y ft publication by more
than �-
a year beyond the planned 2'6 &dates; and ,.
WHEREAS, the NOC analyses andtcommunity engagement /fnfiormation sharingactivities were
accelerated and the planned stx month tirriefhr me was shortened to approximately
a month - and -a -half to aic�ntheVIAC's consideration of the procedures on the
FAA's requested timeline, a:nd,
WHEREAS, at the Noverrmpe��1��201 tinNVer one hundred residents
living n fMst of Ii11 P expressed passionate -cpn ern regarding the speed of the
process 'nd -1ack of PAA efforts to engage communities on the noise impacts of the
procedures, and `}
WHEREAS, .at theN¢uerpber 1 gam, 2012 MACfllCom'mission meeting, in consideration of the
residents"'16.oncerns;q.hF,-�k..MAC voted4b support the proposed STARs to all runways
-at MSP and the propose jSIDs off all runways except Runways 30L and 30R; and,
WHEREAS, smc�Lthe Novemo,Nd9, 2012 -MAC Commission meeting, NOC City
Representatives h�ye received increasing concerns from their constituencies
locatei southeast,and south of MSP regarding the possible noise impacts of RNAV
implementa'on on,feir neighborhoods; and,
WHEREAS, in February 201`4 the FAA determined the RNAV STARs can be implemented as
proposed and that the partial implementation of RNAV SIDs at MSP is not possible
for safety reasons; and,
WHEREAS, the FAA's proposed RNAV STARs integrate the use of Optimized Profile Descents,
are overlays of existing arrival paths, reduce noise impacts under the arrival paths,
and reduce fuel burn and associated emissions,
NOW THEREFORE BE IT RESOLVED, by the Noise Oversight Committee of the Minneapolis -
St, Paul International Airport that:
0
The NOC supports the following FAA actions related to any possible future RNAV SID. design
and implementation at MSP, and requests the MAC's support of the following provisions to be
communicated to the FAA:
1. The NOC remains supportive of the RNAV STARs as presented and the FAA should
move forward with the implementation of these procedures at MSP.
2, The FAA RNAV STAR procedures should incorporate Optimized Profile Descents for all
runways at MSP.
3: Prior to the commencement of any future RNAV SID design and implementation efforts
at MSP, the FAA must present to the NOC and the MAQ:a case study of the successful
implementation of RNAV at an airport with similar chalfendes to those existing at MSP,
which includes the airport's location adjacent to densbly'populated residential areas, The
case study should detail, how the FAA's propo .6 design and implementation plan for
MSP builds on the proven successes at the of ftimilarly situated airport.
4. Any future FAA RNAV SID design and 1 ntation plans: ;must, in addition to the
above, be structured in a way that me orates the provisions communicated in Mr. Jeff
Hamiel's February 1, 2013 letter to theAA,regarding future FAA community outreach
efforts related to RNAV implementation at! MSIP. ` w `L '
5. The NOC acknowledges the�,.AA will need adequate fime to prepare the iequested case
study and community outread nd as such4the FAA's future implementation of
RNAV SID could be delayed urn il.. aic study and uo treach plan are finalized.
Adopted by the Norse Qversight Colmittee oche Minneapolis -Sfi. Paul International
Airport this [INSERT D T ] ^day of [IN Ef f �NtDN [Hj
Representative
Vo:e
Oleson
.
Fields<
Petschel -
Quinc r ,_
Fitzhenr �,�'
�
Bergman i : = r h,z_
�<
t
Hart
Carlson :..
Erazo
Underwood
. _F..
McQuillan
Ryan
K
�f
FY
Resolution adopted by [INSERT VOTE],
10
Christene Sirois Kron, NOC Secretary
City of Evan
2013 -2014 Eagan Airport Relations Commission (ARC) Work Plan (Revised 3 -7-14)
Work Plan Topic
Presenters /Invited
Schedule (tentative)
Guests
Goals and Streets Alive Finalization
Tuesday, September 10,
• Make plans for Streets Alive booth
2013 ARC mtg
• Receive update on RNAV
• Finalize proposed ARC Goals and Work Plan for
December 2013 ,joint meeting with the City Council
Streets Alive (formerly Showcase Eagan)
Sunday, September 15,
• ARC to have booth at Streets Alive, including maps of
2013; 1 -4 p.m.
RNAV tracks if available), noise mitigation, etc.
Main Topic; The Economic Impact of MSP and an
Vicki Stute, DCR
Tuesday, November 12,
Introduction /Summary of efforts by the Noise Oversight
Chamber Director
2013 ARC mtg
Committee (NOC)
• Dana Nelson to provide an update on the 2013 NOC work
Brent Cory, ECVB
plan/aecomplishments
Director
• Ask the CVB and DCR Chamber to highlight the local
economic impact of MSP airport, including the impact on
Dana Nelson, MAC
the business coinnaunity and hospitality industry.
Noise Office
Joint meeting with the Eagan City Council
December 10, 2013
• Review proposed 2013 -2014 work plan
Council Wksp
• Discussion/Update on current airport issues
Tour r A A Air- n Traffic Control Center in Farmington
Tuesday, January' 14,
of oule
Finalize plans for Mareh open hoase CANCELLED
2014 ARC Mtg
DUE TO WEATHER
Tuesday, Mareh 11,
W1
fT�T2TT\ T 1; ti 4 T,. , lrn (FAA A_ 1A d /7 y jzn4pl
FAA Air Tra'(f
Comm--uni-e4e.impaetsofPBN(ifpa#W
Control Tower
ieVlemerAaaluen is approve 92013)
Mnn -age
Fecus the meefing On the impaets to
rN
Y- lai
FAA
rep a
p
*--Open house house to be eo Y-..,,,,- ity wide if PB N f fbeus5 if
PBN is not approved, then epen house ooW"e
• .... rn Y11, crF
Tour of FAA Air Route Traffic Control Center in Farmington
Tuesday, March 11,
• Finalize plans for May and July ARC meetings
2014 (Rescheduled due
to weather delay in
January)
2013 -2014 Airport Relations Commission Work Plan (Revised 3 -7 -14)
Page 2
State of the Airport Address
Jeff Hamiel, MAC
Tuesday, May .13, 2014
• Review fleet mix, operation counts /trends, and get
Executive Director
ARC mtg
update on 2020 Plan capital improvements
• Review 2013 Actual Noise Contour Report
Tammy Mencel, MAC
Commissioner
Regular ARC meeting and 2013 -2014 Goals /Work Plan
Tuesday, July 8, 2014
Workshop
ARC mtg
Ongoing ARC Efforts
Review at monthly ARC
• Monthly review of MAC teclvlical reports, including
meetings in 2013 -2014
Corridor compliance, fleet mix, and runway usage
• Receive feedback from the public on airport issues
• Review and provide feedback on NOC initiatives and
studies
• Ongoing communication efforts about airport issues via
Experience Eagan, City website, Facebook and cable TV
• Participation in MAC aviation disaster drills
iI