BaltimoreLink Implementation February 2018 Status Report Report to the Maryland State Legislature
Joint Chairmen’s Report J00H01
BaltimoreLink Performance Report to the Maryland State Legislature
Executive Summary
BaltimoreLink, implemented on June 18, 2017, is the complete overhaul and rebranding of the core transit system operating within Baltimore City and the greater Baltimore region. The purpose of this document is to provide the Maryland State Legislature with a summary of BaltimoreLink performance in its first full six months of operation (July 2017 to December 2017) based on three key metrics: Ridership, On-Time Performance, and Customer Satisfaction. An analysis of safety has also been provided. The analysis begins with July 2017 when a full month of data was available.
The performance analysis consists of an evaluation of performance at an MDOT MTA system-wide level as well as an evaluation of performance at the route and route category level (CityLink, LocalLink, Express BusLink). Further, the system- wide analysis also includes a comparison to data for the same six-month evaluation period in 2016.
Executive Summary ES-1 BaltimoreLink Performance Report to the Maryland State Legislature
Ridership
Ridership Performance Snapshot Average Daily Ridership by Month: 2016 vs. 2017
Average Daily Ridership – 2016 vs. 2017 Monthly ridership declines in 2017 compared to 2016 reflect the overall declines in ridership during the 6-month evaluation period. However, there is a growing convergence in monthly ridership between 2016 and 2017 in the Weekday, Saturday, and Sunday ridership declined in 2017 when compared to 2016 later months of the year, especially for weekend ridership. for the six months evaluated. The weekday ridership decline between 2016 and 2017 was approximately 10%, the Saturday ridership decline was approximately 9%, and Average Daily Weekday Ridership by Month Average Daily Weekend Ridership by Month the Sunday ridership decline was approximately 5%. Consistent with other system - July Through December - 2016 vs. 2017 - July Through December - 2016 vs. 2017 redesigns throughout the country, declines were expected due to the transition to era e ail eek a i er i era e ail eeken i er i the new system, but also reflect national trends such as less expensive gas and the l ro ecem er l ro ecem er greater use of car-share services. Ridership is down 5% nationally during the same time period analyzed in this report. Similar systems throughout the country have also seen declines in ridership including Washington, D.C. (-9%), Cleveland (-11%), Philadelphia (-12%), and Miami (-13%). Out of the top 20 bus systems in the country, 19 out of 20 experienced ridership declines. Ridership Ridership Average Daily Ridership – July Through December: Comparison of 2016 to 2017 era e ail i er i L S L S ont of l ro ecem er Automatic Onboard Source: MDOT MTA Counting System Passenger Automatic Onboard Source: MDOT MTA Counting System Passenger The forecasted December 2017 average weekday ridership contained in the January 24, 2018 “Overview and Status Update” presented to the Legislature by MDOT MTA Administrator Kevin Quinn is higher than the actual presented above. Forecasted data was utilized in the presentation because actual data was not yet available as the presentation was being developed. The forecasted number used in the presentation was based on detailed analysis of ridership numbers on individual routes as well as overall ridership trends from previous months. Other Ridership Findings CityLink – Daily Average Ridership by Route LocalLink – Daily Average Ridership by Route
Ridership CityLink routes were designed to be the backbone of LocalLink routes provide service to a wide range of the BaltimoreLink system, with high service frequencies different transit markets and the service design of throughout the day, extensive hours of service, and LocalLink routes reflect the markets they serve. A key direct routing that connects major activity centers trend identified in the LocalLink ridership analysis was throughout the Baltimore region. Average daily that the highest ridership LocalLink routes (LocalLink weekday CityLink ridership ranges from 6,100 to routes 22 (8,300 riders), 80 (7,500 riders), and 54 ee day Saturday Sunday 11,600. The highest ridership CityLink routes include the (7,200 riders)) actually have average daily ridership CityLink Red (11,600 riders), running between Towson that is comparable to, or exceeds, ridership on many and downtown Baltimore, the CityLink Gold (9,600 CityLink routes, highlighting their importance within
Source: MDOT MTA Onboard Automatic Passenger Counting System riders), which runs between Walbrook Junction and the BaltimoreLink system. Other LocalLink routes have Canton via North Avenue and Wolfe and Washington ridership under 1,000 riders per day, highlighting the Streets, and the CityLink Orange (9,500 riders), which wide differences between individual LocalLink routes. runs between downtown Baltimore and Essex via Eastern Avenue.
ES-2 Executive Summary BaltimoreLink Performance Report to the Maryland State Legislature
On-Time Performance
On-Time Performance Snapshot CityLink Service Reliability
CityLink Headway Reliability Average System-Wide On-Time Performance – Six-Month Evaluation Period High frequency CityLink routes are scheduled differently than LocalLink and Express BusLink – Percent of Trips Arriving at Scheduled Intervals Between Buses On-time performance in 2017 exceeds on-time performance in 2016, for the six routes. CityLink reliability performance monitoring is month evaluation period, showing the benefits of multiple elements of the overall it Link o te ea a elia ilit focused on how well the scheduled intervals between BaltimoreLink redesign. Redesign elements helping the improvement in on-time l t ro ecem er CityLink buses are maintained. The data shows that performance include more proactive service management, changes to route the average number of CityLink trips arriving at the structures to improve reliability, implementation of dedicated transit lanes, and scheduled interval over the evaluation period is 76%. implementation of transit signal priority. On-time performance improved 7 percentage
points when comparing the 2016 and 2017 evaluation periods.
System-wide Bus On-Time Performance Comparison - July through December: 2016 vs. 2017
tem i e n ime om ari on l t ro ecem er Pre Baltimore Link to l t ro ecem er BaltimoreLink
ed ues hurs ed ed ues Mon hurs hurs ues Mon Mon ed hurs ed hurs ed ues Mon hurs ues ed ues Mon
ee nding ee nding ee nding er entage o rips rri ing at S heduled ead ay rend Source: Field Data Collection
Other On-Time Performance Findings
er ent n i e er ent On-Time Performance On LocalLink Routes Changes in On-Time Performance Due to Route On time performance on LocalLink routes ranges Restructurings and Capital Improvements Such as from a low of approximately 40% to a high of Dedicated Transit Lanes approximately 75%. The average across all LocalLink Comparison of the on-time performance of pre- routes in 2017 was 66%. This compares to an average BaltimoreLink routes to new redesigned BaltimoreLink arly n i e Late on-time performance on local routes in the same routes shows an improvement in on-time performance months of 2016 of 60%, an improvement on LocalLink due to route restructuring, capital improvements, routes of 6 percentage points. and reducing the number of bus stops on a route. Source: MDOT MTA Onboard Automatic Passenger Counting System Redesign examples include splitting long routes, restructuring routes serving large regional job centers, and providing dedicated transit lanes and transit System-wide on-time performance improved by signal priority approximately 7 percentage points in the first six months of BaltimoreLink operations compared to the same six months in 2016.
Executive Summary ES-3 BaltimoreLink Performance Report to the Maryland State Legislature
Customer Satisfaction
Customer Satisfaction Snapshot Other Customer Satisfaction Findings
Total Bus-Related Complaints - 2016 vs. 2017 Late, Early, No-Show Complaint Evaluation 2016 to 2017 Comparison - Complaints Related to Early and Late Bus Arrivals and Bus No-Shows 2017 passenger complaints covering all bus-related complaint types declined over Complaints related to early buses, late buses, and no-shows over the six month evaluation period the first six months of BaltimoreLink operations and also fell below 2016 in four of the eratin elate om laint six months evaluated. 2017 total bus-related complaints fell 49% between a high were lower in 2017 than in 2016 in each complaint l ro ecem er in September to the low in December. This trend shows the BaltimoreLink redesign category. Complaints related to early buses fell by changes resulted in greater passenger satisfaction. 44%, complaints related to late buses fell by 3%, and complaints related to no-show buses fell by 32%. 2016 to 2017 Comparison - All Bus-Related Complaints Between July and December
otal B elate om laint Bet een l an ecem er perating Related o plaints perating Related o Sho arly Late
Source: MDOT MTA Customer Complaint Database
o plaints
L S
Source: MDOT MTA Customer Complaint Database
Customer complaints were lower in 2017 in four of the six months evaluated. Compaints also consistently declined between September and December 2017, falling by 49% over the four month period.
ES-4 Executive Summary BaltimoreLink Performance Report to the Maryland State Legislature
Safety
Safety Performance Snapshot Bus Accident and Mileage Run by Division: 2017
Bus Accidents and Mileage Comparison By Division: 2017 Total Bus Accidents Comparison: 2016 vs. 2017 2017 bus accidents have declined during the six month evaluation period at each of the four MDOT MTA bus The number of total bus accidents in 2017 was lower than 2016 in each of the six B cci ent an ilea e i i ion om ari on divisions. This positive trend is bolstered even further months evaluated. The biggest difference between the two years occurred in l t ro ecem er by the fact that miles run from three of the four divisions November, where 2017 accidents were lower than 2016 by 30%. In addition, total have increased after BaltimoreLink implementation accidents over the six month period in 2017 fell by 20% when compared to total (while miles run at Eastern Division fell 5.1%, accidents accidents in the same period in 2016. there fell by more than 30%). Bus Accident Comparison: 2016 vs. 2017 - Six Month Evaluation Period
B cci ent om ari on l t ro ecem er
l t ro ecem er ush astern ir orth est Mileage idents Source: MDOT MTA Accident Database
Other Safety Findings us idents System-Wide Mileage and Accidents Comparison The data in the table below shows system-wide accidents during the six month evaluation period fell by approximately 20% between 2016 and 2017, even L S while mileage run increased by 2.3%. 2016 2017 Change Source: MDOT MTA Accident Database Mileage 13,832,439 14,153,517 2.3 %
Total accidents over the 2017 six month evaluation period Accidents 1,358 1,089 -19.8% fell by 20% compared to total accidents in the same period in 2016.
Executive Summary ES-5 BaltimoreLink Performance Report to the Maryland State Legislature
ES-6 Executive Summary BaltimoreLink Performance Report to the Maryland State Legislature
Table of Contents
Introduction...... 1 B. On-Time Performance and Headway Reliability...... 11 D. BaltimoreLink Capital Improvement Status...... 23
System-wide Bus On-Time Performance Comparison A. Ridership...... 3 July Through December: 2016 vs. 2017...... 12 Appendices...... 27
Average Daily Ridership By Day Of Week CityLink Route Headway Reliability July Through December: 2016 vs. 2017...... 4 July 2017 Through December 2017...... 13
Average Daily Weekday Ridership By Month LocalLink On-Time Performance Comparison July Through December: 2016 vs. 2017...... 5 July 2017 through December 2017...... 14
CityLink Routes On-Time Performance Comparison Average Daily Weekday Ridership: July 2017 Through December 2017...... 6 Pre-BaltimoreLink 35 to BaltimoreLink LocalLink Routes 56 and 76...... 15
LocalLink Routes On-Time Performance Comparison Average Daily Weekday Ridership: July 2017 Through December 2017...... 7 Pre-BaltimoreLink Service and BaltimoreLink Service to Regional Job Centers...... 16 Express BusLink Routes Average Daily Weekday Ridership: July 2017 Through December 2017...... 8 On-Time Performance Comparison Pre-BaltimoreLink Service to BaltimoreLink LocalLink Service...... 17 Top 10 Routes Average Weekday Daily Ridership: July 2017 Through December 2017...... 9 C. Customer Satisfaction...... 19 Average Weekday Daily Ridership by Route Category July Through December 2017...... 10 Total Bus-Related Complaints July Through December: Comparison of 2016 to 2017...... 20
Operating-Related Complaints Comparison Early and Late Bus Arrivals, and Bus No-Shows - 2016 vs. 2017...... 21
Table of Contents i BaltimoreLink Performance Report to the Maryland State Legislature
Table of Contents Figures
A. Ridership B. On-Time Performance and Headway Reliability C. Customer Satisfaction
Figure 1: Average Daily Ridership Figure 9: System-wide Bus On-Time Performance Comparison Figure 18: 2016 to 2017 Comparison – July Through December: Comparison of 2016 to 2017...... 4 – July through December: 2016 vs. 2017...... 12 – All Bus-Related Complaints Between July and December ...... 20 Figure 2: Average Daily Weekday Ridership by Month Figure 10: CityLink Headway Reliability Figure 19: 2016 to 2017 Comparison – Complaints Related to Early – July Through December - 2016 vs. 2017...... 5 – Percent of Trips Arriving at Scheduled Intervals Between Buses...... 13 and Late Bus Arrivals and Bus No-Shows...... 21 Figure 3: Average Daily Weekend Ridership by Month Figure 11: LocalLink On-Time Performance by Route – July Through December - 2016 vs. 2017...... 5 – July 2017 through December 2017...... 14 Figure 4: Average Weekday Daily Ridership by CityLink Route Figure 12: Express BusLink On-Time Performance by Route – July through December 2017...... 6 – July 2017 through December 2017...... 14 Figure 5: Average Weekday Daily Ridership by LocalLink Route Figure 13: On-Time Performance Comparison – July 2017 through December 2017...... 7 – Pre-BaltimoreLink 35 to BaltimoreLink LocalLink Routes 56 and .76 ....15 Figure 6: Express BusLink Daily Average Ridership by Route Figure 14: On-Time Performance Comparison – July 2017 through December 2017...... 8 – Pre-BaltimoreLink 7 to BaltimoreLink LocalLink Route 65...... 16 Figure 7: Top 10 BaltimoreLink Ridership Routes Figure 15: On-Time Performance Comparison – July 2017 through December 2017...... 9 – Pre-BaltimoreLink 17 to BaltimoreLink LocalLink Route 75...... 16 Figure 8: Average Daily Weekday Ridership by Route Category...... 10 Figure 16: On-Time Performance Comparison – Pre-BaltimoreLink 20 to BaltimoreLink LocalLink Route 78...... 17 Figure 17: On-Time Performance Comparison – Pre-BaltimoreLink 11 to BaltimoreLink LocalLink Route 51...... 17
ii Table of Contents BaltimoreLink Performance Report to the Maryland State Legislature
Introduction
BaltimoreLink, implemented on June 18, 2017, is the complete This monitoring work has focused on: overhaul and rebranding of the core transit system operating åå On-time performance for LocalLink and Express BusLink routes within Baltimore City and the greater Baltimore region. The purpose of this document is to provide the Maryland State åå Assessing whether the scheduled interval between high- Legislature with a summary of BaltimoreLink performance frequency CityLink buses was being maintained (e.g. relative to three key metrics: Ridership, On-Time Performance and buses that are scheduled to arrive at a stop every 10 Customer Satisfaction. minutes are, in fact, arriving every 10 minutes) The analysis and evaluation of each metric is based on the first åå Ongoing interviews with passengers and drivers to full six months of BaltimoreLink operations (July 2017 to December 2017). The analysis begins with July rather than June because July assess potential operational issues was the first month of BaltimoreLink operations where a full month åå Reviewing the impacts of Transit Signal Priority of data was available. In addition, there was concern that June and other methods for providing transit data would be skewed by the fact that a free fare was in effect for exclusivity on travel times and reliability the first two weeks of BaltimoreLink operations (the free fare was instituted as an incentive for existing riders as well as potential åå Tracking of passenger loads and potential riders to become familiar with the redesigned system). overcrowding
The analysis of each metric begins with a system-wide comparison of Short-term modifications have been made July through December data for 2017 versus data in the same months where feasible and larger scale modifications in 2016. This allows for a quick assessment of how BaltimoreLink were also made in the September 2017 and ridership and operations compare to pre-BaltimoreLink ridership and February 2018 schedule changes to reflect operations. This high-level snapshot is followed by more detailed monitoring results. data for individual routes and route categories, summarized for the six months of operations. This more detailed analysis includes an analysis The first metric requested for evaluation of 2017 data only as well as comparisons between 2016 and 2017. by the Legislature, Ridership, is outlined in Section A. On-time Finally, even more detailed data breakdowns are contained in report Performance and Passenger appendices, with the summary data provided in the body of the Satisfaction evaluations are report broken out by each month of BaltimoreLink operations. presented in Sections B and It is important to note that the evaluation completed for this report C respectively. A summary is only a small part of the BaltimoreLink evaluation and monitoring of capital improvements to process that has been undertaken by multiple MDOT MTA support BaltimoreLink is departments. provided in Section D.
Introduction 1
BaltimoreLink Performance Report to the Maryland State Legislature
A. Ridership
The ridership evaluation contained in this section focuses on two levels of data detail. The first evaluation provides a “snapshot” of ridership performance by comparing average daily ridership (for weekday, Saturday, and Sunday) for the first full six months of BaltimoreLink operations (July 2017 to December 2017) to the same months in 2016. This high-level snapshot allows for a quick assessment of how BaltimoreLink ridership compares to pre-BaltimoreLink ridership.
This high-level snapshot is followed by more detailed data for individual routes and route categories, summarized for the six months of BaltimoreLink operations. Some of the analysis in this more detailed evaluation involves comparisons between 2016 and 2017 while others rely just on a review of 2017 data. Also available in Appendix 1 is weekday ridership data at an even more detailed level, showing ridership data broken out by month. Comparable data for weekends is provided in Appendix 3.
Ridership 3 BaltimoreLink Performance Report to the Maryland State Legislature
Average Daily Ridership By Day Of Week July Through December: 2016 vs. 2017
The data in Figure 1 provides a high-level analysis of ridership performance before and after BaltimoreLink Figure 1: Average Daily Ridership – July Through December: Comparison of 2016 to 2017 implementation. The figure presents average daily ridership over the six month evaluation period (July era e ail i er i to December) for the years 2016 (pre-BaltimoreLink ont of l ro ecem er implementation) and 2017 (the first full six months of BaltimoreLink operations). The data in the Figure shows that daily average weekday ridership is lower in 2017 than
in 2016, with the same holding true for Saturday and Sunday service. The data reflects expected declines in the first six months of operations as riders became used to the redesigned system as well as declines in transit ridership overall because of less expensive gas and the increased use of alternative transportation modes such as car share services. These declines in transit ridership constitute a national trend.
Ridership
Weekday, Saturday, and Sunday ridership declined in 2017 when compared to 2016 for the six months evaluated. Some declines were expected due to the transition to the new system but the ee day Saturday Sunday declines also reflect national transit trends.
Source: MDOT MTA Onboard Automatic Passenger Counting System
4 Ridership BaltimoreLink Performance Report to the Maryland State Legislature
Average Daily Weekday Ridership By Month July Through December: 2016 vs. 2017
Figure 2: Average Daily Weekday Ridership by Month The evaluations contained in the following pages provide a more - July Through December - 2016 vs. 2017 detailed analysis of ridership trends both for 2017 alone as well as in comparison to 2016. The data in Figure 2 provides more era e ail eek a i er i detail on weekday average ridership for each of the months l ro ecem er evaluated, for both 2016 and 2017. The data in Figure 2 underscores the lower ridership in 2017 compared to 2016, though it is important to note the trend of ridership between the two years more closely converging at the end of the analysis period. For example, the difference in ridership between the two years in September was approximately 23,000, but this declined to 19,000 in December. We Ridership believe this reflects riders becoming more comfortable with the system as they use it and learn how to gain the most benefit from it. L S Figure 3 is a companion to Figure 2 and shows average daily weekend ridership (Saturday and Sunday combined) for the months July through Source: MDOT MTA Onboard Automatic Passenger Counting System December, for the years 2016 and 2017. As with weekday ridership, the data underscores Figure 3: Average Daily Weekend Ridership by Month the lower ridership overall in 2017, but also - July Through December - 2016 vs. 2017 highlights the trend of convergence in ridership at the end of the analysis period, era e ail eeken i er i l ro ecem er again reflecting, we believe, increased rider comfort with the redesigned system. While 2016 ridership is higher than 2017, there is a convergence in monthly ridership between 2016 Ridership and 2017 in the later months of the year, especially for weekend ridership. L S
Source: MDOT MTA Onboard Automatic Passenger Counting System
Ridership 5 BaltimoreLink Performance Report to the Maryland State Legislature
CityLink Routes Average Daily Weekday Ridership: July 2017 Through December 2017
The next set of data provides more detail on how daily ridership is distributed among the routes in the Figure 4: Average Weekday Daily Ridership by CityLink Route - July through December 2017 BaltimoreLink system. The data in Figure 4 shows average daily weekday ridership for each CityLink route era e eek a ail i er i it Link o te for the months July 2017 to December 2017, the first full l ro ecem er six months of BaltimoreLink operations.
CityLink routes were designed to be the backbone of the system, with high service frequencies throughout the day, extensive hours of service, and direct routing that connects major activity centers throughout the Baltimore region.
The data shows the highest ridership line during the period evaluated is CityLink Red, which runs between the University of Maryland Transit Center in downtown Baltimore and Towson via Greenmount Avenue and York Road and generally mirrors Ridership the 8 route from the pre-BaltimoreLink system. The second highest ridership CityLink route over the six months evaluated is CityLink Gold, which runs between Walbrook Junction and Canton via North Avenue and the Wolfe/Washington one-way pair. It generally mirrors the pre-BaltimoreLink 13 route. The third highest ridership CityLink route Red old range lue reen a y ro n urple Sil er ello Li e in is CityLink Orange which generally mirrors the eastern portion of the pre- ityLin Routes BaltimoreLink 23 route. More detail on weekday ridership on each CityLink route for each of the six Source: MDOT MTA Onboard Automatic Passenger Counting System months evaluated is provided in Appendix 1. Comparable data for weekends is provided in Appendix 3.
The highest ridership CityLink route during the evaluation period is the CityLink Red, which runs between Towson and downtown Baltimore and mirrors the pre-BaltimoreLink 8 route.
6 Ridership BaltimoreLink Performance Report to the Maryland State Legislature
LocalLink Routes Average Daily Weekday Ridership: July 2017 Through December 2017
The data in Figure 5 is a companion to the data in Figure 4 and shows average daily weekday ridership Figure 5: Average Weekday Daily Ridership by LocalLink Route – July 2017 through December 2017 on LocalLink routes over the time period July 2017 through December 2017. LocalLink routes provide era e eek a ail i er i LocalLink o te service to a wide range of different transit markets l ro ecem er and therefore differ in their service frequencies, route directness, and hours of service. The highest ridership LocalLink routes have service characteristics comparable to CityLink routes while other LocalLink routes have lower frequencies and shorter hours of service. In each instance, the service design reflects the markets being served. One key trend in the data is that the three highest ridership LocalLink routes (LocalLink routes 22, 80, and 54) actually have average daily ridership that is comparable to, or exceeds, ridership
Ridership on many of the CityLink routes, highlighting their importance within the BaltimoreLink system. The highest ridership LocalLink route, the 22 , is a crosstown route that runs between the Mondawmin Metro Station and the Johns Hopkins Bayview campus. This high ridership highlights the importance of providing transit connections between job and activity centers outside of downtown Baltimore, a key focus of the BaltimoreLink redesign. The second highest ridership LocalLink route is the Lo alLin Routes 80, which runs between the Rogers Avenue Metro Station and downtown through northwest Baltimore. The 54, which is the third highest ridership Source: MDOT MTA Onboard Automatic Passenger Counting System LocalLink route, runs between the Loch Raven area and downtown Baltimore, predominantly via Harford Road.
More detail on weekday ridership on each LocalLink route for each of the months evaluated is provided in Appendix 1. Comparable data for weekends is provided in Appendix 3.
The highest ridership LocalLink route during the evaluation period is the LocalLink 22, which is a crosstown route between Mondawmin and the Johns Hopkins Bayview Campus.
Ridership 7 BaltimoreLink Performance Report to the Maryland State Legislature
Express BusLink Routes Average Daily Weekday Ridership: July 2017 Through December 2017
The data in Figure 6 shows ridership by route for the final bus route category in the BaltimoreLink system, Figure 6: Express BusLink Daily Average Ridership by Route – July 2017 through December 2017 Express BusLink. These routes are commuter services that are run by the MDOT MTA in the Baltimore area (in era e eek a ail i er i re B Link o te contrast to commuter services such as routes between l ro ecem er Southern Maryland and Washington DC that are run by contract operators).
The data shows the highest ridership Express BusLink route over the six months evaluated is the 120 route, which runs between White Marsh and downtown Baltimore via Interstate 95. The second highest ridership route over the six months evaluated is the 154, which runs between the Carney Park and Ride and downtown Baltimore, predominantly via Harford Road (the Express BusLink 154 follows the same routing as the LocalLink 54 route, which is among the highest ridership LocalLink routes). The Ridership third highest ridership Express BusLink route is the 103, which runs between the Cromwell Bridge Park and Ride in Towson and downtown Baltimore, predominantly via Loch Raven Boulevard. More detail on weekday ridership on each Express BusLink route for each of the months evaluated is provided in Appendix 1.
press usLin Routes
Source: MDOT MTA Onboard Automatic Passenger Counting System
8 Ridership BaltimoreLink Performance Report to the Maryland State Legislature
Top 10 Routes Average Weekday Daily Ridership: July 2017 Through December 2017
The data in Figure 7 shows the top 10 highest ridership routes for the July 2017 to December 2017 Figure 7: Top 10 BaltimoreLink Ridership Routes – July 2017 through December 2017 evaluation period. The data in Figure 7 shows that seven of the top 10 routes in the evaluation period are era e o i e t eek a i er i o te CityLink routes, while the top three highest ridership l t ro ecem er LocalLink routes round out the top 10. This data highlights that while the CityLink routes are designed to be the backbone of the system, LocalLink routes also play an important role in supporting ridership demand.
More detail on the top 10 ridership routes for each of the months evaluated is provided in Appendix 1. Comparable data for weekends is provided in Appendix 3.
Riedership Seven of the 10 highest weekday ridership routes are CityLink routes, but three are LocalLink routes, highlighting LocalLink routes’ importance in meeting passenger demand.
Red old range lue reen a y ro n
alti oreLin Routes
Source: MDOT MTA Onboard Automatic Passenger Counting System
Ridership 9 BaltimoreLink Performance Report to the Maryland State Legislature
Average Weekday Daily Ridership by Route Category July Through December 2017
The final ridership metric evaluated is the breakdown in the CityLink routes do play an substantial role in carrying ridership among the three BaltimoreLink bus categories over the people relative to the number of CityLink routes. This reflects six-month evaluation period. The data in Figure 8 shows that the original focus of the BaltimoreLink redesign, which was to the highest percentage of average daily weekday ridership concentrate resources on those routes serving the largest rider occurs on the LocalLink routes at 53%, followed by the CityLink markets and carrying the highest ridership by providing high routes at 45%. Express BusLink routes carry about 1% of daily service frequencies throughout the day, direct routing, and weekday riders. The data shows that while CityLink routes carry longer hours of service. More detail on the breakdown of a smaller portion of overall BaltimoreLink ridership, the 45% of weekday ridership between route categories is provided in the daily ridership they do carry occurs on only 12 routes, while Appendix 1. Comparable data for weekends is provided there are 42 LocalLink routes. This highlights the fact that while in Appendix 3. the LocalLink routes carry a larger percentage of ridership,
Figure 8: Average Daily Weekday Ridership by Route Category
era e ail eek a i er i o te ate or l t ro ecem er
ityLin Lo alLin press usLin
Source: MDOT MTA Onboard Automatic Passenger Counting System
10 Ridership BaltimoreLink Performance Report to the Maryland State Legislature
B. On-Time Performance and Headway Reliability
On-time performance and headway reliability is the second performance metric requested by the Maryland State Legislature for evaluation. The on-time performance and reliability evaluation contained in this section focuses on two levels of data detail. The first evaluation provides a “snapshot” of on-time performance by comparing on- time performance for the first full six month of BaltimoreLink operations (July 2017 to December 2017) to the same six months in 2016. This high-level “snapshot” allows for a quick understanding of how BaltimoreLink on-time performance compares to pre- BaltimoreLink on-time performance.
This high-level snapshot is followed by more detailed data for individual routes and route categories, summarized for the six months of BaltimoreLink operations. Also available in Appendix 2 is on-time performance data at an even more detailed level, showing on-time data broken out by month for different types of routes.
It should be noted that the CityLink routes are scheduled differently than LocalLink and Express BusLink services and therefore their reliability is also measured differently. More detail is provided in the discussion of Figure 10.
On Time Performance 11 BaltimoreLink Performance Report to the Maryland State Legislature
System-wide Bus On-Time Performance Comparison July Through December: 2016 vs. 2017
Outlined first in Figure 9 is a comparison of average system-wide on-time performance over the first Figure 9: System-wide Bus On-Time Performance Comparison July through December: 2016 vs. 2017 six months of BaltimoreLink operations (July 2017 to December 2017) to on-time performance in the tem i e n ime om ari on l t ro same six months in 2016. The data shows that on-time performance in 2017 has improved compared to 2016. ecem er Pre Baltimore Link to l t ro This improvement reflects a range of factors, including: ecem er BaltimoreLink åå More proactive management of service through the Operations Control Center and on-street supervision
åå Changes to route structures made during the BaltimoreLink redesign such as cutting overly long routes in half to make them more reliable åå Implementation of dedicated transit lanes through downtown Baltimore to improve transit speeds and reliability
er ent n i e er ent åå Implementation of transit signal priority, also focused on improving transit speeds and reliability Service reliability and buses arriving when they are supposed to was a primary complaint of pre-BaltimoreLink riders and thus was a key focus of the redesign. The improvement in on-time performance is a positive arly n i e Late trend that the MDOT MTA will continue to work on to achieve even greater improvements.
Source: MDOT MTA Onboard Automatic Passenger Counting System On-time performance has improved by approximately 7 percentage points since BaltimoreLink implementation due to more proactive line management, changes to route structure to improve reliability, dedicated transit lanes, and transit signal priority.
12 On Time Performance BaltimoreLink Performance Report to the Maryland State Legislature
CityLink Route Headway Reliability July 2017 Through December 2017
The next set of data provides headway maintenance data for the CityLink routes. As noted in the introduction to this section, Figure 10: CityLink Headway Reliability – Percent of Trips Arriving at Scheduled Intervals Between Buses CityLink routes are scheduled differently than LocalLink and Express BusLink routes, and therefore their reliability performance it Link o te ea a elia ilit is monitored differently. l t ro ecem er Specifically, CityLink routes are scheduled such that a person waiting at a stop would see a bus arrive at their stop at specific scheduled intervals, usually 10 minutes apart in the peak periods (this scheduled interval is also called a headway). This scheduling approach is in contrast to LocalLink and Express BusLink routes, where passengers use a timetable to understand the specific time they should arrive at a stop to board the bus. This CityLink scheduling approach reflects higher service frequencies on CityLink routes, which allows passengers to arrive at a CityLink stop without a timetable, based on the understanding that a bus will arrive within a reasonable time given the highly frequent service. Because the CityLink routes are scheduled with a focus on maintaining the correct scheduled intervals between buses, the data presented in Figure 10 focuses on how well these scheduled intervals are maintained. The detriment of not maintaining the scheduled interval is that if buses arrive at a stop at an interval less than the scheduled interval (also known as bunching), there will be a large gap after the trailing buses in the bunch, meaning passengers who arrived at a stop after ed ues hurs ed ed ues Mon hurs hurs ues Mon Mon ed hurs ed hurs ed ues Mon hurs ues ed ues Mon the bunch has passed will have to wait longer than the scheduled headway for a bus
ee nding ee nding ee nding to arrive. er entage o rips rri ing at S heduled ead ay rend The data in Figure 10 shows the percentage of CityLink trips arriving correctly separated between the bus in front and the bus behind based on field data collected over the evaluation period. The average number of trips arriving at the scheduled interval during Source: Field Data Collection this period was approximately 76%. The MDOT MTA has already implemented a number of initiatives to maintain and improve reliability and correct scheduled intervals, including dedicated bus lanes, stricter enforcement of traffic and parking regulations, transit signal priority, and more proactive management of bus separation through a combination of on- street supervision and the Operations Control Center (OCC). In an effort to achieve reliability improvements, the MDOT MTA is expanding the network of dedicated transit lanes and transit signal priority and also evaluating the supervision efforts of the OCC and on-street supervisors to identify potential improvements in their methods.
On Time Performance 13 BaltimoreLink Performance Report to the Maryland State Legislature
LocalLink On-Time Performance Comparison July 2017 through December 2017
Figure 11: LocalLink On-Time Performance by Route The next set of analyses evaluates data at the route and route July 2017 through December 2017 category level to provide an understanding of how individual routes are performing. The first set of data, shown in Figure 11, LocalLink n ime Performance summarizes on-time performance by LocalLink route. The data l ro ecem er shows that on-time performance by route ranges from a low of approximately 40% to a high of approximately 75%. The average across all LocalLink routes is 66%. The data in Figure 12 is a companion to the data in Figure 11 and shows on-time performance for each Express BusLink route. The data shows that on-time performance ranges from a low of approximately 47% to a high of 66%. The average across all Express BusLink routes
er entage o rips n i e o rips er entage is 56%. Part of the lower Express BusLink on-time performance can be attributed to the fact that
Lo alLin Routes many of these routes run at least partially on the interstate highways in the Baltimore region, which
Source: MDOT MTA Onboard Automatic Passenger Counting System experience a wide variability in congestion based on traffic accidents and other incidents, thus impacting average on-time performance. The Figure 12: Express BusLink On-Time Performance by Route nature of the network on which these trips run July 2017 through December 2017 can make it difficult to mitigate poor on-time re B Link n ime Performance performance. l ro ecem er
LocalLink on-time performance in 2017 averaged 66%, versus 60% in the 2016 six-month evaluation period. This is an improvement of 6 percentage points.
er entage o rips n i e o rips er entage
press usLin Routes
Source: MDOT MTA Onboard Automatic Passenger Counting System
14 On Time Performance BaltimoreLink Performance Report to the Maryland State Legislature
On-Time Performance Comparison Pre-BaltimoreLink 35 to BaltimoreLink LocalLink Routes 56 and 76
The next set of data focuses on the impacts of the BaltimoreLink redesign on specific routes through a Figure 13: On-Time Performance Comparison – Pre-BaltimoreLink 35 to BaltimoreLink LocalLink Routes 56 and 76 comparison of pre-BaltimoreLink and BaltimoreLink routes serving the same corridor or destination. The first, shown in Figure 13, provides an on-time comparison of om ar ion of Pre BaltimoreLink o te the pre-BaltimoreLink route 35 to the post-implementation n ime Performance to BaltimoreLink routes 56 and 76. The 35 route was quite long, BaltimoreLink e lacement o te an and was broken in half in the redesign to improve reliability. This resulted in two routes, the LocalLink routes 56 and 76. The data in Figure 13 shows that on-time performance improved on both of the new routes when compared to the original 35 route. Route restructurings such as this were one method used to improve reliability and on-time performance in the BaltimoreLink development.
The split of the pre-BaltimoreLink 35 route resulted in improved on-time performance on the two BaltimoreLink er ent n i e er ent
routes comprising the old route, reflecting the benefits of this type of redesign in BaltimoreLink.
ld Route urrent Route urrent Route arly n i e Late
Source: MDOT MTA Onboard Automatic Passenger Counting System
On Time Performance 15 BaltimoreLink Performance Report to the Maryland State Legislature
On-Time Performance Comparison Pre-BaltimoreLink Service and BaltimoreLink Service to Regional Job Centers
Figure 14: On-Time Performance Comparison The next comparison of Pre-BaltimoreLink routes to new Pre-BaltimoreLink 7 to BaltimoreLink LocalLink Route 65 BaltimoreLink routes focuses on services to regional job centers. The first of these, shown in Figure 14, focuses on the om ari on of n ime Performance Amazon fulfillment center located in southeast Baltimore. Pre- Pre BaltimoreLink er ice an BaltimoreLink Amazon was served by the 7 route. Given the BaltimoreLink er ice to ma on importance of Amazon as a job center, the BaltimoreLink redesign resulted in a more direct and frequent LocalLink 65 route. The data in Figure 14 shows an improvement in overall on-time performance as well as a steep decline in late trips. This data reflects a key focus of the BaltimoreLink redesign, which was to focus on important job centers that have grown over time and which have er ent n i e er ent replaced other legacy job centers that have declined as the region changes.
ld Route urrent Route The data in Figure 15 is a companion to Figure 14, arly n i e Late and shows a comparison of on-time performance for the pre-BaltimoreLink and BaltimoreLink Source: MDOT MTA Onboard Automatic Passenger Counting System service to the BWI Business District. The data shows a significant improvement in overall on- Figure 15: On-Time Performance Comparison time performance on the LocalLink 75 route Pre-BaltimoreLink 17 to BaltimoreLink LocalLink Route 75 when compared to the pre-BaltimoreLink 17 route. Again, this reflects the redesign’s focus om ari on of n ime Performance on improving transit access to important job Pre BaltimoreLink er ice an centers in the region through more direct BaltimoreLink er ice to B B ine i trict and reliable service. BaltimoreLink related redesign of services to major job centers such as the Amazon Fulfillment er ent n i e er ent Center and the BWI Business District resulted in improved
on-time performance for ld Route urrent Route riders to these locations. arly n i e Late
Source: MDOT MTA Onboard Automatic Passenger Counting System
16 On Time Performance BaltimoreLink Performance Report to the Maryland State Legislature
On-Time Performance Comparison Pre-BaltimoreLink Service to BaltimoreLink LocalLink Service
Figure 16: On-Time Performance Comparison The next set of comparisons show the impacts of improvements Pre-BaltimoreLink 20 to BaltimoreLink LocalLink Route 78 such as dedicated bus lanes, decreasing the number of stops on a route, and updating scheduled travel times to reflect current om ari on of n ime Performance operating conditions. The first comparison, shown in Figure Pre BaltimoreLink an BaltimoreLink er ice in ommon orri or 16, is between the pre-BaltimoreLink route 20 and the current LocalLink route 78. The pre-BaltimoreLink 20 ran on the west side of Baltimore and through downtown. The new LocalLink 78 route follows the same alignment on the westside as the pre-BaltimoreLink 20 route but terminates at the West Baltimore MARC station, thus avoiding downtown congestion. Additional redesign elements included fewer stops and adjusted scheduled run times. er ent n i e er ent The data in Figure 17 is a companion to Figure 16, and shows a comparison of the pre-BaltimoreLink ld Route urrent Route 11 route to the BaltimoreLink 51 route. The pre- arly n i e Late BaltimoreLink 11 route ran between Towson and downtown Baltimore and the LocalLink 51 route Source: MDOT MTA Onboard Automatic Passenger Counting System follows the same alignment. The improvement in on-time performance shows the positive Figure 17: On-Time Performance Comparison benefits of dedicated bus lanes on Charles Pre-BaltimoreLink 11 to BaltimoreLink LocalLink Route 51 Street, a winnowing of the number of bus om ari on of n ime Performance stops on the route, and adjustment of Pre BaltimoreLink an run times to reflect current operating BaltimoreLink er ice in ommon orri or conditions.
Improvements such as dedicated bus lanes, removing low ridership stops, and updating schedules, has resulted in improved on- er ent n i e er ent time performance on multiple BaltimoreLink routes
compared to the pre- ld Route urrent Route BaltimoreLink system. arly n i e Late
Source: MDOT MTA Onboard Automatic Passenger Counting System
On Time Performance 17 BaltimoreLink Performance Report to the Maryland State Legislature
18 On Time Performance BaltimoreLink Performance Report to the Maryland State Legislature
C. Customer Satisfaction
The final evaluation requested by the State Legislature is an assessment of customer satisfaction after BaltimoreLink implementation. The foundation of this customer satisfaction analysis is complaints received from customers at two different levels. The first involves a comparison of total complaints by month for the first full six months of BaltimoreLink operations (July 2017 to December 2017) to the same months in 2016. The second analysis evaluates just complaints related to bus operations, specifically complaints about late buses, no-shows, and early buses.
Customer Satisfaction 19 BaltimoreLink Performance Report to the Maryland State Legislature
Total Bus-Related Complaints July Through December: Comparison of 2016 to 2017
The first Customer Satisfaction analysis, shown in Figure 18, evaluates the change in the number of Figure 18: 2016 to 2017 Comparison - All Bus-Related Complaints Between July and December total passenger complaints between 2016 and 2017 for the July through December evaluation period. otal B elate om laint Bet een The data shows two positive trends. The first is the l an ecem er decline in complaints from a high in September, with total complaints falling to a low of 552 in December 2017 (a fall of 525 complaints, or approximately 49% from the September high). The second is that 2017 complaints were below 2016 complaints in four of the six months evaluated. Both of these trends reflect the positive benefits of all elements of the BaltimoreLink redesign. o plaints Customer complaints were lower in 2017 in four of the six months evaluated. Compaints also consistently declined between September and December 2017, falling by 49% over the four month period. L S
Source: MDOT MTA Customer Complaint Database
20 Cusstomer Satisfaction BaltimoreLink Performance Report to the Maryland State Legislature
Operating-Related Complaints Comparison Early and Late Bus Arrivals, and Bus No-Shows - 2016 vs. 2017
The second set of Customer Satisfaction data, as shown in Figure 19, provides a comparison of Figure 19: 2016 to 2017 Comparison - Complaints Related to Early and Late Bus Arrivals and Bus No-Shows passenger complaints related to early, late, and no-show buses between 2016 and 2017. The positive eratin elate om laint trend of declining total complaints as displayed in Figure l ro ecem er 18 is also seen here for the subset of complaints related to bus on-time performance. Specifically, the data in Figure 19 shows a decline in complaints regarding early bus arrivals of 45% while complaints related to no-shows declined by 32%. The decline in these complaint types points to progress on one of the key goals of the BaltimoreLink redesign, which was improved service reliability.
Passenger complaints related to early, late, and no-show buses declined in each category in 2017 compared to 2016. Complaints related to early buses fell by 45%, complaints perating Related o plaints perating Related related to late buses fell by 3%, and complaints related to no- show buses fell by 32%. o Sho arly Late
Source: MDOT MTA Customer Complaint Database
Customer Satisfaction 21 BaltimoreLink Performance Report to the Maryland State Legislature
22 Customer Satisfaction BaltimoreLink Performance Report to the Maryland State Legislature
D. BaltimoreLink Capital Improvement Status
Much of the focus of this Legislative Report has been on the average daily boardings, transfer volumes, identified Title VI service redesign elements of BaltimoreLink, but the redesign issues, service frequency at stops, operator relief points, and effort also included capital improvement initiatives to support adjacent human service facilities such as doctor’s offices or the BaltimoreLink service elements. The purpose of this report elder care facilities. Phase 2 of this program will include section is to outline the implementation status of these capital the installation of 50 additional shelters. The remaining improvements. Each of the initiatives is summarized below. shelters will then be installed following the same procedures in batches of 50 shelters. West Baltimore Enhanced Service Color Destination Signs This capital initiative involved the evaluation of bus stops along the pre-BaltimoreLink QuickBus 40 (which has generally 91 buses procured in 2013 and 2014 have been been replaced by the CityLink Blue route) in order to retrofitted with new destination signs that display identify improvements that would enhance the passenger the bus’s destination in color. In addition, all 2016 wait experience. Improvements, which were completed and 2017 buses were delivered with factory installed in May 2017 prior to BaltimoreLink implementation, Color Destination Signs, and this feature will now included shelter improvements, new trash cans, sidewalk automatically be part of all new bus purchases. improvements, and some accessibility improvements. The retrofit project was completed prior to the BaltimoreLink launch. New Vehicles Bus Wraps MDOT MTA procured 172 new buses in the FY 16/FY 17 procurement as replacements for older vehicles reaching This initiative involved the installation of bus the end of their useful life. All of these buses were in revenue wraps designating a bus as serving either service by the BaltimoreLink launch in June 2017. a LocalLink or CityLink route. 250 buses were wrapped as CityLink buses and Bus Shelters 500 were wrapped as LocalLink Funding has been provided for the installation of 200 new buses. This initiative was completed bus shelters to help improve the passenger experience at prior to the BaltimoreLink launch. high ridership stops throughout the MDOT MTA bus system. 30 shelters have been installed to date. The selection of installation sites is based on a rating system that considers
BaltimoreLink Capital Improvement Status 23 BaltimoreLink Performance Report to the Maryland State Legislature
Signage and Maps Dedicated Transitways Transit Signal Priority
BaltimoreLink involved the wholesale rebranding of the In order to improve vehicle travel times and reliability, the Transit Signal Priority has been installed at 36 intersections Baltimore region’s bus system. To that end, new bus stop MDOT MTA implemented 5.5 miles of dedicated transitways in along Loch Raven Boulevard (CityLink Green) and York signs were installed at each of the 4,000 stops in the the following corridors. Each of these dedicated transitways is Road (CityLink Red). In addition, the required TSP BaltimoreLink network (these were all installed prior to the now in place. equipment on buses has been installed on 251 vehicles BaltimoreLink launch). to date. The MDOT MTA is currently working on equipping the 1. Fayette Street through downtown Baltimore–0.87 miles of remaining vehicles in the MDOT MTA fleet. Additional corridors The new signs include route destinations and service dedicated all-day curb-running transitway. have been identified and MDOT MTA is coordinating with frequencies. To complement the new bus stop signs, several Baltimore City DOT on installation. hundred bus shelters were equipped with new system 2. Baltimore Street through downtown Baltimore–.087 miles of maps reflecting the new BaltimoreLink system. System dedicated all-day curb-running transitway. Transit Transfer Facilities maps were also updated at all Metro SubwayLink and 3. Charles Street through downtown Baltimore–0.55 miles of The redesign of the Baltimore bus system into BaltimoreLink Light RailLink stations as were the station name pylons at dedicated PM peak curb-running transitway. each of these stations. Finally, downtown transfer stations relied heavily on transfer facilities throughout the system. 4. St. Paul Street through downtown Baltimore–0.42 miles of and busy transfer stops outside downtown were equipped Improvements at key transfer locations include the following: with “you are here” neighborhood maps that also show dedicated peak period transitway, consisting predominantly of 1. Development of an off-street transfer facility at the West connections between modes. All of this work was completed curbside running. Baltimore MARC station, which also included the installation of prior to the BaltimoreLink launch. 5. Hillen Street/Guilford Avenue/South Street through downtown real-time bus arrival displays, sheltered waiting areas, bicycle Baltimore–0.52 miles of dedicated all-day curb-running parking, additional CCTV cameras, ticket vending machines, transitway. emergency phones, and a ZipCar parking spot. 6. Gay Street/Ensor Street through downtown Baltimore–0.53 miles 2. Installation of real-time bus arrival information displays, new of dedicated all-day curb-running transitway. shelters, bicycle parking, additional CCTV cameras, emergency 7. Lombard and Pratt Streets through downtown Baltimore – telephones and ticket vending machines at key transfer upgrades of dedicated all-day curb-running bus lanes originally locations throughout the system including at Penn-North Metro, installed in 2009. Upgrades included painting the dedicated Penn Station, Charles Center, Bayview Hospital, State Center, bus lanes on each street red to more strongly communicate and Lexington Market. that these are dedicated transitway facilities. This initiative
also extended the dedicated bus lanes to the blocks between Howard and Greene Streets.
24 BaltimoreLink Capital Improvement Status BaltimoreLink Performance Report to the Maryland State Legislature
Car Sharing/Pop-Up Transit Services Howard Street Audio-Visual Safety Project MDOT MTA has also been working to improve bicycle parking at rail stations throughout the system. Bicycle parking was MDOT MTA has partnered with the Parking Authority of This project involved the installation of audio-visual added to eleven stations around the state. Bike parking and/ Baltimore City (PABC) to expand its existing car sharing warning technology at all 17 intersections along the or lockers were added at these locations that either had no program to transit facilities. PABC has a contract with ZipCar; Central Light Rail Line between the Camden Yards Light bike parking or bike parking that did not meet the needs if PABC puts out a new RFP for car sharing, MDOT MTA will work Rail Station and the Mount Royal Light Rail Station. Signs – at the site. Bicycle parking is also being added at 16 Light with PABC on the RFP to piggyback on the new contract. A one- along with corresponding audible warnings – are activated as a Rail and nine Metro Subway stations. year License Agreement between MDOT MTA and ZipCar has light rail vehicle approaches the intersection. This project adds been executed. ZipCar leases the parking spaces from MDOT an additional level of pedestrian safety in downtown Baltimore. MDOT MTA has also been a partner in the Baltimore Bike MTA for a fee (a tenant-landlord relationship). A total of 18 Share system, working in partnership with the Baltimore stations and 32 spaces are planned, with deployment in Last Mile Investments City Department of Transportation to ensure that Bike Share phases between June 2017 and June 2018. This partnership MDOT MTA has undertaken efforts to improve connections complements the transit system. Of the 25 locations installed to provides increased regional mobility and alternatives to car between bicycling and transit to improve the reach of transit date, seven have been at or adjacent to MARC, Light Rail, or ownership. and make it easier for people to access transit service by bike. Metro Subway stations and four more are planned at locations at or adjacent to rail stations. Fort Meade Connections The first MARC Bike Car service was offered on weekend Penn Line trains starting in December 2014. While folding MDOT MTA, through BaltimoreLink, has developed a bicycles have always been allowed on MARC trains, the transportation shuttle service to connect the Penn and conversion of single-level MARC passenger cars to Bike Cars Camden Line MARC lines with Fort Meade, National has allowed users to bring full-size bicycles on the train. With the Business Park, and the National Security Agency. The start of the BaltimoreLink process in the fall of 2015, additional Regional Transportation Agency of Central Maryland (RTA) is bike cars were added so that all weekend Penn Line trains can providing service on this new route, designated route 504. This carry full-sized bicycles. Bike Car service has also been run on initiative is funded for a two-year period at $460,000 per year, Bike to Work Day, World Car Free Day, and on other occasional which includes the cost of four shuttle buses, operators, and weekdays to improve bicycling access for MARC weekday maintenance expenses. The new service began operating on passengers and those on the Brunswick Line. To allow for October 1, 2017. Ridership is off to a steady start with limited the use of full-size bicycles regularly on weekday MARC but positive feedback from passengers. The 504 provides an service, an effort is now underway to install two bike racks additional layer of service to the Fort Meade internal shuttle and in select MARC passenger cars. bolsters service to the Savage and Odenton MARC stations, and to the 202 Commuter Bus.
BaltimoreLink Capital Improvement Status 25
BaltimoreLink Performance Report to the Maryland State Legislature
Appendices
Appendix 1– Weekday Ridership Detail
Appendix 2 – On-Time Performance Detail
Appendix 3 – Weekend Ridership Detail
Appendices 27 BaltimoreLink Performance Report to the Maryland State Legislature
The data on this page outlines weekday CityLink ridership by route, for the months between July 2017 and December 2017.
App.- Fig. 1: July 2017 Daily Weekday Ridership by CityLink Route App.- Fig. 2: August 2017 Daily Weekday Ridership by CityLink Route App.- Fig. 3: September 2017 Daily Weekday Ridership by CityLink Route
era e eek a ail i er i it Link o te era e eek a ail i er i it Link o te era e eek a ail i er i it Link o te l t e tem er
Ridership Ridership Ridership
Red old range lue reen a y urple ro n ello Sil er in Li e Red old range lue reen a y urple ro n Sil er ello in Li e Red old range lue reen ro n a y Sil er Li e ello in urple ityLin Routes ityLin Routes ityLin Routes
Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System
App.- Fig. 4: October 2017 Daily Weekday Ridership by CityLink Route App.- Fig. 5: November 2017 Daily Weekday Ridership by CityLink Route App.- Fig. 6: December 2017 Daily Weekday Ridership by CityLink Route
era e eek a ail i er i it Link o te era e eek a ail i er i it Link o te era e eek a ail i er i it Link o te cto er o em er ecem er
Ridership Ridership Ridership
range Red lue old reen a y ro n ello Sil er Li e in urple Red range lue old reen a y ro n in ello Sil er urple Li e Red old range lue reen a y ro n ello urple Sil er in Li e ityLin Routes ityLin Routes ityLin Routes
Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System
28 Appendix 1- Weekday Ridership Detail BaltimoreLink Performance Report to the Maryland State Legislature
The data on this page outlines weekday LocalLink ridership by route, for the months between July 2017 and December 2017.
App.- Fig. 3: September 2017 Daily Weekday Ridership by CityLink Route App.- Fig. 7: July 2017 Daily Weekday Ridership by LocalLink Route App.- Fig. 8: August 2017 Daily Weekday Ridership by LocalLink Route App.- Fig. 9: September 2017 Daily Weekday Ridership by LocalLink Route
era e eek a ail i er i LocalLink o te era e eek a ail i er i LocalLink o te era e eek a ail i er i LocalLink o te l t e tem er
Ridership Ridership Ridership
Lo alLin Routes Lo alLin Routes Lo alLin Routes
Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System
App.- Fig. 10: October 2017 Daily Weekday Ridership by LocalLink Route App.- Fig. 11: November 2017 Daily Weekday Ridership by LocalLink Route App.- Fig. 12: December 2017 Daily Weekday Ridership by LocalLink Route
era e eek a ail i er i LocalLink o te era e eek a ail i er i LocalLink o te era e eek a ail i er i LocalLink o te cto er o em er ecem er
Ridership Ridership Ridership
Lo alLin Routes Lo alLin Routes Lo alLin Routes
Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System
LocalLink Route 38 is a seasonal supplemental service school tripper route.
Appendix 1- Weekday Ridership Detail 29 BaltimoreLink Performance Report to the Maryland State Legislature
The data on this page outlines weekday Express BusLink ridership by route, for the months between July 2017 and December 2017.
App.- Fig. 13: July 2017 Daily Weekday Ridership by Express BusLink Route App.- Fig. 14: August 2017 Daily Weekday Ridership by Express BusLink Route App.- Fig. 15: September 2017 Daily Weekday Ridership by Express BusLink Route
era e eek a ail i er i re B Link o te era e eek a ail i er i re B Link o te era e eek a ail i er i re B Link o te l t e tem er
Ridership Ridership Ridership
press usLin Routes press usLin Routes press usLin Routes
Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System
App.- Fig. 16: October 2017 Daily Weekday Ridership by Express BusLink Route App.- Fig. 17: November 2017 Daily Weekday Ridership by Express BusLink Route App.- Fig. 18: December 2017 Daily Weekday Ridership by Express BusLink Route
era e eek a ail i er i re B Link o te era e eek a ail i er i re B Link o te era e eek a ail i er i re B Link o te cto er o em er ecem er
Ridership Ridership Ridership
press usLin Routes press usLin Routes press usLin Routes
Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System
Express BusLink Route 104 was discontinued as part of BaltimoreLink, reinstated in September.
30 Appendix 1- Weekday Ridership Detail BaltimoreLink Performance Report to the Maryland State Legislature
The data on this page outlines the top 10 highest weekday BaltimoreLink routes, for the months between July 2017 and December 2017.
App.- Fig. 19: Top 10 Weekday Daily Ridership Routes - July 2017 App.- Fig. 20: Top 10 Weekday Daily Ridership Routes - August 2017 App.- Fig. 21: Top 10 Weekday Daily Ridership Routes - September 2017
o i e t i er i BaltimoreLink o te o i e t i er i BaltimoreLink o te o i e t i er i BaltimoreLink o te eek a l eek a t eek a e tem er
Ridership Ridership Ridership
Red old range lue reen a y urple Red old range lue reen a y urple Red old range lue reen ro n a y
alti oreLin Routes alti oreLin Routes alti oreLin Routes
Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System
App.- Fig. 22: Top 10 Weekday Daily Ridership Routes - October 2017 App.- Fig. 23: Top 10 Weekday Daily Ridership Routes - November 2017 App.- Fig. 24: Top 10 Weekday Daily Ridership Routes - December 2017
o i e t i er i BaltimoreLink o te o i e t i er i BaltimoreLink o te o i e t i er i BaltimoreLink o te eek a cto er eek a o em er eek a ecem er
Ridership Ridership Ridership
range Red lue old reen a y ro n Red old range lue reen a y urple Red old range lue reen a y ro n
alti oreLin Routes alti oreLin Routes alti oreLin Routes
Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System
Appendix 1- Weekday Ridership Detail 31 BaltimoreLink Performance Report to the Maryland State Legislature
The data on this page shows weekday ridership by route category for the months between July 2017 and December 2017.
App.- Fig. 25: July 2017 Daily Weekday Ridership by Route Category App.- Fig. 26: August 2017 Daily Weekday Ridership by Route Category App.- Fig. 27: September 2017 Daily Weekday Ridership by Route Category
era e eek a ail i er i era e eek a ail i er i era e eek a ail i er i Break o n o te ate or Break o n o te ate or Break o n o te ate or l t e tem er
ityLin Lo alLin pressLin ityLin Lo alLin pressLin ityLin Lo alLin pressLin
App.- Fig. 28: October 2017 Daily Weekday Ridership by Route Category App.- Fig. 29: November 2017 Daily Weekday Ridership by Route Category App.- Fig. 30: December 2017 Daily Weekday Ridership by Route Category
era e eek a ail i er i era e eek a ail i er i era e eek a ail i er i Break o n o te ate or Break o n o te ate or Break o n o te ate or cto er o em er ecem er
ityLin Lo alLin pressLin ityLin Lo alLin pressLin ityLin Lo alLin pressLin
32 Appendix 1- Weekday Ridership Detail BaltimoreLink Performance Report to the Maryland State Legislature
The data on this page outlines LocalLink on-time performance by route, for the months between July 2017 and December 2017.
App.- Fig. 31: LocalLink On-Time Performance – July 2017 App.- Fig. 32: LocalLink On-Time Performance – August 2017 App.- Fig. 33: LocalLink On-Time Performance – September 2017
LocalLink n ime Performance LocalLink n ime Performance LocalLink n ime Performance l t e tem er
rips rri ing as S heduled rips rri ing as S heduled rips rri ing as S heduled rips
Lo alLin Routes Lo alLin Routes Lo alLin Routes
Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System
App.- Fig. 34: LocalLink On-Time Performance – October 2017 App.- Fig. 35: LocalLink On-Time Performance – November 2017 App.- Fig. 36: LocalLink On-Time Performance – December 2017
LocalLink n ime Performance LocalLink n ime Performance LocalLink n ime Performance cto er o em er ecem er
rips rri ing as S heduled rips rri ing as S heduled rips rri ing as S heduled rips
Lo alLin Routes Lo alLin Routes Lo alLin Routes
Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System
Appendix 2- On Time Performance Detail 33 BaltimoreLink Performance Report to the Maryland State Legislature
The data on this page outlines Saturday CityLink ridership by route, for the months between July 2017 and December 2017.
App.- Fig. 37: July 2017 Saturday CityLink Ridership by Route App.- Fig. 38: August 2017 Saturday CityLink Ridership by Route App.- Fig. 39: September 2017 Saturday CityLink Ridership by Route
era e at r a i er i it Link o te era e at r a i er i it Link o te era e at r a i er i it Link o te l t e tem er
Ridership Ridership Ridership Red range old lue ro n a y urple reen Li e in ello Sil er range Red lue ro n a y urple reen old ello in Sil er Li e Red a y lue Li e old ro n range ello urple reen Sil er in ityLin Routes ityLin Routes ityLin Routes
Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System
App.- Fig. 40: October 2017 Saturday CityLink Ridership by Route App.- Fig. 41: November 2017 Saturday CityLink Ridership by Route App.- Fig. 42: December 2017 Saturday CityLink Ridership by Route
era e at r a i er i it Link o te era e at r a i er i it Link o te era e at r a i er i it Link o te cto er o em er ecem er
Ridership Ridership Ridership Red lue a y ro n ello range reen Sil er old urple Li e in Red range lue a y ro n old reen Li e ello urple in Sil er Red range lue old ro n a y reen ello urple Li e in Sil er ityLin Routes ityLin Routes ityLin Routes
Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System
34 Appendix 3- Weekend Ridership Detail BaltimoreLink Performance Report to the Maryland State Legislature
The data on this page outlines Sunday CityLink ridership by route, for the months between July 2017 and December 2017.
App.- Fig. 43: July 2017 Sunday CityLink Ridership by Route App.- Fig. 44: August 2017 Sunday CityLink Ridership by Route App.- Fig. 45: September 2017 Sunday CityLink Ridership by Route
era e n a i er i it Link o te era e n a i er i it Link o te era e n a i er i it Link o te l t e tem er
erage Ridership erage Ridership erage Ridership erage
range Red lue old reen a y ro n Li e ello urple in Sil er Red range old reen lue ro n a y Li e in ello urple Sil er range lue reen Red Sil er old Li e a y ello in urple ro n ityLin Routes ityLin Routes ityLin Routes
Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System
App.- Fig. 46: October 2017 Sunday CityLink Ridership by Route App.- Fig. 47: November 2017 Sunday CityLink Ridership by Route App.- Fig. 48: December 2017 Sunday CityLink Ridership by Route
era e n a i er i it Link o te era e n a i er i it Link o te era e n a i er i it Link o te cto er o em er ecem er
erage Ridership erage Ridership erage Ridership erage
range Red old lue reen a y ello in Sil er Li e ro n urple range Red old lue reen a y Li e in ro n ello Sil er urple range Red old lue reen ello Li e in a y ro n Sil er urple ityLin Routes ityLin Routes ityLin Routes
Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System
Appendix 3- Weekend Ridership Detail 35 BaltimoreLink Performance Report to the Maryland State Legislature
The data on this page outlines Saturday LocalLink ridership by route, for the months between July 2017 and December 2017.
App.- Fig. 49: July 2017 Saturday LocalLink Ridership by Route App.- Fig. 50: August 2017 Saturday LocalLink Ridership by Route App.- Fig. 51: September 2017 Saturday LocalLink Ridership by Route
era e at r a ail i er i LocalLink o te era e at r a ail i er i LocalLink o te era e at r a ail i er i LocalLink o te l t e tem er
Ridership Ridership Ridership
Lo alLin Routes Lo alLin Routes Lo alLin Routes
Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System
App.- Fig. 52: October 2017 Saturday LocalLink Ridership by Route App.- Fig. 53: November 2017 Saturday LocalLink Ridership by Route App.- Fig. 54: December 2017 Saturday LocalLink Ridership by Route
era e at r a ail i er i LocalLink o te era e at r a ail i er i LocalLink o te era e at r a ail i er i LocalLink o te cto er o em er ecem er
Ridership Ridership Ridership
Lo alLin Routes Lo alLin Routes Lo alLin Routes
Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System
36 Appendix 3- Weekend Ridership Detail BaltimoreLink Performance Report to the Maryland State Legislature
The data on this page outlines Sunday LocalLink ridership by route, for the months between July 2017 and December 2017.
App.- Fig. 55: July 2017 Sunday LocalLink Ridership by Route App.- Fig. 56: August 2017 Sunday LocalLink Ridership by Route App.- Fig. 57: September 2017 Sunday LocalLink Ridership by Route
era e n a ail i er i LocalLink o te era e n a ail i er i LocalLink o te era e n a ail i er i LocalLink o te l t e tem er
erage Ridership erage Ridership erage Ridership erage
Lo alLin Routes Lo alLin Routes Lo alLin Routes
Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System
App.- Fig. 58: October 2017 Sunday LocalLink Ridership by Route App.- Fig. 59: November 2017 Sunday LocalLink Ridership by Route App.- Fig. 60: December 2017 Sunday LocalLink Ridership by Route
era e n a ail i er i LocalLink o te era e n a ail i er i LocalLink o te era e n a ail i er i LocalLink o te cto er o em er ecem er
erage Ridership erage Ridership erage Ridership erage
Lo alLin Routes Lo alLin Routes Lo alLin Routes
Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System
Appendix 3- Weekend Ridership Detail 37 BaltimoreLink Performance Report to the Maryland State Legislature
The data on this page outlines the top 10 highest Saturday BaltimoreLink routes, for the months between July 2017 and December 2017.
App.- Fig. 61: Top 10 Highest Saturday Ridership Routes - July 2017 App.- Fig. 62: Top 10 Highest Saturday Ridership Routes - August 2017 App.- Fig. 63: Top 10 Highest Saturday Ridership Routes - September 2017
o i e t i er i BaltimoreLink o te o i e t i er i BaltimoreLink o te o i e t i er i BaltimoreLink o te at r a l at r a t at r a e tem er
Riedership Riedership Riedership Red range old lue ro n a y urple reen range Red lue ro n a y urple reen old Red a y lue Li e old ro n range ello
alti oreLin Routes alti oreLin Routes alti oreLin Routes
Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System
App.- Fig. 64: Top 10 Highest Saturday Ridership Routes - October 2017 App.- Fig. 65: Top 10 Highest Saturday Ridership Routes - November 2017 App.- Fig. 66: Top 10 Highest Saturday Ridership Routes - December 2017
o i e t i er i BaltimoreLink o te o i e t i er i BaltimoreLink o te o i e t i er i BaltimoreLink o te at r a cto er at r a o em er at r a ecem er
Riedership Riedership Riedership Red lue a y ro n ello range reen Sil er Red range lue a y ro n old reen Red range lue old ro n a y reen ello urple
alti oreLin Routes alti oreLin Routes alti oreLin Routes
Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System
38 Appendix 3- Weekend Ridership Detail BaltimoreLink Performance Report to the Maryland State Legislature
The data on this page outlines the top 10 highest Sunday BaltimoreLink routes, for the months between July 2017 and December 2017.
App.- Fig. 67: Top 10 Highest Sunday Ridership Routes - July 2017 App.- Fig. 68: Top 10 Highest Sunday Ridership Routes - August 2017 App.- Fig. 69: Top 10 Highest Sunday Ridership Routes -September 2017
o i e t i er i BaltimoreLink o te o i e t i er i BaltimoreLink o te o i e t i er i BaltimoreLink o te n a l n a t n a e tem er
Riedership Riedership Riedership
range Red lue old reen a y ro n Red range old reen lue ro n a y range lue reen Red Sil er old Li e
alti oreLin Routes alti oreLin Routes alti oreLin Routes
Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System
App.- Fig. 70: Top 10 Highest Sunday Ridership Routes - October 2017 App.- Fig. 71: Top 10 Highest Sunday Ridership Routes - November 2017 App.- Fig. 72: Top 10 Highest Sunday Ridership Routes -December 2017
o i e t i er i BaltimoreLink o te o i e t i er i BaltimoreLink o te o i e t i er i BaltimoreLink o te n a cto er n a o em er n a ecem er
Riedership Riedership Riedership
range Red old lue reen a y range Red old lue reen a y Li e in ro n range Red old lue reen ello Li e in a y
alti oreLin Routes alti oreLin Routes alti oreLin Routes
Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System Source: MDOT MTA Onboard Automatic Passenger Counting System
Appendix 3- Weekend Ridership Detail 39