Tornadoes · United States · Indiana · 2026
EF1 tornado, Shipshewana Fld Arpt to Howe, Indiana, June 11, 2026
From Shipshewana Fld Arpt to Howe, this EF1 tornado ran 9.9 miles across LaGrange County on June 11, 2026, touching down at 10:59 PM EDT and reaching 1,300 yards wide. It killed nobody and injured 1.
Preliminary. This is NWS IWX's damage survey, filed in the Damage Assessment Toolkit as Shipshewana. The rating, the path and the casualties are the survey's and can change while it is revised. The Storm Prediction Center compiles the official record of 2026 from these surveys and publishes it in the spring of 2027; this page moves to that tornado's permanent address when it does.
The rating scale
Tracks are drawn in the color of the rating. The Enhanced Fujita scale rates the damage rather than measuring the wind: the speeds are what that damage is taken to imply.
EF065 to 85 mph
Light damage. Surface peeled off some roofs, gutters and siding damaged, branches broken, shallow-rooted trees pushed over.
EF186 to 110 mphthis tornado
Moderate damage. Roofs badly stripped, mobile homes overturned or badly damaged, exterior doors lost, windows broken.
EF2111 to 135 mph
Considerable damage. Roofs torn off well-built houses, frame homes shifted on their foundations, mobile homes destroyed, large trees snapped or uprooted, cars lifted off the ground.
EF3136 to 165 mph
Severe damage. Whole stories of well-built houses destroyed, large buildings badly damaged, trains overturned, trees debarked, heavy cars lifted and thrown.
EF4166 to 200 mph
Devastating damage. Well-built houses leveled, structures with weak foundations moved some distance, cars thrown and large missiles generated.
EF5over 200 mph
Incredible damage. Strong frame houses swept off their foundations, car-sized missiles thrown more than 100 meters, steel-reinforced concrete badly damaged, high-rise buildings deformed.
Unrated
The survey recorded a tornado but could not put a number on it, most often because it crossed open country and damaged nothing a rating can be read from.
The survey
- Rating, as surveyed
- EF1, preliminary
- Date
- June 11, 2026
- Touchdown
- 10:59 PM EDT (02:59 UTC)
- Lifted
- 11:06 PM EDT (03:06 UTC)
- On the ground
- 7 minutes
- Path length
- 9.9 miles (15.9 km)
- Path width
- 1,300 yards (1189 m)
- Deaths
- 0
- Injuries
- 1
- County
- LaGrange County
- Touchdown point
- 41.722, -85.647
- Lift-off point
- 41.740, -85.468
- Highest wind the damage implies
- 100 mph
- Surveyed by
- NWS IWX
- The office's name for it
- Shipshewana
- Survey last edited
- June 22, 2026
- Record number
- None yet. SPC numbers 2026 in the spring of 2027.
What the survey found
The same storm that produced the EF-2 tornado in Bristol, IN continued eastward into LaGrange County. While radar suggested the correlation coefficient signature persisted between Bristol and this tornado (albeit weaker), damage was very sparse, and there was not enough confidence or evidence to definitively connect the two areas of concern. Due to a 10-mile separation, it was determined to treat these as two separate tornadoes.
The tornado in LaGrange paralleled SR 120, producing an impressive swath of tree damage and causing visible damage to barns and center pivots. Given the time elapsed between the storm and the ground survey, it is likely some homes had already been repaired. The circulation reached a maximum width of 0.75 miles on the north side of Shipshewana, with a maximum intensity estimated to be EF-1 at 100 mph. The tornado occluded on the western side of Twin Lakes before a broader swath of straight-line wind damage took over in the Howe, IN and Sturgis, MI areas.
Written by NWS IWX in the NWS Damage Assessment Toolkit. A survey is revised as better evidence arrives.
The damage survey
68 damage points were recorded along this path by NWS IWX, in the Damage Assessment Toolkit the survey teams carry. The strongest indicator was rated EFU. The highest wind the damage implies is 115 mph.
- Emailed photos of pine tree snapped at the base.
- Emailed photos of one large tree uprooted. One tree snapped several feet from the base; some sign of rot. Author states other property damage occurred; roofs, outbuildings etc.
- Full roof reconstruction underway, rafters included. Some roof panels in treeline to the NNE. Perhaps dozens of trees damaged to the NNE of here. Some narrower trunks snapped toward top.
- 3 to 4 sections of center pivot flipped. West of here, another larger section flipped as well
Survey points are preliminary and are the raw material the published rating was built from. Source: NWS Damage Assessment Toolkit.
What the Weather Service recorded
A squall line raced through northern Indiana and spawned numerous tornadoes. Most tornadoes were narrow and lasted less then 10 minutes. Additional areas of straight line wind damage were noted as well.
The same storm that produced the EF-2 tornado in Bristol, IN|continued eastward into LaGrange County. While radar suggested|the correlation coefficient signature persisted between Bristol|and this tornado (albeit weaker), damage was very sparse, and|there was not enough confidence or evidence to definitively|connect the two areas of concern. Due to a 10-mile separation, it|was determined to treat these as two separate tornadoes.The|tornado in LaGrange paralleled SR 120, producing an impressive|swath of tree damage and causing visible damage to barns and|center pivots. Given the time elapsed between the storm and the|ground survey, it is likely some homes had already been repaired.|The circulation reached a maximum width of 0.75 miles on the|north side of Shipshewana, with a maximum intensity estimated to|be EF-1 at 100 mph. The tornado occluded on the western side of|Twin Lakes before a broader swath of straight-line wind damage|took over in the Howe, IN and Sturgis, MI areas.
From NOAA NCEI's Storm Events Database, the narrative the local forecast office wrote for Storm Data.
The warnings
8 minutes of warning. NWS IWX issued a tornado warning for this county at 02:51 UTC, 8 minutes before the tornado touched down, in force until 03:11 UTC.
The county was under a tornado watch, issued at 00:08 UTC and running to 03:44 UTC.
| Issued (UTC) | Expired | Product | Office |
|---|---|---|---|
| 16:00 UTC | 21:51 UTC | Heat Advisory | IWX |
| 00:08 UTC | 03:44 UTC | Tornado Watch | IWX |
| 02:49 UTC | 03:30 UTC | Severe Thunderstorm Warning | IWX |
| 02:51 UTC | 03:11 UTC | Tornado Warning | IWX |
| 03:18 UTC | 03:39 UTC | Severe Thunderstorm Warning | IWX |
Every warning and watch covering the touchdown point that day, from the Iowa Environmental Mesonet's archive of National Weather Service products. Lead time is measured from the issue of the warning in force to the touchdown time in the database, both of which were recorded to the minute by different people.
The forecast that day
The Storm Prediction Center had this point in a Enhanced Risk, with a 0.10 chance of a tornado within 25 miles, in the hatched area where significant tornadoes were expected. The outlook in force was issued at 01:00 UTC.
SPC's Day 1 convective outlook as it stood when the tornado began, read at the touchdown point. The same archive is on the radar archive.
The air that afternoon
The radiosonde launches on either side of the tornado, from the nearest station that was launching then, drawn and analyzed the way Storm Lab does: the same diagram, the same parcel and shear definitions SPC's mesoanalysis uses.
Detroit, MI (KDTX), 00:00Z
3.0 hours before the tornado, 207 km from the path. June 12, 2026.
- Mixed-layer CAPE
- 161 J/kg
- Mixed-layer CIN
- -184 J/kg
- Surface CAPE
- 1082 J/kg
- Mixed-layer LCL
- 1444 m above ground
- 0-6 km bulk shear
- 35 kt
- 0-1 km bulk shear
- 13 kt
- 0-1 km storm-relative helicity
- 86 m²/s²
- 0-3 km storm-relative helicity
- 127 m²/s²
- Significant tornado parameter
- 0.0
- Supercell composite
- 1.5
- 0-3 km lapse rate
- 6.0 K/km
Detroit, MI (KDTX), 12:00Z
9.0 hours after it, 207 km from the path. June 12, 2026.
- Mixed-layer CAPE
- 0 J/kg
- Mixed-layer CIN
- -84968 J/kg
- Surface CAPE
- 13 J/kg
- Mixed-layer LCL
- 843 m above ground
- 0-6 km bulk shear
- 44 kt
- 0-1 km bulk shear
- 25 kt
- 0-1 km storm-relative helicity
- -80 m²/s²
- 0-3 km storm-relative helicity
- -1 m²/s²
- Significant tornado parameter
- 0.0
- Supercell composite
- 0.0
- 0-3 km lapse rate
- 3.3 K/km
The surface observations
Sturgis/Kirsch (IRS), 13 km from the path, in the two hours either side.
| Time (UTC) | Temp (°F) | Dew point (°F) | Wind | Gust (kt) | Pressure (mb) | Weather |
|---|---|---|---|---|---|---|
| 01:15 UTC | 80.6 | 68 | 180° 9 kt | 1006.1 | ||
| 01:35 UTC | 80.6 | 68 | 180° 9 kt | 1006.1 | ||
| 01:55 UTC | 80.6 | 68 | 170° 9 kt | 1005.8 | ||
| 02:15 UTC | 80.6 | 69.8 | 160° 11 kt | 1005.4 | ||
| 02:35 UTC | 80.6 | 69.8 | 170° 10 kt | 1005.4 | ||
| 02:56 UTC | 80.6 | 71.6 | 170° 12 kt | 19 | 1005.4 | |
| 03:17 UTC | 77 | 69.8 | 290° 32 kt | 50 | 1009.1 | +RA HZ |
| 03:35 UTC | 68 | 66.2 | 280° 10 kt | 22 | 1008.1 | -RA |
| 04:03 UTC | 68 | 66.2 | 190° 8 kt | 1006.4 | -RA |
From the Iowa Environmental Mesonet's archive of airport observations.
The radar
The Northern Indiana radar (KIWX), 43 km away, was scanning. The volume nearest the touchdown began at 03:00 UTC.
Open the radar archive at this moment, over the track
Reflectivity and velocity, decoded from the Level II archive in the browser. Volumes take a few seconds to open the first time.
What was reported nearby
Local storm reports within 60 km of the path, in the three hours either side.
| Time (UTC) | Report | Where | County | Remark |
|---|---|---|---|---|
| 02:22 UTC | TSTM WND DMG | 4 Ne Bourbon | Marshall, IN | multiple structures impacted. |
| 02:22 UTC | TORNADO | 3 Ne Bourbon | Marshall, IN | Another tornado, perhaps from the same parent circulation that spawned the Argos tornado, developed on the northeast side of Bourbon in Marshall County. The tornado touched down in a field, with tree damage observed in t |
| 02:25 UTC | TSTM WND GST 56 | 3 E Chain-O-Lakes | St. Joseph, IN | |
| 02:27 UTC | TSTM WND DMG | Hastings | Kosciusko, IN | tree on house and multiple broken limbs. |
| 02:30 UTC | TSTM WND DMG | 1 E Georgetown | St. Joseph, IN | Large pine trees topped, wood picket fence snapped, grass and dirt plastered to buildings. |
| 02:30 UTC | TSTM WND DMG | South Bend | St. Joseph, IN | numerous trees down in the South Bend area. |
| 02:42 UTC | TSTM WND DMG | Dunlap | Elkhart, IN | large tree and numerous branches down. |
| 02:42 UTC | TORNADO | 2 Ne Elkhart | Elkhart, IN | *** 1 INJ *** Corrects previous tornado report from 3 NE Elkhart for an injury. Correction to the previously reported Bristol, IN tornado to expand the track both west and east. A National Weather Service storm survey de |
| 02:42 UTC | TORNADO | 2 Ne Elkhart | St. Joseph, IN | *** 1 INJ *** Update to the previously reported Bristol Tornado. The track has expanded both west and east. A National Weather Service storm survey determined that an EF-2 tornado occurred in association with a line of s |
| 02:42 UTC | TORNADO | 3 Ne Elkhart | Elkhart, IN | Corrected lat/lon and county. Correction to the previously reported Bristol, IN tornado to expand the track both west and east. A National Weather Service storm survey determined that an EF-2 tornado occurred in associat |
| 02:43 UTC | TSTM WND GST 75 | 2 N North Webster | Kosciusko, IN | |
| 02:45 UTC | TSTM WND DMG | 4 W Bristol | Elkhart, IN | several homes damaged and trees down. |
| 02:46 UTC | TORNADO | 4 Ene Elkhart | Elkhart, IN | A National Weather Service storm survey determined that an EF-2 tornado occurred in association with a line of severe thunderstorms across northern Elkhart County. The path of the tornado began in the County Road 15 and |
| 02:50 UTC | FLOOD | 2 Se South Bend | St. Joseph, IN | Report from mPING: River/Creek overflowing; Cropland/Yard/Basement Flooding. |
| 02:55 UTC | TSTM WND DMG | 2 Nne Middlebury | Elkhart, IN | several trees and large branches down. |
| 02:55 UTC | TSTM WND GST 59 | 2 Nnw Elkhart | Elkhart, IN | |
| 02:59 UTC | TORNADO | 4 Wsw Scott (Nw Shipshe | Lagrange, IN | The same storm that produced the EF-2 tornado in Bristol, IN continued eastward into LaGrange County. While radar suggested the correlation coefficient signature persisted between Bristol and this tornado (albeit weaker) |
| 03:00 UTC | TSTM WND DMG | 2 Ese Scott | Lagrange, IN | Along SR-120, especially near/west of N 450 W through approximately SR-5. Structural damage to a silo, barns, and some shingle and siding damage on several homes. There were a couple of center pivots that were damaged. T |
| 03:03 UTC | TSTM WND DMG | 1 Ne Scott | Lagrange, IN | *** 1 INJ *** large limb fell onto a camper and injured the person inside. |
| 03:05 UTC | TSTM WND DMG | 2 W Howe | Lagrange, IN | Large mature white pine snapped off 15 feet above ground, large locust tree uprooted, large limbs stripped from mature oak and maple trees. |
| 03:10 UTC | TSTM WND DMG | Brighton | Lagrange, IN | Numerous 6-8 inch diameter or less limbs downed around the area between Brighton and Howe, IN. Pine tree snapped halfway (appears healthy). Metal roofing appears to have been damaged and was tossed into a field. One tree |
| 03:12 UTC | TORNADO | 2 Sse Big Long Lake | Lagrange, IN | A tornado embedded within a line of severe thunderstorms developed Thursday night in extreme southeast LaGrange County. Around Taylor Lake and Lake of the Woods, damage to electrical poles, along with impressive tree dam |
| 03:20 UTC | TSTM WND DMG | Orland | Steuben, IN | Numerous 6-8 diameter or less limbs downed, a couple of uprooted pines between Wall Lake and the Greenlawn Cemetery areas near Orland, IN. |
| 03:25 UTC | TSTM WND DMG | 1 Nne Lake James | Steuben, IN | tree into house. |
| 03:25 UTC | TSTM WND DMG | Angola | Steuben, IN | trees down. |
From the Iowa Environmental Mesonet's archive of National Weather Service local storm reports.
This ground now
The live radar over the trackEvery 2026 tornado in IndianaEvery tornado in Indiana since 1950Warnings in force in Indiana nowThe forecast where you are
The other tornadoes of June 11, 2026
65 more have been surveyed in the United States that day, so far.
| Date | Time | Rating | Where | Path (mi) | Width (yd) | Deaths | Injuries | Damage |
|---|---|---|---|---|---|---|---|---|
| June 11 | 5:10 AM CDT | EF1 | Cass, NE | 2.0 | 40 | |||
| June 11 | 5:15 AM CDT | EF0 | Cass, NE | 0.3 | 20 | |||
| June 11 | 5:21 AM CDT | EF1 | Cass, NE | 2.0 | 40 | |||
| June 11 | 5:29 AM CDT | EF1 | Fremont, IA | 1.5 | 30 | |||
| June 11 | 5:33 AM CDT | EF0 | Mills, IA | 1.7 | 20 | |||
| June 11 | 5:58 AM CDT | EF1 | Page, IA | 7.2 | 100 | |||
| June 11 | 6:08 AM CDT | EF1 | Montgomery, IA | 5.7 | 0 | |||
| June 11 | 6:08 AM CDT | EF1 | Montgomery, IA | 5.7 | 0 | |||
| June 11 | 6:11 AM CDT | EF1 | Page, IA | 1.9 | 50 | |||
| June 11 | 6:26 AM CDT | EF2 | Adams, IA | 6.0 | 200 | |||
| June 11 | 4:05 PM CDT | Unrated | Washington, IA | 0.1 | 0 | |||
| June 11 | 4:15 PM CDT | Unrated | Hancock, IL | 0.2 | 0 | |||
| June 11 | 4:54 PM CDT | Unrated | McDonough, IL | 0.1 | 0 | |||
| June 11 | 4:56 PM CDT | EF3 | Woodford, IL | 11.2 | 930 | |||
| June 11 | 5:17 PM CDT | EF0 | Fulton, IL | 2.4 | 30 | |||
| June 11 | 5:31 PM CDT | Unrated | Fulton, IL | 0.2 | 20 | |||
| June 11 | 5:31 PM CDT | EF1 | LaSalle, IL | 4.4 | 500 | |||
| June 11 | 5:32 PM CDT | EF3 | Livingston, IL | 11.9 | 600 | 7 | ||
| June 11 | 5:44 PM CDT | EF1 | Livingston, IL | 22.8 | 900 | |||
| June 11 | 5:55 PM CDT | Unrated | Livingston, IL | 0.8 | 250 | |||
| June 11 | 5:58 PM CDT | Unrated | LaSalle, IL | 0.3 | 100 | |||
| June 11 | 6:08 PM CDT | EF1 | Tazewell, IL | 12.9 | 300 | |||
| June 11 | 6:12 PM CDT | EF1 | Kenosha, WI | 0.5 | 75 | |||
| June 11 | 6:12 PM CDT | Unrated | Bureau, IL | 1.4 | 0 | |||
| June 11 | 7:01 PM CDT | Unrated | Lee, IL | 6.0 | 50 | |||
| June 11 | 7:06 PM CDT | EF0 | McLean, IL | 11.0 | 100 | |||
| June 11 | 7:08 PM CDT | Unrated | Kankakee, IL | 0.6 | 50 | |||
| June 11 | 7:11 PM CDT | EF0 | Lake, IN | 6.0 | 150 | |||
| June 11 | 7:20 PM CDT | EF1 | Champaign, IL | 9.1 | 0 | |||
| June 11 | 7:23 PM CDT | EF1 | Ford, IL | 6.9 | 100 | |||
| June 11 | 7:25 PM CDT | EF2 | Lake, IN | 6.5 | 700 | 1 | ||
| June 11 | 7:26 PM CDT | EF1 | Champaign, IL | 3.0 | 150 | |||
| June 11 | 7:32 PM CDT | EF0 | Lake, IN | 4.1 | 150 | |||
| June 11 | 7:36 PM CDT | EF0 | Lake, IN | 12.7 | 200 | |||
| June 11 | 7:39 PM CDT | EF1 | Vermilion, IL | 13.6 | 100 | |||
| June 11 | 7:44 PM CDT | EF1 | Vermilion, IL | 8.1 | 100 | |||
| June 11 | 7:45 PM CDT | EF0 | Iroquois, IL | 2.1 | 250 | |||
| June 11 | 7:48 PM CDT | EF1 | Iroquois, IL | 1.2 | 50 | |||
| June 11 | 7:48 PM CDT | EF3 | Lake, IN | 22.5 | 450 | |||
| June 11 | 7:52 PM CDT | EF1 | DuPage, IL | 3.0 | 400 | |||
| June 11 | 7:58 PM CDT | EF0 | Newton, IN | 12.6 | 200 | |||
| June 11 | 8:58 PM EDT | EF1 | Benton, IN | 12.3 | 250 | |||
| June 11 | 7:58 PM CDT | EF0 | Newton, IN | 15.6 | 200 | |||
| June 11 | 8:59 PM EDT | EF0 | Warren, IN | 10.5 | 75 | |||
| June 11 | 8:04 PM CDT | EF0 | DuPage, IL | 1.3 | 150 | |||
| June 11 | 8:15 PM CDT | EF2 | Cook, IL | 8.3 | 350 | 6 | ||
| June 11 | 8:23 PM CDT | Unrated | Porter, IN | 0.2 | 10 | |||
| June 11 | 9:29 PM EDT | EF0 | Barry, MI | 4.6 | 50 | |||
| June 11 | 9:31 PM EDT | EF0 | Kent, MI | 4.2 | 70 | |||
| June 11 | 9:31 PM EDT | EF0 | Carroll, IN | 3.4 | 75 | |||
| June 11 | 9:43 PM EDT | EF0 | Carroll, IN | 0.3 | 25 | |||
| June 11 | 9:46 PM EDT | EF1 | Cass, IN | 0.8 | 250 | |||
| June 11 | 9:58 PM EDT | EF1 | Cass, IN | 1.5 | 100 | |||
| June 11 | 10:11 PM EDT | EF1 | Marshall, IN | 0.7 | 125 | |||
| June 11 | 10:11 PM EDT | EF0 | Marshall, IN | 2.9 | 125 | |||
| June 11 | 10:22 PM EDT | EF1 | Wabash, IN | 4.7 | 0 | 2 | ||
| June 11 | 10:22 PM EDT | EF1 | Marshall, IN | 3.4 | 300 | |||
| June 11 | 10:33 PM EDT | EF1 | Huntington, IN | 5.8 | 75 | |||
| June 11 | 10:39 PM EDT | EF1 | Huntington, IN | 7.9 | 50 | |||
| June 11 | 10:42 PM EDT | EF2 | Elkhart, IN | 6.1 | 100 | 1 |
What this means
Ratings are the survey's, read off the damage rather than measured; the rating scale is above. A survey can be revised, so the rating, the path and the casualties can all still change.
Sources
NWS Damage Assessment Toolkit, the record the survey teams file from the damage, and NOAA Storm Prediction Center storm reports. Neither is the official database for 2026, which SPC publishes in the spring of 2027.