My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
Draft EUG Master Plan Update, February 2010
COE
>
City of Eugene
>
Ordinances
>
2010 No. 20450-20469
>
Ordinance No. 20463
>
Draft EUG Master Plan Update, February 2010
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/29/2010 5:36:43 PM
Creation date
9/29/2010 5:35:49 PM
Metadata
Fields
Template:
Council Ordinances
CMO_Document_Number
20463
Document_Title
Draft EUG Master Plan Update, February 2010
Adopted_Date
9/27/2010
Approved Date
9/27/2010
Signer
Kitty Piercy
Jump to thumbnail
< previous set
next set >
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
218
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
CHAPTER 6 <br />LANDUSECOMPATIBILITY <br />3. Land Acquisition <br />As properties around the Airport become available, and as the Airport's priorities are developed, <br />consideration should be given to land acquisition. The RPZs for Runway Ends 16R and 16L extend to <br />parcels not owned by the Airport. Parcels in the RPZ, and other parcels near runway ends, are <br />candidates for acquisition, as Airport control of these parcels allows for protection of aircraft operation and <br />for people and property on the ground. Acquisition of RPZ parcels has generally been an FAA priority. <br />Consideration should be given to the total acquisition of a parcel, as compared to the acquisition of only a <br />conditional use, restriction, or height protection, often in the form of an easement. The Airport may <br />benefit from leasing interests in a parcel, as opposed to purchasing that parcel. <br />Parcels may also be acquired to allow the Airport to facilitate desired development, and to better control <br />development around the Airport. The parcel located at the southwest corner of the intersection of <br />Douglas Drive and Airport Road may be such a parcel. The Airport Layout Plan shows the Airport's <br />existing property, as well as parcels to be considered for acquisition. <br />As a parcel is being evaluated by the Airport for acquisition, consideration should be given to the parcel's <br />functional opportunity, revenue possibility, and environmental conditions. Consideration should also be <br />given to the parcel's land use designation, including the designation's compatibility with the Airport's <br />intended purpose for that parcel, and the possibility and impact of changing that designation, before or <br />after acquisition. <br />4. Summary of Recommendations <br />Proper protection and use of off-airport properties are and will remain paramount in preserving the safety <br />and operational utility of the Airport. Proper land use compatibility planning now will allow the Airport to <br />continue to operate into the future, and to connect the City of Eugene and Lane County to the rest of the <br />world. <br />Conduct a detailed analysis of existing land use protection measures and what changes may be <br />required to accommodate future airport improvements (Section 1.5). <br />Prepare Property Acquisition Plan (Section 1.5). <br />Acquire properties for RPZ protection (Section 1.5.1 and 3). <br />Coordinate changes to Part 77 surfaces with Lane County’s Commercial Airport Safety <br />Combining Zone (Section 1.5.3). <br />Acquire land within the 55 DNL noise contour where feasible (Section 2.3). <br />Prevent land being from rezoned to residential, or being used for “noise sensitive” purposes <br />within Lane County’s Commercial Airport Safety Combining Zone (Section 2.3). <br />Submit a noise impact boundary and protections for the next five, ten and twenty years to the <br />Oregon Department of Environmental Quality. <br /> <br />6-17 <br />Eugene Airport Master Plan Update <br />(February 2010) <br /> <br />
The URL can be used to link to this page
Your browser does not support the video tag.