| October, 1998 |
TEA-21 enacted; establishes Maglev Deployment
Program |
| |
|
| February, 1999 |
Application submitted to Federal Railroad
Administration (FRA) for Baltimore-Washington project |
| |
|
| May, 1999 |
U.S. Department of Transportation Secretary
Rodney Slater announces selection of seven project corridors
to receive funds for pre-construction planning such as
engineering feasibility and environmental studies. |
| |
|
| July, 1999 |
Maryland Transit Administration (MTA), in
cooperation with Washington, D.C., Baltimore City and
Baltimore County, begins environmental assessment and
project description of Baltimore-Washington corridor project. |
| |
|
| October, 1999 |
Public information meetings held in Baltimore
City, Washington, D.C., and Anne Arundel County. |
| |
|
| October, 1999 – February, 2000 |
Ongoing study evaluating analysis, alignments
and environmental impacts. |
| |
|
| February, 2000 |
Environmental assessment submitted to Federal
Railroad Administration (FRA) on February 29, 2000. |
| |
|
| April, 2000 |
Public information meetings held in Baltimore
City, Washington, D.C., and Prince George’s County. |
| |
|
| June, 2000 |
FRA completed Draft Programmatic Environmental
Impact Statement (PEIS) of seven corridor projects. |
| |
|
| June, 2000 |
Project Description submitted to FRA |
| |
|
| August, 2000 |
FRA and MTA hosted a public information
meeting for the Draft Programmatic EIS in Baltimore. |
| |
|
| January, 2001 |
U.S. Department of Transportation Secretary
Rodney Slater announces Baltimore-Washington corridor
project is one of two project corridors to be considered
for further funding study. |
| |
|
| July, 2001 |
MTA initiates Draft EIS and Preliminary
Engineering work |
| |
|
| Fall 2001 |
Industry roundtables to encourage formation
of private sector teams to design, build, operate, maintain
the system, furnish technology components and develop
stations. Study group to consider ownership legislation. |
| |
|
| March, 2002 |
MTA holds public workshops on three alternative
alignments |
| |
|
| Spring, 2002 |
General Assembly considers legislation to
establish task force to recommend entity to develop, own
and operate project |
| |
|
| October, 2002 – February, 2003 |
Task Force meets; makes recommendations
to Governor, General Assembly |
| |
|
| October, 2002 |
Alternatives Analysis portion of EIS complete;
MTA holds community meetings to review detailed findings
regarding impacts |
| |
|
| September, 2003 |
Draft EIS completed; submitted to FRA |
| |
|
| December 2003 |
FRA holds public hearings on DEIS; single
“preferred” alignment selected |
| |
|
| October, 2003 – March, 2004 |
TEA-21 Reauthorization (project must be
reauthorized to continue to receive federal funds) Federal
Funds secured. |
| |
|
| Summer, 2004 |
Final EIS completed; final hearing held. |
| |
|
| Fall, 2004 |
Record of Decision (ROD) issued. |
| |
|
| Winter, 2004 |
Maryland General Assembly approval of the design, construction
and funding. New legislation to establish entity to develop,
own and operate project |
| |
|
| 2004 - 2005 |
Actions to place local project funding in Consolidated
Transportation Program and Metropolitan Transportation
Improvement Program |
| |
|
| 2004 - 2005 |
Prepare Bid Documents, geotechnical investigations,
plans to 30% completion |
| |
|
| 2005 |
Non-Federal budget appropriations |
| |
|
| 2005 |
Project revenue bonds secured |
| |
|
| 2005 - 2006 |
Procurement of a Design/Build team
Design preparation and Right-of-way acquisition |
| |
|
| 2006 - 2009 |
Construction of guideway, facilities and stations |
| |
|
| 2009 - 2010 |
Safety testing and certification |
| |
|
| 2010, 2011 |
Revenue service begins |
| |
|
| Note: All future dates assume preceding
steps completed on schedule. |
