12.07.2015 Views

MCAS Miramar Airport Land Use Compatibility Plan - San Diego ...

MCAS Miramar Airport Land Use Compatibility Plan - San Diego ...

MCAS Miramar Airport Land Use Compatibility Plan - San Diego ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

APPENDIX EGENERAL PLAN CONSISTENCY CHECKLISTZoning or Other Policy Documents, Continued Open <strong>Land</strong> Requirements—<strong>Compatibility</strong> plan requirements,if any, for assuring that a minimum amount ofopen land is preserved for the airport vicinity must be reflectedin local policies. Normally, the locations whichare intended to be maintained as open land would beidentified on a map with the total acreage within eachcompatibility zone indicated. If some of the area includedas open land is private property, then policiesmust be established which assure that the open land willcontinue to exist as the property develops. Policies specifyingthe required characteristics of eligible open landalso must be established. Infill Development—If a compatibility plan contains infillpolicies and a jurisdiction wishes to take advantage ofthem, the lands which meet the qualifications must beshown on a map. Height Limitations and Other Hazards to Flight—Toprotect the airport airspace, limitations must be set onthe height of structures and other objects near airports.These limitations are to be based upon Part 77 of theFederal Aviation Regulations, but may include exceptionsfor objects on high terrain if provided for in thecompatibility plan. Restrictions also must be establishedon other land use characteristics which can cause hazardsto flight (specifically, visual or electronic interferencewith navigation and uses which attract birds). Notethat many jurisdictions have already adopted an airportrelatedhazard and height limit zoning ordinance which,if up to date, will satisfy this consistency requirement. Noise Insulation Requirements—Some compatibilityplans call for certain buildings proposed for constructionwithin high noise-impact areas to demonstrate that theywill contain sufficient sound insulation to reduce aircraftrelatednoise to an acceptable level. These criteria applyto new residences, schools, and certain other buildingscontaining noise-sensitive uses. Local policies must includeparallel criteria. Buyer Awareness Measures—As a condition for approvalof development within certain compatibility zones,some compatibility plans require either dedication of anavigation easement to the airport proprietor or placementon deeds of a notice regarding airport impacts. Ifso, local jurisdiction policies must contain similar requirements.<strong>Compatibility</strong> plans also may encourage,but should not require, local jurisdictions to adopt a policystating that airport proximity and the potential for aircraftoverflights be disclosed as part of real estate transactionsregarding property in the airport influence area. Nonconforming <strong>Use</strong>s and Reconstruction—Local jurisdictionpolicies regarding nonconforming uses andreconstruction must be equivalent to or more restrictivethan those in the compatibility plan, if any.REVIEW PROCEDURESIn addition to incorporation of ALUC compatibility criteria,local jurisdiction implementing documents must specify themanner in whish development proposals will be reviewed forconsistency with the compatibility criteria. Actions Always Required to be Submitted for ALUCReview—State law specifies which types of developmentactions must be submitted for airport land usecommission review. Local policies should either listthese actions or, at a minimum, note the jurisdiction’s intentto comply with the state statute. Other <strong>Land</strong> <strong>Use</strong> Actions Potentially Subject to ALUCReview—In addition to the above actions, compatibilityplan may identify certain major land use actions forwhich referral to the ALUC is dependent upon agreementbetween the jurisdiction and the ALUC. If the jurisdictionfully complies with all of the items in this generalplan consistency check list or has taken the necessarysteps to overrule the ALUC, then referral of the additionalactions is voluntary. On the other hand, a jurisdictionmay elect not to incorporate all of the necessary compatibilitycriteria and review procedures into its own policies.In this case, referral of major land use actions tothe ALUC is mandatory. Local policies should indicatethe jurisdiction’s intentions in this regard. Process for <strong>Compatibility</strong> Reviews by Local Jurisdictions—Ifa jurisdiction chooses to submit only the mandatoryactions for ALUC review, then it must establish apolicy indicating the procedures which will be used toassure that airport compatibility criteria are addressedduring review of other projects. Possibilities include: astandard review procedure checklist which includes referenceto compatibility criteria; use of a geographic informationsystem to identify all parcels within the airportinfluence area; etc. Variance Procedures—Local procedures for granting ofvariances to the zoning ordinance must make certainthat any such variances do not result in a conflict withthe compatibility criteria. Any variance which involvesissues of noise, safety, airspace protection, or overflightcompatibility as addressed in the compatibility plan mustbe referred to the ALUC for review. Enforcement—Policies must be established to assurecompliance with compatibility criteria during the lifetimeof the development. Enforcement procedures are especiallynecessary with regard to limitations on usage intensitiesand the heights of trees. An airport combiningdistrict zoning ordinance is one means of implementingenforcement requirements.Source: California <strong>Airport</strong> <strong>Land</strong> <strong>Use</strong> <strong>Plan</strong>ning Handbook (January 2002)E–2 <strong>MCAS</strong> <strong>Miramar</strong> <strong>Airport</strong> <strong>Land</strong> <strong>Use</strong> <strong>Compatibility</strong> <strong>Plan</strong> (Adopted October 2008)

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!