This is a good article. Click here for more information.

Washington Metro

From Infogalactic: the planetary knowledge core
(Redirected from Washington DC Metro)
Jump to: navigation, search

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Lua error in package.lua at line 80: module 'strict' not found.

Washington Metro
Black and white Washington Metro logo with a big white M above smaller white letters spelling Metro
Overview
Locale Washington, D.C.
Transit type Rapid transit
Number of lines 6
Line number Red Line Red Line
Blue Line Blue Line
Orange Line Orange Line
Yellow Line Yellow Line
Green Line Green Line
Silver Line Silver Line
Number of stations 91
Daily ridership 712,843 (May 2015, weekday)[1]
Annual ridership 209 million (2013, approx.)[2]
Chief executive Paul Wiedefeld[3]
Headquarters 600 5th St NW
Washington, D.C. 20001
Website www.wmata.com
Operation
Began operation March 27, 1976; 48 years ago (1976-03-27)
Operator(s) Washington Metropolitan Area Transit Authority (WMATA)
Character At-grade, elevated, and underground
Number of vehicles 1,126 railcars
Train length 6 or 8 cars
Headway 6 mins peak; 12–20 mins offpeak
Technical
System length 117 mi (188 km)
No. of tracks 2
Track gauge 4 ft 8¼ in (1429 mm) [4]
Electrification Third rail 750 V DC
System map

Washington Metro diagram sb.svg

The Washington Metro, commonly called Metro and branded Metrorail,[5] is the rapid transit system serving the Washington, D.C. metropolitan area in the United States. It is administered by the Washington Metropolitan Area Transit Authority (WMATA), which also operates Metrobus service under the Metro name.[6] Besides the District, Metro serves several jurisdictions in Maryland and Virginia. In Maryland, Metro provides service to Montgomery and Prince George's counties; in Virginia, to Fairfax and Arlington counties and the independent city of Alexandria. The system is currently being expanded into Loudoun County, Virginia. The Metro service area is largely coextensive with the inner ring of the Washington metropolitan area. Opened in 1976, the network now includes six lines, 91 stations, and 117 miles (188 km) of route.[7][8]

Metro is the second-busiest rapid transit system in the United States in number of passenger trips, after the New York City Subway.[9] There were 215.3 million trips, or 712,843 trips per weekday, on Metro in fiscal year 2015.[1] In June 2008, Metro set a monthly ridership record with 19,729,641 trips, or 798,456 per weekday.[10] Fares vary based on the distance traveled, the time of day, and the type of card used by the passenger. Riders enter and exit the system using a stored-value card in the form of a paper magnetic stripe farecard or a proximity card called SmarTrip.

History

Metro under construction at the Navy Yard in 1989

During the 1960s, plans were laid for a massive freeway system in Washington. Harland Bartholomew, who chaired the National Capital Planning Commission, thought that a rail transit system would never be self-sufficient because of low density land uses and general transit ridership decline.[11] But the plan met fierce opposition, and was altered to include a Capital Beltway system plus rail line radials. The Beltway received full funding; funding for the ambitious Inner Loop Freeway system was partially reallocated toward construction of the Metro system.[12]

In 1960, the federal government created the National Capital Transportation Agency to develop a rapid rail system. In 1966, a bill creating WMATA was passed by the federal government, the District of Columbia, Virginia, and Maryland,[13] with planning power for the system being transferred to it from the NCTA.[14]

Passengers sit in fixed two-seat units. There are metal poles and bars for standees to hold.
Interior of a rehabilitated Breda car

WMATA approved plans for a 98-mile (158 km) regional system in 1968.[14] Construction began after a groundbreaking ceremony on December 9, 1969, when Secretary of Transportation John A. Volpe, District Mayor Walter Washington, and Maryland Governor Marvin Mandel tossed the first spade of dirt at Judiciary Square.[15] The first portion of the system opened March 27, 1976, with 4.6 miles (7.4 km) available on the Red Line with five stations from Rhode Island Avenue to Farragut North, all in the District of Columbia.[16] Arlington County, Virginia was linked to the system on July 1, 1977;[17] Montgomery County, Maryland, on February 6, 1978;[18] Prince George's County, Maryland, on November 20, 1978;[19] and Fairfax County, Virginia, and Alexandria, Virginia, on December 17, 1983.[13][20] Underground stations were built with cathedral-like arches of concrete, highlighted by soft, indirect lighting.[21] The name Metro was suggested by Massimo Vignelli, who designed the subway maps for the New York City Subway.[22]

The 103-mile (166 km), 83-station system was completed with the opening of the Green Line segment to Branch Avenue on January 13, 2001. This did not mean the end of the growth of the system: a 3.22-mile (5.18 km) extension of the Blue Line to Largo Town Center and Morgan Boulevard opened on December 18, 2004. The first in-fill station, NoMa – Gallaudet University (at the time called the New York Ave–Florida Ave–Gallaudet University station) on the Red Line between Union Station and Rhode Island Ave-Brentwood, opened November 20, 2004. Construction began in March 2009 for an extension to Dulles Airport to be built in two phases and opening in 2014 and 2018.[23] The first phase, five stations connecting East Falls Church to Tysons Corner and Wiehle Avenue in Reston, opened on July 26, 2014.[24]

Metro construction required billions of federal dollars, originally provided by Congress under the authority of the National Capital Transportation Act of 1969 (Public Law 91-143). The cost was paid with 67% federal money and 33% local money. This act was amended on January 3, 1980 by Public Law 96-184, "The National Capital Transportation Amendment of 1979" (also known as the Stark-Harris Act), which authorized additional funding of $1.7 billion to permit the completion of 89.5 miles (144.0 km) of the system as provided under the terms of a full funding grant agreement executed with WMATA in July 1986, which required 20% to be paid from local funds. On November 15, 1990, Public Law 101-551, "The National Capital Transportation Amendments of 1990", authorized an additional $1.3 billion in federal funds for construction of the remaining 13.5 miles (21.7 km) of the 103-mile (166 km) system, completed via the execution of full funding grant agreements, with a 63% federal/37% local matching.[25]

The highest ridership for a single day was on the day of the inauguration of Barack Obama, January 20, 2009, with 1,120,000 riders. It broke the previous record, set the day before, of 866,681 riders.[26] June 2008 set several ridership records: it set the single-month ridership record of 19,729,641 total riders, the record for highest average weekday ridership with 1,044,400 weekday trips, had five of the ten highest ridership days, and had 12 weekdays in which ridership exceed 800,000 trips.[10]

