Major DC Flood History: A Timeline of Significant Events

The District floods in three distinct ways — from the rivers (the Potomac and Anacostia), from the tide, and from stormwater that overwhelms an aging combined sewer — and its flood history is really three histories braided together. This page is a documented timeline of the significant events, organized so the cause of each is clear and each entry is tied to a public source. It is a data reference, not a narrative of any one storm.

Timeline of significant DC-area flood events

The table below collects the events most often cited in District flood records. Magnitudes for riverine events refer to high water on the Potomac at Washington unless noted; confirm exact stage and discharge against the USGS gauge records before formal citation.

The riverine record: 1936 as the benchmark

For high water on the Potomac, the March 1936 flood is the event against which others are measured. A combination of heavy rainfall and rapid snowmelt across the upper Potomac basin sent an extraordinary volume of water past Washington, inundating low-lying riverfront areas. It remains a reference point in USGS and Army Corps flood-frequency analysis for the region.

Subsequent benchmark riverine floods — 1942, Hurricane Agnes in 1972, 1985, and 1996 — fill out the record. The throughline is that the District’s riverine floods are episodic and basin-driven: they originate upstream, from large rain or rain-on-snow events across the Potomac watershed, and arrive as a flood wave. The regulatory high-risk zones along the rivers — see DC flood zone designations — are drawn around exactly this hazard.

The tidal story: Isabel and the slow rise

Hurricane Isabel (2003) is the modern reference for storm surge in the tidal Potomac. Rather than an upstream flood wave, Isabel pushed water up the river from the Chesapeake, flooding the Georgetown and Alexandria waterfronts. It demonstrated that the District’s riverfront is exposed to coastal surge, not only upstream flooding.

Layered on top of episodic surge is a slower trend: tidal “nuisance” flooding — minor flooding at high tide, absent any storm — has grown more frequent along the Potomac and Anacostia as sea level has risen. It rarely makes headlines, but it is the clearest signal that the District’s flood baseline is shifting, and it is a core input to DOEE’s future-conditions flood modeling.

The interior story: 2006, Bloomingdale, and the combined sewer

The events that most affect ordinary District residents are not riverine at all — they are stormwater backups in the older, combined-sewer parts of the city, where one pipe network carries both sewage and rainwater. When an intense downpour exceeds the system’s capacity, water backs up into streets and basements.

• The June 2006 Federal Triangle flood put this on the federal radar, flooding the basements of major buildings near Constitution Avenue and causing some of the most expensive damage in the District’s core.
• The 2012 Bloomingdale and LeDroit Park flash floods put it on residents’ radar: a string of summer storms repeatedly inundated the same low-lying neighborhoods, prompting DC Water’s Clean Rivers mitigation work, including the First Street Tunnel built to store stormwater and relieve the backups.
• The July 8, 2019 cloudburst showed how fast it can happen — a single morning of extreme rain flooded streets, the Metro, and federal buildings across the city.

Reading the gauges: what the numbers mean

The riverine entries above are ultimately statements about gauge readings, and a little vocabulary makes the record usable:

• Stage is the height of the water surface at a gauge, in feet, relative to the gauge datum — what people mean by “the river crested at X feet.”
• Discharge is the volume of water passing the gauge, in cubic feet per second; it is the more physically meaningful measure of a flood’s size but is less intuitive than stage.
• Flood stage is the level at which a gauge’s location begins to experience flooding; major flood stage is a higher NWS threshold tied to significant impacts.
• Recurrence interval (the “100-year flood”) expresses a flood’s size as an annual probability, not a schedule — a 1%-annual-chance flood can occur in consecutive years. The same framing underlies the regulatory zones on DC flood zone designations.

When you pull a historical event on a USGS gauge, you are usually looking at the peak stage and peak discharge for that event, which is what lets analysts rank floods like 1936, 1942, and 1996 against one another.

What the historic events changed

Each major event left a mark on District policy and infrastructure, which is part of why the timeline is worth keeping:

• 1936 anchored the federal flood-frequency analysis still referenced for the Potomac and informed the levee and floodwall protections around the federal core.
• 2003 (Isabel) sharpened attention on tidal storm surge and the vulnerability of the Georgetown and Alexandria waterfronts.
• 2006 (Federal Triangle) drove flood-proofing of federal buildings and pump/floodgate improvements near Constitution Avenue.
• 2012 (Bloomingdale) prompted DC Water’s First Street Tunnel and accelerated the Clean Rivers combined-sewer program, plus the District’s basement backwater-valve and basement-flooding assistance efforts.
• 2019 reinforced the case for green-infrastructure stormwater capture of the kind DOEE’s RiverSmart programs promote.

In other words, the timeline is not just a record of damage — it is the lineage of the District’s current flood-mitigation programs.

How to verify these events yourself

For a data audience, the point of a timeline is that each entry can be checked:

1. River stage and discharge — pull the historical peaks for the relevant gauge on the USGS National Water Dashboard or WaterWatch.
2. Rainfall and storm context — the National Weather Service Baltimore/Washington office documents storm events and rainfall totals.
3. District risk context — DOEE’s flood-risk management program ties past events to current and future modeled risk.

This site’s DC flood data desk collects these datasets and the agency directory in one place.

What the record suggests

Read together, the timeline shows a District whose flood risk is not static. Riverine flooding remains the episodic, basin-driven hazard it always was. But the interior stormwater events have become more consequential as development increased runoff and the climate produced more intense short-duration storms, and tidal flooding is creeping upward with sea level. The District’s response — the Clean Rivers tunnels, RiverSmart retrofits, and the Flood Task Force — is organized around that shifting picture.

Where to go next

• The full flood-data desk and agency directory: DC flood data
• What the regulatory zones mean today: DC flood zone designations
• The interior-flooding programs that address the recurring hazard: basement-flooding assistance
• Coverage for flood losses: flood insurance in DC (NFIP)
• If you are flooding right now: first-24-hours checklist