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

More documents

Recommendations

Info

AIRPORT LAND USE COMMISSION POLICIES CHAPTER 2(c)(d)(e)including a list and thorough description of the specific information needed tocomplete the application for a determination of consistency.(3) If the written response as to the completeness of the application is not made bythe ALUC within thirty (30) calendar days after receipt of the consistencyapplication, and/or after receipt of any additional information requested, theproject will be evaluated using the ALUCP in effect on the date of expiration ofthe thirty (30) calendar day time limit for determining completeness of theapplication materials submitted.(4) Nothing in this policy precludes a local agency and the ALUC from mutuallyagreeing, with the concurrence of the project owner, to an extension of any timelimit provided by this policy.Subsequent Review of Project(s) Found Consistent: A project previously reviewed by theALUC and found to be consistent with the compatibility plan in effect at the time ofthe project review shall not be subject to further review under a subsequently adoptedcompatibility plan unless the project changes in a substantive manner—as determined bythe local agency or by the ALUC when the ALUC concludes that further review iswarranted based on criteria provided in Policy 2.10.4(b)—that potentially wouldinvalidate the original ALUC consistency findings.(1) Any project requiring subsequent ALUC review will be evaluated using theALUCP in effect at the time the re-application was deemed complete by the localagency, unless the ALUC determines that such re-application lacks one or moreof the components required in Policy 2.7.2, in which case the project will beevaluated in accordance with Policies 2.3.2 (b)(2) through (4), inclusive, above.(2) Any project requiring subsequent ALUC review need not be resubmitted forALUC review if, prior to resubmission, the general plan of the local agency inwhich the project is situated has been reviewed by the ALUC and found to beconsistent with this Compatibility Plan; and the revised project is consistent withthat ALUC-approved general plan.ALUC Project Review Not Required: A project application which was deemedcomplete by the local agency prior to the effective date of this Compatibility Plan, andwhich did not require ALUC review because it was located beyond the boundary of theAIA defined by the compatibility plan in place at the time the application was deemedcomplete shall not require subsequent ALUC review under this Compatibility Plan, unlessthe project changes in a substantive manner (see Policy 2.10.4).Long-Term Project: Except as otherwise provided in Paragraphs (a) through (d) above,a long-term project, such as a master plan, large subdivision with several phases, orfunctionally comparable discretionary permit or action ("original long-term project"),and any subsequent discretionary or ministerial implementing permit or action for thatproject, shall be governed by the compatibility plan in effect at the time the first suchpermit or action for the project was issued by the local agency, provided all of thefollowing exist:(1) The project applicant has obtained from a local agency final approval of theoriginal long-term project prior to the effective date of this Compatibility Plan;(2) The local agency has obtained a consistency determination for the original longtermproject (for those local agencies where the General Plan is not consistentwith compatibility plan);MCAS Miramar Airport Land Use Compatibility Plan (Adopted October 2008 Amended December 2010) 2–7
CHAPTER 2AIRPORT LAND USE COMMISSION POLICIES(3) The original long-term project approval(s) remain(s) in effect;(4) Final approval of the original long-term project(s) was (were) obtained not morethan fifteen (15) years prior to the effective date of this Compatibility Plan;(5) The project applicant has used reasonable good faith efforts in proceeding withthe original long-term project, including without limitation, processing any othergovernmental permits and approvals necessary to implement the originalapproval(s) (such as preparing and processing any subsequent or additionalCEQA documents or resource agency permits), preparing architectural orengineering plans, or constructing infrastructure for the original approval(s), suchas roadways, storm drains, parks, sewer, water or other utilities;(6) The local agency has approved a related implementing permit or action for theoriginal approval(s) within five (5) years prior to the effective date of thisCompatibility Plan or the project applicant has an application on file that hasbeen deemed complete by the local agency for any related implementing permitor action as of the effective date of this Compatibility Plan; and(7) The original long-term project(s) has/have not changed in a substantive manner,as determined by the local agency or the ALUC (see Policy 2.10.4).2.4 TYPES OF AIRPORT IMPACTS2.4.1 Principal Compatibility Concerns: As established by state law (Pub. Util. Code, §21670), the ALUChas the responsibility both "to provide for the orderly development of airports" and "to preventthe creation of new noise and safety problems." ALUC policies thus have the dual objective ofprotecting against constraints on airport expansion and operations that can result fromencroachment of incompatible land uses and minimizing the public's exposure to excessivenoise and safety hazards.(a) In order to meet these objectives, this Compatibility Plan addresses potential Airportcompatibility impacts related to four specific airport-related factors/layers:(1) Noise—Exposure to aircraft noise;(2) Safety—Land use factors that affect safety both for people on the ground andthe occupants of aircraft;(3) Airspace Protection—Protection of Airport airspace; and(4) Overflight—Annoyance and other general concerns related to aircraftoverflights.(b) Compatibility policies concerning each of these factors/layers are enumerated inChapter 3. Each factor/layer is addressed separately. Proposed land use developmentactions must comply with the compatibility policies and maps for each compatibilityfactor/layer, as well as all policies in this chapter.2.4.2 Policy Objectives: For each compatibility factor/layer, specific policy objectives are as follows:(a) Noise: The purpose of noise compatibility policies is to avoid establishment of newsensitive land uses and exposure of the users to levels of aircraft noise that can disrupt theactivities involved. The characteristics of the Airport and the surrounding communityare taken into account in determining the level of noise deemed acceptable for eachtype of land use.2–8 MCAS Miramar Airport Land Use Compatibility Plan (Adopted October 2008 Amended December 2010)
Page 1: MCAS MiramarAirport Land UseCompati
Page 18 and 19: San Diego County Regional Airport A
Page 20 and 21: TABLE OF CONTENTS3.6 Overflight Com
Page 22 and 23: Chapter 1Introduction1.1 OVERVIEW O
Page 24 and 25: INTRODUCTION CHAPTER 1LimitationsTh
Page 26 and 27: INTRODUCTION CHAPTER 1guidance for
Page 28 and 29: INTRODUCTION CHAPTER 1implementing
Page 30 and 31: Chapter 2Airport Land Use Commissio
Page 32 and 33: AIRPORT LAND USE COMMISSION POLICIE
Page 52 and 53: Chapter 3MCAS MiramarPolicies and M
Page 54 and 55: MCAS MIRAMAR POLICIES AND MAPS CHAP
Page 56 and 57: MCAS MIRAMAR POLICIES AND MAPS CHAP
Page 58: MCAS MIRAMAR POLICIES AND MAPS CHAP
Page 61 and 62: CHAPTER 3MCAS MIRAMAR POLICIES AND
Page 73 and 74: CHAPTER 3 MCAS MIRAMAR POLICIES AND
Page 88 and 89:
CHAPTER 3MCAS MIRAMAR POLICIES AND
Page 91 and 92:
Chapter 4Background Data:MCAS Miram
Page 93 and 94:
CHAPTER 4BACKGROUND DATA: MCAS MIRA
Page 95:
Page 98 and 99:
BACKGROUND DATA: MCAS MIRAMAR AND E
Page 101 and 102:
Page 103:
Page 119 and 120:
A P P E N D I X AState Laws Related
Page 121 and 122:
STATE LAWS RELATED TO AIRPORT LAND
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
A P P E N D I X BFederal Aviation R
Page 163 and 164:
FEDERAL AVIATION REGULATIONS PART 7
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
A P P E N D I X CAirport Land Use C
Page 181 and 182:
AIRPORT LAND USE COMPATIBILITY CONC
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
A P P E N D I X DMethods for Determ
Page 195 and 196:
METHODS FOR DETERMINING CONCENTRATI
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
A P P E N D I XGeneral Plan Consist
Page 203 and 204:
A P P E N D I X FSample Implementat
Page 205 and 206:
SAMPLE IMPLEMENTATION DOCUMENTSAPPE
Page 207 and 208:
A P P E N D I XGOn-Line Implementat
Page 209 and 210:
APPENDIX HGLOSSARY OF TERMSAirport
Page 211 and 212:
APPENDIX HGLOSSARY OF TERMSEasement
Page 213 and 214:
APPENDIX HGLOSSARY OF TERMSNoise Le
Page 215:
APPENDIX HGLOSSARY OF TERMSregulati
show all

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

Create successful ePaper yourself

Delete template?

Save as template?