In February 2006, Metro officials chose Randi Miller, a car dealership employee from Woodbridge, Virginia, to record new "doors opening", "doors closing", and "please stand clear of the doors, thank you" announcements after winning an open contest to replace the messages recorded by Sandy Carroll in 1996. The "Doors Closing" contest attracted 1,259 contestants from across the country.[27]

On October 30, 2010, the crowd at the Rally to Restore Sanity and/or Fear broke a 19-year record in Saturday ridership, with 825,437 trips. The previous record had been set on June 8, 1991 at 786,358 trips during the Desert Storm rally.[28][29]

Opening dates

Year Line From To
March 27, 1976 Red Farragut North Rhode Island Avenue
December 15, 1976 Red (opening of Gallery Place) Farragut North Rhode Island Avenue
January 17, 1977 Red Dupont Circle Rhode Island Avenue
July 1, 1977 Blue National Airport Stadium-Armory
February 6, 1978 Red Dupont Circle Silver Spring
November 20, 1978 Orange/Blue National Airport New Carrollton
December 1, 1979 Orange Ballston New Carrollton
November 22, 1980 Blue/Orange National Airport/Ballston Addison Road/New Carrolton
December 5, 1981 Red Van Ness-UDC Silver Spring
April 30, 1983 Yellow National Airport Gallery Place
December 17, 1983 Yellow Huntington Gallery Place
August 25, 1984 Red Grosvenor Silver Spring
December 15, 1984 Red Shady Grove Silver Spring
June 7, 1986 Orange Vienna New Carrollton
September 22, 1990 Red Shady Grove Wheaton
May 11, 1991 Yellow Huntington U Street-Cardozo
June 15, 1991 Blue Van Dorn Street Addison Road
December 28, 1991 Green U Street-Cardozo Anacostia
December 11, 1993 Green Fort Totten Greenbelt
June 29, 1997 Blue Franconia-Springfield Addison Road
July 25, 1998 Red Shady Grove Glenmont
September 18, 1999 Green (connecting previous two segments) Greenbelt Anacostia
January 13, 2001 Green Greenbelt Branch Avenue
November 20, 2004 Red (addition of New York Ave Station) Shady Grove Glenmont
December 18, 2004 Blue Franconia-Springfield Largo Town Center
July 26, 2014 Silver Wiehle – Reston East Largo Town Center
TBA 2019 or 2020 Silver Ashburn Largo Town Center

[30]

Architecture

Many Metro stations were designed by Chicago architect Harry Weese and are examples of late-20th century modern architecture. With their heavy use of exposed concrete and repetitive design motifs, Metro stations display aspects of brutalist design. The stations also reflect the influence of Washington's neoclassical architecture in their overarching coffered ceiling vaults. Weese worked with Cambridge, Massachusetts-based lighting designer Bill Lam for the indirect lighting used throughout the system.[31][32] All of Metro's original Brutalist stations are found in Downtown Washington, D.C. and neighboring urban corridors of Arlington, Virginia, with newer stations incorporating simplified cost-efficient designs.[33]

In 2007, the design of the Metro's vaulted-ceiling stations was voted number 106 on the "America's Favorite Architecture" list compiled by the American Institute of Architects (AIA), and was the only brutalist design to win a place among the 150 selected by this public survey.

In January 2014, the AIA announced that it would present its Twenty-five Year Award to the Washington Metro system for "an architectural design of enduring significance" that "has stood the test of time by embodying architectural excellence for 25 to 35 years". The announcement cited the key role of Weese, who conceived and implemented a "common design kit-of-parts", which continues to guide the construction of new Metro stations over a quarter-century later, albeit with designs modified slightly for cost reasons.[34]

System

System maps
The published system map has every line drawn in its own distinct color. All stations are marked and labeled by name. The map is drawn for clarity and simplicity, not to scale by actual distances and exact relative station locations. There are transfer stations marked where lines cross each other.
Stylized map of existing lines and stations, based on an official September 2013 publicized map, including the Silver Line to Reston and later to Dulles Airport and Loudoun County.
An actual map with correct distances and geographic placement illustrates how all lines intersect and have many stations in the downtown area, and extend with more widely spaced stations far out into the neighboring areas.
Map of system drawn to scale

Since opening in 1976, the Metro network has grown to include six lines, 91 stations, and 118 miles (190 km) of route.[2] The rail network is designed according to a spoke-hub distribution paradigm, with rail lines running between downtown Washington and its nearby suburbs. The system makes extensive use of interlining – running more than one service on the same track. There are six operating lines.[2][35] The system's iconic official map was designed by noted graphic designer Lance Wyman[36] and Bill Cannan while they were partners in the design firm of Wyman & Cannan in New York City.[37]

About 50 miles (80 km) of Metro's track is underground, as are 47 of the 91 stations. Track runs underground mostly within the District and high-density suburbs. Surface track accounts for about 46 miles (74 km) of the total, and aerial track makes up 9 miles (14 km).[2]

In an effort to gain revenues, WMATA has started to allow retail ventures in Metro stations. WMATA has authorized DVD-rental vending machines and ticket booths for the Old Town Trolley Tours and is seeking additional retail tenants.[38]

Washington Metro lines
Line Name Opened Stations Distance Termini
mi km Western/Southern Eastern/Northern
Red Line Red Line 1976 27 31.9 51.3 Shady Grove Glenmont
Blue Line Blue Line 1977 27 30.3 48.8 Franconia–Springfield Largo Town Center
Orange Line Orange Line 1978 26 26.4 42.5 Vienna New Carrollton
Yellow Line Yellow Line 1983 17 15.07 24.25 Huntington
Franconia–Springfield (Rush+)
Mount Vernon Square (rush hours)
Greenbelt (Rush+)
Fort Totten (other times)
Green Line Green Line 1991 21 23.04 37.08 Branch Avenue Greenbelt
Silver Line Silver Line 2014 28 29.6 47.6 Wiehle–Reston East
Ashburn (opens 2019)
Largo Town Center

Financing

Metro relies extensively on passenger fares and appropriated financing from the Maryland, Virginia, and Washington DC governments, which are represented on Metro's board of directors. The system does not have a dedicated revenue stream as other city's mass transit systems do. Critics allege that this has contributed to Metro's recent history of maintenance and safety problems.[39]

For Fiscal Year 2015, the estimated farebox recovery ratio (fare revenue divided by operating expenses) was 66 percent, based on the WMATA approved budget.[40]

Infrastructure

Stations

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

There are 40 stations in the District of Columbia, 15 in Prince George's County, 11 in Montgomery County, 11 in Arlington County, 11 in Fairfax County, and three in the City of Alexandria.[2] The second phase of the Silver Line will add 6 new stations, three more in Fairfax County and three in Loudoun County, Virginia in 2019 or 2020.[41]

