Who Was Responsible for the Potomac Sewage Failure—and Where Did the Money Go?

Graphic discussing responsibility and financial accountability regarding the Potomac sewage failure featuring images of a sewage pipe, regulatory logos for Maryland and EPA, and names of key individuals involved.

By MDBayNews Staff

As details continue to emerge from one of the largest sewage spills in U.S. history, the environmental damage to the Potomac River is no longer the only issue demanding scrutiny. The spill—nearly 300 million gallons of raw sewage discharged over eight days, with E. coli levels reaching 12,000 times the legal safety limit—has exposed a deeper problem: a persistent lack of accountability when critical public infrastructure fails.

This was not a sudden or unforeseeable catastrophe. It was the failure of a major sewer interceptor pipe located dangerously close to the river—an asset that had been known, monitored, and budgeted for over many years.

Which raises the next question Maryland and regional residents are now asking: who was responsible, and why was this allowed to happen?


Leadership Has Names—So Should Accountability

The Potomac Interceptor is owned, operated, and maintained by DC Water, formally known as the District of Columbia Water and Sewer Authority. Day-to-day operational control and long-term planning fall under its executive leadership.

At the top of that structure is David L. Gadis, Chief Executive Officer and General Manager since 2018. As CEO, Gadis oversees the entire agency, including:

  • A $1 billion-plus annual budget
  • Approximately 1,200 employees
  • Major capital initiatives such as the Clean Rivers Project
  • A 10-year, $625 million rehabilitation program for the Potomac Interceptor itself

Below the CEO, operational responsibility for sewer maintenance, inspection, and emergency response resides with Jeffrey F. Thompson, the agency’s Chief Operating Officer, whose portfolio includes wastewater operations, pumping systems, and engineering.

Communications and public updates during the incident have been handled by senior staff including John Lisle and Kirsten Williams, reflecting the agency’s coordinated response strategy.

Finally, governance oversight rests with the DC Water Board of Directors, whose members are appointed by the D.C. Mayor and confirmed by the D.C. Council, with representation from neighboring jurisdictions including Maryland and Virginia.

None of this implies malfeasance. But it does establish something essential: this system has clear lines of authority.


Accountability Without Ownership: Maryland’s Role in a Regional Failure

While the Potomac Interceptor failure occurred within Montgomery County, Maryland does not own, operate, or repair the pipe itself. That responsibility rests squarely with DC Water, which manages the interceptor as part of a regional sewer system carrying wastewater from portions of Maryland, Virginia, and the District to the Blue Plains treatment facility in Washington.

That distinction matters.

Maryland agencies are not hands-off, but their role is fundamentally different from operational control. The Maryland Department of the Environment (MDE) is coordinating with federal regulators and DC Water to monitor water quality impacts, enforce state clean water laws, and oversee reporting and public notification requirements tied to sanitary sewer overflows. Montgomery County and the National Park Service, which manages the C&O Canal corridor where the rupture occurred, are also involved in response and site coordination.

However, Maryland regulators do not inspect, replace, or rehabilitate the Potomac Interceptor. They cannot schedule preventative maintenance, accelerate capital repairs, or decide when a compromised pipe segment is taken offline. Those decisions—and the budgets behind them—are made by DC Water’s executive leadership and approved through its governing board.

This layered oversight exposes a familiar problem in regional infrastructure governance: many agencies share visibility, but none bear sole accountability when prevention fails.

Maryland can monitor and enforce environmental standards after a disaster. It cannot prevent one caused by neglected infrastructure it does not control.

That gap is not an excuse—it is the core issue.


This Was Not an “Act of God”

According to independent sampling released by the Potomac Riverkeeper Network, contamination levels near Lockhouse 10 reached almost 4.9 million MPN of E. coli—nearly 12,000 times the threshold for safe human contact. Public access areas showed similarly alarming results, while upstream waters remained clean, confirming the failure point.

This matters because infrastructure failures of this scale do not happen overnight. Interceptor pipes are inspected, rated, prioritized, and funded years in advance. Budgets are approved. Capital plans are published. Risk assessments are performed.

Which leads to legitimate public-interest questions:

  • When was this section of pipe last inspected?
  • What condition rating did it receive?
  • Was it scheduled for rehabilitation or replacement?
  • If so, why had that work not yet occurred?

These are not political questions. They are basic governance questions.


Follow the Spending, Not the Spin

DC Water has spent billions over the past decade on environmental compliance, sewer overflow reduction, and large-scale tunnel projects. Ratepayers have been repeatedly told that these investments would modernize the system and prevent disasters like this.

Yet when a known, aging interceptor failed, the emergency response relied on temporary pumps and a century-old canal system to divert sewage—an improvisation that underscores how unprepared the system was for a foreseeable failure.

That gap between spending and outcomes deserves scrutiny.

Audits are not punishments. They are how public trust is maintained.


The Accountability Gap

Time and again, environmental failures follow a familiar script:

  1. A crisis occurs
  2. Agencies issue updates and reassurances
  3. Task forces or reviews are announced
  4. Reports are filed
  5. Life goes on—unchanged

What almost never follows is individual accountability, performance consequences, or structural reform.

As one prominent journalist noted online this week, the public is increasingly frustrated by a system where “there are no consequences for incompetence and corruption.” That frustration is not partisan. It reflects a growing belief that public institutions are insulated from the results of their own decisions.


Why This Matters to Maryland

Although the failure occurred under a D.C. utility, its effects do not respect jurisdictional boundaries. Contaminated water flowed downstream into Maryland-adjacent recreation areas, threatening public health, fisheries, and regional ecosystems.

Maryland residents pay the price—without having any direct say over DC Water’s leadership or governance structure.

That reality makes transparency and accountability even more essential.


The Bottom Line

No one is calling for scapegoats. But naming responsibility is not the same as assigning blame.

The Potomac sewage disaster should not quietly fade into the background once repairs are completed. It should prompt a serious review of:

  • Infrastructure prioritization
  • Budget execution
  • Risk management
  • Executive accountability

Public utilities exist to serve the public—not to operate behind a shield of complexity and silence.

If no one is ever responsible when systems fail, then failure becomes the default.

MDBayNews will continue following this story.


Editor’s Note

The Potomac Interceptor is a regional sewer line owned and operated by DC Water, serving parts of Maryland, Virginia, and Washington, D.C. Although the rupture occurred within Montgomery County, Maryland does not control the pipe’s inspection, maintenance, or repair schedule. Maryland agencies, including the Maryland Department of the Environment, are involved in regulatory oversight and environmental monitoring—but operational responsibility for the infrastructure rests with DC Water. This article focuses on accountability within that governance structure.


Keep MDBayNews Reporting Free

MDBayNews exists to help Marylanders understand decisions made by state and local leaders — especially when those decisions affect daily life, rights, and public services.

If this article helped clarify what’s happening or why it matters, reader support makes it possible to keep publishing clear, independent reporting like this.

👉 Support Local Journalism

Have a tip or documents to share?

We review submissions carefully and confidentially. Anonymous tips are welcome when appropriate.

 👉 Submit a Tip


Discover more from Maryland Bay News

Subscribe to get the latest posts sent to your email.

Leave a Reply

Discover more from Maryland Bay News

Subscribe now to keep reading and get access to the full archive.

Continue reading