WHATS ASSUMABLE? DSL PROPOSAL MAY 9, 2012 Defining Assumable - - PowerPoint PPT Presentation

what s assumable
SMART_READER_LITE
LIVE PREVIEW

WHATS ASSUMABLE? DSL PROPOSAL MAY 9, 2012 Defining Assumable - - PowerPoint PPT Presentation

WHATS ASSUMABLE? DSL PROPOSAL MAY 9, 2012 Defining Assumable Waters for 404 Assumption in Oregon Who Gets to Decide? You. Offer a fully-formed proposal as best approach for starting conversation. Use CWA, Section 404 (g)(1) as


slide-1
SLIDE 1

WHAT’S ASSUMABLE? DSL PROPOSAL MAY 9, 2012

Defining Assumable Waters for 404 Assumption in Oregon

slide-2
SLIDE 2

Who Gets to Decide?

You.

 Offer a fully-formed proposal as best approach for starting

conversation.

 Use CWA, Section 404 (g)(1) as foundation for State’s

proposal.

 Outcome is codified in MOA between DSL and Corps.

Goal: Define non-assumable waters in a way that minimizes case-by-case determinations and maximizes applicant’s ability to self-identify need for a 404 permit using web tools.

slide-3
SLIDE 3

CWA 404 (g) (1)

The Governor of any State desiring to administer its own individual and general permit program for the discharge of dredged or fill material into the navigable waters (other than those waters which are presently used, or are susceptible to use in their natural condition or by reasonable improvement as a means to transport interstate or foreign commerce shoreward to their ordinary high water mark, including all waters which are subject to the ebb and flow of the tide shoreward to their mean high water mark, or mean higher high water mark on the west coast, including wetlands adjacent thereto), within its jurisdiction may submit to the Administrator a full and complete description of the program it proposes to establish and administer under State law or under an interstate compact. In addition, such State shall submit a statement from the attorney general (or the attorney for those State agencies which have independent legal counsel), or from the chief legal officer in the case of an interstate agency, that the laws of such State, or the interstate compact, as the case may be, provide adequate authority to carry out the described program.

slide-4
SLIDE 4

Breaking That Down…

 Non-assumable waters include:

1.

Waters subject to ebb & flow of tide (incl. ocean)

2.

Waters currently used for interstate/foreign commerce

3.

Waters susceptible to use for interstate/foreign commerce (in natural condition or w/reasonable improvement)

4.

Wetlands adjacent to 1-3, above.

slide-5
SLIDE 5
  • 1. Waters Subject to Ebb/Flow of Tide

Proposal:

 Length: Up to the head of tide

 DSL heads of tide survey, 1989

  • OR -

 Point where the waterway exits a mapped (Scranton

2005) tidal wetland

 Whichever is further upstream.  Use direct observation for lower Columbia R. tributaries

unless Corps has mapped the reach of tide in those lower tribs.

slide-6
SLIDE 6
slide-7
SLIDE 7
slide-8
SLIDE 8
slide-9
SLIDE 9

The Proposal

slide-10
SLIDE 10

Non Assumable Water Type per 404 (g)(1) Limit Proposed Data Source for Defining the Limit Waters subject to the ebb and flow

  • f tide (incl. Pacific Ocean)

Length: head of tide Tidal waterway up to the mapped head of tide (“Heads of Tide for Coastal Streams in Oregon”, DSL, March 1989)

  • OR -

Point where the waterway exits mapped Tidal Wetland area (Adamus, Larsen, Scranton, 2005 ) Whichever is further upstream. (Datasets do not extend to tidal tributaries of the lower Columbia River, therefore, direct observation of tidal influence will be the determinant here.) Elevation: Mean higher high water (MHHW) line DLCD mapping of MHHW elevation where available. Otherwise use standard tools to identify MHHW:

  • Nearest tidal station data
  • On-site tidal gage
  • Field indicators
slide-11
SLIDE 11

Waters currently used for interstate/foreign commerce Length: federally established navigational limit “Navigable Riverways Within the State of Oregon” and “Navigable Harbors and Bays Within the State

  • f Oregon”, US Army Corps of

