Browse
Search
ORD-2005-127 - Revisions to the Flood Damage Prevention Ordinance
OrangeCountyNC
>
Board of County Commissioners
>
Ordinances
>
Ordinance 2000-2009
>
2005
>
ORD-2005-127 - Revisions to the Flood Damage Prevention Ordinance
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
4/29/2013 11:54:17 AM
Creation date
11/19/2010 4:12:43 PM
Metadata
Fields
Template:
BOCC
Date
9/20/2005
Meeting Type
Regular Meeting
Document Type
Ordinance
Agenda Item
5m
Document Relationships
Agenda - 09-20-2005-5m
(Linked To)
Path:
\Board of County Commissioners\BOCC Agendas\2000's\2005\Agenda - 09-20-2005
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
48
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
More <br />specificity as <br />per NC <br />Flood Act of <br />2000 <br />09/15/2005 19 <br />h. If the Floodplain Administrator issues a floodplain development permit for placement of <br />recreational vehicles and/or temporary structures, documentation to ensure compliance <br />with Section 42 -92(4 and 7) of this Ordinance. <br />If a watercourse is proposed to be altered and/or relocated, a description of the extent of <br />watercourse alteration or relocation, an engineering report on the effects of the proposed <br />project on the flood- carrying capacity of the watercourse and the effects to properties <br />located adjacent both upstream and downstream; and a map, drawn to scale, (f not <br />shown on plot plan) showing the location of the proposed watercourse alteration or <br />relocation. <br />2. Floodplain Development Permit Data Requirement The following information shall be <br />provided at a minimum on the floodplain development permit to ensure compliance with this <br />Ordinance. <br />a. A description of the development under the floodplain development permit issuance. <br />b. The SFHA determination for the proposed development per available data specified in <br />Section 42 -37. <br />c. The regulatory flood protection elevation required for the reference level and all <br />. attendant utilities. <br />d. The regulatory flood protection elevation required for the protection of all public <br />utilities. <br />e. All certification submittal requirements with timelines. <br />f. A statement that no fill material shall encroach into the jloodway or non - encroachment <br />area of any watercourse, if applicable. <br />g. Yin an A, AO, AE or AI-3 O zone, specify the minimum foundation opening requirements <br />h. State limitations of below BFE enclosure uses (if applicable) such as, parking, building <br />access and limited storage only). <br />3. Certification requirements <br />a. An Elevation Certificate (FEMA Form 81 -31) or Flood Proofing Certificate (FEMA <br />Form 81 -65) is required after the reference level is completed. Within twenty -one (21) <br />calendar days of establishment of the reference level elevation, or flood proofing, by <br />whatever construction means, whichever is applicable, it shall be the duty of the permit <br />holder to submit to the Floodplain Administrator a certification of the elevation of the <br />reference level, or flood proofing elevation, whichever is applicable, in relation to mean <br />sea level. Said certification shall be prepared by, or under the direct supervision of, a <br />North Carolina licensed professional Land Surveyor or Professional Engineer and <br />certified by them. Any work done within the twenty -one (21) day calendar period and <br />before submission of the certification shall beat the permit holder's risk The floodplain <br />administrator shall review the certificate data submitted. Deficiencies detected by such <br />review shall be corrected by the permit holder immediately and before further work being <br />
The URL can be used to link to this page
Your browser does not support the video tag.