StormProof unlimited NWS storm verification · for pros

StormProofhail seasonsWashington, DC → 2000

Washington, DC hail season 2000

33 NWS-recorded hail reports ≥1″ within 35 miles, across 11 storm days, max 2.00". Every one of those reports is a dated, located, citable official record — the context behind this market's 2000 claim volume.

Biggest storm days (2000, final record)

Date≥1″ reportsMax hailAreas named in the record
April 21, 2000101.75"CHARLES, CALVERT, MONTGOMERY, HOWARD
August 7, 200051.25"PRINCE GEORGE'S, DISTRICT OF COLUMBIA, FAIRFAX
July 14, 200041.50"PRINCE WILLIAM, LOUDOUN
May 13, 200042.00"PRINCE WILLIAM, MANASSAS (C), CARROLL
July 16, 200021.00"ANNE ARUNDEL, PRINCE GEORGE'S

“Half dollar sized hail stripped leaves from trees, put small dents in cars, and chipped paint off houses.”

— NWS event narrative, April 21, 2000 (NCEI Storm Events)

When it fell

Mar 1 · Apr 10 · May 8 · Jun 3 · Jul 6 · Aug 5

Wind context: the record also holds 14 thunderstorm-wind events ≥50 kt (≈58 mph, the NWS severe criterion) in this radius for 2000 — relevant where the dispute is wind vs hail causation.

Working a Washington, DC claim from 2000?

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.