25.12.2014 Views

Middle St. Johns - Florida Department of Environmental Protection

Middle St. Johns - Florida Department of Environmental Protection

Middle St. Johns - Florida Department of Environmental Protection

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

184<br />

Water Quality Assessment Report: <strong>Middle</strong> <strong>St</strong>. <strong>Johns</strong><br />

Total Maximum Daily Load Development<br />

During Phase 3 <strong>of</strong> the watershed management cycle, TMDLs will be<br />

developed for both point and nonpoint sources <strong>of</strong> pollutants in impaired<br />

waterbodies and will be adopted by rule at the end <strong>of</strong> this phase.<br />

TMDL development involves determining the maximum amount <strong>of</strong><br />

a given pollutant that a waterbody can assimilate and still meet the applicable<br />

numeric or narrative water quality criterion for the pollutant. In<br />

most cases, this “assimilative” capacity will be determined using computer<br />

modeling (both hydrodynamic and water quality models) that predicts<br />

the fate and transport <strong>of</strong> pollutants in the receiving waters. Modeling for<br />

the typical TMDL will include model setup, calibration, and verification,<br />

followed by a variety <strong>of</strong> model runs that determine the assimilative capacity<br />

<strong>of</strong> the water under worst-case conditions.<br />

<strong>St</strong>ate law and federal regulations require that TMDLs include a margin<br />

<strong>of</strong> safety (MOS) that takes into account “any lack <strong>of</strong> knowledge concerning<br />

the relationship between effluent limitations and water quality.” The EPA<br />

has allowed states to establish either a specific MOS (typically some percentage<br />

<strong>of</strong> the assimilative capacity) or an implicit MOS based on conservative<br />

assumptions in the modeling. To date, the <strong>Department</strong> has elected to<br />

establish an implicit MOS based on predictive model runs that incorporate<br />

a variety <strong>of</strong> conservative assumptions (they examine worst-case ambient<br />

flow conditions and worst-case temperature, and assume that all permitted<br />

point sources discharge at their maximum permitted amount).<br />

It is important to note that TMDLs will be developed only for the<br />

actual pollutants causing the impairment in the listed waterbody. These are<br />

called the “pollutants <strong>of</strong> concern.” In <strong>Florida</strong>, the most commonly listed<br />

pollutants <strong>of</strong> concern are nutrients, sediments, and coliforms. TMDLs<br />

will not be developed for impairments not due to pollutant discharges—for<br />

example, natural conditions, physical alterations such as dams and channelization,<br />

or changes in the flow <strong>of</strong> the water. In other cases, a waterbody<br />

may be deemed potentially impaired based on bioassessment data or toxicity<br />

data. In these cases, the <strong>Department</strong> must determine the actual pollutant<br />

causing the impairment before a TMDL can be developed.<br />

Total Maximum Daily Load Allocation and<br />

Implementation<br />

Initial Allocation <strong>of</strong> Pollutant Loadings<br />

The <strong>Florida</strong> Watershed Restoration Act (FWRA) requires that a<br />

TMDL include the “establishment <strong>of</strong> reasonable and equitable allocations<br />

. . . among point and nonpoint sources . . . .” The <strong>Department</strong> refers to<br />

this as the “initial allocation,” which is adopted by rule. For the purposes<br />

<strong>of</strong> allocating the required pollutant loadings, the term “point sources”<br />

primarily includes traditional sources such as domestic and industrial<br />

wastewater discharges.

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

Saved successfully!

Ooh no, something went wrong!