Agencies learn from missteps during last year’s flooding in Nashville

Federal agencies are revamping their data-sharing and communications practices along the lines of criticisms laid out last week in a National Weather Service self-assessment of the May 2010 response to deadly flooding around Nashville, Tenn.

The report, written by a team of Weather Service specialists not directly involved in the record flooding in Tennessee and Kentucky that resulted in 26 deaths and more than $2 billion in damage, said the Weather Service and the U.S. Army Corps of Engineers "did not communicate effectively regarding updated releases (outflows) from USACE reservoirs. This lack of critical information exchange and mutual understanding of each other's operations led to inaccurate river crest forecasts on the Cumberland River."

Because the actual rainfall and river heights turned out to be much higher than predicted, local authorities and "many residents of Nashville who were interviewed stated that they 'had no warning,' despite numerous watches and warnings issued" by the local NWS forecasting office, the report said. "The residents perceived that flood warnings did not directly affect them; they could not relate river levels to flooding at specific locations."

A lack of interactive high-resolution maps, the NWS assessment added, hampered the ability of local authorities responsible for evacuation decisions to issue warnings with enough specifics to help citizens flee.

Among the report's recommendations were new training; more frequent interagency contact; multiagency cooperation in producing dynamic inundation maps; improved real-time exchange of technological data to form a common operating picture; and more conference calls between field offices to circulate forecasts and up-to-the minute reports of water levels.

NWS officials in response said Nashville-area officials already are pursuing the report's recommendations. Jane Hollingsworth, a Reno, Nev.-based NWS meteorologist who led the 10-member assessment team, told Government Executive the Tennessee-area teams are "working with the Corps of Engineers on automated data feeds and holding meetings to learn more about our operations." They are focusing on the "wording and dissemination of flood warnings, their effectiveness and how [local] people interpreted them," she said. "We're working with social scientists on how to get the word out using mobile phones."

Lt. Col. Anthony Mitchell, district engineer for the Nashville district of the Army Corps of Engineers, said the NWS report jibes with the Corps' own after-action assessments. "We never said there weren't some miscommunications -- it was an unprecedented event and chaotic in nature," he said. "None of the agencies perceived we'd receive that amount of rainfall. NWS had predicted three to five inches, but we got two to three times that in certain areas."

Mitchell agreed with the need for "a management structure to relay information and communications. The Corps is working not just with NWS but also with the U.S. Geological Survey and the city of Nashville on broader flood preparedness initiatives."

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 G Suite

    Cross-Agency Teamwork, Anytime and Anywhere

    Dan McCrae, director of IT service delivery division, National Oceanic and Atmospheric Administration (NOAA)

  • Data-Centric Security vs. Database-Level Security

    Database-level encryption had its origins in the 1990s and early 2000s in response to very basic risks which largely revolved around the theft of servers, backup tapes and other physical-layer assets. As noted in Verizon’s 2014, Data Breach Investigations Report (DBIR)1, threats today are far more advanced and dangerous.

  • 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 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.


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