Tornado History

Virginia Beach (c) Tornado History

This county-level tornado history page focuses on Virginia Beach (c), Virginia. The records below identify 14 tornadoes from 1967 through 2023, including a highest listed rating of EF3 (Severe damage). NOAA damage estimates in this group total at least $24.9M, with 0 deaths and 12 injuries recorded across the listed events.

Key Tornado Statistics

Total Tornadoes14
Total Deaths0
Total Injuries12
Property Damage$24.9M
Avg Length1.0 mi
Avg Width98 yd

Key Tornado Facts for Virginia Beach (c), Virginia

Top local patterns from the historical tornado records in this group.

Average 0.2 tornadoes per year (0.2/yr in last decade)
July is the peak tornado month with 6 recorded events
Deadliest tornado: F1 in Virginia Beach (c), Virginia with 0 deaths
2014 was the most active year with 2 tornadoes
The 2010s had the most tornado activity (4 events)
Longest tornado: 4.5 miles in Virginia Beach (c), Virginia
Widest tornado: 350.0 yards in Virginia Beach (c), Virginia
Most tornadoes in one day: 1 on Oct 25, 1967

Monthly Distribution

Shows tornado frequency across months of the year, highlighting seasonal patterns and peak tornado periods.

January
February
March
April
May
June
July
August
September
October
November
December

Summary: In Virginia Beach (c), Virginia, July is the most active month with 6 tornadoes.

Annual Tornado Trend

Shows year-by-year tornado counts, making active years and quiet stretches easier to spot.

20

Summary: 2014 was the most active year with 2 recorded tornadoes.

Tornado Intensity Distribution

Shows the breakdown of tornadoes by EF/F rating.

F0
EF0
F1
F2
EF2
EF3
Unknown

Summary: F0 tornadoes are the most common in this group, with 4 recorded events.

Property Damage Trends

Visualizes reported property damage over time. Bars use a log-like scale so very large damage years do not flatten the rest of the chart.

$20.0M$2.0M$200K$0

Summary: The highest reported property damage year in this group is 2023 with at least $20.0M in NOAA-listed property damage.

Historical Track Sketch

EF3 April 30, 20232023EF2 March 31, 20172017F2 August 3, 19881988F1 October 25, 19671967F1 July 27, 19721972F1 July 4, 19811981EF0 July 10, 20142014EF0 August 27, 20112011EF0 July 4, 20142014F0 July 24, 20002000F0 August 8, 20032003F0 July 14, 20052005F0 August 15, 19921992Unknown October 2, 19771977© OpenStreetMap contributors
This map covers the wider location—not your exact property.Measure the closest recorded track to a street address in or near Virginia Beach (c), Virginia.
Measure distance free

Notable Tornado Records

The table highlights the strongest and most damaging records in this page's local dataset. Damage totals are NOAA-reported minimum estimates where available.

DateRatingAreaLengthWidthDeathsInjuriesMin. property damage
April 30, 2023EF3Virginia Beach (c), Virginia4.5 mi350 yd00$20.0M
March 31, 2017EF2Virginia Beach (c), Virginia4.21 mi350 yd00$4.0M
August 3, 1988F2Virginia Beach (c), Virginia0.2 mi50 yd00$250K
October 25, 1967F1Virginia Beach (c), Virginia2 mi333 yd00$25K
July 27, 1972F1Virginia Beach (c), Virginia0 mi33 yd02$25K
July 4, 1981F1Virginia Beach (c), Virginia0.1 mi3 yd00$25K
July 10, 2014EF0Virginia Beach (c), Virginia0.34 mi30 yd010$300K
August 27, 2011EF0Virginia Beach (c), Virginia0.14 mi50 yd00$150K
July 4, 2014EF0Virginia Beach (c), Virginia0.31 mi30 yd00$25K
July 24, 2000F0Virginia Beach (c), Virginia0.2 mi20 yd00$20K
August 8, 2003F0Virginia Beach (c), Virginia0.2 mi50 yd00$5K
July 14, 2005F0Virginia Beach (c), Virginia0.2 mi25 yd00$2K
Did any of these records occur near a property you care about?Use an exact street address for a property-centered preview around Virginia Beach (c), Virginia.
Check a Virginia Beach (c), Virginia address

Source And Limits

Data sourced from NOAA Storm Prediction Center and the NCEI Storm Events Database. TornadoTrace summarizes reported weather events for screening and research; it is not a damage assessment, inspection, or insurance determination. Coordinates and records can be approximate, incomplete, revised, or missing. No warranty of completeness or accuracy.

Terms · Privacy