Laserfiche WebLink
<br />~ <br />~ <br /> <br />2 <br /> <br />Please forward your payment to one of the addresses listed below. <br /> <br />Using U.S. Postal Service: <br />Federal Emergency Management Agency <br />Fee-Charge System Administrator <br />P.O. Box 3173 <br />Merrifield, VA 22116-3173 <br /> <br />Using overnight service: <br />Fee-Charge System Administrator <br />c/o Dewberry & Davis, METS Division <br />840 I Arlington Boulevard <br />Fairfax, VA 22031 <br /> <br />We have completed an inventory ofthe items that you submitted. The items identified below are <br />required before we can begin a detailed review of your request. Please submit two copies of any <br />additional data required. <br /> <br />I. This proposed revision extends downstream into the City of Thornton. Please submit a letter from <br />the Chief Executive Officer (CEO), or designee, of the City of Thornton, stating they have <br />reviewed the proposed project and are in concurrence with the proposed changes to the FIRM. <br /> <br />2. Please submit a copy of the public notice distributed by your community stating its intent to revise <br />the regulatory floodway, or a statement by your community that it has notified all affected <br />property owners and affected adjacent jurisdictions. <br /> <br />3. Please submit letters from your community and the City of Thornton stating the modified <br />regulatory floodway will be adopted and enforced. <br /> <br />4. Please submit a set of as-built drawings for the portion of the project in the vicinity of 1-25. <br /> <br />5. Please submit an annotated FIRM at the scale of the effective FIRM showing the revised 100- and <br />500-year floodplain and the floodway boundaries, and how they tie-in to those shown on the <br />effective FIRM downstream and upstream of the revisions. <br /> <br />6. Please submit a set ofworkmaps showing the items listed on MT-2 Form 5. In particular, the <br />items left-off of the workmaps submitted include: The location and alignment of the cross <br />sections downstream of Section 200 and upstream of Section 4500; current community <br />boundaries; the effective 100-year floodplain and floodway boundaries from the FIRM reduced or <br />enlarged to the scale of the workmap; tie-ins between the effective and revised 100-, 500-year and <br />floodway boundaries; community easements; the signed certification of a registered professional <br />engineer; the location and description of reference marks; and the vertical datum of the workmap. <br /> <br />7. The profiles submitted are confusing (there appears to be multiple 500- and I OO-year profiles, with <br />some of these profiles below the 10-year profile). Please submit profiles for the 10-, 50-, 100-, <br />and 500-year flood events, at the scale of the profiles shown in the effective Flood Insurance <br />Study (FIS), that include the information listed on MT-2 Form 4. <br /> <br />8. A computer disk containing full input and output listings of the hydraulic models. The post- <br />project HEC-RAS model submitted will be reviewed for use in this revision, and the input and <br />output files are required (as well as files for the duplicate, corrected, and pre-project models). <br />However, the post-project conditions HEC-2 model submitted is erroneous and unnecessary, and <br />will not be used in this revision unless it reflects the as-built channel conditions. <br /> <br />9. The downstream starting water surface elevations (WSELs) of the hydraulic models do not tie-in <br />to the effective information. Please revise and resubmit the analysis. If necessary refer to the <br />Adams County and Incorporated Areas FlS for the correct starting WSELs. <br /> <br />10. The HEC-RAS post-project floodway model has surcharges (the difference in WSEL between the <br />floodway profile and the 100-year floodplain profile) greater than 1.00 foot at cross sections 10, <br />540,3000, and 3800, and surcharges less than 0.00 at cross sections 605, 800, and 4100. Please <br /> <br />Updated 6-11-01 <br /> <br />316-ACK.FRQ <br />