Jurisdiction Of Federal Waters Washington State Explained Fast
.jpg)
Federal waters off Washington state are generally managed by the federal government from 3 nautical miles seaward out to the outer limit of the U.S. Exclusive Economic Zone (EEZ), while Washington state (and local governments through state-authorized programs) regulates waters within 3 nautical miles of the coastline-creating a jurisdictional "split" that can feel confusing for permitting, enforcement, and planning.
In practice, the "jurisdiction" question is really three overlapping questions: (1) who has authority for coastal management (state vs. federal), (2) what law controls permitting for a specific activity, and (3) whether you're dealing with "state waters" vs. "federal waters" vs. a special case like the EEZ boundary. The short rule you can use is: if you're inside three nautical miles of Washington's coast, expect state shoreline jurisdiction; if you're farther out (up to the EEZ), expect federal primary jurisdiction.
Why it gets tricky: the word "federal waters" gets used in public conversations for multiple things, including Coast Guard operational areas, Clean Water Act "waters of the United States," and maritime boundaries. But when the question is specifically "jurisdiction of federal waters Washington state," the cleanest answer is the geographic split described in Washington's Ocean Resources Management Act and related state shoreline guidance, which explicitly ties primary jurisdiction to three nautical miles and then to the federal government through the EEZ.
Below is a practical map of how agencies generally think about offshore authority-and how that affects what you should check before you plan dredging, structures, discharges, marine construction, or resource harvest. I'll also include a "quick screen" workflow you can use to avoid wasting time on the wrong permit track.
Primary jurisdiction by distance
Washington state's coastal waters are governed by state primary jurisdiction out to three nautical miles from the shoreline, while federal primary jurisdiction runs from "three miles seaward" to the boundary of the two hundred mile exclusive economic zone. This framework is stated directly in Washington law summarizing how coastal and ocean resources are managed across the maritime boundary.
State shoreline programs (including local shoreline master program functions) are tied to the geographic scope of Washington's state waters; for Pacific coast counties, the state-local shoreline permitting limit extends westward the same distance as Washington's state waters: three nautical miles offshore. After that, the local/state shoreline permitting construct does not extend into federal waters.
- 0-3 nautical miles: Washington state primary jurisdiction; local shoreline permitting functions depend on local geographic boundaries authorized by the state program.
- 3-EEZ boundary (up to ~200 nautical miles): U.S. federal government has primary jurisdiction for ocean resource management under the state law's framing.
- What "federal" means on paper: not just "who you call," but which permitting systems and policy authority apply-state frameworks do not authorize local policies for federal waters.
How to translate that into action
If your real-world need is a permit decision, the fastest approach is to determine (a) your distance from the shoreline baseline and (b) which "program family" controls your activity (shoreline permitting, marine spatial planning, or federal environmental jurisdiction). The state guidance explicitly notes that state shoreline management statutes and guidelines do not authorize local shoreline permitting in federal waters and do not authorize local policies for federal waters or federal agencies.
In other words, you can't assume the local shoreline process "extends outward" to the point of conflict; you have to switch tracks at the jurisdiction line described above. This is the core reason people experience "tricky" jurisdiction in Washington: the authority boundary is distance-based, but the day-to-day project details (construction, discharge, navigation, habitat impacts) can be fact-specific.
- Measure your project location in nautical miles from Washington's coastline (not miles on a map).
- Decide whether you're inside or outside three nautical miles (state) or in the federal-primary zone (up to the EEZ boundary).
- Use the correct authority pathway: within three nautical miles, state/local shoreline programs may apply; beyond that, local shoreline permitting authority generally should not be treated as controlling.
Washington's jurisdiction rule in a table
| Maritime band (rule-of-thumb) | Primary jurisdiction | Practical "permit expectation" | Key wording to remember |
|---|---|---|---|
| 0 to 3 nautical miles | Washington state (with possible local shoreline master program functions) | State shoreline frameworks likely relevant for eligible activities | "out to three nautical miles" |
| 3 to EEZ boundary | U.S. federal government | Expect federal-primary management for ocean resources and related authority | "three miles seaward to... the two hundred mile exclusive economic zone" |
| Local shoreline programs (westward limit) | Stays within state water boundary | Local shoreline permitting generally does not extend into federal waters | "do not authorize local shoreline permitting in federal waters" |
That table uses the "distance bands" language that appears in Washington's own jurisdiction framing, which makes it particularly useful for interpreting why a shoreline master program might stop at a boundary. If you've ever seen conflicting advice online, this table is the cleanest grounding to re-anchor your questions to what Washington law actually states.
Why it feels confusing in real projects
One reason is that people mix up the location-based boundary (three nautical miles vs. federal-primary zone) with the subject-matter boundaries used in environmental law. For example, different laws can use different definitions (like "waters" categories), and that can cause someone to conclude "federal waters" means the same thing everywhere-even though the jurisdiction boundary for coastal/ocean resource management is explicitly distance-based in Washington's framework.
Another reason: local governments can have strong permitting roles near shore, but the legal text describing Washington's shoreline management authority draws a bright line between state waters and federal waters. That means "local process familiarity" can mislead you when your project's footprint or impacts extend beyond the state-water limit.
"The Shoreline Management Act, Ocean Resources Management Act, and the Ocean Management Guidelines do not authorize local shoreline permitting in federal waters..."
So the practical takeaway is not just "who's in charge," but "what you should not assume." If the project extends into the band where federal primary jurisdiction applies, the safe assumption is that local shoreline permitting authority is not the controlling mechanism for the federal zone.
Historical context that matters
Washington's approach to ocean governance emphasizes that coastal and ocean natural resources face "conflicting use demands," and that the state has an inherent interest in how resources within the broader marine area are managed-especially as economic and environmental outcomes cross administrative boundaries. That context helps explain why Washington codifies a clear split at three nautical miles while still recognizing that the federal zone (out to the EEZ boundary) directly affects Washington.
In that same legal framing, Washington states that protection, conservation, and development of the natural resources in the EEZ directly affect the state's economy and environment. That's a reason the state doesn't ignore the offshore zone-it just recognizes federal primary jurisdiction for that offshore band, so coordination and planning logic becomes crucial when projects cross the boundary.
FAQ
Quick project screen (example)
Example: a proposed offshore installation site located about 12 nautical miles from the Washington coast would fall outside the three-nautical-mile state-primary zone and into the federal-primary band described by Washington's ocean resource jurisdiction framework (up to the EEZ boundary). In that scenario, you should expect federal-primary management for the relevant ocean resource and jurisdictional questions rather than relying on local shoreline permitting authority.
Expert answers to Jurisdiction Of Federal Waters Washington State Explained Fast queries
What distance counts as "federal waters" off Washington?
Under Washington's jurisdiction framing for ocean resources, federal primary jurisdiction begins at three nautical miles seaward and continues to the boundary of the exclusive economic zone (described as a "two hundred mile exclusive economic zone" in the statute summary).
Does local shoreline permitting apply in federal waters?
No-Washington's shoreline management guidance states that the shoreline permitting framework does not authorize local shoreline permitting in federal waters. Local shoreline master program functions are tied to the geographic boundaries of state waters, which extend to three nautical miles.
Why do people get different answers online?
Because "federal waters" can be used loosely to refer to different legal concepts (distance-based primary jurisdiction vs. other environmental jurisdiction categories), but Washington's offshore jurisdiction split for ocean resources is explicitly distance-based. When you anchor to the three nautical miles rule, you can avoid mixing in unrelated definitions.
What should I verify before applying for permits?
Verify where your project footprint lies relative to the three nautical mile line, and then confirm which authority pathway applies to your activity. Washington's guidance indicates local shoreline permitting is not authorized in the federal-primary zone, so the permit track you choose should align to the correct jurisdiction band.