The funnel doesn't drop.
It descends.
Most people think a tornado is a really bad storm. It's not. A tornado is the bottom of a rotating column that started turning thirty thousand feet above your head, half an hour before the funnel ever became visible. This lab pulls that column apart so you can see how it actually works.
§1.1What's in here
Tab 02 · Anatomy takes you inside a supercell — the four ingredients (CAPE, shear, moisture, lift) that turn a regular thunderstorm into a rotating one. Tab 03 · The Funnel is the headline: a 3D tornado you can orbit around, with a time slider that shows formation from the top down. Tab 04 · Intercept drops you on I-22 between Birmingham and Tupelo with a storm bearing down — same corridor the Hackleburg EF5 traveled. The storm doesn't move in a straight line, and neither do you.
§1.2Dixie Alley
This is a teaching lab. The visualizations are stylized — the 3D funnel uses a particle system that captures the look of tornado formation, not a real fluid dynamics simulation. Storm intercept geometry uses simplified vector math with Monte Carlo noise on the storm's path; real tornadoes are far less predictable. Numbers, EF ratings, and historical events are accurate to published sources.
This is not a forecasting tool. If you are actually in a tornado warning, take shelter on the lowest floor of the most interior room, put as many walls between you and outside as possible, and stay there until the warning expires. If you are on the road, do not try to outrun a tornado — get to a sturdy building. If no building is available, abandon your vehicle and lie flat in a ditch with your hands over your head.
§1.3Notation
Through the lab: CAPE = Convective Available Potential Energy (J/kg), the fuel. shear = vertical change in wind direction/speed (kt), the twist. SRH = Storm-Relative Helicity, a measure of streamwise rotation available to a storm. vs = storm motion (mph). vc = your car's velocity. σ = uncertainty in storm direction, in degrees.
Anatomy · four ingredients of a rotating storm
A regular thunderstorm rises and rains itself out. A supercell does something the regular one can't: it tilts the horizontal wind into vertical rotation and keeps the updraft and downdraft separated. That separation is the whole game.
Ingredients
Cross-section · the storm pulled apart
The updraft (warm, moist air rising on the right) feeds the storm. The forward-flank and rear-flank downdrafts (cool, rain-cooled air sinking on the left) wrap around it. Where the rear-flank downdraft meets the inflow at the surface — that's the tornado cyclone, the small-scale rotation that produces the funnel.
Why the four ingredients matter
CAPE is gasoline. It measures how much energy a rising parcel of air has available to it. High CAPE means strong, deep updrafts that can reach 60+ mph upward — strong enough to suspend hailstones, strong enough to keep precipitation out of the rotation column.
Shear is the twist. If the wind direction and speed change with height — say, south at 15 mph at the ground, southwest at 35 mph at 3,000 ft, west at 60 mph at 6,000 ft — that creates a horizontal rolling motion in the air column. The updraft tilts that horizontal roll into the vertical, and the storm starts to rotate. Without shear you get a thunderstorm; with shear you get a supercell.
Moisture is the trigger condition. Without enough water vapor near the surface, rising air doesn't condense enough to release the latent heat that powers a deep convective cloud. Gulf of Mexico moisture is why the Southeast is a tornado factory in spring.
Lift is what gets the air parcel moving up in the first place — a cold front plowing in, a dry line, a warm front, an outflow boundary from a previous storm. The lift initiates; the other three ingredients decide what kind of storm you get.
↗ Roadmap · v0.1 and beyond
v0.1 Add hodograph display showing wind vectors with height — the visual signature of streamwise vorticity.
v0.2 SRH (storm-relative helicity) calculation tied to the shear slider.
v0.3 Storm-mode classifier with multicell / linear / discrete supercell / HP supercell / LP supercell decision tree.
v1.0 Real sounding data loader (RAOB / RAP analysis) so you can pull April 27 2011 12Z Birmingham and see what the actual setup looked like.
The Funnel · top-down formation, in 3D
Rotate around it. Scrub the time slider. Watch the funnel descend from the cloud base, touch down, and become a tornado.
Formation stage
What you're watching
Stage 1 · Wall cloud. A lowered, rotating base of cloud hanging from the southwest flank of the supercell. The mesocyclone — 2 to 6 miles wide — is the rotation aloft that the wall cloud is the visible bottom of. Most wall clouds don't produce tornadoes; the ones that do typically take 10 to 20 minutes to spin up first.
Stage 2 · Funnel cloud. Condensation extends downward from the wall cloud as the pressure inside the rotating column drops below the surrounding air. The drop in pressure cools the air enough to condense moisture — that's why you can see the funnel. The wind is rotating all the way to the ground long before the visible funnel reaches it.
Stage 3 · Touchdown. The pressure drop reaches the surface; if there's enough moisture, the funnel cloud becomes continuous to the ground. If the air is dry, you'll see a debris cloud at the base before the condensation funnel ever fills in.
Stage 4 · Mature. Full intensity. The funnel is widest, the debris cloud is largest, and the inflow at the base is moving 100+ mph horizontally toward the tornado.
Stage 5 · Rope-out. The tornado tilts, narrows, and contorts into a thin rope as the rear-flank downdraft cuts off the inflow. This is often the most photogenic and most dangerous stage — rope tornadoes can suddenly snap and change direction.
↗ Roadmap · v0.1 and beyond
v0.1 Real angular momentum conservation: rotation speed varies inversely with radius (skater pulling arms in).
v0.2 Multi-vortex tornado mode — sub-vortices orbiting the main circulation, like the El Reno 2013 event.
v0.3 Pressure drop visualization · color-coded core showing the >100 mb deficit at the center.
v0.4 Touch/drag orbit instead of slider only.
v1.0 True 3D scene with Three.js, optional VR.
Intercept · the I-22 corridor, with uncertainty
Birmingham, Alabama to Tupelo, Mississippi. The I-22 corridor — the same path the Hackleburg EF5 traveled on April 27, 2011. Your car is moving northwest. A supercell is coming out of the southwest. Storms don't drive in straight lines. Neither do you.
The storm
You
§4.1The corridor · plan view
The math you're playing with
Two objects, two velocity vectors. The classic geometry problem is: given object A moving with velocity vA from position pA, and object B with vB from pB, when (if ever) are they closest, and how close do they get?
The answer is just algebra — you find the time when the squared distance is minimized, then check whether that distance is less than the radius of the storm's damage path. If your closest approach is less than the tornado radius, you got hit. If it's bigger, you punched through.
But the storm doesn't go in a straight line. Every minute or so it wobbles a few degrees — the rotation isn't perfectly steady, the surrounding flow shifts, the storm interacts with terrain. The uncertainty cone shows where the storm might be in 10 minutes, given how much it's wobbling. Run the simulation once and you get one outcome. Run it 25 times with the same dials and you get a probability — that's why the Monte Carlo button is there.
v0.1 note Two things had to change to make storm width matter. First: the radius slider now goes up to El Reno's 2.6-mile damage path, because the geometry can produce closest-approach values bigger than 1 mile and you were stuck capped below them. Second: the wobble was too tight — sigma had almost no visible effect on path variance, so every Monte Carlo run came out nearly identical and width either always-hit or never-hit.
v0.3.2 MATH FIX Then Travis noticed: at vertical (0°) and horizontal (90°) bearings the Monte Carlo fan was symmetric, but every diagonal bearing (45°, 135°, etc.) skewed the trails toward the "south end" of the spread. That's a real second-order curvature bias in the original "add a random angle to the bearing" model — Taylor-expand sin(b+w) and -cos(b+w) and the w² terms break left/right symmetry at diagonals. Fix: wobble the perpendicular velocity instead of the bearing angle (same sigma input, same OU damping, no curvature bias). Now the Monte Carlo fan is centered exactly on the deterministic trajectory at every bearing.
v0.2 BUG FIX The storm's starting position used to be anchored to the car's starting waypoint — 35 miles SW of wherever you began. That meant Birmingham start → storm at SW Birmingham; Tupelo start → storm at SW Tupelo. The corridor never crossed the storm path; the car was always ahead of the storm by design. v0.2 fixes this: the storm has a fixed origin regardless of where you put the car. Your car-start choice is a real choice about WHERE you are along I-22 when the storm crosses it.
v0.3 BUG FIX v0.2 picked a storm anchor that was actually off-canvas at (1.04, 0.96), and worse: the picture-rendering function still used the OLD car-derived anchor while the simulation used the new one. Picture and math diverged — that's why you saw the storm icon sitting south of Winfield but Monte Carlo reported 288,000-yard closest approach and the red trail lines disappeared. v0.3 unifies the anchor (now 0.41, 0.59, just SW of Winfield in real-world Marion County AL).
v0.3.3 — Designed intercept default (BHM → NW) Travis: "Whatever your starting settings are, hit Monte Carlo, take out the car somewhere along that path with high probability." Done. Defaults now ship as: car starts Birmingham, going NW toward Tupelo at 70 mph; storm bearing 68° NE at 29 mph from Marion County, σ=8°, damage radius 2,500 yd. The storm's centerline trajectory crosses the I-22 corridor near mile 75 (just SE of Winfield) at t≈64 min — exactly when a 70-mph BHM-NW car arrives at that mile mark. Hit RUN 25 TIMES → expect ~60–70% hit rate. The car gets taken out somewhere between Jasper and Winfield, most of the time. Move sliders away to explore: switch to PULLED OVER and the storm misses the empty-corridor crossing point; switch to SE and you'll be driving away from the intercept; bump σ up to 15° and the wobble disperses the hit rate.
↗ Roadmap · v0.1 and beyond
v0.1 SHIPPED Monte Carlo hit logic now responds to storm width — slider max raised to El Reno's 4,576 yd; wobble dampening loosened so sigma actually produces path variance.
v0.2 Real I-22 road geometry from OpenStreetMap with actual mile markers.
v0.2 "Pull off here" overpasses and gas stations along the route (note: NWS now actively discourages overpass sheltering — show why).
v0.3 Multiple storms (squall line vs discrete cells) and storm splitting (right-mover / left-mover).
v0.4 Time-of-day toggle — Dixie Alley's killer feature is night tornadoes you can't see.
v1.0 Hurricane mode · larger scale, longer timescale, storm surge inundation model. Same rotational physics, three orders of magnitude bigger and slower.