Flying Cloud Airport has been an airport in Eden Prairie since the 1940’s. It is now a MAC owned and operated airport. It is a reliever airport for the Minneapolis-St. Paul International (MSP) airport. It is classified as a general aviation airport. There are corporate jets, flying lessons, and other aviation businesses based at Flying Cloud, but there is no scheduled air passenger service or freight services there.
I would characterize Eden Prairie’s historical relationship with its local airport as, at best, “mixed”. When I arrived here in 2002 the City and the Metropolitan Airports Commission (MAC) were in the middle of a struggle that involved multiple lawyers on both sides and a high degree of anxiety about the future of Flying Cloud Airport. The essence of the struggle was MAC’s plans for the development and expansion of the airport. The MAC believed an expansion of the airport was necessary. The City, on behalf of the residential neighborhoods surrounding the airport, believed it was not. The conflict was set. Would the airport be allowed to expand, or not?
After years of struggle and many thousands of dollars spent on legal counsel by both sides, the City and MAC reached an agreement on the matter of airport expansion in December of 2002. The agreement, which is cleverly called the Final Agreement, required concessions from both sides. MAC agreed to implement mandatory and voluntary noise control measures, to abide by limits on future growth and expansion at Flying Cloud, to impose voluntary restrictions on certain aviation activities and to be generally more cooperative with the City about future development of Flying Cloud. The City agreed to withdraw its opposition (and not to assist third parties in their opposition) to two elements of MAC’s proposed Flying Cloud development plan: widening and lengthening the two principle runways and constructing a new hangar area on the south side of the airport.
There were also a number of other issues covered in the Final Agreement, such as special assessment costs, future road rights-of-ways, future residential development near the airport, park land commitments, water & sewer services, etc. But the issues having to do with airport expansion were clearly the most important. When the Council finally approved the agreement in December 2002, we had a nice signing ceremony and photo in the Council Chambers that included representatives from the City Council, MAC and Zero Expansion, the local citizens group concerned about airport growth at Flying Cloud.
The issue has jumped into the public view again recently because of a perception among residents concerned about the airport that something has changed in the City-MAC relationship and its impact on the future development of Flying Cloud. There has been a change. There’s no denying that. But the change started in 2002, not 2007. The change in the City’s relationship with the airport and MAC started when the City Council approved the Final Agreement, which recognized and consented to the MAC’s right to develop their airport in Eden Prairie. The Final Agreement also set into motion a new relationship between the City and MAC. This new relationship would be based on constructive engagement and partnership instead of distrust and suspicion. The belief behind the change in relationship was that the City could accomplish more good at less cost for residents with regard to the airport by having a good relationship with MAC than by having a bad relationship with MAC. I believe that to be true as well, and I can tell you that it has worked out that way over the past five years on numerous occasions.
I have been receiving a lot of letters and emails from residents expressing disappointment and concern about the City’s change of heart on the airport. A common theme in these communications is that the City must have “beat” the MAC back in 2002 because the airport never developed after the Final Agreement was signed, and that the current City Council is somehow caving into the MAC and allowing them to expand the airport. I would not at all say the City “beat” the MAC in the 2002 Final Agreement. It’s true that the airport has not developed as the MAC has hoped it would, but there are other reasons for that. I would say that the Final Agreement gives MAC the local governmental consent they need to do the two development projects when they decide its necessary to do them. No more. No less.
In an attempt to address some of the concerns I’ve been hearing, I prepared and submitted to the local newspapers an editorial article which I hope explains the City’s current and past positions on the airport. Take a look at it and let me know what you think:
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Airport Commentary
Scott Neal, City Manager
April 2, 2007
I read the papers. I can tell when someone is upset about something the City has done, or not done, as the case may be. I don’t often directly respond in the public sphere because, frankly, it’s difficult to do that without making the situation worse, not better. But I am going to respond publicly to the concerns about the City and Flying Cloud Airport because there is an information gap between the facts, the truth and the concerns I’ve been hearing from citizens.
Prior to December 2002, the City and the Metropolitan Airports Commission (MAC) were locked in a protracted struggle regarding the future of Flying Cloud Airport. The City spent hundreds of thousands of dollars on specialized aviation legal counsel to engage MAC on several legal fronts. But in December 2002, the struggle came to a peaceful conclusion with the City Council and MAC’s mutual approval of the Final Agreement. Among the many mutual commitments in the Final Agreement, the City agreed to withdraw its opposition to MAC’s plan to develop Flying Cloud Airport. MAC agreed to adopt and enforce mandatory and voluntary noise control measures, abide by limits on future growth and expansion, impose voluntary restrictions on certain aviation activities, and to be cooperative with the City regarding future development at Flying Cloud.
MAC’s development plan, as envisioned in the 2002 Final Agreement, includes expansion of the width and length of the two principle runways. It also includes development of a new hangar area on the south side of the airport, and the extension of City water and sewer services into the airport property. This development plan has been delayed several times since 2002 due to the downturn in the aviation economy and to MAC’s struggles with Northwest Airlines.
The current City Council supports the same MAC development plan for Flying Cloud that was supported and approved by the 2002 Council in the Final Agreement. The 2002 Council did not support a change in the functional classification of the airport. The 2007 Council also does not support a change in the airport’s functional classification. The 2002 Council supported the preservation of Flying Cloud as a local general aviation airport. The 2007 Council feels the same way.
The change people perceive is not one of outcome, but of strategy. The final outcome of the 2002 Final Agreement, as it concerns the development of the airport, is the same today as it was in 2002. Prior to 2002, the City’s strategy was to fight MAC. The thought was the City could achieve more benefits and concessions for its residents by challenging MAC in the courts. The Council’s approval of the Final Agreement in 2002 started a new strategy of positive engagement and partnership with MAC. The Council believed the City could achieve more benefit and consideration for residents from MAC by working more closely with it on airport development issues. I was a strong advocate for the change in strategy in 2002. I believe it has been a positive change for the City, for MAC and for Flying Cloud Airport.
Three weeks ago I was part of a City delegation including City Council Member Sherry Butcher and Fire Chief George Esbensen who traveled to Washington, DC to participate in the annual National League of Cities legislative advocacy conference. We briefed our congressional representatives on current federal issues that are impacting Eden Prairie. We addressed issues as varied as light rail transit, access to the Minnesota River Valley, Community Development Block Grant funding and, yes, Flying Cloud Airport.
We told the legislators of the more positive relationship between the City and MAC and of the City’s support for MAC’s 2002 development plan for Flying Cloud. We left each office with a copy of the City’s 2007 federal legislative agenda packet, which included a cover letter from me that referenced the City’s support of the “expansion” of the airport. It is important to note the context of this statement. I used the term to apply to the widening and lengthening of the runways, and the development of the new south side hangar area. Those are the only two things that are planned to “expand” under the 2002 Final Agreement.
MAC’s plans call for the runway projects to start in 2008, but these plans have been scheduled and then rescheduled before. What I can assure you of is this: the City’s strategic relationship with MAC has evolved, but the commitments made to Eden Prairie residents in the 2002 Final Agreement have not changed. The City Council supports improving and modernizing Flying Cloud Airport in a manner that does not compromise the quality of life for our residents.
-end-