It took longer than I’d have liked to publish the results of this contest. I was traveling out of the country. But I’d like to congratulate KP on winning the Lee forecast contest.
One thing that I realized after the fact: my changes below made it so only whole numbers could be used for latitude and longitude. I’ve fixed that for next time!
The prodigal game returns! A technical glitch ruined the Dorian contest in 2019, so we haven’t seen a Funnel Fiasco tropical forecast game since Hurricane Matthew in 2016. But I’m pleased to announce that we’re up and running for Hurricane Lee. You can submit your landfall forecast by 2100 UTC on Wednesday 13 September.
In keeping with tradition, we’re still using the same crappy Perl script I wrote in 2005. Despite the fact that I’ve been putting off a total rewrite for over a decade, I did make a few improvements recently:
Numerical fields now require numeric input. If you were hoping to submit “butts” as your wind speed, I’m sorry to disappoint you.
Coordinates are constrained to reasonable ranges. I refuse to give in to Kevin’s whining about west being negative numbers. (I believe my exact words to him were “take it up with the Prime Meridian.”) But I was feeling magnanimous so I’ve constrained the latitude to 0–90 degrees north and the longitude to 180 degrees west to 10 degrees east.
Similarly, wind speed is now constrained to realistic values. You can’t submit a wind speed less than zero or above 200 miles per hour.
Furtherly similar, the time segments can’t be negative or overflow.
So go ahead and submit your forecast by 2100 UTC on Wednesday so you can join in the grand tradition.
Over the weekend, the volcanic island of Hunga Tonga-Hunga Ha’apai erupted in the south Pacific. People as far away as Alaska heard the sound. Here in Indiana, we did not. But we were able to detect the shock wave from the explosion as a rapid pressure change.
In fact, you can watch it cross the continental US by plotting the pressure changes, as Daryl Herzmann did.
A little after midnight, the pressure wave came around from the other side of the globe. Alerted to this possibility by Daniel Dawson, I grabbed the graph from my weather station again.
A couple of friends independently directed me to a recent forecast discussion from Peachtree (Atlanta). Forecaster Kyle Thiem embraced his inner poet when he wrote the long-term discussion entirely in haiku. (Full disclosure: I didn’t count syllables to verify.) The discussion is now forever enshrined in the Forecast Discussion Hall of Fame.
On Friday, I was looking at the radar and I thought “gee, that storm a few miles away from me looks like it might have a little bit of rotation.” I talked myself out of it. This means, of course, that it produced two tornadoes an 18 minute drive from my house. On Saturday when I saw some storms getting their spin on in central Illinois, I refused to be fooled again. So I woke my girlfriend from a nap and we got in the car heading toward Paxton.
As we pulled into Hoopeston, I had a choice to make. There were some cells popping up from Paxton to Mahomet that looked interesting but not particularly spinny. The main squall line was meh except further north. I had to pick an option. My risks were basically “nothing happens” to the south or “stuff happens but you can’t see it” to the north. Given the choices, I decided to engage to the south.
We turned down IL 1 toward Rossville. I figured we’d cut west from there to get under the storms. Unfortunately, the storms were speeding up, and I quickly decided that staying near IL 9 was the better option. We took a county road back north and made it all the way to IL 9 when we encountered a flooded roadway. With John Fausett in mind, we turned around (and didn’t drown) after driving about half a mile in reverse. We picked the next county road west and went north.
The storm was near Rankin at this point and it seemed to be showing some signs of rotation. We stopped to watch it for a few minutes and saw some lowerings, but there was no spinning.
After a few minutes, it was time to reposition again. The storm had become uninteresting, so I decided to follow it’s friend slightly to the south. From our position looking southwest, it looked pretty nice.
We dropped south a bit to meet it and then followed east and a little north to watch it further. At that point, we were a little east of Wellington. The lowering maybe showed a little bit of weak rotation, but it was never obvious. After a few minutes, it became an mess.
These storms were basically done (although there was a report of a funnel cloud near Earl Park, IN later). There were some tornado warnings in the line near Villa Grove. After driving through near-zero visibility on the east side of Hoopeston, we went south on IL 1 for a little bit. But after a few minutes, the line looked less interesting and it didn’t seem worth staying out for. Also, the bag of Combos that I ate was not a reasonable dinner.
We managed to beat the line back to Lafayette by 5-10 minutes. For an unplanned chase, I’m okay with how this turned out. I feel like the decisions I made were reasonable, which was not a given considering I haven’t seriously chased in ten-plus years. Missing a photogenic tornado minutes from my house still stings, but I feel good about doing this again in the future.
Well it took approximately forever, but I finally got around to updating the back end tech for my website (post coming soon!). That means I can catch up on a backlog of Forecast Discussion Hall of Fame nominees.
I have added four new entries to the Social Media Foyer: tweets from NWS offices in Atlanta, Paducah, and Pittsburgh, as well as a Facebook post from Nashville. Plus: a Public Information Statement that includes a map, a Santa Claus watch, forecasters in Juneau telling you to go outside, a sweet discussion with no tricks, an “I’m only doing this because I have to”, a not-so-super Mario, and monster wrestling. Because you’ve all been so patient, there’s also a new entry in the ISIXTYFIVE section where he comes to the conclusion that he sucks.
Some of these have been sitting in my inbox since January 2018, so I apologize in being slow to add them. You get what you pay for sometimes.
The National Weather Service (NWS) is collecting public comment on some proposed changes to severe thunderstorm warnings. These changes would add damage threat labels for wind and hail threats. The three tiers are (no label), considerable, and destructive.
> 60 mph
> 70 mph
> 80 mph
As part of the proposal, the NWS says, they will recommend that destructive severe thunderstorms trigger a wireless emergency alert (WEA) message. This means most modern cell phones will receive an alert for the highest-end storms. According to an analysis by Joseph Patton, this would apply to just over 1% of severe thunderstorm warnings. (This percentage will vary by time and location.)
I am 100% on board with this proposal. Let’s be honest with ourselves: most people ignore severe thunderstorm warnings. I’ll be the first to admit that I do. Once I’m inside, I’m safe enough without taking extra precautions. But those top-end storms can do damage similar to tornadoes. Being able to distinguish between “get inside” and “get to the basement” severe storms is helpful.
Now I’ve suggested before that tornado and severe thunderstorm warnings should be combined into a single product. I still hold that opinion. Intensity of the threat matters more than the specific mechanics of the threat. But I very much doubt the NWS will implement that idea any time soon. This proposal at least allows for cleaner communication of the most life-threatening thunderstorms.
You can give the NWS your own opinion via online survey before July 30, 2020.
Sporting events — particularly in the spring and summer when they’re generally done outdoors — present a hazard to participants and spectators alike. Thunderstorms can send a bolt of lightning in an instant, which can prove lethal. Part of the danger is that lightning can strike miles away from the storm, which means people who think they aren’t at risk might be very much at risk.
Many leagues and venues have adopted a largely sensible lighting policy. If lightning strikes within a certain radius, the activity is suspended and everyone is sent to shelter. After some amount of time without a strike (often 30 minutes), the activity resumes. This is, as a general concept, good advice.
Of course, it’s not quite as simple as “if you can see it, flee it. If you can hear it, clear it.” That’s the advice given to the public because it’s simple and easy to remember. But it doesn’t always capture the full story.
To give an example, this summer my local baseball team was playing a game as thunderstorms approached the area. A lightning strike occurred within the 10 mile radius defined by the Prospect League (as an aside, I appreciate the fact that they increased it from the 5 miles it used to be). The umpires suspended play late in the game (it was the 8th inning if I recall).
The trouble with this is that the storm was traveling perpendicular to the stadium. The strike that triggered the delay was well away from the storm and just inside the 10 mile radius. Essentially, it was as close as lightning would come. In this case, continuing play would be a safe decision. And it would have meant pitchers could stay warm and the crowd would have stuck around.
When it comes to weather safety, I’d always prefer overcaution to undercaution. But weather is complex, and the simple rules don’t always fit the situation. Sporting events should always leave weather decisions to meteorologists. High-profile near-misses have raised awareness, but it’s still not universal.
Due to a technical error with the forecast submission script. the contest is cancled. I’m not sure I want to invest any more time in fixing this old and busted script, and I have yet to make good on my ten years of “I will rewrite it this winter”, so this may be the end of tropical forecast contests on Funnel Fiasco.
It’s that time of year again! Submit your forecast for mainland landfall by 0000 UTC on 29 August (8pm ET on Wednesday).
Longtime readers of Blog Fiasco know that I have some opinions about how the National Weather Service (NWS) issues and communicates warnings. Just check out the “warning” tag on this site if you’re interested. But it turns out that I have as-yet-unwritten opinions. This post is inspired by a recent tweet from an NWS meteorologist:
I mentioned in a previous post that warning products tend to be technically correct instead of useful, as in the case of the non-hurricane Sandy. This is a fine example. Tornadoes over water are waterspouts and the NWS treats maritime areas (including larger lakes) differently than land areas. The end result is that forecasters are unable to properly communicate threats to the public. This is harmful.
I understand treating land and water areas differently. A storm that is unremarkable on land could be deadly to watercraft. Special marine warnings are usefully distinct. But a tornado warning over water can be useful, too, particularly to folks on land who happen to be downstream. But forecasters aren’t allowed to provide that information because it’s not technically correct.
The National Weather Service is a great agency. The dedicated forecasters are at work around the clock to provide life-saving (and life-enhancing) forecasts and warnings. I just wish it would get out of it’s own way on this issue.
It’s no secret that the Saffir-Simpson scale, used to rate the strength of hurricanes, is inadequate. It is based solely on wind speed, which does a poor job of communicating the potential impacts. I wrote just a few months ago that it’s time to consider retiring it. So when I heard that AccuWeather rolled out a new hurricane scale, you might think I’d be in favor of it.
You would be wrong.
It’s not that I think AccuWeather’s leadership is awful. I do, but that’s not the point here. The AccuWeather RealImpact Scale for Hurricanes does not address the fundamental weakness of the Saffir-Simpson scale because it still produces a single number. That this number is produced from more inputs isn’t novel (the original Saffir-Simpson scale included other aspects of a hurricane threat) nor is it better at explaining the threat. You still need to tell the public why it received a particular rating, and the preparation for wind damage may be different from storm surge may be different from inland flooding.
Not to mention the fact that the scale is opaque. It cannot be reviewed by researchers and meteorologists outside of AccuWeather. There’s no indication that it’s had any input from social scientists and science communication experts to make sure it even accomplishes the stated goal of improving communication to the general public. In short, it’s just AccuWeather acting on its own and pretending there’s value.
After insulting National Weather Service employees by falsely implying that forecasts are degraded during this government shutdown, AccuWeather would do well to shut up for a little bit and work with the meteorological community.