Community. Driven. Weather. Data. | Always Ad-Free | Developer FriendlyChecking statusDiscord
WxAlerts.org, Community Driven Weather Data
Support us
Sign in
Lesson 09 of 0930 minBeyond SKYWARN

Capstone: Hurricane Ivan, 15 to 16 September 2004

Everything in this module, applied to one documented event where almost nothing was visible and the warnings went out anyway.

By the end of this lesson
M4.9.aSequence rotation cues chronologically from imagery and radar for a real event.
M4.9.bMake reportable and not-reportable calls carrying time, location and measured-or-estimated metadata.
M4.9.cJustify each call against the NWS criteria stated earlier in the module.

The event

Ivan came ashore near the Alabama and Florida line early on 16 September 2004. The tornado outbreak in its rainbands had already begun the day before and ran across the south-east.

Two of those deaths and much of the damage in this office's area came from a pair of F2s on 15 September: Panama City Beach in Bay County, one death and seven injuries, and Blountstown in Calhoun County, four deaths and one injury. The Tallahassee forecast area counted 24 tornadoes in all: 14 F0, 8 F1 and 2 F2.

A note on the count, because you will meet a different one: NCDC catalogues the wider continuous outbreak at 120 tornadoes, passing Hurricane Beulah's 1967 record of 117. This lesson uses the NWS and AMS figure of approximately 117 throughout so the numbers here agree with each other. Both are real counts of slightly different things.

What the office was working with

This is the part worth studying. NWS Tallahassee monitored more than fifty identified mesocyclones over the event and issued 130 tornado warnings.

NWS Tallahassee, Ivan
Tornado warnings issued130
Verified20
Not verified110
Tornado events23 (21 warned, 2 unwarned)
Probability of DetectionOf the severe weather events that actually happened, the fraction that were warned. Events nobody warned pull it down.0.913
False Alarm RatioOf the warnings issued, the fraction that were not followed by a verified event. An office could drive it to zero by warning almost nothing, at the cost of its POD.0.846
Critical Success IndexA single score combining hits, misses and false alarms, so an office cannot look good by warning either far too much or far too little. Lower than both POD and FAR would suggest on their own.0.152
Average How long between a warning being issued and the severe weather arriving. Quoted two ways: counting only the warnings that beat the event, or averaging in the events nobody warned at all, which roughly halves it.11.2 min
Events with lead time above zero78.3%

Watson, Jamski, Turnage, Bowen & Kelley, NWS Tallahassee. These are the office's own published numbers for its own performance.

Why nobody could see anything

Every difficulty from lesson 8 was present at once. The storms were A supercell with a shallower, smaller and weaker rotating updraft than a classic one, typical of tropical cyclone rainbands. Produces tornadoes in an environment with a fraction of the instability a Plains supercell needs. in tropical rainbands with shallow, small circulations. They were rain-wrapped. Much of the activity ran through the night. And the whole region was already inside a landfalling hurricane, so the conventional advice to find a safe vantage with a clear view to the south-west was not available to anybody.

A spotter's value in that event was not in confirming funnels. It was in damage reports, timings and locations after the fact, which is what turned 20 of those 130 warnings into verified events and left a record precise enough that we can read the office's performance twenty years later.

What a report needed to carry

The WHEN clause is the one that decides whether a report verifies a warning. A damage report timed to when you called it in rather than when the damage happened can fall outside the warning The shape a warning is drawn on, replacing whole-county warnings in 2007. Being inside the shape is what matters, not which county you are in.'s valid window and verify nothing. In a nocturnal, rain-wrapped outbreak where after-the-fact damage reports are most of the ground truth available, that detail is doing more work than any funnel identification.

Knowledge checkNot graded · the exam draws a fresh variant of this item

NWS Tallahassee finished the Ivan outbreak with a POD of 0.913 and a FAR of 0.846. What does that pair of numbers describe?

POD is measured against events. FAR is measured against warnings. They can move independently.
Sources for this lessonWatson, Jamski, Turnage, Bowen & Kelley, NOAA/NWS Tallahassee: the tornado outbreak across the north Florida panhandle in association with Hurricane Ivan (AMS 32nd Radar Conference, paper 10R.3)NWS Weather Spotter's Field Guide (YPA-201154, June 2011)Edwards 2012, Electronic J. Severe Storms Meteor. 7(6), 1–61: tropical cyclone tornadoes, a review of knowledge in research and predictionNSSL Severe Weather 101, tornado basics and tornado types

← Module overview
Sign in to save your progress
End of module 04Identifying rotationBack to the module overview and what comes nextOverview