Just thinking my way through challenges faced in the field of Meteorology... Disclaimer: The views expressed in this blog are my own and do not necessarily reflect those of my employer.
Showing posts with label Hurricane Katrina. Show all posts
Showing posts with label Hurricane Katrina. Show all posts
Wednesday, March 18, 2020
Hurricane COVID
August 23rd, 2005. Yet another tropical system, in an active 2004-2005 period, begins getting better organized over the Bahamas. At 5 pm, the first advisory comes out from the National Hurricane Center (NHC) for Tropical Depression 12.
That depression would eventually go on to become the devastating, Hurricane Katrina. What some may not know, or remember, is that Katrina wasn't always expected to have as big of an impact along the north-central Gulf Coast. Two days after becoming better organized, model guidance seemed to be honing in on a possible Gulf Coast landfall near, or just west, of the Florida Big Bend area. This would have been well east of the New Orleans/Biloxi/Mobile areas.
I remember one of my Meteorology professors saying at the end of class that week that they would see us all on Monday (I was going to college at the University of South Alabama in Mobile at the time). I never sensed much doubt in the room as it appeared it would make the northward turn shortly after emerging off the west coast of Florida. After class, I went to work at the grocery story I'd been working at since starting college. With the storm forecast to pass well east of Mobile, I expected a mostly normal day, with perhaps some increase in customers with the storm in the vicinity.
Around 4 or 5 that afternoon, something happened. There was a noticeable increase in customers coming into the store. We always had an evening rush as people got off work, but this was different. There were literal streams of people pouring in from the parking lot. It's one of many images etched in my mental photo library from that hurricane. All of us at the store soon found out why...
Katrina wasn't making that northward turn yet. The delayed turn caused the track to shift further west. The 4 pm CT advisory from the NHC now forecast Katrina to run right into Mobile. That change in the forecast sent residents of Mobile into a whole other level of preparedness. By Sunday morning, August 28, the first visible satellite images of Katrina were absolutely stunning...and worrisome.
Katrina was now a Category 5 hurricane with max sustained winds of 175 mph! The level of preparedness on Friday, August 26th was noticeable, but that level increased even more once people saw the whites of her eye that Sunday morning.
As it relates to COVID-19 (I'll call it COVID for short), I feel like the United States is currently somewhere between the Sunday morning Category 5 image of Katrina and the Monday morning landfall.
There have been preparations and actions taken across the U.S. in recent weeks, but the past few days feel like a whole other level of action. The medical field is outside my expertise, but like Katrina, it seems like something has triggered this recent uptick in response...something equivalent to seeing a category 5 hurricane approaching the coastline.
Human response to weather is something we, as Meteorologists, deal with on a regular basis and it's interesting how similar the response seems to be during non-weather disasters. When COVID started getting more attention, some probably took action right away, while others have waited until seeing the worsening forecast (like Mobile residents seeing Katrina's forecast track shift right over them). And then you still have those that wait to respond until those worrisome "category 5" images appear. For COVID, that might be like seeing a friend or family member get sick (or worse), or watching how bad things have gotten in other countries (like Italy).
In every hurricane I went through while living in Mobile, there was always this anticipatory waiting period. Whatever level of preparation you took, there came a time when preparation mostly ceased, and everyone was left to ride it out and watch it all unfold. I feel like the U.S. is getting into that wait-and-see period. Last-minute preparations are still ongoing, but many seem to be hunkering down for the longer haul.
The "outer bands" of COVID have already reached our shores...now we wait for "landfall". The tough part of waiting is you don't know how it will all turn out. Katrina changed the landscape of the Gulf Coast. What will COVID do? I don't mean that to sound dire or dramatic. It's simply the reality of waiting. It could be as bad as some forecast, or the forecasts could be wrong.
What my family and I have learned from all of the big weather events we've experienced is to take each one seriously, while finding that balance between fear and wisdom. I didn't plan well before Katrina and I paid a price. There probably is a healthy line between preparing and over-preparing, but I'd rather find myself on the over prepared side than the under prepared.
One of the great things I've seen in so many weather events is how people, businesses, and communities put their differences and financial needs aside and come together to help each other. I've already seen that with COVID and it's very encouraging. Once this storm passes, I believe we will look back and see numerous stories of people helping people...that there is still good sprinkled throughout humanity. Weather the storm, then watch for those opportunities as they arise.
There will be hard times in the coming weeks and months, but as a community, we have the choice to come together in preparedness, then come together in recovery. I've seen it work before and after hurricanes, tornadoes, and floods...and I hope to see it after COVID.
Tuesday, February 7, 2017
Messaging Significant Events
Over the past few days, a part of our CWA (NWS Great Falls) has been pounded with heavy snow (here's a PDF from our office with some of the impressive snowfall amounts, records, and pictures). And, when I say pounded, I mean 30-50+" of snow, avalanches, roads nearly impassable or closed, roofs/buildings endanger of collapsing, emergency declarations, people stranded and/or unable to travel, etc. Perhaps pounded isn't a strong enough word, which brings me to the challenge of the day. How do we approach events like these from a forecasting and messaging standpoint?
I am a firm believer that a good message starts with a good forecast and good forecast starts with sound science. For me personally, my approach to forecasting (and this is by no means the only way to do it) has been to pour over the data, then build a forecast that best represents what I am seeing from model data, current observations, input from other forecasters, experience, etc. From there, I step back, look at the finished product, and then try to determine what, if anything, needs messaging. This is all well and good, but what happens when the finished product shows the potential, or even likelihood, of an anomalous event?
Perhaps more experienced forecasters than I don't struggle with this as much, but while working this recent event, stepping back and looking at the forecast prior to the event got me wondering if the ridiculous snowfall amounts I was coming up with were valid. So much so, as soon as I calculated my snowfall amounts, me and the other forecaster I was working with immediately picked up the phone and called a neighboring office that would also be impacted. When they answered, their response was the same. They also were, somewhat dumbfoundedly, looking at the amounts they were coming up with. In fact, in their words, they said, "We [the two forecasters at the other office] have been staring at our computers trying to figure out if these amounts are real."
Turns out, those amounts were real. But, hindsight is always 20/20 and, for many of us in the moment, I think there can be a hesitation to put out such a forecast. For me (and I assume I'm not alone in this), there is that concern of, well what happens if this doesn't actually pan out? This points to a larger question. What is more helpful/harmful? To see the potential and not put the forecast out, or to put it out? If you forecast the high-end event and it happens...awesome! If you forecast the high-end event and it doesn't happen...not so good. But, what if you don't forecast the high-end event and it does happen? Which is worse...forecasting the event and it not happening or not forecasting the event and it happening? Both have negative consequences and this is where the challenge comes in.
Sometimes, I think there is a tendency to back off from higher-end events. Let's face it, oftentimes at least one or two models show a worst-case scenario, only to back off as the event draws near. Or, maybe they never back off, only to be way off in the end. This isn't always the case, but it does happen. And, then, there is the issue of over-hyping an event or the boy who cried wolf syndrome.
But, at the same time, when even one model indicates the potential for a higher-end event, it probably isn't prudent to immediately write it off (outliers do verify at times). And, while never 100% perfect, I think this is where sound science, experience, and collaboration comes in. If after all of this, there is above average, or maybe even average, confidence, perhaps it is time to go ahead and pull the trigger on messaging the event as a higher-end event. Afterall, that is part of our job as Meteorologists. To inform people of the weather. If the weather is going to be really bad, people need to know so they can prepare. We can't make people prepare, but we can at least stress the expected magnitude of an event.
If there was a Messaging Hall of Fame, two statements/events come to mind to be included (and, of course, this is in now way an exhaustive list!) 1) The statement issued by NWS New Orleans prior to the landfall of Hurricane Katrina. That's not a statement any NWS office issues on a regular basis. 2) The higher-end wording by SPC, NWS offices, and the media during the April 27, 2011 tornado outbreak. Both of these events fell outside of the norm, in my opinion, and forecasters had to make the not-always-easy go/no go call on these higher-end watches, warnings, and statements. Should all events be messaged just as hard or do higher-end events need stronger wording?
At the moment, I would tend to lean towards higher-end events need to be messaged harder. A 40" snowfall in a non-mountainous area probably deserves higher-end wording/statements than a 10" snowfall. Winter Storm Warnings, for example, would likely be issued for both, but 40" has the potential to cause more significant impacts/disruptions to everyday life than a 10" snowfall. Both are significant, but again, the challenge is how to approach these higher-end events.
In our case, wind wasn't much of a concern for much of the hardest hit areas, so we felt that a Blizzard Watch/Warning wasn't warranted. Granted, it would certainly grab people's attention. I would imagine, and this is purely speculation, that a Tornado Watch also grabs a lot of attention and probably even more so than a Severe T-storm Watch. But, do you put out a Tornado Watch if you are not expecting any tornadoes? I hadn't thought of this before, but could it be that we approach winter storms like convective events and have PDS Winter Storm Warnings in addition to regular Winter Storm Warnings? For our CWA, I think this event would have justified such a warning. 10" of snow in a snow-prone area is definitely warning-worthy and causes significant issues. But, even here, 40" basically shuts everything down. The local DOT here mentioned in a statement that they are going to have to bring in heavy equipment to remove all the snow and that it would take multiple days to get through. Cars are buried, roads impassable, roofs are struggling to hold the amazing weight of the newly fallen snow. That's not your average winter storm. One of the shifts after mine added wording into the original warning, stating this is a dangerous situation. I thought this was a great idea and reminded me of the kind of enhanced wording SPC uses in PDS Tornado/Severe T-storm Watches.
I think it is always important to look back at an event as an office and as individuals to see how things played out and what, if anything, could be improved on. For me, I put out the higher-end forecast, but wasn't bold enough to go all in with the messaging, even after collaboration with national centers and a neighboring office. Basically, I used the process I mentioned above, but didn't fully apply it, unfortunately. I think the fear of being wrong and the fear of over-hyping or messaging too strongly got the best of me. It's important to make sure you're not missing something, but at the same time, if after a careful scientific/collaborative process, confidence is still above average, I think at a certain point you just have to pull the trigger. I think the lesser of two evils is people preparing for an event that doesn't happen as opposed to not being told of an event and it happening. The latter case, using a snow example, has the potential to leave people stranded with no food, water, power, etc, because who is going to prepare for an event they don't know is coming? Having extra food, water, candles, etc doesn't hurt anyone, but NOT having those things and then NOT having a way to get those things is much worse in my opinion. Perhaps these types of events only happen a few times in any of our careers, but when they do, don't fall into the trap I did of letting fear prevent a stronger-worded message from going out.
On a quick side-note, this event has reminded me that, no matter how good the models become in the future, I still hold firmly to the idea that an understanding of the science behind what the models spit out is vitally important to our messaging. Knowing WHY a model is showing something can help us explain HOW an event is going to play out and even know what to stress that even the best models might be missing out on.
I am a firm believer that a good message starts with a good forecast and good forecast starts with sound science. For me personally, my approach to forecasting (and this is by no means the only way to do it) has been to pour over the data, then build a forecast that best represents what I am seeing from model data, current observations, input from other forecasters, experience, etc. From there, I step back, look at the finished product, and then try to determine what, if anything, needs messaging. This is all well and good, but what happens when the finished product shows the potential, or even likelihood, of an anomalous event?
Perhaps more experienced forecasters than I don't struggle with this as much, but while working this recent event, stepping back and looking at the forecast prior to the event got me wondering if the ridiculous snowfall amounts I was coming up with were valid. So much so, as soon as I calculated my snowfall amounts, me and the other forecaster I was working with immediately picked up the phone and called a neighboring office that would also be impacted. When they answered, their response was the same. They also were, somewhat dumbfoundedly, looking at the amounts they were coming up with. In fact, in their words, they said, "We [the two forecasters at the other office] have been staring at our computers trying to figure out if these amounts are real."
Turns out, those amounts were real. But, hindsight is always 20/20 and, for many of us in the moment, I think there can be a hesitation to put out such a forecast. For me (and I assume I'm not alone in this), there is that concern of, well what happens if this doesn't actually pan out? This points to a larger question. What is more helpful/harmful? To see the potential and not put the forecast out, or to put it out? If you forecast the high-end event and it happens...awesome! If you forecast the high-end event and it doesn't happen...not so good. But, what if you don't forecast the high-end event and it does happen? Which is worse...forecasting the event and it not happening or not forecasting the event and it happening? Both have negative consequences and this is where the challenge comes in.
Sometimes, I think there is a tendency to back off from higher-end events. Let's face it, oftentimes at least one or two models show a worst-case scenario, only to back off as the event draws near. Or, maybe they never back off, only to be way off in the end. This isn't always the case, but it does happen. And, then, there is the issue of over-hyping an event or the boy who cried wolf syndrome.
But, at the same time, when even one model indicates the potential for a higher-end event, it probably isn't prudent to immediately write it off (outliers do verify at times). And, while never 100% perfect, I think this is where sound science, experience, and collaboration comes in. If after all of this, there is above average, or maybe even average, confidence, perhaps it is time to go ahead and pull the trigger on messaging the event as a higher-end event. Afterall, that is part of our job as Meteorologists. To inform people of the weather. If the weather is going to be really bad, people need to know so they can prepare. We can't make people prepare, but we can at least stress the expected magnitude of an event.
If there was a Messaging Hall of Fame, two statements/events come to mind to be included (and, of course, this is in now way an exhaustive list!) 1) The statement issued by NWS New Orleans prior to the landfall of Hurricane Katrina. That's not a statement any NWS office issues on a regular basis. 2) The higher-end wording by SPC, NWS offices, and the media during the April 27, 2011 tornado outbreak. Both of these events fell outside of the norm, in my opinion, and forecasters had to make the not-always-easy go/no go call on these higher-end watches, warnings, and statements. Should all events be messaged just as hard or do higher-end events need stronger wording?
At the moment, I would tend to lean towards higher-end events need to be messaged harder. A 40" snowfall in a non-mountainous area probably deserves higher-end wording/statements than a 10" snowfall. Winter Storm Warnings, for example, would likely be issued for both, but 40" has the potential to cause more significant impacts/disruptions to everyday life than a 10" snowfall. Both are significant, but again, the challenge is how to approach these higher-end events.
In our case, wind wasn't much of a concern for much of the hardest hit areas, so we felt that a Blizzard Watch/Warning wasn't warranted. Granted, it would certainly grab people's attention. I would imagine, and this is purely speculation, that a Tornado Watch also grabs a lot of attention and probably even more so than a Severe T-storm Watch. But, do you put out a Tornado Watch if you are not expecting any tornadoes? I hadn't thought of this before, but could it be that we approach winter storms like convective events and have PDS Winter Storm Warnings in addition to regular Winter Storm Warnings? For our CWA, I think this event would have justified such a warning. 10" of snow in a snow-prone area is definitely warning-worthy and causes significant issues. But, even here, 40" basically shuts everything down. The local DOT here mentioned in a statement that they are going to have to bring in heavy equipment to remove all the snow and that it would take multiple days to get through. Cars are buried, roads impassable, roofs are struggling to hold the amazing weight of the newly fallen snow. That's not your average winter storm. One of the shifts after mine added wording into the original warning, stating this is a dangerous situation. I thought this was a great idea and reminded me of the kind of enhanced wording SPC uses in PDS Tornado/Severe T-storm Watches.
I think it is always important to look back at an event as an office and as individuals to see how things played out and what, if anything, could be improved on. For me, I put out the higher-end forecast, but wasn't bold enough to go all in with the messaging, even after collaboration with national centers and a neighboring office. Basically, I used the process I mentioned above, but didn't fully apply it, unfortunately. I think the fear of being wrong and the fear of over-hyping or messaging too strongly got the best of me. It's important to make sure you're not missing something, but at the same time, if after a careful scientific/collaborative process, confidence is still above average, I think at a certain point you just have to pull the trigger. I think the lesser of two evils is people preparing for an event that doesn't happen as opposed to not being told of an event and it happening. The latter case, using a snow example, has the potential to leave people stranded with no food, water, power, etc, because who is going to prepare for an event they don't know is coming? Having extra food, water, candles, etc doesn't hurt anyone, but NOT having those things and then NOT having a way to get those things is much worse in my opinion. Perhaps these types of events only happen a few times in any of our careers, but when they do, don't fall into the trap I did of letting fear prevent a stronger-worded message from going out.
On a quick side-note, this event has reminded me that, no matter how good the models become in the future, I still hold firmly to the idea that an understanding of the science behind what the models spit out is vitally important to our messaging. Knowing WHY a model is showing something can help us explain HOW an event is going to play out and even know what to stress that even the best models might be missing out on.
Subscribe to:
Posts (Atom)



