13.07.2015 Views

Brown Field Municipal Airport Land Use Compatibility Plan

Brown Field Municipal Airport Land Use Compatibility Plan

Brown Field Municipal Airport Land Use Compatibility Plan

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

CHAPTER 4BACKGROUND DATA: BROWN FIELD MUNICIPAL AIRPORT AND ENVIRONSTable IV-3 Continued<strong>Airport</strong> Environs Information – <strong>Brown</strong> <strong>Field</strong> <strong>Municipal</strong> <strong>Airport</strong>Local Agency General <strong>Plan</strong>s (Continued)City of San Diego General <strong>Plan</strong> (2008) (Continued)DescriptionImplement the height standards used by FAA as defined by Code of FederalRegulations Title 14, Part 77 through development regulations and zoningordinances. (<strong>Land</strong> <strong>Use</strong> and Community <strong>Plan</strong>ning Element, p. LU-33)Require that all proposed development projects (ministerial and discretionaryactions) notify FAA in areas where the proposed development meets the notificationcriteria as defined by Code of Federal Regulation Title 14, Part 77.• Require that all proposed development projects that are subject to FAAnotification requirement provide documentation that FAA has determinedthat the project is not a Hazard to Air Navigation prior to project approval.• Require that <strong>Plan</strong>ning Commission and City Council approve anyproposed development that FAA has determined to be a Hazard to AirNavigation once state and ALUC requirements are satisfied.Evaluate the siting and expansions of airports, heliports, and helipads/helistops onthe basis of aviation and land use need and potential safety and noise impacts onexisting and planned surrounding land uses. (<strong>Land</strong> <strong>Use</strong> and Community <strong>Plan</strong>ningElement, p. LU-33)Submit all airport/heliport master plans and development plans to ALUC prior to CityCouncil adoption. (<strong>Land</strong> <strong>Use</strong> and Community <strong>Plan</strong>ning Element, p. LU-33)Coordinate with Navy and Marine Corps to ensure that future land use and General<strong>Plan</strong> community plan, specific plan, development regulations and zoning ordinancesamendments are consistent with the Air Installation Compatible <strong>Use</strong> Zone study formilitary air installations. (<strong>Land</strong> <strong>Use</strong> and Community <strong>Plan</strong>ning Element, p. LU-33)Encourage civilian and military airport operators, to the extent practical, to:• Ensure safe airport operations to minimize noise and safety concerns;• Purchase land within the airport runway protection zone, given availablefunding sources, to protect airport operations; and• Obtain avigation easements or deed restrictions from property ownerswithin the airport influence area to prevent air navigation obstructions andincrease awareness of aircraft operating overhead. (<strong>Land</strong> <strong>Use</strong> andCommunity <strong>Plan</strong>ning Element, p. LU-33)Encourage noise-compatible land use within airport influence areas in accordancewith federal and state noise standards and guidelines. (Noise Element, p. NE-14)Limit future residential uses within airport influence areas to the 65 dBA CNEL airportnoise contour, except for multiple-unit, mixed-use, and live work residential useswithin the San Diego International <strong>Airport</strong> influence area in areas with existingresidential uses and where a community plan and the <strong>Airport</strong> <strong>Land</strong> <strong>Use</strong> <strong>Compatibility</strong><strong>Plan</strong> allow future residential uses. (Noise Element, p. NE-14)4-25<strong>Brown</strong> <strong>Field</strong> <strong>Municipal</strong> <strong>Airport</strong> <strong>Land</strong> <strong>Use</strong> <strong>Compatibility</strong> <strong>Plan</strong>January 25, 2010

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

Saved successfully!

Ooh no, something went wrong!