recommended reading

FCC plans post-Sandy hearings in New York and New Jersey

Mike Groll/AP

The Federal Communications Commission will hold public hearings in New York and New Jersey on Feb. 5 to assess the havoc Hurricane Sandy wreaked on telecommunications networks last fall and explore ways to improve survivability in natural disasters.

The October Northeast superstorm knocked out 25 percent of the cellphone sites in its path, due to both physical damage and a lack of power, problems that persisted for weeks. Roughly one-quarter of broadband, home phone or cable services also experienced widespread outages, FCC officials said at the time.

When he announced plans to hold the hearings last November, FCC Chairman Julius Genachowski said that since telecommunications firms had advance notice of the storm, he wanted to examine how they took advantage of this warning to stage assets, such as portable cell towers, before Sandy hit.

FCC also plans to examine the need for beefed up back-jump power systems and improved backhaul links that connect cell towers to central switches and wired networks, Genachowski said.

The hearings also will focus on the slow restoration of services in the wake of Sandy and how future operations could be improved by giving telecommunications companies priority access to generators and fuel.

Genachowski said FCC also wants to determine how libraries, schools and community centers can serve as temporary post-disaster communications centers and the role social media can play as a communications backstop.

The agency said the hearings next month will help “facilitate a wider national dialogue about the resiliency of communications networks by focusing on the impact of Superstorm Sandy, and help inform recommendations and actions to strengthen wired and wireless networks in the face of such large-scale emergencies.”

The two hearings on Feb. 5 will be at the Alexander Hamilton U.S. Customs House in Manhattan and the Stevens Institute of Technology in Hoboken, N.J. Live audio or video coverage of the hearings will be accessible from the FCC website.

Threatwatch Alert

Thousands of cyber attacks occur each day

See the latest threats


Close [ x ] More from Nextgov

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

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

  • Featured Content from RSA Conference: Dissed by NIST

    Learn more about the latest draft of the U.S. National Institute of Standards and Technology guidance document on authentication and lifecycle management.

  • PIV- I And Multifactor Authentication: The Best Defense for Federal Government Contractors

    This white paper explores NIST SP 800-171 and why compliance is critical to federal government contractors, especially those that work with the Department of Defense, as well as how leveraging PIV-I credentialing with multifactor authentication can be used as a defense against cyberattacks

  • Toward A More Innovative Government

    This research study aims to understand how state and local leaders regard their agency’s innovation efforts and what they are doing to overcome the challenges they face in successfully implementing these efforts.

  • From Volume to Value: UK’s NHS Digital Provides U.S. Healthcare Agencies A Roadmap For Value-Based Payment Models

    The U.S. healthcare industry is rapidly moving away from traditional fee-for-service models and towards value-based purchasing that reimburses physicians for quality of care in place of frequency of care.

  • GBC Flash Poll: Is Your Agency Safe?

    Federal leaders weigh in on the state of information security


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