At 196 feet (60 m) below the surface, the Forest Glen station on the Red Line is the deepest in the system. There are no escalators; high-speed elevators take 20 seconds to travel from the street to the station platform. The Wheaton station, next to Forest Glen station on the Red Line, has the longest continuous escalator in the USA and in the Western Hemisphere, at 230 feet (70 m).[2][42] The Rosslyn station is the deepest station on the Orange/Blue Line, at 117 feet (36 m) below street level. The station features the second-longest continuous escalator in the Metro system at 194 feet (59 m); an escalator ride between the street level and the mezzanine level takes nearly two minutes.[43]

The system is not centered on any single station, but Metro Center is at the intersection of the Red, Orange and Blue Lines, the three busiest lines, as well as the new Silver Line.[44] The station is also the location of WMATA's main sales office. Metro has designated five other "core stations" that have high passenger volume, including:[45] Gallery Place, transfer station for the Red, Green and Yellow Lines; L'Enfant Plaza, transfer station for the Orange, Blue, Silver, Green and Yellow Lines; Union Station, the busiest station by passenger boardings;[44] Farragut North; and Farragut West.

In order to deal with the high number of passengers in transfer stations, Metro is studying the possibility of building pedestrian connections between nearby core transfer stations. For example, a 750-foot (230 m) passage between Metro Center and Gallery Place stations would allow passengers to transfer between the Orange/Blue/Silver and Yellow/Green Lines without going one stop on the Red Line. Another tunnel between Farragut West and Farragut North stations would allow transfers between the Red and Orange/Blue/Silver lines, decreasing transfer demand at Metro Center by an estimated 11%.[45] The Farragut pedestrian tunnel has yet to be physically implemented, but was added in virtual form effective October 28, 2011. The SmarTrip system now interprets an exit from one Farragut station and entrance to the other as part of a single trip, allowing card holders to transfer on foot without having to pay a second full fare.[46]

Rolling stock

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

An exterior perspective view of a train, with its distinct brown and metallic design, at a station platform.
Train of Rohr cars arriving at the Cheverly station

Metro’s fleet consists of 1,126 rail cars, each 75 feet (22.86 m) long.[47] Trains have a maximum speed of 75 mph (121 km/h), and average 33 mph (53 km/h) including stops. Operating rules presently limit their top speed to 59 mph (95 km/h).[2] All cars operate as married pairs (consecutively numbered even-odd), with systems shared across the pair.[48] Metro currently operates 850 cars during rush hours. 814 cars are in active service, four cars have been permanently removed from revenue service for use as the "money train", and the remaining 36 cars compose gap trains to serve as backup should a train experience problems.[49]

Metro's rolling stock was acquired in six phases, and each version of car is identified with a separate series number. The original order of 300 rail cars (290 of which are in operation as of June 2009[50]) was manufactured by Rohr Industries, with final delivery in 1978. These cars are numbered 1000–1299 and were rehabilitated in the mid-1990s. Breda Costruzioni Ferroviarie (Breda), now AnsaldoBreda, manufactured the second order of 76 cars delivered in 1983 and 1984. These cars, numbered 2000–2075, were rehabilitated in the early 2000s by Alstom in Hornell, New York. A third order of 288 cars, also from Breda, were delivered between 1984 and 1988. These cars are numbered 3000–3291 and were rehabilitated by Alstom in the early 2000s. An order of 100 cars from Breda, numbered 4000–4099, were delivered between 1992 and 1994. A fifth order of 192 cars was manufactured by Construcciones y Auxiliar de Ferrocarriles (CAF) of Spain. These cars are numbered 5000–5191 and were delivered from 2001 through 2004. A sixth order of 184 cars from Alstom Transportation, are numbered 6000-6183 and were delivered between 2005 and 2007. The cars have body shells built in Barcelona, Spain with assembly completed in Hornell, New York.[51]

The 7000 series of cars, currently being built by Kawasaki Heavy Industries Rolling Stock Company of Kobe, Japan are being delivered for on-site testing during winter 2013, and first entered service April 14, 2015 on the Blue Line. The new cars are different from previous models in that while still operating as married pairs, the cab in one car can be removed, essentially turning it into a B car. The new design allows for increased passenger capacity, elimination of redundant equipment, greater energy efficiency, and lower maintenance costs. Metro plans to eventually purchase up to 748 cars to increase system capacity and replace its older rolling stock.[47][52] The National Transportation Safety Board investigation of the fatal June 22, 2009, accident led it to conclude that the 1000 series cars are unsafe and unable to protect customers in a crash.

As a result, on July 26, 2010, Metro voted to purchase 300 7000 series cars to replace the remaining 1000 series cars.[53][54] An additional 128 7000 series cars were also ordered to serve the new Silver Line to Dulles Airport (64 for each phase). In May 2013, Metro placed another order for 100 7000 series cars, which will replace all of the 4000 series cars.[55] By June 2015 WMATA plans to exercise their remaining options to purchase an additional 220 7000 series railcars for fleet expansion, bringing the total number of 7000 series railcars on order to 748.[56]

In May, 2015, WMATA's plan to replace 192 of the chronically problematic 5000-series cars built in the early 2000s with 220 new 7000-series cars was at risk because the older cars were funded by federal money and requires FTA approval.[57]

Signaling and operation

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

During normal passenger operation on revenue tracks, trains are designed to be controlled by an integrated Automatic Train Operation (ATO) and Automatic Train Control (ATC) system that accelerates and brakes trains automatically without operator intervention. All trains are still manned with train operators who open and close the doors, make station announcements, and supervise their trains. The system was designed so that an operator could manually operate a train when necessary.[58]

Since June 2009, when two Red Line trains collided and killed nine people due in part to malfunctions in the ATC system, all Metro trains have been manually operated.[59] The current state of manual operation has led to heavily degraded service, with new manual requirements such as absolute blocks, speed restrictions, and end-of-platform stopping leading to increased headways between trains, increased dwell time, and worse on-time performance.[60] Metro will begin phasing back in ATC in October 2014.[61]

The train doors were originally designed to be opened and closed automatically and the doors would re-open if an object blocked them, much as elevator doors do. Almost immediately after the system opened in 1976 Metro realized these features were not conducive to safe or efficient operation and they were disabled. At present the doors may be opened automatically or manually. If a door tries to close and it meets an obstruction, the operator must re-open the door.

Hours and headways

