Baltimore-Washington Parkway, Maryland : traffic safety plan
archive: archived pipeline: cataloged verified
Get this paper ↗ (full text — opens at the source; we link to it, we don't host it)
Summary
This report presents the Baltimore-Washington Parkway Traffic Safety Plan, developed by the Volpe Center for the National Park Service (NPS) to address persistent safety issues on the 19-mile NPS-owned segment of the corridor in Maryland. The plan was motivated by a high crash rate, averaging six fatalities and 547 crashes annually since 2006, and the conflicting demands of preserving the parkway’s historic character while managing heavy commuter traffic approaching 120,000 vehicles per day. Previous studies had focused primarily on infrastructure, but this plan adopts a comprehensive "4E" framework—Engineering, Enforcement, Education, and Emergency Services—to reduce serious injuries and fatalities while maintaining the park’s resources. The methodology involved a collaborative process with NPS staff, the U.S. Park Police, and external stakeholders, including workshops and web conferences held in 2014. The project team reviewed existing conditions, crash history, and prior studies to identify key challenges. Major findings included inconsistent crash data collection, infrastructure deficiencies such as non-compliant signage and narrow shoulders that hindered law enforcement, and limited resources for safety campaigns. Stakeholders identified speeding, distracted driving, and congestion as the top safety concerns. The plan structures its recommendations around these findings, aiming to improve roadway infrastructure, enhance enforcement visibility, educate drivers, and streamline emergency response. The report provides specific short- and medium-term recommendations for each of the 4E components. Engineering recommendations include improving pavement markings and signage at high-risk interchanges, widening shoulders at eight locations to allow for safe law enforcement stops, and installing permanent variable message signs. Enforcement strategies involve hiring additional officers, installing automated enforcement equipment, and creating agreements with state agencies. Education recommendations focus on coordinating with Maryland’s highway safety plans and launching public awareness campaigns, requiring the hiring of two full-time employees. Emergency services improvements include installing mile markers, developing traffic incident management training, and purchasing additional maintenance equipment. Long-term "big ideas" include opening a restricted ramp to ease congestion and exploring high-occupancy vehicle lanes. The significance of this plan lies in its structured approach to implementation and monitoring. It recommends convening a B-W Parkway Task Force to oversee progress, identify funding champions, and ensure accountability. The plan outlines potential funding sources, including federal grants and state programs, and emphasizes the need for consistent crash data collection to inform future investments. By integrating safety improvements with the park’s preservation mission, the plan aims to demonstrate positive momentum in reducing crashes while leveraging partnerships to overcome resource limitations.
Key finding
The Baltimore-Washington Parkway experiences an average of six fatalities and 547 crashes per year, with primary safety challenges stemming from inconsistent crash data collection, non-compliant signage, and limited law enforcement capacity.
Methodology
review
Provenance
The full processing record for this entry. Every stage of this paper's journey through the pipeline is logged — what ran, with which tool and model, how many attempts it took, and when it last completed. Discovered via bulk_ingest_rosap on 2026-05-23 (6 acquisition events logged).
| Stage | Outcome | Tool | Model | Prompt | Attempts | Completed |
|---|---|---|---|---|---|---|
| discover | success | rosap | — | — | 2 | 2026-05-23 |
| archive | success | — | — | — | 1 | 2026-05-23 |
| extract | success | cached | — | — | 2 | 2026-06-10 |
| clean | success | — | — | — | 1 | 2026-06-01 |
| chunk | success | — | — | — | 1 | 2026-06-01 |
| embed | success | — | — | — | 1 | 2026-06-02 |
| enrich | success | — | — | — | 1 | 2026-05-23 |
| promote | success | — | — | — | 1 | 2026-05-23 |
| summarize | success | llm | qwen3.6-27b-prismaquant | summ-v5 | 3 | 2026-06-10 |
| tag | success | vector_similarity | — | — | 19 | 2026-06-11 |
| verify | success | — | — | — | 2 | 2026-06-10 |
Summary generated by qwen3.6-27b-prismaquant on 2026-06-10; verification: verified.
Topics
Ranked by relevance to this paper. Hover a topic for its definition.
Information type
What kind of knowledge this paper contributes, grouped by family — independent of topic (what it is about) and method (how it was studied).
- Applied Guidance: countermeasure evaluation
- Empirical Findings: crash risk outcomes
- Methodological Resource: dataset resource