In wake of MSP runway suspension, lawmakers demand further analysis of airport expansion plans

Delta airplane landing at MSP
Sen. Scott Dibble: “Before we get locked down on a big expansion plan at the airport … what are the implications?”

Seizing on the suspended use of a critical runway, nine Minnesota legislators are demanding more analysis of plans to expand Minneapolis-St. Paul International Airport and the impact of noise and pollution on nearby neighborhoods.

“Now that the runway cannot be used in the manner anticipated … communities should be engaged on next steps,” the Minneapolis legislators said in a letter to Metropolitan Airports Commission (MAC) Chairman Dan Boivin. “The longer term impacts are as yet unknown, but vitally important to the people we represent.”

The letter cited a July order by the Federal Aviation Administration suspending arrivals on runway 35 for safety reasons. The agency acted out of concern that planes aborting landings on the runway could fly into the path of flights departing from nearby runway 30L, one of two parallel runways that handle most of the traffic at the airport.

The FAA order, first reported by MinnPost, reduced landings from 90 to 60 an hour at the airport on days when weather conditions are such that runway 35 would normally be used. In August, the FAA relaxed that ban by allowing some landings on runway 35 when takeoffs aren’t occurring on runway 30L. That resulted in 75 landings an hour. But the agency hasn’t ruled out returning to the stricter prohibition.

“We are still evaluating the new procedure,” said FAA spokeswoman Elizabeth Cory.

The runway, roughly parallel to County Hwy. 77, handles flights arriving from the south of the airport over Burnsville, Apple Valley and Bloomington.

The 8,000-foot runway was conceived in the 1990s as a way to accommodate air traffic at MSP instead of replacing the airport with a larger one in Dakota County. Costing about $700 million, it was one of the state’s priciest public works projects when it opened in 2005, roughly as expensive as the Hiawatha light rail line. It’s considered in excellent condition.

The prospect that runway 35 will continue taking fewer landings than anticipated prompted the legislators to urge greater scrutiny of airport plans to spend about $2 billion to improve terminals and other facilities it says will be needed to handle a 24 percent increase in flights by 2035, from 412,000 last year.

‘Let’s slow this baby down’

“It would be imprudent to plan capital investments and a significant expansion of the airport based on incorrect assumptions,” said the letter, sent Aug. 31, which was signed by Sen. Scott Dibble, chairman of the Senate Transportation and Public Safety Committee, House Minority Leader Paul Thissen, Sen. Jeff Hayden, Sen. Patricia Torres Ray, and Reps. Frank Hornstein, Karen Clark, Susan Allen, Jean Wagenius and Jim Davnie.

“Let’s slow this baby down,” Dibble said in an interview Monday. “Before we get locked down on a big expansion plan at the airport … what are the implications?”

Boivin said Monday that the MAC hasn’t formally responded to the legislators but is hoping to set up meetings with some of them.

Boivin said he was generally aware that the FAA was looking at new procedures for airports with runways like 35 that sometimes route planes in the path of flights using other runways, “though I had no idea when they would address the issue and in what manner.”

“Other than the FAA, I do not believe anyone knew how and when they would act,” he said.

Airport spokesman Patrick Hogan defended the MSP plans for more flights, saying future traffic will still be less than what it was when traffic was at its peak a decade ago, before the economic downturn.

“MSP has adequate airfield capacity for the forecasted number of aircraft operations through 2035,” Hogan said. “There were more than 540,000 aircraft operations at MSP in 2004, when MSP had only three runways, and we forecast only 511,000 operations in 2035, with four runways to handle the traffic.”

He said the FAA’s current limits on runway 35 landings will reduce operations less than 2 percent of the year.

Runway map of MSP
Federal Aviation Administration
Arriving flights aborting a landing on runway 35 could fly north into the path of a plane departing from 30L.

“The new procedures will not significantly reduce capacity … nor will the new procedures have a major impact on aircraft noise,” he said.

The legislators are not so sure about that. They noted that the FAA’s statement suspending use of runway 35 signaled a potential shift in traffic patterns harmful to parts of south Minneapolis. “The July 31 statement says the FAA ‘may, at times restrict departures to only runway 30R’ over Minneapolis,” the lawmakers wrote. “This creates significant concern about the potential to concentrate noise over some Minneapolis residents.”

They also cited the problem with runway 35 to renew calls for a more elaborate environmental review of the increased traffic expected at the airport. Dibble and some other DFL legislators have pressed for an environmental impact statement on the plans instead of the environmental assessment proposed by airport officials.

“A thorough environmental review provides the opportunity to explain how air pollution, including those pollutants causing climate change, will be reduced while air traffic is increasing,” the letter said.

Hogan said the lesser review was adequate for the expansion planned.

Approved and halted

The FAA approved construction of runway 35 in 1998 on the condition that it would not be used for landings and takeoffs over Minneapolis except as a last resort. Runway 35 took up some traffic from runways 30L-12R, which route traffic over Minneapolis, when they were under construction in 2007.

Fitting the new runway into MSP’s cramped airfield, hemmed in by freeways and the Minnesota River, required it to be angled toward runway 30L traffic, but the federal government didn’t initially recognize a potential safety hazard.

“What on earth were they thinking at the time?” asked Dibble in the interview.

That thinking began to change in 2013, when the National Traffic Safety Board called on the FAA to alter flight patterns at airports with such “converging runways” to reduce risk of collisions when a plane aborts a landing and goes around for another try. The NTSB cited instances of “flight crews having to execute evasive maneuvers at low altitude to avoid collisions.” It did not identify any instances at MSP.

In January 2014, the FAA  issued new regulations dealing with converging runways at MSP and 16 other major U.S. airports.

