Jump to content

BeauDodson

Meteorologist
  • Posts

    413
  • Joined

  • Last visited

Posts posted by BeauDodson

  1. I doubt that's it. It's hard to go against 200 kt couplet with debris ball. My thinking is the forecaster put the location as "Joplin" in AWIPS, which spat out an alternate location of "6 NE Galena". The Downtown Joplin *dot* is in fact north and east of the central Galena *dot*, and that's all that AWIPS has. In the whole confusion during that time, and dealing with multiple TORs in close proximity, the forecaster(s) may have not paid as much attention to that error, or they may have felt it would take to long to correct, given the urgency of the situation.

    This is a problem. I hope this issue has been addressed within the NWS. I am a bit alarmed by the incident a few weeks ago in my local area - afternoon reading your comments and this book. If a computer is spitting out these names and errors and the NWS isn't "catching it" - then we have a problem.

    I don't know if this is a bigger issue or not. It is a question worth discussing. Surely the NWS can correct the storm movement based on what they were seeing. Or - perhaps in this case - it was simply just a bad error.

  2. My take on this.

    1) SW side of Joplin/Iron Gates had had minimum 15-20 min lead time, using the 5:38 PM radar image posted above and the fact the relevant TOR was issued at 5:17.

    2) The first relevant TOR indicated that the storm was moving NE, which was ultimately incorrect, however while the storm was still in its fledgling stage this may have been a valid extrapolation of the motion. In their formation stages, supercells often move with the mean wind at a rapid clip, before sharply turning right and slowing down as the updraft matures (but not always!). So, until we are more sure with our science, and given the software that's in use, extrapolated motion's the best we got. Of course everything is clearer in hindsight.

    3) The SVS's correct the initial TORs and give a correct heading -- except for the last one.

    3) The cities impacted -- Iron Gates, Joplin, and Duquesne, are mentioned in every SVS as well as the initial relevant TOR -- except for the last one WRT Duquesne.

    4) I agree that there is this (dare I say it?) --myth-- about the tornado forming right over town. There was a good chunk of time between spotter confirmation and tornado doing damage in Joplin. I think by the second SVS, a tornado emergency may have been justified, given the confirmation and the statement that the tornado was in fact moving straight into town.

    So the only thing I would have a beef with is SGF's 5:42 SVS, but by then the tornado was over the city and doing damage so it doesn't really matter as much. I also agree that the proximity of the two TORs may have confused media. Many things could've been done better, but the warning system hardly 'failed' Joplin.

    I don't disagree with your assessment after the fact. My concern is that people were not reading the warnings. Who do we know that reads tornado warnings? They were likely going on what the on-air people were saying (and according to Mikes book) the radar stations were telling them. They were not telling them that they were in danger.

    It is obvious - after seeing the warnings/svs - that there was a lot of confusion. Mike is likely correct on that subject. I think there may have been more confusion than some of us from outside the region realize. This is because of the on-air meteorologists and radio broadcasters reading the warnings and not checking their own radars for verification of what the NWS was saying.

    Mike even goes as far to say that the on-air mets didn't even realize they were looking at a tornado on their tower cam - they thought some of the power flashes were lightning. It wasn't until it was too late that they realized they were looking at a very large tornado hitting their city.

    Was a tornado emergency issued? I don't remember. I remember being in chat that day and telling them that there was a lot of damage being reported - also reported some baseball size hail. Mike says - implies or says - that hail was never a concern and that baseball size hail never occurred.

    I remember making a report to their office of baseball size hail somewhere north of Jomo. Do not remember exactly where - but it the report was made. Of course nobody cared about the hail at that point - it was too late.

    Mike also has some eye witness accounts that told him they felt the main concern for Joplin was hail and this was based on what the media was saying.

    I should pull up the logs from that day and see what was being said in the room.

  3. Yep, that was the mistake. The tornado was not 6 miles NE of Galena and it was not moving NE at 45. The area was in the polygon either way, just the SVS statement was incorrect. I think the next tornado warning was issued at 5:48.

    And this is apparently where the confusion was - on-air mets and radio rip and read were telling people the wrong area.

    I guess the next question is how many residents heard the wrong information and thought "that is not near me - I am safe"

    We will never know. According to the book some people interviewed said they kept talking about Galena and they felt safe in southern Joplin.

    Someone with a radar should have caught the mistake. Private meteorologists - on-air television meteorologists - others. We knew this was an error on the forum - or we at least knew Joplin was in serious trouble. Why didn't others know this? Was it because they were too busy covering the storm - weekend - not enough staff?

    Had this been in Oklahoma City then I can almost guarantee you that the on-air mets would have caught it. They have their own radars - they would have been able to see that the storm was forming and moving east into the part of Joplin that was hit.

    Do any stations in the Joplin region have their own radar equipment - Barron or other?

  4. TRAINED WEATHER SPOTTERS REPORTED A TORNADO NEAR

    JOPLIN...OR 6 MILES NORTHEAST OF GALENA...MOVING NORTHEAST AT 45 MPH.

    LOCATIONS IMPACTED INCLUDE AIRPORT DRIVE...ALBA...ATLAS...BROOKLYN

    HEIGHTS...CARL JUNCTION...CARTERVILLE...LAKESIDE...NECK CITY...

    NORTHEASTERN JOPLIN...OAKLAND PARK...ORONOGO...PURCELL AND WEBB CITY.

    I think there is the issue - brought up in the book.

    That does not mesh.

    If the tornado was 6 miles northeast of Galena and moving northeast then the tornado would not have hit Joplin or at least southern Joplin. On that track it would have taken the tornado north of Joplin - or most of Joplin.

    This raises the question - was it a mistake? Were they playing the odds on where the tornado was located based on radar and conflicting other reports? The storm evolved so fast that they did not know what was going on? They had spotter reports indicating a tornado in an area that their radar wasn't even showing the tornado - yet?

    I don't know what was going on.

    If spotters reported the tornado near Joplin - did the NWS believe them on the location? Did someone assume that the spotter was wrong and the tornado was actually further north (or according to that statement - 6 miles northeast of Galena)

  5. I'm pretty sure Mike and the media were confused. There were two different storms issued for separately. I suspose it was unfortunate they were in close proximity to each other spatially and temporally. But nonetheless, there were separate defining warnings for each storm

    At 509 LT, a warning (VTEC 30) went out for the nrn storm, while the Joplin storm (VTEC 31) was still developing on the SW flank.

    post-866-0-93765400-1337736582_thumb.jpg

    At 517 LT, the warning (VTEC 31) went out for the Joplin storm.

    post-866-0-02114100-1337736599_thumb.jpg

    Yes, I remember that during the event - we were discussing it in the forums. I think a lot of people among our group realized the risk for confusion was high. Thus the nature of multiple tornado warnings.

    I think some in the media were caught off-guard by the extreme nature of the tornado - as mentioned also on WeatherBrains the other week. Developed fast - grew in size and intensity fast - sirens sounded county wide for the first storm - confusion over the second storm - media focused on storm A instead of A and B. It was an episode of "It Could Happen Tomorrow"

  6. On page 23 of the book - Mike says -

    Begin - from the book:

    At 5:39, even though the tornado was on Joplin's doorstep, the NWS wrote, "At 5:34 p.m., trained weather spotters reported a tornado near Galena (emphasis added by Mike in the book)...moving east at 25 mph. This storm is moving into the city of Joplin." Although Galena was old news, the statement "this storm is moving into the city of Joplin" was correct. But, by saying "near Galena" they misled people in west Joplin into thinking they had more time than they actually had.

    Unfortunately, just three minutes later, the NWS contradicted its own statement with a confusing and factually inaccurate "severe weather statement," in which I've emphasized a crucial two words:

    At 5:38 p.m., trained spotters reported a tornado near Joplin or 6 miles northeast of Galena, moving northeast at 45 mph:

    End of passage from the book.

    ------

    That is exactly what he said - the above - from the book.

    He says the media was then further confused and were visibly confused on air. He also says that local residents said the NWS kept saying Galena and they thought they were out of danger in Joplin. This is what Mike is saying in his book.

    He also says that radio stations were repeating what the NWS was saying - confusing people further.

    Bottom line is that the book states people were very confused by the NWS.

    Again - I am just telling you what the book says and these are not my opinions. To be clear. :) The book repeatedly says that their private service was accurate and that the NWS was inaccurate. It is the most severe and critical criticism of the NWS that I have ever seen in print.

  7. The book goes into complete detail as to who made the reports and how the reports were either ignored or misrepresented in future warning/statements.

    The book did raise one question - which is significant. Does the NWS have a problem with their pathcast system/algorithm? I noticed my local office issued a warning earlier this year and said a storm was moving northeast. The storm was actually moving east. I pointed this out to them and their response was along the lines of "oh that is probably just a product of the computer software"

    Hmmm - is this a problem? Mike raises the question in the book. I have no idea if this is a bigger problem (as he mentions) or if he is incorrect. It did make me remember the incident earlier this year in my local region. If it is a problem then it is a fairly serious issue. If media is telling people a storm is moving northeast and the storm is actually moving east then that is a problem.

    Of course anyone with any radar skills can determine for themselves what direction a storm is moving (talking about on-air mets here). However - should on-air mets be telling people something different from the NWS (and in the heat of battle would they even notice - or would they trust the NWS)? Obviously I already know the correct answer to the question.

  8. Wow - just Read Mike Smith's new book about the Joplin, MO tornado. A damninnnnnnnnngggggg assessment against the Springfield, MO NWS. I don't think it could have been any more stinging than what is written in that book. Ouch.

    Has anyone else read the new book? Took me about an hour to read it - was surprised to see just how sharp the negative comments were towards the NWS.

    The book made a lot of mention that the NWS got the path-cast wrong - on more than one occasion/statement. Also mentions that their private service was more accurate.

×
×
  • Create New...