Metrorail begins service at 5 am Monday through Friday and at 7 am Saturdays and Sundays; it ends service at midnight Sunday through Thursday nights and at 3 am on Friday and Saturday nights, although the last trains leave the end stations inbound about half an hour before these times.[62] Trains run more frequently during rush hours on all lines, with scheduled peak hour headways of 3 minutes on the Red Line and 6 minutes on all other lines. Headways are much longer during midday and evening on weekdays and all weekend. The midday six-minute headways are based on a combination of two Metrorail lines (Orange/Blue and Yellow/Green) as each route can run every 12 minutes; in the case of the Red Line, every other train bound for Glenmont terminates at Silver Spring instead. Night and weekend service varies between 8 and 24 minutes, with trains generally scheduled only every 20 minutes. As of 2012, the WMATA board of directors was considering adopting a new policy that would codify maximum acceptable headways as 15 minutes during peak hours and 30 minutes during off-peak.[63]

Other service truncations also occur in the system during rush hour service only. On the Red Line, every other train bound for Shady Grove terminates at Grosvenor-Strathmore, in addition to the alternating terminations at Silver Spring mentioned above. For the Yellow Line, all non-Rush+ trains (that is, all trains originating from Huntington, not Franconia-Springfield) bound for Fort Totten terminate at Mount Vernon Square. These are primarily instituted due to a limited supply of rail cars and the locations of pocket tracks throughout the system.

Until 1999, Metro ended service at midnight every night, and weekend service began at 8 am. That year, WMATA began late night service on Fridays and Saturdays until 1 am. By 2007, with encouragement from businesses, that closing time had been pushed back to 3 am.[64] There were plans floated to end late night service due to costs in 2011, but they were met with resistance by riders.[65]

Special service patterns

Metro runs special service patterns on holidays and when events in Washington may require additional service. Independence Day activities require Metro to adjust service to provide extra capacity to and from the National Mall.[66] WMATA makes similar adjustments during other events, such as presidential inaugurations. Metro has altered service and used some stations as entrances or exits only to help manage congestion.[67]

Rush Plus

In 2012, WMATA announced enhanced rush period service that was implemented on June 18, 2012 under the name Rush+ (or Rush Plus). Rush Plus service occurs only during portions of peak service: 6:30-9 AM and 3:30-6 PM, Monday through Friday.

The Rush+ realignment was intended to free up space in the Rosslyn Portal (the tunnel between Rosslyn and Foggy Bottom), which operates at full capacity already. When Silver Line service began, those trains would be routed through the tunnel, and so some of what were Blue Line trains to Largo Town Center were now diverted across the Fenwick Bridge to become Yellow Line trains running all the way up the Green Line to Greenbelt. Select Yellow Line trains running south diverted along the Blue Line to Franconia-Springfield (as opposed to the normal Yellow line terminus at Huntington). Until the start of Silver Line service, excess Rosslyn Tunnel capacity was used by additional Orange Line trains that traveled along the Blue Line to Largo (as opposed to the normal Orange Line terminus at New Carrollton). Rush+ had the additional effect of giving some further number of passengers transfer-free journeys, though severely increasing headways for the portion of the Blue Line running between Pentagon and Rosslyn.

Passenger information systems

PIDS signs at the Gallery Place station

A Passenger Information Display System (PIDS) was installed in all Metrorail stations in 2000. Displays are located on all track platforms and at the mezzanine entrances of stations, and provide real-time information on next train arrivals, delayed trains, emergency announcements, and related information.[68] WMATA also provides current train and related information to customers with conventional web browsers, as well as users of smartphones and other mobile devices.[69] In 2010 Metro began sharing its PIDS data with outside software developers, for use in creating additional real-time applications for mobile devices. Free apps are available to the public on major mobile device software platforms (iPhone/iPad, Android, Windows Phone, Palm).[70][71] WMATA also began providing real-time train information by phone in 2010.[72]

Fare structure

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

A row of fare-card machines, each with buttons, slots for money and farecards, and printed instructions.
Standard self-service vending machines for passes and farecards located at each station

Riders enter and exit the system using a stored-value card in the form of a paper magnetic stripe farecard or a proximity card known as SmarTrip. The fare is deducted from the balance of the card; on paper farecards, the new balance is printed upon exiting the system.[73] Farecards are purchased primarily at vending machines in each station. Paper farecards can hold up to $45 in value and are reused until the value of the card reaches zero. If the card contains the exact fare needed to exit, leaving the card at a zero balance, the card is not returned by the exit gate. SmarTrip cards can be purchased at station vending machines, online or at retail outlets, and can store up to $300 in value.

Metro fares vary based on the distance traveled and the time of day at entry. During peak hours (weekdays from opening until 9:30 a.m. and 3–7 p.m., and Friday and Saturday nights from midnight to closing), fares (effective 2014) range from $2.15 to $5.90, depending on distance traveled. At all other times, fares range from $1.75 to $3.60 based on distance traveled. Customers using a paper farecard must add an additional $1.00 fee for each ride. Discounted fares are available for school children, the disabled, and the elderly.[74] Metro charges reduced fares on all federal holidays.[75]

Metro farecard has a column of printed dollar amounts, a magnetic strip along the edge, and in this example a drawing of two pandas.
Front face of a Metro farecard, listing declining-balance value remaining

Passengers may purchase passes at most farecard vending machines. The passes are used the same way as farecards but grant riders unlimited travel within the system for a certain period of time. All the passes are gate-activated, with the period of validity starting with the first use of the pass, and for the paper versions, the expiration date of the pass is printed on the pass when exiting the system at the end of the first trip. Four types of passes are currently sold:[76][77]

  • A One Day Pass for $14.50, valid for one day of unlimited Metrorail travel. The pass expires at the end of the operating day. Since July 1, 2012, this pass has been available on SmarTrip as well as a paper pass. Prior to that time the cost of the pass was much less ($9 vs. $14), but it was not valid for the morning peak period on weekdays. Since June 1, 2013, this has been the only pass available on a paper card.
  • A 7-Day Short Trip Pass for $36, valid for seven consecutive days for Metrorail trips costing up to $3.60 (the maximum off-peak fare) during peak fare times and any trip during off-peak hours. (The $1 paper farecard surcharge is not applicable.) If the trip costs more than $3.60 the difference had to be paid at the Exitfare machine (for paper passes) before leaving, or is deducted from the cash balance of a SmarTrip card. A positive stored value is required to enter the Metrorail system. It became available on SmarTrip on May 20, 2013, and has not been sold as a paper pass after May 31, 2013.[78]
  • A 7-Day Fast Pass for $59.25, valid for seven consecutive days of unlimited Metrorail travel. Since April 16, 2012, users have been able to purchase the Fast Pass on a SmarTrip card.[79] The 7-Day Fast Pass has not been sold as a paper pass since September 1, 2012, and has not been accepted on a paper pass after December 31, 2012.
  • Since July 1, 2012, a 28-Day Metrorail Fast Pass available on SmarTrip only for $237. Like the version of this pass offered years ago on a thin plastic mag-stripe farecard, this is for convenience only, offering no savings over four uses of the 7-Day Fast Pass.

