Red Tape and Bureaucracy Bungled Hurricane Sandy Warnings

John Huntington/

A few hours before slamming into the East Coast, flooding basements, splintering boardwalks, and destroying whole communities, Hurricane Sandy did something that crucially changed the national response to the storm—it stopped being a hurricane.

It didn't matter that Sandy was a gigantic (expletive) storm. It had combined into something more like a nor'easter. Technically, it was a post-tropical cyclone, a name that surely has less connotative meaning than "hurricane."

And then the bureaucracy got in the way. Yes, it appears not even the weather is free of red tape. Below, see how the hurricane-warning model looked when Sandy came ashore. When the storm became "post-tropical" (and therefore not technically a hurricane) as it approached land, it dropped out of the National Hurricane Center's purview.


Warnings about the storm didn't drop altogether. They did, however, change hands to another branch of the weather bureaucracy: local National Weather Service offices. "That choice meant that local meteorological offices, without the NHC's hurricane expertise, determined what local warnings to issue," an article in the September issue of Earth magazine, published by the American Geosciences Institute, explains. "It meant that local government officials had to determine their own evacuation orders from the local meteorologists."

The Earth piece is an interesting and at times frustrating outline of the chaos of what happens when nature intersects with rigid government protocols. Before the storm struck, the National Oceanic and Atmospheric Administration (the weather service's parent agency) was worried that if the electronic systems had sent out a hurricane warning but called it a "post-tropical storm," the systems could have failed, they were that rigid. James L. Franklin, the chief of the Hurricane Specialist Unit at the National Hurricane Center, told Earth "it might have worked, but we had no way to test it.... We are obligated to follow the rules that we told [weather reporters, local governments, and emergency responders] we will follow."

Earth explains what happened next:

In the end, NHC stuck with the NOAA protocol and went with the suite of warnings prescribed for nontropical storms, consistent with the NHC's forecasts. But that choice meant that local meteorological offices, without the NHC's hurricane expertise, determined what local warnings to issue; it meant that local government officials had to determine their own evacuation orders from the local meteorologists. There was no unified message, such as would have come from NHC if the team had retained control in a hurricane scenario. Every warning would have come from NHC, labeled as a hurricane from start to finish, had Sandy hit land as a hurricane.

So what the change of storm class did was change the message, and perhaps watered it down in the process. "NWS was concerned that if it issued hurricane watches and warnings and then dropped them before the storm struck land (and after the storm transitioned to post-tropical), there would be significant confusion on the part of decision makers and the public," the official NOAA assessment of the storm reads.

Those in the weather media were irked. Bryan Norcoss at The Weather Channel told Earth, "The public messages were very garbled on the level of threat." And this trickled down to the public's understanding of the storm. A University of Pennsylvania assessment found that:

While there was universal awareness of the threat that Sandy posed and almost all took some preparatory action, there was also widespread confusion about the nature of warnings issued about Sandy, and preparation that was insufficient for the threat Sandy posed. For example, as short as six hours before landfall and after tropical-storm-force winds had been affecting the coast for a number of hours, 40 percent of respondents mistakenly believed they were under a hurricane watch (instead of a hurricane-force wind warning). Likewise, most coastal residents misconstrued the primary threat of Sandy as coming from wind rather than water.

And it was the storm surge that caused the worst of the damage. The episode, however, did spur NOAA to change its warning protocols. Now, if a hurricane gets downgraded and it's still a massive storm set to do damage, we're still going to treat it like a hurricane. This is what the new model looks like.


(Top image via John Huntington/

Stay up-to-date with federal news alerts and analysis — Sign up for GovExec's email newsletters.
Close [ x ] More from GovExec

Thank you for subscribing to newsletters from
We think these reports might interest you:

  • Sponsored by Brocade

    Best of 2016 Federal Forum eBook

    Earlier this summer, Federal and tech industry leaders convened to talk security, machine learning, network modernization, DevOps, and much more at the 2016 Federal Forum. This eBook includes a useful summary highlighting the best content shared at the 2016 Federal Forum to help agencies modernize their network infrastructure.

  • Sponsored by CDW-G

    GBC Flash Poll Series: Merger & Acquisitions

    Download this GBC Flash Poll to learn more about federal perspectives on the impact of industry consolidation.

  • Sponsored by One Identity

    One Nation Under Guard: Securing User Identities Across State and Local Government

    In 2016, the government can expect even more sophisticated threats on the horizon, making it all the more imperative that agencies enforce proper identity and access management (IAM) practices. In order to better measure the current state of IAM at the state and local level, Government Business Council (GBC) conducted an in-depth research study of state and local employees.

  • Sponsored by Aquilent

    The Next Federal Evolution of Cloud

    This GBC report explains the evolution of cloud computing in federal government, and provides an outlook for the future of the cloud in government IT.

  • Sponsored by Aquilent

    A DevOps Roadmap for the Federal Government

    This GBC Report discusses how DevOps is steadily gaining traction among some of government's leading IT developers and agencies.

  • Sponsored by LTC Partners, administrators of the Federal Long Term Care Insurance Program

    Approaching the Brink of Federal Retirement

    Approximately 10,000 baby boomers are reaching retirement age per day, and a growing number of federal employees are preparing themselves for the next chapter of their lives. Learn how to tackle the challenges that today's workforce faces in laying the groundwork for a smooth and secure retirement.

  • Sponsored by Hewlett Packard Enterprise

    Cyber Defense 101: Arming the Next Generation of Government Employees

    Read this issue brief to learn about the sector's most potent challenges in the new cyber landscape and how government organizations are building a robust, threat-aware infrastructure

  • Sponsored by Aquilent

    GBC Issue Brief: Cultivating Digital Services in the Federal Landscape

    Read this GBC issue brief to learn more about the current state of digital services in the government, and how key players are pushing enhancements towards a user-centric approach.

  • Sponsored by CDW-G

    Joint Enterprise Licensing Agreements

    Read this eBook to learn how defense agencies can achieve savings and efficiencies with an Enterprise Software Agreement.

  • Sponsored by Cloudera

    Government Forum Content Library

    Get all the essential resources needed for effective technology strategies in the federal landscape.


When you download a report, your information may be shared with the underwriters of that document.