My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
INSPEC30002
DRMS
>
Back File Migration
>
Inspection
>
INSPEC30002
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
8/24/2016 9:33:11 PM
Creation date
11/18/2007 10:24:02 AM
Metadata
Fields
Template:
DRMS Permit Index
Permit No
C1981008
IBM Index Class Name
Inspection
Doc Name
Inspection Report
Inspection Date
7/11/2006
Media Type
D
Archive
No
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
8
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
.> <br />III. COMMENTS -COMPLIANCE <br />Below are comments on the inspection. The comments include discussion of observations <br />made during the inspection. Comments also describe any enforcement actions taken during <br />the inspection and the facts or evidence supporting the enforcement action. <br />(flow in ditch had apparently passed through the culvert without over-topping). <br />Abatement of Breach #2a will need to include verification that collection ditch is adequately <br />sized, or excavation to provide proper design capacity (operator indicated that ditch would be <br />enlarged). Further abatement will need to include grading of gullies at toe of slope inside permit <br />boundary and associated stabilization seeding, and cleanout of sediment in and adjacent to <br />county road ditch to restore design capacity and function. <br />Breach #2b <br />This apparently smaller breach occurred approximately 50 yards east of #2a. Ditch was substantially <br />deeper in this location; measured 20" deep and approximately 128" wide. There was no significant <br />erosion at this location, but a ditch segment along the county road in the flow path from the breach was <br />silted in. There was a skim of deposition that extended only part of the way across the county road. <br />There was a hog pen located south of the county road; no discernible impact from the ditch breach <br />south of the road. Photo # 2601 shows #2b location. <br />Abatement of Breach #2b will need to include verification that ditch is adequately sized, and <br />maintenance of county road ditch segment impacted by breach to restore design capacity and <br />function. <br />Breach #3 <br />This breach occurred on the Sediment Pond #8 collection ditch, which runs along the east side of <br />County Road 2700, north of Pond #8. The breach occurred approximately 30 to 40 yards north of the <br />inlet of the 18" CMP culvert that conveys ditch flow into Pond #8. The culvert outlet is submerged <br />beneath the surface of the pond. Back-up of water at the culvert inlet may have caused the breach. The <br />ditch is a wide grass lined channel, measured to be approximately 200" wide and 12-14" deep at the <br />point of the breach. <br />At the point where the ditch was over-topped, a flow path of matted grass 25' to 30' wide was evident. <br />Flow that escaped the collection ditch flowed south between the ditch and 2700 Road down to a <br />location immediately west of the Pond 8 embankment. This is the bottom of a draw which runs to the <br />west. At this location there was sediment deposition in the county road ditch, and a culvert under the <br />road may have been covered over (presence of culvert was not verified during the inspection). There <br />was a skim of sediment across the county road, leading to a stock pond on private property <br />immediately west of 2700 Road. The stock pond was full to the level of the emergency spillway. It <br />was evident from matted grass that the spillway had recently flowed, but there was no evidence of <br />erosion or sediment deposition of the spillway or downstream along the draw below the stock pond. <br />The stock pond embankment appeared to be stable, with no evidence of breaching. <br />5 <br />
The URL can be used to link to this page
Your browser does not support the video tag.