Engineers, October 1993; and as interpreted by DSL mapping, 2012 Elevation: Ordinary high water line (inland) or mean higher high water line (tidal) DLCD mapping of MHHW elevation where available. Otherwise use standard tools to identify MHHW:

  • Local gage/tidal station data
  • Field indicators
  • Corps published OHW

elevations for Columbia R. and Willamette R.

slide-12
SLIDE 12

Waters susceptible to use interstate/foreign commerce (either in natural condition or w/reasonable improvement) To be determined as such waters may be identified by the Corps in future. Wetlands adjacent to tidal and navigable waters Coastal areas: Tidally- influenced wetlands Mapped Tidal Wetlands (Adamus, Larsen, Scranton, 2005 )1 (Dataset does not extend to lower Columbia River or its tidal tributaries, therefore, use 1,000 foot buffer) Inland areas: Activity in wetlands within 1,000 feet of the

  • rdinary high water

line of the navigable waterway(similar to New Jersey’s agreement with New York District) 1,000 foot buffer parallel to the ordinary high water line of the mainstem of the navigable waterway.

slide-13
SLIDE 13
  • 1. Waters Subject to Ebb/Flow of Tide

Proposal:

 Elevation: Mean higher high water (MHHW) line

DLCD mapping when available Standard tools elsewhere:

 Tidal station data  On-site tidal gage  Field indicators

slide-14
SLIDE 14

New Jersey MOA with Corps North Atlantic District

 404(g)(1) is quoted verbatim  “Adjacent wetlands” defined as: wetlands partially or totally within 1,000

feet of OHW or MHW. Line drawn parallel with the river/waterbody.

 Tidal waters are defined using head of tide maps.  Non-assumed waters specifically identified as:  Full length of Delaware R.  Tidal water bodies to the head of tide  Greenwood Lake  Any waterway served by an existing or proposed federal navigation

project – Corps district to provide list of those projects and updates as necessary

 Modification process identified for future navigability determinations by

fed.

slide-15
SLIDE 15

Michigan MOA with Corps North Central District

 404(g)(1) is quoted verbatim.  Reference to appendix for list of navigable waters  Waterways in the appendix are specified as

“navigable throughout” or from mouth to a specified point.

 List additionally states that “All federal navigation

projects are navigable waters of the U.S. to upstream and/or landward limit of project”.

slide-16
SLIDE 16
slide-17
SLIDE 17
  • 2. Waters Currently Used for Interstate
  • r Foreign Commerce – Proposal:

 Corps Portland District published 1993 list of

navigable waters

 Assume list is “currently” navigable waters unless Corps

will identify and remove historically navigable waters

 124 waterways = 1,470 miles (excl. ocean); 50% of

that is Columbia + Willamette + Snake

 DSL has mapped these waters.

slide-18
SLIDE 18
slide-19
SLIDE 19
  • 3. Waters Susceptible to Use for

Interstate or Foreign Commerce

 Unclear if Portland District’s 1993 list of navigable

waters includes “susceptible” waters.

 How should we handle this? Acknowledge that it is

a non-assumable water type and add to the non- assumable list if or as the Portland District may chose to identify “susceptible” waters.

slide-20
SLIDE 20
  • 4. Adjacent Wetlands – Proposal:

 Wetlands Adjacent to Tidal Waters: Use mapped tidal

wetlands (Scranton, 2005)

 Highly defensible  Well defined for coastal region

 Wetlands Adjacent to Non-tidal Waters: 1,000 foot buffer

parallel to ordinary high water line of navigable waterway.

 Discharges within the buffer would be regulated by Corps.  Easily identified/mapped.  Precedent established by New Jersey.  EPA guidance does allow for using fixed distance as means to define

“adjacency”.

 Justifiable considering general morphology of Willamette River valley

wetlands.

slide-21
SLIDE 21
slide-22
SLIDE 22
slide-23
SLIDE 23
slide-24
SLIDE 24