Aircraft activity over some Twin Cities communities recently has neighbors in those areas asking, “What’s going on?” During the past two months, many flights to and from Minneapolis-St. Paul International Airport (MSP) have been following flight paths and procedures in a south flow day after day, which is unusual, particularly during this time of year.
The MAC Noise Program Office sponsors quarterly Public Input Meetings for residents to receive updates on the Minneapolis-St. Paul International Airport (MSP) Noise Oversight Committee (NOC) and its activities, to be briefed on MSP operational levels and procedures, and to have an opportunity to provide comments on and voice concerns about aircraft noise issues.
The Metropolitan Airports Commission (MAC) voted to defer publication of the Minneapolis-St. Paul International Airport (MSP) Long-Term Comprehensive Plan (LTCP) during its board meeting on September 21, 2015. The decision to delay the document followed a MAC staff recommendation to complete the draft LTCP document after an evaluation of runway use data is conducted that includes results of an arrival procedure that is currently being evaluated by the Federal Aviation Administration (FAA) at MSP.
On Friday, August 27 the Federal Aviation Administration (FAA) announced that, weather permitting, it would begin allowing limited use of Runway 35 for arriving aircraft at Minneapolis-St. Paul International Airport (MSP) after having temporarily suspended arrivals on that runway a month ago due to changes in safety requirements.
The MSP Noise Oversight Committee (NOC) is an advisory board to the Metropolitan Airports Commission (MAC), and is comprised of industry and community representatives who address aircraft noise issues related to activity at the Minneapolis-St. Paul International Airport (MSP). The group meets bi-monthly on the third Wednesday of odd-numbered months.
On Friday, July 24, the Federal Aviation Administration (FAA) suspended certain operations at Minneapolis-St. Paul International Airport (MSP) - specifically, aircraft arriving on Runway 35 (over Apple Valley, Burnsville and Bloomington) when aircraft are also departing to the northwest and west (over Minneapolis and Richfield) off Runway 30L. This operation does not comply with the FAA’s converging runway requirement.
Selecting which runways to use for aircraft departures and arrivals at Minneapolis-St. Paul International Airport (MSP) is a complex task that falls under the responsibilities of Federal Aviation Administration (FAA) Air Traffic Control (ATC). Decisions about runway use at MSP are made carefully and continuously by ATC, taking into consideration numerous flight factors that include: safety, efficiency, wind direction and wind speed (on the surface and aloft), air traffic congestion, aircraft weight, the number of inbound and scheduled outbound aircraft, noise abatement, and others.
On May 7, 2015, the Federal Aviation Administration (FAA) announced it would begin evaluating its methods for measuring aircraft noise. For decades federal regulations prescribed a process under 14 CFR Part 150 for calculating aircraft noise impacts using the Day-Night Average Sound Level (DNL) metric.
The airfield at Minneapolis-St. Paul International Airport (MSP) is one of the busiest in the United States. Maintaining airfield features (i.e. runways, taxiways, aircraft parking surfaces, etc.) requires coordination of regularly-scheduled construction and/or maintenance tasks that involve pavement, painting, electrical work, signage, navigational aids, and area protection barriers.