StormProof → hail seasons → Tulsa → 2003
Tulsa hail season 2003
14 NWS-recorded hail reports ≥1″ within 30 miles, across 5 storm days, max 2.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 |
|---|---|---|---|
| November 18, 2003 | 6 | 2.75" | OKMULGEE, TULSA, CREEK, ROGERS |
| May 10, 2003 | 4 | 2.75" | CREEK, TULSA, SEQUOYAH |
| May 19, 2003 | 2 | 1.00" | OSAGE, TULSA |
| June 14, 2003 | 1 | 1.00" | TULSA |
| May 13, 2003 | 1 | 1.25" | OSAGE |
“Baseball hail was reported at 31st and Harvard and then again at 21st and Harvard. The hail broke windows and damaged numerous roofs of buildings and cars. Damage is estimated; pending supplemental insurance reports.”
— NWS event narrative, November 18, 2003 (NCEI Storm Events)
When it fell
May 7 · Jun 1 · Nov 6
Wind context: the record also holds 65 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 Tulsa 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 30 miles of the Tulsa 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.