⚠️ This is an independent informational resource. Data is provided for informational purposes only. Full disclaimer →

58750 Lansford, ND — Natural Disaster History

📊 Disaster Profile: Lansford, ND (58750)

Federal records document 64 natural disaster events in the Lansford, ND area (ZIP 58750). These include 45 hailstorms, 7 blizzards, and 7 severe wind events. Total documented property damage amounts to $12M. These events have resulted in 2 recorded deaths and 3 injuries.

⛈️ Hailstorms — Most Frequent Hazard

With 45 recorded incidents (70% of all events), hailstorms are the leading natural hazard for this ZIP code. Hail-related events have caused a combined $110K in documented property damage. The most recent recorded hailstorm occurred on Jul 10, 2025.

❄️ Blizzards

Lansford has experienced 7 blizzards on record. Of these, 7 (100%) were rated at severity level 4 or 5 — the most intense on the normalized scale. The highest recorded severity for winter storm events here is 5/5 (extreme). Winter storm events have caused a combined $5.4M in documented property damage. 2 fatalities have been attributed to blizzards in this area. The most recent recorded blizzard occurred on Apr 23, 2022.

💨 Severe wind events

Lansford has experienced 7 severe wind events on record. Wind-related events have caused a combined $6.4M in documented property damage. The most recent recorded severe wind event occurred on Jun 9, 2016.

🌊 Floods

Lansford has experienced 4 floods on record. One event reached severity level 4 or 5 on the normalized scale. The highest recorded severity for flood-related events here is 4/5 (severe). Flood-related events have caused a combined $85K in documented property damage. The most recent recorded flood occurred on Jun 25, 2011.

🔥 Wildfires

Lansford has experienced 1 wildfire on record. The most recent recorded wildfire occurred on Aug 15, 2015.

Notable Events

The most significant disaster event on record for Lansford was 100 mph Thunderstorm Wind on Jun 9, 2016, which caused $5.3M in property damage. Another major event was Blizzard (Apr 23, 2022), causing $3M in damages. Blizzard on Jan 9, 1997 also caused significant damage ($1.5M).

📍 Nearby ZIP Codes

Explore disaster history for adjacent areas

Frequently Asked Questions

What natural disasters have occurred in Lansford, ND (58750)?

Based on federal and state records, ZIP code 58750 has experienced 64 natural disaster events. The hazard types affecting this area include hailstorms (45 events), blizzards (7 events), severe wind events (7 events), floods (4 events), and wildfire (1 event). The primary hazard is hailstorms, which account for 70% of all recorded events.

What is the most common natural hazard in ZIP code 58750?

Hailstorms are the most frequently recorded hazard in Lansford, ND, with 45 events documented. These events have caused a combined $110K in property damage.

Is ZIP code 58750 (Lansford) prone to flooding?

Yes, Lansford (ZIP 58750) has 4 recorded flood events. These floods have caused $85K in total property damage. The most recent flood on record occurred on Jun 25, 2011.

What was the worst natural disaster in Lansford, ND?

The most damaging natural disaster on record for ZIP code 58750 was 100 mph Thunderstorm Wind, which occurred on Jun 9, 2016. This event caused $5.3M in documented property damage. It was rated at severity level 3/5.

How much property damage have natural disasters caused in ZIP code 58750?

Natural disasters have caused a documented total of $12M in property damage in the Lansford, ND area (ZIP 58750). This figure is based on historical records from FEMA, NOAA Storm Events Database, and USGS, and covers events from the 1950s through the present. Actual damages may be higher, as not all events have complete damage assessments.

Data sourced from FEMA (disaster declarations, NFIP flood claims), NOAA Storm Events Database, USGS Earthquake Hazards Program, and NIFC wildfire records. Historical coverage varies by source, with most records beginning in the 1950s–1970s. Full methodology →

Facebook WhatsApp Report Issue