“These intersecting paths pose potential risks if a landing aircraft discontinues its approach and must go around, crossing the departure flight path for the other runway,” the FAA said in its order this July. “This action could bring the airplane too close to an aircraft departing from the other runway, risking a mid-air collision.”

The agency noted in July that it had approved specific new plans for all airports but MSP — the only airport where the agency suspended landings on such a runway.

Comments (6)

  1. Submitted by Jim Million on 09/30/2015 - 12:09 pm.

    Contention Validated

    The approval process of runway 17/35 was highly contentious when proposed, resulting in a highly “restrictive covenant” regarding take-offs and landings over downtown and the northern suburbs. As noted in previous comment, these restrictions were valid then and are still.

    The MAC then basically bulldozed the opposition and poured itself into a corner, if you will, and now seems quite ready to challenge those protocols. After years of virtually no outbound traffic to the North, recent weeks have brought some regular departures overhead, seemingly not “weather related.”

    Is the MAC “pushing the envelope” by testing this covenant? What does FAA have to say today?

    Somebody needs to “talk to the tower” about this.

  2. Submitted by Jim Boulay on 10/01/2015 - 06:32 am.

    Blame Richard Anderson

    Bottom line, Northwest Airlines didn’t want a new airport out in Dakota County that would have allowed more competition. Anderson et al, controlled the debate with threats to move the hub if they built further out. Then it was a matter of fitting a square peg in a round hole with making the expansion work on the small footprint they have at MSP. The 35 runway was then shoehorned into that location. Plenty of people at the time pointed out the convergence of the flights from these runways and that there was a huge risk with this layout but it was the only way they could fit it into the boundries of the proper and still get a long enough runway. It was a bad decision THEN and even more so in hindsight NOW! I still can’t believe they are flying so close to the Mall Of America where 100,000 people are shopping on any weekend! MOVE IT LIKE THEY SHOULD HAVE 25 YEARS AGO!

    • Submitted by Adam Froehlig on 10/01/2015 - 07:39 am.

      It’s more than just that…

      An airport out in the boondocks (which would’ve been necessary just to have the space and to avoid even larger land costs) would’ve incurred HUGE transportation costs…both in terms of the infrastructure necessary for most of the Metro to get to the airport, plus the increase in time and cost for travelers to get there. As hemmed-in and noisy as the current airport is, it’s MUCH closer to most of the Metro than something way out in Rosemount would’ve been.

      • Submitted by Jesse S. on 10/01/2015 - 06:34 pm.

        Old and Tired

        The convenience argument really needs to fade away. It is not a good enough reason to justify the status quo. We always talk about convenience and the safety of the air travelers, but we completely disregard the health, safety, and well-being of the residents below.

        Also, this issue really isn’t exclusive to housing “near the airport”, because as we all know, airplanes fly around in the sky. As someone who’s tried to find decent housing in the south metro (because I’ve always worked in the area and am trying to avoid adding to the traffic issue by commuting), it’s quite hard to find a house that’s not significantly impacted by airplane noise (in addition to freeway noise, and so on) that’s not out past the 494 belt.

  3. Submitted by Ray Schoch on 10/01/2015 - 06:49 am.

    Just a thought

    If airport expansion becomes a genuine issue, instead of yet another kerfluffle over not much, local officials might want to consider Denver. It won’t happen, for a variety of economic reasons, but if local residents and legislators are genuinely serious about complaints regarding airport noise, one solution would be to move the airport, which is what they did in Denver. The existing airport was inside, but at the edge of, the city, much like Minneapolis, and it was subject to constant noise complaints, not to mention the visual impact, for drivers on I-70, of tunneling under the main runway, with big jets rolling across one’s field of vision.

    Their solution was to build a new airport, about 20 miles northeast of downtown Denver on a gentle ridge surrounded by prairie, and at least a dozen miles from any existing residential areas. If you live on the west side of metro Denver, it’s a 45-minute drive, one way – on the highway, not city streets – to the airport.

    There’s plenty of farmland left in the 7-county Twin Cities metro area, including Hennepin County, that might be quite suitable for such a move, and it might well be less expensive than buying out existing neighborhoods to facilitate expansion. Denver’s former airport is now a thriving “new urbanist” mixed-use neighborhood, and the new airport, already huge, has room to expand further if necessary.

    That said, you can’t fix stupid, so shortsighted decisions by local officials and developers in metro Denver have allowed new residential development near the new airport, where people who live in new housing built at the edge of airport property are now… complaining about the aircraft noise.

    Having lived less than a mile from the end of the main runway at Lambert Field in St. Louis for many years, my sympathy for those complaining about the noise is limited. My impression is that, in many instances, the neighborhoods affected were built up AFTER the airport already existed – that is/was the case in St. Louis, where Lambert Field is landlocked – so residents who don’t like noise apparently bought or rented their homes without considering the outside environment. I do understand the problem, but if you truly can’t stand the noise, the logical response is to avoid housing near the airport.

    • Submitted by Jim Million on 10/01/2015 - 10:00 am.

      Too True

      When I once lived in Uptown, Friday afternoons brought air traffic in over the lakes at five-minute intervals. That was 1972. A recent mid-week visit to that old neighborhood prompted me to note current inbound traffic, seemingly no more than one minute apart after all these years of runway extension/expansion.

      Indianapolis, with seemingly sensible vision, built its new airport well south of downtown. Today, many people live in newly adjacent housing. Fargo built its terminal well west of town, but not far enough to prevent West Fargo from expanding right up to the fences, it seems. In the meantime, St. Cloud airport withers.

      Rational planning seems only a short-term alleviation, not a solution. Perhaps a boldly irrational plan is in order, whatever that might be.

Leave a Reply