Users can add value to any farecard, but riders must pay an exit fare if the cost of a trip is higher than their card’s balance. Riders may transfer for free, provided they do not exit through the faregates. SmarTrip users receive a $0.50 discount on bus-to-rail and rail-to-bus transfers.[74] On October 28, 2011 Metro launched Farragut Crossing, a “virtual tunnel” between Farragut West and Farragut North stations that allows SmarTrip customers to transfer above ground for free, provided that they do so within 30 minutes.[80]

The contract for Metro's fare collection system was awarded in 1975 to Cubic Transportation Systems.[81] The current electronic fare collection started on July 1, 1977, a little more than a year after the first stations opened. Prior to electronic fare collection, exact change fareboxes were used.[82] Metro's paper farecard system is also shared by Bay Area Rapid Transit, which Cubic won a contract for in 1974.[81] In May 2014, Metro announced plans to retrofit more than 500 fare vending machines throughout the system to dispense SmarTrip cards, rather than paper fare cards, and eventually eliminate magnetic fare cards entirely.[83] The faregates are scheduled to stop accepting paper farecards in March 2016.[citation needed]

Students at District of Columbia public schools ride both Metrobus and Metrorail for free.[84]

Safety and security

Security

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Metro Transit Police cruiser

Metro planners designed the system with passenger safety and order maintenance as primary considerations. The open vaulted ceiling design of stations and the limited obstructions on platforms allow few opportunities to conceal criminal activity. Station platforms are built away from station walls to limit vandalism and provide for diffused lighting of the station from recessed lights. Metro's attempts to reduce crime, combined with how the station environments were designed with crime prevention in mind,[85] has contributed to Metro being among the safest and cleanest subway systems in the United States.[86] There are nearly 6,000 video surveillance cameras used across the system to enhance security.[87]

Metro is patrolled by its own police force, which is charged with ensuring the safety of passengers and employees. Transit Police officers patrol the Metro system and Metrobuses, and they have jurisdiction and arrest powers throughout the 1,500-square-mile (3,900 km2) Metro service area for crimes that occur on or against transit authority facilities, or within 150 feet (46 m) of a Metrobus stop. The Metro Transit Police Department is one of two U.S. police agencies that has local police authority in three "state"-level jurisdictions (Maryland, Virginia, and the District of Columbia), the U.S. Park Police being the other.[88]

Each city and county in the Metro service area has similar ordinances that regulate or prohibit vending on Metro-owned property, and which prohibit riders from eating, drinking, or smoking in Metro trains, buses, and stations; the Transit Police have a reputation for enforcing these laws rigorously. One widely publicized incident occurred in October 2000 when police arrested 12-year-old Ansche Hedgepeth for eating french fries in the Tenleytown-AU station.[89] In a 2004 opinion by John Roberts, now Chief Justice of the United States, the D.C. Circuit Court of Appeals upheld Hedgepeth's arrest.[90] By then WMATA had answered negative publicity by adopting a policy of first issuing warnings to juveniles, and arresting them only after three violations within a year.

Metro's zero-tolerance policy on food, trash and other sources of disorder embodies the "broken windows" philosophy of crime reduction. This philosophy also extends to the use of station restroom facilities. A longstanding policy, intended to curb unlawful and unwanted activity, has been to only allow employees to use Metro restrooms.[86] Station managers may make exceptions for passengers with small children, the elderly, or the disabled.[91] Metro now allows the use of restrooms by passengers who gain a station manager's permission, except during periods of heightened terror alerts.[92]

Random bag searches

On October 27, 2008, the Metro Transit Police Department announced plans to immediately begin random searches of backpacks, purses, and other bags. Transit police would search riders at random before boarding a bus or entering a station. It also explained its intent to stop anyone acting suspiciously.[93] Metro claims that the United States Court of Appeals for the Second Circuit decision in MacWade v. Kelly,[94] which upheld random searches on the New York City Subway, allows Metro Transit Police to take similar action.[95] Metro Transit Police Chief Michael Taborn stated that, if someone were to turn around and simply enter the system through another escalator or elevator, Metro has "a plan to address suspicious behavior".[96] Security expert Bruce Schneier characterized the plan as "security theater against a movie plot threat" and does not believe random bag searches actually improve security.[97]

The Metro Riders' Advisory Council recommended to WMATA’s board of directors that Metro hold at least one public meeting regarding the search program. As of December 2008, Metro had not conducted a single bag search.[98]

In 2010 Metro once again announced that it would implement random bag searches, and conducted the first such searches on December 21, 2010.[99] The searches consist of swabbing bags and packages for explosive residue, and X-raying or opening any packages which turned up positive. On the first day of searches, at least one false positive for explosives was produced, which Metro officials indicated could occur for a variety of reasons including if a passenger had recently been in contact with firearms or been to a firing range.[100] The DC Bill of Rights Coalition and the Montgomery County Civil Rights Coalition circulated a petition against random bag searches, taking the position that the practice violates the Fourth Amendment to the United States Constitution and would not improve security.[101] On January 3, 2011 Metro held a public forum for the searches at a Metro Riders' Advisory Council meeting, at which more than 50 riders spoke out, most of them in opposition to the searches. However at the meeting Metro officials called random bag inspections a "success" and claimed that few riders had complained.[102]

Safety

Accidents and incidents

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

Several collisions have occurred on Washington Metro, resulting in injuries and fatalities, along with numerous derailments with few or no injuries. WMATA has been criticized for disregarding safety warnings and advice from experts. The Tri-State Oversight Committee oversees WMATA, but has no regulatory authority. Metro's safety department is usually in charge of investigating incidents, but cannot require other Metro departments to implement its recommendations.[103]

Collisions
A badly damaged subway car sticks up at an angle where it had partially ridden over another car in an underground station.
Accident at the Woodley Park station on November 3, 2004

During the Blizzard of 1996, on January 6, a Metro operator was killed when a train failed to stop at the Shady Grove station. The four-car train overran the station platform and struck an unoccupied train that was awaiting assignment. The National Transportation Safety Board (NTSB) investigation found that the crash was a result of a failure in the train's computer-controlled braking system. The NTSB recommended that Metro grant train operators the ability to manually control the braking system, even in inclement weather, and recommended that Metro prohibit parked rail cars on tracks used by incoming outbound trains.[104]

