My WebLink
|
Help
|
About
|
Sign Out
Home
1988 Correspondence
Ramsey
>
Public
>
Dissolved Boards/Commissions/Committees
>
Airport Commission
>
Correspondence
>
1988 Correspondence
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
12/27/2016 12:42:24 PM
Creation date
5/11/2010 12:48:51 PM
Metadata
Fields
Template:
Miscellaneous
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
30
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
2. Planning and reconfiguration of runway 16/34 to provide a 75' x <br />3,300' paved runway. <br />3. Development of a parallel and connecting taxiway system. <br />4. Obstruction removal. <br />5. Building area improvements to provide operating and tie -down aprons, <br />hangars, auto parking and airport related activities. <br />6. Relocate a portion County Road 116. <br />This proposed development is projected to handle 52 based aircraft, 37,000 <br />total annual operations, and 41,500 itinerant passengers by the year 2005. The <br />3,300' runway would be capable of serving most single engine and light twin <br />engine aircraft weighing less than 12,500 pounds. As proposed, the airport <br />would complement the regional system, and if successfully converted to <br />municipal ownership, would provide long-term capability to meet the local needs <br />of the Anoka/Ramsey/Elk River service area. The recommended airport layout <br />plan is shown in figure 1-2. Ultimate development costs; including relocation <br />of the 54 displaced residents and hangar development is estimated at $8,707,000 <br />dollars. <br />DISCUSSION <br />When the Metropolitan Council reviewed and commented on the draft Gateway <br />Master Plan in 1985 (referral 12993-1), several areas of concern were raised: <br />1. (LACK OF QUANTITATIVE EVALUATION IN REGARD TO ENVIRONMENTAL COMPA- <br />TIBILITY.) The EIAR does include an assessment of existing <br />and projected aircraft noise impacts. Figure 2-4 portrays the impact <br />area for the year 2005. Areas of LDN55 noise levels, reflecting <br />federal and local guidelines for compatibility with single-family <br />residential uses, are shown to be contained within the future airport <br />property limits.. <br />2. (NEED TO -ADDRESS LAND USE COMPATIBILITY ISSUES.) The focus of this <br />concern relates primarily to land use safety zoning and operational <br />hazards. Under Council policy and Mn/DOT requirements, there is a <br />need to control land uses in the runway approach zones. The EIAR <br />identifies these safety zones; determined the properties for <br />acquisition in Zone (A); established relocation requirements and <br />program; identified additional mitigation measures for Zone B, in <br />order to control nor. -residential land use and future residential <br />subdivision as shown in Figure.2-8. In safety zone C, the concern is <br />with height above ground of the existing land -fill, associated bird <br />hazards and, the new potential Anoka regional landfill (site P). In <br />1987 the City adopted an airport zoning ordinance to effectuate Mn/DOT <br />requirements for safety zones A, B, and C. This ordinance defines the <br />existing landfill (see Diagram A) as a prohibited incompatible use and <br />restricts its height to 1,020 feet above sea level. <br />The non -conforming use allows the landfill to reach its currently <br />permitted capacity, but prevents future permitting for expansion <br />purposes or new landfills. The EIAR addresses the implications of <br />this landfill development to airport development, birdstrike <br />mitigation pressures, and control of the landfills end-use to mitigate <br />operational hazards. Progress with proposed airport improvements and <br />enforcement of the related zoning ordinance may be effectively. <br />-2- <br />
The URL can be used to link to this page
Your browser does not support the video tag.