StormProof → hail seasons → Topeka → 2003
Topeka hail season 2003
26 NWS-recorded hail reports ≥1″ within 25 miles, across 10 storm days, max 1.75". Every one of those reports is a dated, located, citable official record — the context behind this market's 2003 claim volume.
Biggest storm days (2003, final record)
| Date | ≥1″ reports | Max hail | Areas named in the record |
|---|---|---|---|
| August 20, 2003 | 5 | 1.25" | SHAWNEE |
| July 30, 2003 | 5 | 1.75" | SHAWNEE |
| March 12, 2003 | 5 | 1.50" | OSAGE, WABAUNSEE, DOUGLAS, JEFFERSON |
| August 5, 2003 | 3 | 1.25" | DOUGLAS, JACKSON |
| May 6, 2003 | 2 | 1.25" | OSAGE, DOUGLAS |
When it fell
Mar 5 · Apr 2 · May 2 · Jun 1 · Jul 6 · Aug 9 · Nov 1
Wind context: the record also holds 19 thunderstorm-wind events ≥50 kt (≈58 mph, the NWS severe criterion) in this radius for 2003 — relevant where the dispute is wind vs hail causation.
Working a Topeka claim from 2003?
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 25 miles of the Topeka 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.