SB 639 designates four named subareas in the Sacramento–San Joaquin Valley — the Natomas subarea (city and unincorporated portions), the Beach Lake subareas (city and county pieces), and the City of Marysville ring-levee area — and requires those locations to achieve the statutory “urban level of flood protection” by 2030 for purposes of certain zoning and land-use statutes.
The bill also creates a conditional cost‑sharing rule: if a city or county “unreasonably approves” new development that increases the state’s exposure to property‑damage liability from flooding, that jurisdiction may be required to contribute a fair and reasonable share of property damage until the area attains the urban level of protection. The measure defines the affected geographic boundaries by reference to roads, levees, and local resolutions or plans.
At a Glance
What It Does
SB 639 identifies specific subareas and imposes a 2030 deadline to meet the statutory ‘‘urban level of flood protection’’ for those areas when applying Sections 65865.5, 65962, and 66474.5. It also conditions potential local cost‑sharing of flood property damage on a finding that a locality ‘‘unreasonably approved’’ development that increased the state’s liability exposure.
Who It Affects
The bill directly affects the City of Sacramento (Natomas and Beach Lake subareas), the City of Marysville, and the Counties of Sacramento, Sutter, and Yuba; it also affects developers, landowners, flood control agencies, and state attorneys who handle claims tied to flood damage. Local planning departments will need to treat these designations in permitting and zoning determinations referenced by the three cited code sections.
Why It Matters
By tying a hard deadline and a liability trigger to specific mapped areas, the bill shifts the practical calculus on permitting, infrastructure investment, and risk allocation. The designation can constrain development approvals, create exposure to shared recovery costs for local governments, and accelerate flood‑control project planning and financing for these high‑risk zones.
More articles like this one.
A weekly email with all the latest developments on this topic.
What This Bill Actually Does
SB 639 takes three connected steps in one short statute. First, it says that for the limited purposes of three existing land‑use code sections the listed parts of Natomas, Beach Lake, and Marysville must have reached the statutory ‘‘urban level of flood protection’’ by 2030.
That is a deadline tied to how those other statutes apply to land use and development in those areas.
Second, the bill creates a conditional duty for local governments: if a city or county ‘‘unreasonably approves’’ new development in one of the listed areas and that approval increases the state’s exposure to property‑damage liability from a flood, the locality may be required to pay a fair and reasonable share of any resulting property damage until the area meets the urban protection standard. The text borrows the ‘‘unreasonable approval’’ concept from the Water Code, importing that standard into how liability will be allocated between state and local actors.Third, SB 639 supplies precise boundary definitions for each named area.
It anchors the Beach Lake and Natomas subareas to street, highway, river, and levee limits and links Marysville’s covered area to the city’s 2021–29 housing plan resolution. Those geographic definitions matter because they determine which parcels and approvals fall subject to the 2030 deadline and the conditional cost‑sharing rule.Taken together, the statute forces local planners and flood managers in the listed jurisdictions to reconcile near‑term development decisions with a legally imposed protection deadline and a potential financial consequence if courts later find approvals were ‘‘unreasonable.’"},
The Five Things You Need to Know
The bill requires the Natomas subarea (city and county portions), the Beach Lake subareas (city and county portions), and the City of Marysville protected by the Marysville Ring Levee to achieve the statutory urban level of flood protection by 2030 for purposes of Sections 65865.5, 65962, and 66474.5.
If a city or county ‘‘unreasonably approves’’ new development in one of the listed areas that increases the state’s exposure to flood property‑damage liability, that jurisdiction may be required to contribute a fair and reasonable share of damages until the area meets the urban protection standard.
SB 639 explicitly ties its liability trigger to paragraph (2) of subdivision (a) of Water Code Section 8307 by reference, importing the ‘‘unreasonably approving’’ legal standard from the Water Code into this cost‑sharing rule.
The statute defines the covered boundaries with specific geographic anchors — streets, highways, rivers, levees, and local resolutions — for each subarea rather than leaving coverage to broader municipal boundaries.
The phrase ‘‘urban level of flood protection’’ used in the bill points to subdivision (n) of Section 65007 as the metric to be achieved, meaning technical flood‑protection criteria (not an ad hoc political judgment) will determine compliance.
Section-by-Section Breakdown
Every bill we cover gets an analysis of its key sections.
Designated areas and 2030 compliance deadline
This subdivision names the four covered locations and makes them subject to the requirement to attain an ‘‘urban level of flood protection’’ by 2030 when applying Sections 65865.5, 65962, and 66474.5. Practically, the language anchors the deadline to the administration of those three code sections, so agencies and courts will evaluate whether a locality has met the 2030 target in disputes or decisions that invoke those specific land‑use provisions.
Conditional local cost‑sharing for flood property damage
Subdivision (b) creates the new financial mechanism: notwithstanding a Water Code paragraph, a named city or county may be required to contribute its fair and reasonable share of flood property damage if the state’s exposure was increased by the locality ‘‘unreasonably approving’’ development in the listed areas and the locality has not yet achieved the urban protection standard. This is not an automatic tax or penalty; it’s a liability allocation principle that will require factual findings about the reasonableness of approvals and any causal link to state exposure, and it likely invites litigation over both elements.
Precise geographic definitions
This subsection fixes the statute’s reach by defining each subarea with street, highway, river, levee, and local‑plan references and by identifying Natomas as including multiple jurisdictional pieces. Because the bill relies on these definitions to determine which approvals and parcels are covered, mapping accuracy and administrative interpretation will be pivotal during implementation and disputes.
This bill is one of many.
Codify tracks hundreds of bills on Environment across all five countries.
Explore Environment in Codify Search →Who Benefits and Who Bears the Cost
Every bill creates winners and losers. Here's who stands to gain and who bears the cost.
Who Benefits
- Residents and property owners in the designated areas — They gain a statutory push toward higher flood protections and, over time, reduced flood risk if the urban‑level projects are completed, which may protect property values and safety.
- State government and taxpayers — By creating a framework to hold localities partially accountable where approvals increased state liability exposure, the bill aims to limit uncapped state payouts and align development approvals with risk reduction.
- Regional flood management agencies and planners — The deadline creates political leverage and an operational imperative to prioritize projects, funding, and coordination to meet a defined target.
- Insurers and mortgage lenders serving those zones — Clearer statutory designations and a mandate for urban‑level protection reduce uncertainty about long‑term flood risk, which can inform underwriting and lending decisions.
Who Bears the Cost
- City and county governments named in the statute (City of Sacramento, City of Marysville, Counties of Sacramento, Sutter, Yuba) — They face potential liability contributions for flood damage and must budget for engineering, permitting, and capital projects to reach the 2030 standard.
- Local flood control districts and special districts — They will confront accelerated timelines for levee repair, project delivery, and environmental review, often without new dedicated statewide funding in the statute.
- Developers and landowners in the designated areas — Approvals may be delayed, conditioned, or denied while jurisdictions demonstrate compliance with the urban protection metric, increasing carrying costs and mitigation obligations.
- State agencies and taxpayers indirectly — If localities cannot pay their ‘‘fair share,’’ the state may still shoulder initial costs of emergency response and repairs, and disputes over allocation could increase litigation and administrative expense.
Key Issues
The Core Tension
The central tension is between reducing public flood liability and protecting public safety by forcing higher levels of flood infrastructure, versus preserving local flexibility to permit development and meet housing goals; the bill's liability trigger pressures localities to invest in costly, time‑consuming protection measures but offers no clear funding or procedural path, so the policy trade‑off pits risk reduction against feasibility, development rights, and municipal fiscal capacity.
The statute leaves two core implementation problems unresolved. First, the key legal hooks — ‘‘unreasonably approving’’ and ‘‘fair and reasonable share’’ — are standards, not formulas.
Determining when an approval increased the state’s exposure and how to quantify a locality’s share will demand fact‑intensive litigation, technical hydrology evidence, and judgments about counterfactual land‑use scenarios. The bill does not define the procedural path for those determinations or identify which court or agency makes them.
Second, the 2030 deadline is aggressive for major flood infrastructure projects that typically require multi‑year environmental review, design, right‑of‑way acquisition, and construction. The statute places the burden on local governments to meet a performance standard without specifying funding sources or streamlining measures.
That gap risks a stalemate: jurisdictions cannot demonstrate compliance without expensive projects, but funding constraints may make it infeasible to complete them before the deadline. Additionally, the statute’s reliance on specific municipal resolutions and older planning documents to define boundaries could produce coverage disputes where maps or property descriptions have moved on since those instruments were adopted.
Try it yourself.
Ask a question in plain English, or pick a topic below. Results in seconds.