D.C. Mun. Regs. tit. 10-A, § 424
424.1 In light of terrorist attacks, public health emergencies, and major weather events, every major American city has embarked on emergency preparedness and traveler information systems designed to inform citizens how to respond in the event of an emergency. As the nation’s capital, the District considers emergency preparedness a critically important issue.
424.2 Should the District face an emergency situation, the transportation system provides the critical means to evacuate residents, workers, and visitors; to support the movement of emergency service response teams; and/or to connect residents to critical services and essential workers to their job sites. Depending on the nature of an incident, persons may need to rely on car, train, bus, bike, and/or walking. It is essential that the District maintain and plan for a well-functioning, coordinated system that can adapt to the needs of an incident. Given the District’s reliance on the regional transportation network in the event of an evacuation, close coordination with partners in Maryland and Virginia and at WMATA would also be needed to respond to the event.
424.3 DDOT is the lead District agency for all regional and federal emergency transportation coordination and activities that affect the District. Another key agency is the Homeland Security and Emergency Management Agency (HSEMA), which partners with District agencies, businesses, and communities to help plan for the management of an emergency event. There is also increasing coordination among regional departments of transportation, the federal government, and other agencies, primarily through MWCOG.
424.4 The region has identified 25 corridors radiating from Downtown Washington, DC as emergency event/evacuation routes. Each of the routes extends to the Capital Beltway (I-495) and beyond. Customized roadway signs allow for easy identification of direction; outbound signs direct motorists to I-495 in Maryland and Virginia, and inbound signs show images of monuments. Evacuation routes are also identified by street name signs, which include the red and white District flag.
424.5 If directions are given to evacuate the Central Business District, Pennsylvania Avenue NW, between Rock Creek Park and the U.S. Capitol, serves as the dividing line for routes. None of the evacuation routes cross each other, and no vehicles would be permitted to cross Pennsylvania Avenue. Traffic signals would be timed to move traffic away from the incident area. In addition, police officers would be present at critical intersections on the evacuation routes within the District to expedite the flow of traffic and prevent bottlenecks. Bike trails could also be used by cyclists or pedestrians in the event of an evacuation.
424.6 Although the District is more equipped now than it has been in the past to respond to emergencies, additional planning is needed to better prepare the region’s transportation systems to respond to and rapidly recover from disruptions. The District should not only continue to plan for evacuations at the local level and provide the necessary information to the public, it should also improve coordination with its regional partners and take advantage of new technologies and federal support in preparing for the transportation needs resulting from a wide range of potential emergencies.
424.7 As home to the largest concentration of federal agencies and facilities in the country, the District and the federal governments should continue to coordinate extensively to address the District’s security and mobility needs. Over the past decade, several of the District’s streets have been closed by the federal government to protect the White House and the U.S. Capitol. These street closures have disrupted mobility for pedestrians and vehicles, requiring extensive re-routing of Metrobus and vehicular travel through downtown and Capitol Hill. This has led to delays for residents, workers, visitors, and emergency service providers.
Please refer to the Community Services and Facilities Element for additional policies and actions related to emergency preparedness, and to the Urban Design Element for policies on security and design.
424.8 Policy T-4.1.1: Balancing Security Measures and Desires for an Open District
Balance and mitigate security requirements against daily mobility, efficiency, and quality of life concerns of District residents and visitors, and the potential for negative economic, environmental, and historic impacts. The trade-offs associated with potential street closures or changes to transportation access should be adequately assessed.
424.9 Policy T-4.1.2: Coordination with the Federal Government
Work closely with federal agencies to find alternative security solutions and to avoid street closings to the greatest extent possible.
424.10 Policy T-4.1.3: Providing Redundancies
Provide alternate routes and modes of travel, or redundancies, across the District to promote the security of District residents and visitors and reduce the effects on non-routine incidents.
424.11 Policy T-4.1.4: Accommodating Evacuation Needs
Ensure evacuation planning and implementation considers and addresses issues of race, poverty, disability, and age.
424.12 Action T-4.1.A: Pennsylvania Avenue Closure
Work with federal agency partners to implement the Presidents Park South project along E Street NW near the White House to provide an excellent public space as well as a key east-west bicycle and pedestrian connection. Use the security requirements for closing the street to vehicles to create a space for bicycles and pedestrians.
424.13 Action T-4.1.B: Coordination with the Federal Government
Continue to work with the federal government to assess the impacts of security measures on the quality of life of District residents and businesses.
424.14 Action T-4.1.C: Emergency Evacuation Plan
Continue to refine an emergency evacuation plan that not only describes evacuation procedures and routes, but also defines the modes of transportation to use in the event that certain modes, such as the Metrorail system, become unavailable. Increase public education and awareness of local emergency management plans and make information on evacuation routes and procedures more accessible and understandable to residents, employees, and visitors.
SOURCE: District of Columbia Comprehensive Plan Act of 1984, effective April 10, 1984 (D.C. Law 5-76; 31 DCR 1049 (March 9, 1984)); as amended by District of Columbia Comprehensive Plan Act of 1984 Land Use Element Amendment Act of 1984, effective March 16, 1985 (D.C. Law 5-187; 32 DCR 873 (February 15, 1985)); as amended by District of Columbia Comprehensive Plan Amendments Act of 1989, effective May 23, 1990 (D.C. Law 8-129; 37 DCR 55 (January 5, 1990)); as amended by District of Columbia Comprehensive Plan Amendments Act of 1989 NCPC-Recommended Amendments, and Closing of Public Alleys in Square 669, S.O. 88-452, Act of 1990, effective May 23, 1990 (D.C. Law 8-132; 37 DCR 2213 (April 6, 1990)); as amended by District Government Land Use Temporary Amendment Act of 1994, effective October 1, 1994 (D.C. Law 10-190; 41 DCR 5360 (August 12, 1994)); as amended by Comprehensive Plan Amendments Act of 1994, effective October 6, 1994 (D.C. Law 10-193; 41 DCR 5536 (August 19, 1994)); as amended by District of Columbia Comprehensive Plan Act of 1984 Land Use Amendment Act of 1994, effective March 21, 1995 (D.C. Law 10-235; 42 DCR 30 (January 6, 1995)); as amended by Technical Amendments Act of 1996 effective April 18, 1996 (D.C. Law 11-110; 43 DCR 530 (February 9, 1996)); as amended by Second Technical Amendments Act of 1996 effective April 9, 1997 (D.C. Law 11-255; 44 DCR 1271 (March 7, 1997)); as amended by Comprehensive Plan Amendment Act of 1998, effective April 27, 1999 (D.C. Law 12-275; 46 DCR 1441 (February 19, 1999)); as amended by Technical Amendments Act of 1999, effective April 12, 2000 (D.C. Law 13-91; 47 DCR 520 (January 28, 2000)); as amended by Comprehensive Plan Amendment Act of 2006, effective March 8, 2007 (D.C. Law 16-300; 54 DCR 924 (February 2, 2007)); as amended by Technical Amendments Act of 2008, effective March 25, 2009 (D.C. Law 17-353; 56 DCR 1117 (February 6, 2009)); as amended by Comprehensive Plan Amendment Act of 2010, effective April 8, 2011 (D.C. Law 18-361; 58 DCR 908 (February 4, 2011)); as amended by Comprehensive Plan Amendment Act of 2021, effective August 21, 2021 (D.C. Law 24-20; 68 DCR 006918 (July 16, 2021)).