On November 3, 2004, an out-of-service Red Line train rolled backwards into the Woodley Park station, hitting an in-service train stopped at the platform. The rear car (1077) was telescoped by the first car of the standing train (4018). No one was killed, but 20 people were injured.[105] A 14-month investigation concluded that the train operator was most likely not alert as the train rolled backwards into the station. Safety officials estimated that had the train been full, at least 79 people would have died. The train operator was dismissed and Metro officials agreed to add rollback protection to more than 300 rail cars.[106]

June 22, 2009 accident, in which nine people were killed.

On June 22, 2009 at 5:02 pm, two trains on the Red Line collided. A southbound train heading toward Shady Grove stopped on the track short of the Fort Totten station, and another southbound train collided with its rear. The front car of the moving train (1079) was telescoped by the rear car of the standing train (5066),[107] and passengers were trapped. Nine people died and more than 70 were injured, dozens of whom were described as "walking wounded".[108] Red Line service was suspended between the Fort Totten and Takoma stations, and New Hampshire Avenue was closed.[109][110] One of the dead was the operator of the train that collided with the stopped train.

On November 29, 2009, at 4:27 am, two trains collided at the West Falls Church train yard. One train pulled in and collided into the back of the other train. No customers were aboard, and only minor injuries to the operators and cleaning staff were reported. However, three cars (1106, 1171, and 3216) were believed to be damaged beyond repair.[111]

Derailments
The crushed end of a subway car.
Green Line train following the January 7, 2007 derailment

On January 13, 1982, a train derailed at a malfunctioning crossover switch south of the Federal Triangle station. In attempting to restore the train to the rails, supervisors failed to notice that another car had also derailed. The other rail car slid off the track and hit a tunnel support, killing three people and injuring 25. Coincidentally, this accident occurred about 30 minutes after Air Florida Flight 90 crashed into the nearby 14th Street Bridge during a major snowstorm.[13]

On January 20, 2003, during construction of a new canopy at the National Airport station, Metro began running trains through the center track even though it had not been constructed for standard operations, and a Blue Line train derailed at the switch. No injuries resulted, but the accident delayed construction by a number of weeks.[112]

On January 7, 2007, a Green Line train carrying approximately 120 people derailed near the Mount Vernon Square station in downtown Washington. Trains were single-tracking at the time, and the derailment of the fifth car occurred where the train was switching from the south to northbound track. The accident injured at least 18 people and prompted the rescue of 60 people from a tunnel.[113] At least one person had a serious but non-life-threatening injury.[114]

The Mount Vernon Square accident was one of a series of five derailments involving 5000-Series cars, with four of those occurring on side tracks and not involving passengers.[114]

On June 9, 2008, an Orange Line train (2000-series) derailed between the Rosslyn and Court House stations.[115][116]

On February 12, 2010, a Red Line train derailed at about 10:13 am as it left the Farragut North station in downtown Washington. After leaving the station, the train entered the pocket track north of the station. As it continued, an automatic derailer at the end of the pocket track intentionally derailed the train as a safety measure. If the train had continued moving forward on the pocket track, it would have entered the path of an oncoming train. The wheels of the first two cars in the six-car, White-Flint-bound train were forced off the tracks, stopping the train. Almost all of the estimated 345 passengers were evacuated from the damaged train by 11:50 am and the NTSB arrived on the accident scene by noon. Two minor injuries were reported, and a third passenger was taken to George Washington University Hospital.[117] The NTSB ruled the accident was due to the train operator's failure to follow standard procedures, and WMATA management for failure to provide proper supervision of the train operator which resulted in the incomplete configuration of the train identification and destination codes leading to the routing of the train into the pocket track.[118]

On April 24, 2012, around 7:15 pm, a Blue Line train bound for Franconia–Springfield derailed near Rosslyn. No injuries were reported.[119]

On July 6, 2012, around 4:45 pm, a Green Line train bound for downtown Washington, DC and Branch Avenue derailed near West Hyattsville. No injuries were reported. A heat kink, due to the hot weather, was identified as the probable cause of the accident.[120]

Smoke incident

On January 12, 2015, during early evening rush, a Yellow Line train stopped in the tunnel and filled with smoke just after departing L'Enfant Plaza for Pentagon due to "an electrical arcing event" ahead in the tunnel. Everyone on board was evacuated; 84 people were taken to hospitals and one person died.[121]

Safety measures

On July 13, 2009, WMATA adopted a "zero tolerance" policy for train or bus operators found to be texting or using other hand-held devices while on the job. This new and stricter policy came after investigations of several mass-transit accidents in the U.S. found that operators were texting at the time of the accident. The policy change was announced the day after a passenger of a Metro train videotaped the operator texting while operating the train.[122]

Future expansion

WMATA expects an average of one million riders daily by 2030. The need to increase capacity has renewed plans to add 220 cars to the system and reroute trains to alleviate congestion at the busiest stations.[123] Population growth in the region has also revived efforts to extend service, build new stations, and construct additional lines.

Silver Line

New Tysons Corner Metro Station under construction next to Virginia State Route 123.

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

The most prominent expansion is the Dulles Corridor Metrorail Project, dubbed the Silver Line, a 23-mile (37 km) extension from the Orange Line into Loudoun County, Virginia, by way of Tysons Corner and Washington Dulles International Airport. Rail to Dulles has been discussed since the system opened in 1976. The current Silver Line project was formally proposed in 2002 and initially approved by the Federal Transit Administration in 2004.[124] After several delays, federal funding for Phase 1 was secured in December 2008[125] and construction began in March 2009.[126] The line will be constructed in two phases; the first phase to Wiehle – Reston East in Reston, Virginia opened July 26, 2014,[127] and the second phase to Virginia Route 772, beyond Dulles Airport, is projected for completion in 2019 or 2020.[128]

Blue Line realignment

Blue Line trains share a single tunnel with Orange Line and Silver Line trains to cross the Potomac River. The current tunnel limits service in each direction, creating a choke point. A 2001 proposal would have rerouted the Blue Line between the Rosslyn and Stadium–Armory stations by building a bridge or tunnel from Virginia to a new station in Georgetown.[129] The proposal was later rejected due to cost,[130] but Metro again started considering a similar scenario in 2011.[131]

Orange Line extension

The Virginia Department of Transportation (VDOT) announced on Jan 18, 2008 that it and the Virginia Department of Rail and Public Transportation (VDPRT) had begun work on a draft environmental impact statement (EIS) for the I-66 corridor in Fairfax and Prince William counties. According to VDOT the EIS, officially named the I-66 Multimodal Transportation and Environment Study, would focus on improving mobility along I-66 from the Capital Beltway (I-495) interchange in Fairfax County to the interchange with U.S. Route 15 in Prince William County. The EIS also allegedly includes a four station extension of the Orange Line past Vienna. The extension would continue to run in the I-66 median and would have stations at Chain Bridge Road, Fair Oaks, Stringfellow Road and Centreville near Virginia Route 28 and U.S. Route 29.[132] In its final report published June 8, 2012, the study and analysis revealed that an "extension would have a minimal impact on Metrorail ridership and volumes on study area roadways inside the Beltway and would therefore not relieve congestion in the study corridor."[133]

