Contact

Reaching the correct department or office within the Baltimore Metro system depends on the nature of the inquiry — whether that involves service operations, accessibility accommodations, fare and pass questions, or administrative governance matters. This page outlines the primary channels for contacting Baltimore Metro authority offices, the geographic service area those offices cover, and the information that helps route an inquiry efficiently. Matching the request to the right office reduces response delays and ensures the inquiry reaches staff with direct authority over that subject.

Additional contact options

Beyond direct office contact, the Baltimore Metro system provides structured pathways for riders and stakeholders to engage with specific operational units.

Service alerts and real-time disruptions are tracked on the Baltimore Metro service alerts page, which is updated when scheduled service is affected by maintenance, weather, or infrastructure conditions. For time-sensitive service issues, that page offers the fastest available resolution path without waiting for a staff response.

Public meetings and comment periods are the appropriate venue for substantive policy input, particularly on topics such as expansion plans, budget and funding decisions, and equity and access initiatives. The schedule and participation instructions for those sessions appear on the Baltimore Metro public meetings page.

Accessibility accommodation requests that require advance coordination — including station-specific assistance or paratransit eligibility inquiries — are handled through the accessibility office rather than general contact channels. The Baltimore Metro accessibility page documents the dedicated process for those requests.

Fare and pass account issues, including transit benefit programs and pass replacement, are handled separately from operational complaints. The Baltimore Metro fares and passes page describes the applicable account management procedures.

How to reach this office

Inquiries directed to Baltimore Metro administrative offices are routed based on subject category. The 3 primary categories and their corresponding handling paths are:

1. Rider operations — Questions about schedules, parking, bike and transit integration, and station facilities fall under rider operations. These are the highest-volume inquiries and are typically resolved through published reference pages before escalation to staff contact is necessary.

2. Safety and security incidents — Reports of safety concerns, lost property, or observed security issues are directed to the Baltimore Metro safety and security office. Emergency incidents are handled through standard emergency services (911) first; the Metro safety office handles non-emergency follow-up, documentation, and reporting.

3. Governance and administrative matters — Inquiries related to authority governance, federal funding oversight, transit-oriented development, and environmental compliance are routed to administrative staff rather than operations personnel.

Written correspondence directed to administrative offices should use formal documentation standards, particularly for matters involving public records requests, contract inquiries, or regulatory compliance questions. Phone inquiries are appropriate for operational matters where a faster exchange is needed; written communication is preferred for anything requiring a documented record.

Service area covered

The Baltimore Metro system's service footprint spans Baltimore City and extends into Baltimore County, covering the subway line corridor and the light rail network as distinct but connected systems. The Baltimore Metro subway line operates along an 15.5-mile corridor between Owings Mills in Baltimore County and Johns Hopkins Hospital in East Baltimore. The Baltimore Metro light rail extends from Hunt Valley in the north to Cromwell Station/Glen Burnie in the south, with a branch to BWI Thurgood Marshall Airport.

Inquiries originating from outside this corridor — such as those related to regional connectivity with MARC commuter rail or connecting bus networks — may involve coordination with the Maryland Transit Administration (MTA), which administers the full regional transit network. The Baltimore Metro regional connectivity page outlines how the Metro system interfaces with those adjacent services.

Station-specific questions, including facility conditions or accessibility at individual stops, are best referenced against the Baltimore Metro stations directory before contacting operations staff directly.

What to include in your message

Providing complete information at the point of first contact significantly reduces the number of follow-up exchanges required to resolve an inquiry. The following 6 elements, where applicable, should be included in any written message:

1. Station or line name — Specify the subway line or light rail segment involved, using the names documented in the system map.
2. Date and approximate time — For incident reports or service complaints, include the date and the nearest 15-minute time window.
3. Direction of travel or platform — For issues occurring on board or at a platform, note inbound versus outbound direction.
4. Train or vehicle identifier — If visible, the car number or vehicle identifier assists operations staff in pulling corresponding records.
5. Nature of the request — Distinguish between a complaint, an information request, an accommodation request, or a formal public records inquiry. These are handled by different staff and processed under different timelines.
6. Preferred response format — Specify whether a written response, a phone callback, or documentation for formal records purposes is needed.

Inquiries submitted without a station reference or time window for incident-related matters may be delayed while staff attempt to identify the relevant operational record. For questions that do not involve a specific incident — such as general ridership statistics requests or history documentation — items 1 through 4 are not required.

Privacy Policy