StormProof → hail seasons → Washington, DC → 2019
Washington, DC hail season 2019
37 NWS-recorded hail reports ≥1″ within 35 miles, across 8 storm days, max 2.00". Every one of those reports is a dated, located, citable official record — the context behind this market's 2019 claim volume.
Biggest storm days (2019, final record)
| Date | ≥1″ reports | Max hail | Areas named in the record |
|---|---|---|---|
| June 2, 2019 | 21 | 2.00" | DISTRICT OF COLUMBIA, FAIRFAX, MONTGOMERY, LOUDOUN |
| August 20, 2019 | 4 | 1.75" | PRINCE GEORGE'S, DISTRICT OF COLUMBIA, FAIRFAX |
| August 1, 2019 | 4 | 1.75" | CHARLES, ANNE ARUNDEL |
| June 29, 2019 | 3 | 1.50" | CALVERT, FAIRFAX |
| June 17, 2019 | 2 | 1.75" | PRINCE GEORGE'S, HOWARD |
“Hail up to the size of quarters (1.0 diameter) was reported along the George Washington Parkway near Turkey Run Road.”
— NWS event narrative, June 2, 2019 (NCEI Storm Events)
When it fell
May 1 · Jun 27 · Aug 9
Wind context: the record also holds 444 thunderstorm-wind events ≥50 kt (≈58 mph, the NWS severe criterion) in this radius for 2019 — relevant where the dispute is wind vs hail causation.
Working a Washington, DC claim from 2019?
These are aggregates. A claim file needs the per-address record: every recorded event within 1, 3 and 10 miles of the property, distances, official narratives, and citations an adjuster can check line by line. That's the report — generated in seconds, hosted on HailEvidence (the neutral evidence surface), formatted as an insurance-appeal attachment.
Unlimited reports — Pro $99/mo Single report $29
Provenance
Final counts: NCEI Storm Events Database, file vintage c20260527, hail events with recorded magnitude ≥1.00″ and point coordinates within 35 miles of the Washington, DC anchor. NWS records are point and path observations. The absence of a nearby report does NOT prove that no hail fell at this address — it means no observation was logged nearby. A report of nearby hail documents the event; it does not by itself prove damage to a specific structure. Spotted an error? Email the address on our terms page and we correct against the source.