Fort Belvoir and Fort Meade extensions

In 2005, the Defense Department announced that it would be shifting 18,000 jobs to Fort Belvoir in Virginia and at least 5,000 jobs to Fort Meade in Maryland by 2012, as part of that year's Base Realignment and Closure plan. In anticipation of such a move, local officials and the military proposed extending the Blue and Green Lines to service each base. The proposed extension of the Green Line could cost $100 million per mile ($60 million per kilometer), and a light rail extension to Fort Belvoir was estimated to cost up to $800 million. Neither proposal has established timelines for planning or construction.[134][135]

Potomac Yard station

In 2008, officials began to explore the possibility of adding an infill station called Potomac Yard in the Potomac Yard area of Alexandria, on the Blue and Yellow Lines between the National Airport and Braddock Road stations. In 2010, the Alexandria City Council approved a portion of the proposed $240 million construction of the station. If the council approves the final budget, construction would start in 2017 and the station would be scheduled to open in late 2018 or early 2019.[136]

Other new rail lines

In 2011, Metro began studying the needs of the system through 2040.[131] New Metro rail lines and extensions under consideration as part of this long term plan include: a new line which parallels the Capital Beltway; a new line from the Friendship Heights Metro station to White Oak, Maryland, which would pass through the District and Silver Spring; an extension of the Green Line to National Harbor in Maryland; and re-routing the Blue Line in the District between the Orange Line and Green Line. None of these lines are yet funded for planning or construction.[131]

Related non-WMATA projects

A scaled map illustrating the Purple Line route and its intersections with existing subway lines.
Proposed route of the Purple Line

A number of light rail and urban streetcar projects have been proposed to extend or supplement service provided by Metro. Like the Silver Line in Virginia, the proposed Purple Line has been in planning since the 1980s.[137] The project was originally envisioned as a circular heavy rail line connecting the outer stations on each branch of the Metrorail system, in a pattern roughly mirroring the Capital Beltway.[138] The current proposal would create a light rail system in Maryland between the Bethesda and New Carrollton stations by way of Silver Spring and College Park. Such a plan would connect both branches of the Red Line to the Green and Orange Lines, and would decrease the travel time between suburban Metro stations.[137][139]

The Corridor Cities Transitway (CCT) is a proposed 15 miles (24 km) bus rapid transit line that would link Clarksburg, Maryland in northern Montgomery County with the Shady Grove station on the Red Line.[140] Assuming that the anticipated federal, state, and local government funds are provided, construction of the first 9 miles (14 km) of the system would begin in 2018.[141] In 2005, a Maryland lawmaker proposed a light rail system to connect areas of Southern Maryland, especially the rapidly growing area around the town of Waldorf, to the Branch Avenue station on the Green Line. The project is still in the planning stages.[142]

The District of Columbia Department of Transportation is building the new DC Streetcar system to improve transit connectivity within the District. A tram line to connect Bolling Air Force Base to the Anacostia station and was originally expected to open in 2010. Streetcar routes have been proposed in the Atlas District, Capitol Hill, and the K Street corridor.[143] While streetcars were originally expected to begin service in 2011, only the Atlas District route, known as the H/Benning Street route, is under construction and has experienced several delays and as of June 2015 has not opened.[144][145]

See also

