13.07.2015 Views

underline-strikeout version of the final draft ordinance - Pima County ...

underline-strikeout version of the final draft ordinance - Pima County ...

underline-strikeout version of the final draft ordinance - Pima County ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

For May 4, 2010 BOS HearingTHIS THE CLERK OF THE BOARD FORMAT!!!iii4) . The certified opening elevationflood vent certification required in Chapter 16.20;.iv. The floodway encroachment certification required in Chapter 16.24v. The certifications <strong>of</strong> elevation required for additional development standards, includingsubdivisions required in Chapter 16.36vi. A record <strong>of</strong> all variance actions, including justification for <strong>the</strong>ir issuance, and report suchvariances in <strong>the</strong> biennial report submitted to FEMA; andvii. All improvement calculations used to determine substantial improvement.c. Whenever a federally regulated watercourse is to be altered or relocated, provide notificationas required by this title.B. The Chief Engineer is responsible forauthorized to:1. Interpretation <strong>of</strong> this title and associated technical flood and watercourse documents includingfloodplain maps and riparian habitat maps identified within this title;2. Establishment <strong>of</strong> engineering standards and guidance manuals, as necessary for activitiesregulated by this title;3. Administration Administer <strong>of</strong> appeals requesting waivers or modifications to engineeringstandards and guidance manuals and administrative interpretation as provided within provisions<strong>of</strong> this title. Appeals to <strong>the</strong> Chief Engineer shall follow <strong>the</strong> requirements <strong>of</strong> 16.56.010;4. Make tTechnical interpretations including base flood data and elevations consistent withfederal and state floodplain management requirements;.5. Take actions Render <strong>final</strong> decisions and orders on violations <strong>of</strong> this <strong>ordinance</strong> as required inChapter 16.64 herein.C. The Board is responsible forauthorized to:1. Adoption <strong>of</strong> rules and bylaws for enforcement <strong>of</strong> regulation <strong>of</strong> floodplains, erosion hazardsand riparian habitats,2. Hearing requests for variances from <strong>the</strong> regulations to <strong>the</strong> extent permitted by A.R.S. Section48-3609,3. Hearing requests for appeals <strong>of</strong> written findings decisions <strong>of</strong> <strong>the</strong> Chief Engineer; and4. Exerciseing all powers and duties to carry out regulatory functions, as required by A.R.S.Section 48-3603, including establishment <strong>of</strong> a fee schedule for <strong>the</strong> review <strong>of</strong> applications forpermits and variances from, or interpretations <strong>of</strong>, <strong>the</strong> provision <strong>of</strong> this title.D. The Technical Review Committee may be requested by <strong>the</strong> Chief Engineer, or <strong>the</strong> Board, toprovide technical review and recommendations on complex technical issues for administration,compliance and enforcement <strong>of</strong> this title.(Ord. 2010 FC-1; Ord. 2005 FC-2 § 2 (part), 2005)16.54.030Compliance.A Compliance mechanisms: Title compliance is sought through:1. A review procedure for floodplain use permits, subdivision plats, development plans and o<strong>the</strong>rplans;2. A permitting system that will deny <strong>the</strong> issuance <strong>of</strong> a permit if <strong>the</strong> proposed activity conflictswith title requirements;3. An enforcement system that will provide for compliance and enforcement <strong>of</strong> <strong>the</strong> title; and4. An organizational structure that identifies specific <strong>of</strong>ficers and employees empowered toadminister <strong>the</strong> above methods <strong>of</strong> compliance. (Ord. 2005 FC-2 § 2 (part), 2005)74

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

Saved successfully!

Ooh no, something went wrong!