Citizen Portal
Sign In

Get Full Government Meeting Transcripts, Videos, & Alerts Forever!

Get email alerts on the Stormwater Code Clarification topic

No spam. Unsubscribe anytime.

Emerald Isle committee debates clarifying '2‑foot fill' rule, considers BUA limits and site visits

Stormwater Committee · August 28, 2024
AI-Generated Content: All content on this page was generated by AI to highlight key points from the meeting. For complete details and context, we recommend watching the full video. so we can fix them.

Summary

At a Stormwater Committee meeting, members and builders debated ambiguous wording that can force engineered plans for any 2‑foot spot of brought‑in fill; they discussed build‑upon area limits, enforcement capacity and agreed to recommend code edits, schedule site visits and produce GIS inventories for planning review.

The Stormwater Committee in Emerald Isle spent its meeting reviewing a broadly written code provision that says "2 feet of fill" triggers an engineered plan and stormwater review, and debated whether that language should instead specify a 2‑foot elevation increase across the overall lot or a combined area threshold.

Chair opened the discussion by saying the code currently reads that bringing in "2 feet of fill" requires a sealed engineering document and suggested changing the trigger to "if it elevates the overall lot 2 feet or more, then it requires a stormwater plan." The change, members said, would prevent small, localized landscaping changes from automatically requiring a professional engineering submittal.

Why it matters: under Emerald Isle's current rules, projects that disturb 10,000 square feet or more and those that create over a specified built‑upon area often require an engineered plan and recorded maintenance obligations. Committee members and local builders said the literal 2‑foot wording risks pulling minor works — planter boxes, small grading — into a long technical review process that can take weeks while engineers prepare sealed documents.

Discussion highlights focused on three technical points: the vertical trigger (2 feet), the horizontal scale at which that trigger applies (one square foot versus hundreds of square feet), and a separate but related standard that all sites must demonstrate on‑site capture of a 2‑inch rainfall. One builder told the panel, "This island does not have a stormwater problem. This island has a groundwater problem," arguing much of the standing water reflects a high groundwater table rather than runoff from new construction. Engineers and other members pushed back, saying groundwater issues do not remove the need for consistent stormwater safeguards and that some developments have caused off‑site impacts.

State context and technical benchmark: committee members noted that state coastal stormwater rules apply to larger disturbances (the committee cited the 10,000 sq ft threshold) and that design commonly uses NOAA "1‑year, 24‑hour" rainfall curves (roughly 3.6 inches in the committee discussion) as a reference for higher‑tier designs. The committee's draft of Commissioner Brownlow's ordinance would apply engineered plan requirements to larger projects while using a town‑wide built‑upon area (BUA) limit (examples discussed included 25–35% depending on sub‑area) and retention/BMP standards for new development.

Enforcement and capacity: staff said projects with 1,000 sq ft or more of impervious surface must submit a stormwater plan; disturbance above 10,000 sq ft still triggers an engineered submission and deeded maintenance requirements. Several members raised concerns about staff capacity—planning and enforcement staff were described as roughly 1.5 full‑time equivalents—saying the community could see long review timelines if many small projects were forced into the sealed‑engineer pathway.

Next steps and committee direction: the panel agreed to pursue language that narrows the 2‑foot trigger (for example, coupling vertical change with a minimum affected area or tying review to a BUA threshold), to compile examples and a GIS inventory of vacant and redevelopment‑prone lots, and to schedule site visits (proposed for the September or October meeting) so members could inspect representative lots in the field. The committee will bundle its recommended code adjustments and forward them to the planning board and then to the board of commissioners for formal consideration. No formal vote on code language was taken at the meeting.

The committee also adjusted its meeting cadence to monthly and discussed specific dates for the fall calendar; members asked staff to circulate revised invites and the GIS materials before the next session.