The Fix Is In: Fairfax County’s RPA System Fails Our Streams and Communities

On paper, Fairfax County’s Resource Protection Areas (RPAs) are presented as powerful shields for streams and watersheds—a bulwark against unchecked development. The county touts these corridors of sensitive land as essential for protecting water quality, filtering pollutants, reducing stormwater runoff, and preventing erosion. But the reality on the ground tells a very different story: what’s advertised as a strict environmental safeguard is, in practice, a porous system that routinely bends to accommodate development.

What resembles environmental protection on paper appears to be a development facilitation system—and our watersheds are paying the price.

The rules are riddled with escape hatches — by design

The county’s own FAQ confirms that existing structures and uses in the RPA — including lawns, gardens, and maintained landscaping — may remain as they existed when RPAs were first designated in 1993 or 2003, but “may not be expanded upon unless a waiver or exception is granted.” That sounds strict until you read what comes next: decks are “commonly” treated as minor additions and allowed through an administrative waiver. Sheds, patios, and detached garages can be approved through a public hearing exception process. New homes can be built in RPAs under a “loss of buildable area” provision that allows up to 5,000 square feet of impervious coverage in the RPA 100’ buffer zone. There is, it turns out, almost nothing that cannot be permitted through one pathway or another.

The county even recommends hiring a specialist: “Given the technical aspects involved in the application process, we strongly recommend hiring a consultant specialized in RPA applications.” Read that again. The county is telling you, in its own official FAQ, that you need to hire someone who knows how to navigate the exceptions system. That is not the language of environmental protection. That is the language of a permitting industry.

The “pre-application conference” is a backroom deal

Before a site plan ever reaches public view, the developer and county land use and engineering staff have already worked out what it will take to get a yes. The county strongly recommends a pre-application meeting before submitting any Water Quality Impact Assessment to pursue a public hearing exception — and has set up a dedicated online portal just for scheduling those meetings. There is no public notice for these early conversations, no community input, no environmental advocate in the room. It is the applicant, their consultants, and county staff — all working toward the same outcome: approval. By the time the interested community hears about a project, the key decisions have already been made.

The consultants know exactly how the game is played

Many of the engineers and lawyers pushing these projects through are former county employees. They know the staff, they know the process, and they know exactly how to package an exception request to get it approved. The county’s own advice to hire an RPA specialist is a wink and a nod to this cottage industry. Community and environmental advocacy groups are fighting with one hand tied behind their back.

A ‘Public Hearing’ With a Predetermined Outcome

The Exception Review Committee — an 11-member body appointed by the Board of Supervisors — reviews applications to conduct land-disturbing activities in RPAs, with decisions based on “fact and law” under Article 6 of the Chesapeake Bay Preservation Ordinance. That sounds rigorous. However, consider the ERC’s own meeting history: the committee convenes only a handful of times per year, typically reviewing one or two cases at each meeting. Each case involves a single property owner seeking to build something — a patio, a pool, a house — in a protected buffer. The volume of administrative waivers that never even reach the ERC is vastly larger, and entirely invisible to the public.

Larger disturbances connected to rezonings don’t even go to the ERC — they are reviewed directly by the Board of Supervisors as part of the rezoning process, where land use politics, developer contributions, and economic development priorities carry far more weight than stream health.

“Exceptions” have swallowed the rule entirely

The exception criteria — hardship, loss of buildable area, minor additions, redevelopment — sound like narrow safety valves. In practice, they cover nearly everything a developer or homeowner wants to do. When a system has this many doors labeled “exit,” the rule becomes nominal. Essentially, the county is operating a framework where the default is approval and the burden falls on nature — and on the public — to prove otherwise.

Our streams are suffering a death-by-a-thousand-cuts

Fairfax County’s 30 watersheds are on the front lines of a slow-moving environmental crisis. With every approved exception, another thread is pulled from the fabric of stream health and ecosystem resilience. No single construction project poisons a watershed overnight — and that’s the tragedy. Instead, decades of piecemeal approvals, each justified as a minor impact, have collectively gutted the ecological integrity of places like Four Mile Run, Difficult Run, and Pohick Creek. The harm is insidious, cumulative, and largely invisible until it’s too late: altered stream flows that erode banks and destroy habitats, aquatic life vanishing as stream-bed life collapses, water quality slipping below thresholds for safe recreation and wildlife. USGS research on Fairfax’s own streams documents this form of death by a thousand cuts, as the mounting toll that is never reckoned with as a whole. The review process is calibrated for approval, not protection. Accountability is nowhere, even as the damage spreads everywhere. The watersheds bear the burden for a system that treats nature as expendable, one rubber-stamped permit at a time.

The reality behind the rules

The RPA framework gives the county — and the developers who work it — political cover. They can point to buffers, mitigation plans, and public hearings while approving project after project in sensitive areas. The process isn’t broken. It is working exactly as the people who administer it intend it to work.

Our streams, our increasing community flood risk, and our community character are being traded away in meetings that community stakeholders are not invited to, by a process designed to say yes.

What can concerned citizens do?

•  Demand transparency,
•  Attend ERC hearings,
•  Track cumulative watershed impacts across your community, and
•  Report to Fairfax County Code Compliance (codecompliance@fairfaxcounty.gov) suspected land disturbance activities that appear to impact RPAs. 

These are not just civic virtues, by the way. They are apparently the only check on a system that has none built in.

Peter Falcone

Citizens For Great Falls

Sources: Fairfax County Land Development Services FAQ on Resource Protection Areas; Exception Review Committee page https://www.fairfaxcounty.gov/landdevelopment/exception-review-committee; Fairfax County Chesapeake Bay Preservation Ordinance Chapter 118; USGS Scientific Investigations Report 2023-5027.