References

  1. 1.0 1.1 http://www.wmata.com/pdfs/planning/2015_historical_rail_ridership.pdf
  2. 2.0 2.1 2.2 2.3 2.4 2.5 2.6 Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.Google Books search/preview
  6. Washington Metropolitan Area Transit Authority, Frequently Asked Questions, accessed July 2009: "What do I need to know to build near Metro property? Metro reviews designs and monitors construction of projects adjacent to Metrorail and Metrobus property..."
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. 10.0 10.1 Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. 13.0 13.1 13.2 Lua error in package.lua at line 80: module 'strict' not found.
  14. 14.0 14.1 Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Luz Lazo, "Riders: Let there be light"; Express (Washington, D.C.), Dec 3, 2012, p. 12.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. Dana Hedgpeth, "After more than 30 years, Metro map is being redesigned by creator Lance Wyman", The Washington Post, June 4, 2011.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. Mullins, Luke, "The Infuriating History of How Metro Got So Bad", The Washingtonian, 9 December 2015
  40. WMATA (2014-05-22). "FY2015 Approved Budget Effective July 1, 2014.". Percentage calculated from figures in Table 2.1, p. II-14; and Table 3.3, p. III-3. $696 mil./$1022.6 mil = 66%.
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. Lua error in package.lua at line 80: module 'strict' not found.
  43. Lua error in package.lua at line 80: module 'strict' not found.
  44. 44.0 44.1 Lua error in package.lua at line 80: module 'strict' not found.
  45. 45.0 45.1 Lua error in package.lua at line 80: module 'strict' not found.
  46. Lua error in package.lua at line 80: module 'strict' not found.
  47. 47.0 47.1 Lua error in package.lua at line 80: module 'strict' not found.
  48. Lua error in package.lua at line 80: module 'strict' not found.
  49. Lua error in package.lua at line 80: module 'strict' not found.
  50. Lua error in package.lua at line 80: module 'strict' not found.
  51. Lua error in package.lua at line 80: module 'strict' not found.
  52. Lua error in package.lua at line 80: module 'strict' not found.
  53. Lua error in package.lua at line 80: module 'strict' not found.
  54. Lua error in package.lua at line 80: module 'strict' not found.
  55. Lua error in package.lua at line 80: module 'strict' not found.
  56. Lua error in package.lua at line 80: module 'strict' not found.
  57. Lua error in package.lua at line 80: module 'strict' not found.
  58. Lua error in package.lua at line 80: module 'strict' not found.
  59. Lua error in package.lua at line 80: module 'strict' not found.
  60. Customer Services, Operations, and Safety Committee, "Manual vs. Automatic Operation and Operational Restrictions," Information Item IV-B, Washington Metropolitan Area Transit Authority Board, March 11, 2010.
  61. Lua error in package.lua at line 80: module 'strict' not found.
  62. Lua error in package.lua at line 80: module 'strict' not found.
  63. Michael Perkins, "Metro Headway Policy Needs Clarity," Greater Greater Washington, August 23, 2012.
  64. Luke Roziak, "Metro Eyes 12 AM Weekend Closing," Washington Post, February 11, 2011.
  65. J. Freedom DuLac et al., "Metro's proposal to end late-night weekend trains rankles Washington's party crowd" Washington Post, February 13, 2011.
  66. Lua error in package.lua at line 80: module 'strict' not found.
  67. Lua error in package.lua at line 80: module 'strict' not found.
  68. WMATA (March 26, 2004). "Metro offers enhancements for the passenger information display monitors." News release.
  69. WMATA. "Mobile Services." Accessed November 19, 2012.
  70. WMATA (August 6, 2010). "Metro invites software developers to discuss new transit data feed." News release.
  71. WMATA. "Developer Resources." Accessed November 19, 2012.
  72. WMATA (August 31, 2010). "Real-time next train arrival information now available by phone." News release.
  73. Lua error in package.lua at line 80: module 'strict' not found.
  74. 74.0 74.1 Lua error in package.lua at line 80: module 'strict' not found.
  75. Lua error in package.lua at line 80: module 'strict' not found.
  76. Lua error in package.lua at line 80: module 'strict' not found.
  77. Lua error in package.lua at line 80: module 'strict' not found.
  78. Lua error in package.lua at line 80: module 'strict' not found.
  79. Lua error in package.lua at line 80: module 'strict' not found.
  80. Lua error in package.lua at line 80: module 'strict' not found.
  81. 81.0 81.1 http://cts.cubic.com/Portals/CTS/Collection-Point/18/files/assets/basic-html/page18.html
  82. http://www.wmata.com/about_metro/docs/history.pdf
  83. Lua error in package.lua at line 80: module 'strict' not found.
  84. Lua error in package.lua at line 80: module 'strict' not found.
  85. Lua error in package.lua at line 80: module 'strict' not found.
  86. 86.0 86.1 Lua error in package.lua at line 80: module 'strict' not found.
  87. Lua error in package.lua at line 80: module 'strict' not found.
  88. Lua error in package.lua at line 80: module 'strict' not found.
  89. Lua error in package.lua at line 80: module 'strict' not found.
  90. Hedgepeth v. Washington Metropolitan Area Transit Authority, 386 F.3d 1148 (D.C. Cir. 2004) (Argued September 17, 2004 decided October 26, 2004)
  91. Lua error in package.lua at line 80: module 'strict' not found.
  92. Lua error in package.lua at line 80: module 'strict' not found.
  93. Lua error in package.lua at line 80: module 'strict' not found.
  94. Appeals court decision: Lua error in package.lua at line 80: module 'strict' not found. Original complaint: Lua error in package.lua at line 80: module 'strict' not found.
  95. Lua error in package.lua at line 80: module 'strict' not found.
  96. Lua error in package.lua at line 80: module 'strict' not found.
  97. Lua error in package.lua at line 80: module 'strict' not found.
  98. Lua error in package.lua at line 80: module 'strict' not found.
  99. Lua error in package.lua at line 80: module 'strict' not found.
  100. Lua error in package.lua at line 80: module 'strict' not found.
  101. Lua error in package.lua at line 80: module 'strict' not found.
  102. Lua error in package.lua at line 80: module 'strict' not found.
  103. Lua error in package.lua at line 80: module 'strict' not found.
  104. Lua error in package.lua at line 80: module 'strict' not found.
  105. Lua error in package.lua at line 80: module 'strict' not found.
  106. Lua error in package.lua at line 80: module 'strict' not found.
  107. Lua error in package.lua at line 80: module 'strict' not found.
  108. Lua error in package.lua at line 80: module 'strict' not found.
  109. Lua error in package.lua at line 80: module 'strict' not found.
  110. Lua error in package.lua at line 80: module 'strict' not found.
  111. Lua error in package.lua at line 80: module 'strict' not found.
  112. Lua error in package.lua at line 80: module 'strict' not found.
  113. Lua error in package.lua at line 80: module 'strict' not found.
  114. 114.0 114.1 Lua error in package.lua at line 80: module 'strict' not found.
  115. Lua error in package.lua at line 80: module 'strict' not found.
  116. Lua error in package.lua at line 80: module 'strict' not found.
  117. Lua error in package.lua at line 80: module 'strict' not found.
  118. Lua error in package.lua at line 80: module 'strict' not found.
  119. Lua error in package.lua at line 80: module 'strict' not found.
  120. Lua error in package.lua at line 80: module 'strict' not found.
  121. http://edition.cnn.com/2015/01/12/politics/smoke-lenfant-plaza/
  122. Lua error in package.lua at line 80: module 'strict' not found.
  123. Lua error in package.lua at line 80: module 'strict' not found.
  124. Lua error in package.lua at line 80: module 'strict' not found.
  125. Lua error in package.lua at line 80: module 'strict' not found.
  126. Lua error in package.lua at line 80: module 'strict' not found.
  127. http://www.wmata.com/about_metro/news/PressReleaseDetail.cfm?ReleaseID=5731
  128. Lua error in package.lua at line 80: module 'strict' not found.
  129. Lua error in package.lua at line 80: module 'strict' not found.
  130. Lua error in package.lua at line 80: module 'strict' not found.
  131. 131.0 131.1 131.2 Lua error in package.lua at line 80: module 'strict' not found.
  132. Lua error in package.lua at line 80: module 'strict' not found.
  133. http://virginiadot.org/projects/resources/NorthernVirginia/I-66_Multimodal_-_Final_Report.pdf
  134. Lua error in package.lua at line 80: module 'strict' not found.
  135. Lua error in package.lua at line 80: module 'strict' not found.
  136. Lua error in package.lua at line 80: module 'strict' not found.
  137. 137.0 137.1 Lua error in package.lua at line 80: module 'strict' not found.
  138. Lua error in package.lua at line 80: module 'strict' not found.
  139. Lua error in package.lua at line 80: module 'strict' not found.
  140. Montgomery County Planning Department, Silver Spring, MD. "Corridor Cities Transitway." Accessed October 15, 2013.
  141. Maryland Transit Administration. "Corridor Cities Transitway: Schedule." Accessed October 15, 2013.
  142. Lua error in package.lua at line 80: module 'strict' not found.
  143. Lua error in package.lua at line 80: module 'strict' not found.
  144. Lua error in package.lua at line 80: module 'strict' not found.
  145. Lua error in package.lua at line 80: module 'strict' not found.

External links

Official websites

Transit enthusiast sites

Maps

Equipment

  • Lua error in package.lua at line 80: module 'strict' not found.
  • Lua error in package.lua at line 80: module 'strict' not found.

Other websites