Maryland Route 200

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

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

Toll plate yellow.svg
MD Route 200.svg

Maryland Route 200
Intercounty Connector
Route information
Maintained by MdTA
Length: 17.468 mi[1] (28.112 km)
Existed: February 23, 2011 – present
Major junctions
West end: I-370 in Gaithersburg
  <templatestyles src="Plainlist/styles.css"/>
East end: US 1 in Laurel
Location
Counties: Montgomery, Prince George's
Highway system
MD 198 MD 201

Maryland Route 200 (MD 200), more commonly known as the Intercounty Connector or ICC, is a tolled freeway in Maryland which connects Gaithersburg in Montgomery County and Laurel in Prince George's County. The highway was originally proposed in the 1960s as part of the Washington Outer Beltway. While other parts of the Outer Beltway were canceled, the ICC and the Fairfax County Parkway remained on master plans. The road's long history as an unbuilt proposed road stems from the controversy that has surrounded it over the years, including the cost which exceeded $2.56 billion.

Proponents of the highway claimed that it would improve the flow of interregional traffic, relieve traffic congestion on local roads, spur economic development, and enhance access to Baltimore-Washington International Airport.[2] Opponents of the highway claimed that the road would instead harm significant traffic flow characteristics, negatively harm the environment, and disrupt established communities through which it passes.[3]

Fulfilling a 2002 campaign promise, Maryland Governor Robert Ehrlich pushed to begin construction of the road and conducted a formal groundbreaking in October 2006.[4] With additional support from his successor, Governor Martin O'Malley,[5] construction began on November 13, 2007.[6] The first segment, from I-370 to Maryland Route 28, opened on February 23, 2011, while the extension to Interstate 95 opened on November 22, 2011. The final segment to US 1 opened on November 7, 2014.

Route description

Route Marker for ICC
ICC westbound near mile marker 4.2
Sign indicating that MD 200 ended at MD 28 (Norbeck Road)—since November 22, 2011 this is no longer the case
MD 200 exit 9 sign—this interchange was renumbered exit 8 on November 22, 2011

MD 200 begins at a trumpet interchange with Interstate 370 (I-370) near Gaithersburg in Montgomery County, between its MD 355 and Shady Grove Road interchanges as a six-lane freeway. Several new ramps and collector-distributor roads were built between this interchange and MD 355. MD 200 continues northeast from there through Redland Station, turning east to pass over Shady Grove Road, and then under Redland Road, paralleling Mill Creek. This is the location of the eastbound toll gantry. MD 200 shortly curves to the east on the approach to the six-lane overpass for Olde Mill Run, which was built wide enough for a fourth lane in the eastbound direction. The Olde Mill Run overpass is the only section of MD 200 with full 12-foot (3.7 m) shoulders on each side. After the overpass, MD 200 turns southeast, passing under Needwood Road, before turning sharply back to the east as it passes under MD 115 (Muncaster Mill Road). The route, now running slightly to the southeast begins the approach to MD 97 (Georgia Avenue).

MD 200 turns more eastward, running towards North Branch Stream Valley Park, and passing over the north branch of Rock Creek and a second stream over a bridge. This is the location of the westbound toll gantry. The route enters the Norbeck area, and passes under Emory Lane. Just east of there is where a hybrid cloverleaf interchange with MD 97 (Georgia Avenue) is located. A park-and-ride may be built at this interchange. When the road opened in February 2011, it temporarily came to an end at a traffic light located just east of MD 97 at MD 28 (Norbeck Road).[7]

The route then curves southeastward, passing under MD 28 and Longmead Crossing Drive, running parallel to Wintergate Drive/Park Vista Drive. MD 200 then curves slightly more eastward toward Aspen Hill, where the freeway intersects MD 182 (Layhill Road), shortly after entering the Northwest Branch Recreational Park. The route travels though the park for a stretch, bridging the Northwest Branch three times (the second bridge also carries MD 200 over Bonifant Road), exits the park, and then turns eastward, passing under Notley Road. MD 200 then turns slightly to the northeast near Colesville and meets MD 650 at a single-point urban interchange.

MD 200 then continues eastward, passes through Upper Paint Branch Park and bridges several creeks, including the namesake Paint Branch, and passes between several neighborhoods upon exiting the park. The route then passes under Old Columbia Pike with no access to this local road.[8] Just beyond, MD 200 reaches a large interchange with US 29, combining cloverleaf and stack elements. This interchange also adds connections to Fairland Road with both MD 200 and US 29. The route continues eastward, featuring a partial interchange with Briggs Chaney Road (westbound exit and eastbound entrance), and then, just after crossing the border into Prince George's County, it passes over the Little Paint Branch just south of the Fairland Recreational Park. The route then passes under Old Gunpowder Road.

The route then enters Calverton, where the expansive interchange with I-95 is located. The interchange, marked as Exit 31 on I-95, is mostly a cloverleaf hybrid, and features several collector-distributor roads built along I-95, stretching from Old Gunpowder Road south of the interchange to MD 198 north of it. The community of Konterra is planned for construction near this interchange.

Beyond I-95, MD 200 narrows to four lanes.[9] MD 200 curves sharply, first to the south then to the east, and meets a diamond-interchange providing access to Konterra Drive. MD 200 then turns gradually to the southeast and ends at a traffic-signal at US 1 (Baltimore Avenue) in Beltsville.

MD 200 is a part of the main National Highway System for its entire length.[1][10]

Tolls

The Intercounty Connector uses all-electronic tolling, with tolls payable through E-ZPass or billed using Automatic Number Plate Recognition. ICC users without E-ZPass are mailed a bill to pay the toll along with a 50% surcharge for non-E-ZPass use (minimum of $1).[11] The tolls along the full length of the road (between I-370 and I-95) vary by time of day, ranging from $1.60 overnight to $3.20 in off-peak daytime, and $4 at rush hour (for E-ZPass users; for others toll rates will be approximately 50% higher).[12] Tolls were waived along the road between February 23 and March 7, 2011, and again between November 22 and December 4, 2011.

History

Washington Outer Beltway

The Intercounty Connector can be traced to plans developed in the 1950s for a 122-mile (196 km) Outer Beltway.[13] The National Capital Park and Planning Commission issued a Comprehensive Plan for the Nation's Capital and Its Environs in 1950. The comprehensive plan included three different circular roads in and around the District of Columbia. The original Outer Beltway had been planned to pass south of the corporate limits of the City of Rockville, as shown on a map published in the Washington Post in 1951 with the caption "Ring Road suggested by Bureau of Public Roads".[14] In 1953, the portion of the Outer Beltway between Montgomery County and Prince George's County was included in the Master Plan of Highways of the Maryland–National Capital Park and Planning Commission. It was later included in the Commission's General Plan in 1957, and the Commission's On Wedges and Corridors plan in 1964.[13]

In the 1960s, an "outer circumferential highway" was proposed between 5 and 10 miles (8.0 and 16.1 km) outside the Capital Beltway.[13] The original proposed routing of the Intercounty Connector was south and east of the current alignment.[15] The new route was motivated in part by a desire to move the routing of the proposed bridge over the Potomac River upstream from the area of River Bend to Watkins Island.[16] Virginia residents and the United States Department of the Interior objected to the proposed bridge over the Potomac River because they wanted to create state and federal parks along the river in order to protect sugar maple trees, vegetation, and bald eagles. Because of these concerns, the Maryland State Roads Commission moved the proposed Outer Beltway to a route north of Rockville and eliminated a new bridge crossing the Potomac River. The Montgomery County Planning Board accepted the state's newly proposed route in 1970, but the Montgomery County Council rejected it, and Prince George's County and Virginia dropped it from their plans.[13]

In 1975, the National Capital Region Transportation Planning Board of the Metropolitan Washington Council of Governments endorsed a request from the State Highway Administration "for federal support of a $1.1 million planning and engineering study of the first 8-mile [13 km] segment of the road" (then called the Outer Beltway),[13] which was to "run from the Baltimore-Washington Parkway near Beltsville westward to a point near Interstate Rte 70S at Gaithersburg."[17] By 1976, Maryland's Secretary of Transportation no longer supported state financial support of the Outer Beltway, although Montgomery County still supported it in concept.[13]

Initial Intercounty Connector plan

In 1980, the state of Maryland dropped the Outer Beltway from its plans, with the exception of the Intercounty Connector.[18] Meanwhile, the State Highway Administration was studying constructing a 22-mile (35 km) Intercounty Connector with a 10-mile (16 km) spur called the Rockville Facility.[13]

After six days of public workshops, the Maryland State Highway Administration released its first report about the Intercounty Connector and the Rockville Facility in January 1980. The majority of participants supported the highway, although almost everyone said they would prefer building more east-west public transportation instead.[13]

In 1983, the federal National Capital Planning Commission formally requested that the eastern end of the Intercounty Connector be shortened by four miles (6.4 km), so that the eastern terminus of the road would be at I-95 rather than the Baltimore–Washington Parkway.[19] In 1984, Maryland Secretary of Transportation Lowell K. Bridwell designated land in Montgomery and Prince George's counties as the future site of the Intercounty Connector so that the right-of-way would be preserved,[20] even though Montgomery County Executive Charles W. Gilchrist had voiced very critical comments about the Intercounty Connector as it was envisioned in 1983—at least in part because he felt that construction of the ICC by the year 2000 was "infeasible", and advocated construction of a "shorter and less-costly" east–west highway instead.[21]

Prior to Governor Parris N. Glendening declaring the Intercounty Connector "dead" before leaving office in January 2003, two environmental impact studies had been conducted. In 1977, the Patuxent Wildlife Research Center expressed concerns about the impact that the ICC would have on its experiments.[22] An initial environmental study was undertaken in the late 1970s, and extended into the 1980s. A second study was initiated around 1992, and a draft environmental impact statement was issued in 1997. The final environmental impact statement was drafted by 1989 but did not receive federal approval, leading to the abandonment of the study until a new study began in 1992; the 1992–1997 study pointed to a similar conclusion, though it was never completed. By 1997, millions of dollars had been spent on planning and preliminary engineering, but the only segments of the road that had been built were I-370 between I-270 and the Shady Grove Metrorail station on WMATA's Red Line.[23]

Glendening rejects Transportation Solutions Group recommendations

After the 1997 Intercounty Connector Draft Environmental Impact Statement process was put on hold by Governor Glendening, much controversy resulted between groups and persons in favor of the ICC and those opposed.[24] The Intercounty Counnector became a political issue in 1998,[25] an election year in Maryland. A blue-ribbon committee entitled the Transportation Solutions Group was formed in 1998 to tell the Governor's Smart Growth Sub-Cabinet about intermodal transportation that complied with state and regional goals.[26] The Transportation Solutions Group, chaired by Thomas B. Deen, former executive director of the Transportation Research Board, met at a series of meetings over about 14 months in 1998 and 1999.[27] Policy suggestions and recommendations made by the Transportation Solutions Group included that most of the group supports "providing high-speed bus transit, HOV and SOV access through a new east-west, value priced, limited-access parkway", with some opposition to the parkway[28] and that the group had a divided opinion on a freeway, with most supporting it.[29] The Transportation Solutions Group had initially voted to oppose the Intercounty Connector on its master planned route,[30] but voted 10 in favor and 4 opposed in February 1999 to endorse a highway alternative with the condition that single-occupant vehicles be charged a toll.[31] At its final meeting in June 1999, the Transportation Solutions Group held a public hearing in College Park and voted 12 to 4 in favor of a "parkway-like highway from I-270 to I-95, following the general path of the ICC."[32]

The Transportation Solutions Group also made a recommendation that a system of high-occupancy toll lanes (with variable pricing) be implemented on major freeways of the region, including the Intercounty Connector, I-95, the Capital Beltway, I-270 and US 50.[33]

On September 22, 1999, Glendening chose to reject the Transportation Solutions Group recommendation, asserting that the project was "wrong", "inconsistent with Smart Growth doctrine",[34] and an "environmental disaster".[13] The Washington Post quoted Glendening quoted as saying, "It is a proposal that has fractured our communities. It has pitted neighbor against neighbor. And it has created political gridlock while traffic gridlock has only worsened."[35]

Even though Glendening chose to ignore the Transportation Solutions Group's primary recommendation, its work was not entirely in vain, as its efforts were to be cited prominently some years later in the Intercounty Connector's Final Environmental Impact Statement .[36] The concept of a regionwide network of HOT lanes (to be called "variably priced highway lanes") was further developed by the the Transportation Planning Board, and a regional network (including the Intercounty Connector) was described in a report published in February 2008.[37]

After rejecting the Intercounty Connector, Glendening and opponents of the Intercounty Connector then examined the possibility of selling its right-of-way, but proponents of the Intercounty Connector would have been able to stop such a sale at the Board of Public Works,[38] which must approve transactions involving the sale of state-owned real estate.

Montgomery County steps in

In 1999, staff to the Montgomery County Planning Board said that the Intercounty Connector could be removed from master plans, but that such an effort would take "six or seven years" to accomplish.[39] In November 1999, the Montgomery County Council discussed removing the Intercounty Connector from master plans, and while five of the nine members were opposed to the Intercounty Connector, the District 4 member, Marilyn Praisner, declined to agree to removal of the master-planned route, for fear that the so-called Northern Alignment (Corridor 2 in the 2005 Draft Environmental Impact Statement) would become a de facto Intercounty Connector in the future.[40] The effort by Montgomery County politicians to remove the Intercounty Connector from its plans irritated powerful members of the Maryland General Assembly (notably Senate President Thomas V. "Mike" Miller), who discussed legislative measures that could be taken in the General Assembly to thwart such a move.[41][42] In February 2000, an agreement between Montgomery County's politicians and members of the General Assembly reached an agreement "memorialized in two letters but not cast in stone" that the "... Council agreed not to take any action to kill the ICC during the next three years."[43]

In 2000, Montgomery County Planning Board established the Transportation Policy Report and then the more-inclusive Transportation Policy Report II Task Force "... in an effort to establish a framework for future Master Plans and to help set priorities for future infrastructure."[44] The Transportation Policy Report II Task Force had 33 members, including persons in favor of the Intercounty Connector and those opposed.[45] The Transportation Policy Report II Task Force listed the Intercounty Connector in its recommended network, following a caveat that "If they are found feasible and ultimately judged desirable to implement, the priority of implementation could be established at that time.[46] When the Montgomery County Council was briefed on the report, discussions quickly shifted to the Intercounty Connector and the controversy associated with it.[47] The Intercounty Connector's Final Environmental Impact Statement makes specific reference to the work done by the Transportation Policy Report II Task Force.[48]

The Maryland State Senate, in its 2002 session, passed Senate Joint Resolution 8, which asked Glendening to restart the Intercounty Connector Environmental Impact Statement that had been put on hold in 1997. The Maryland House of Delegates passed an accompanying resolution, House Joint Resolution 10 with essentially similar provisions. The Intercounty Connector study was not to be restarted until Glendening left office at the end of 2002.

Revival

Logo used for the Intercounty Connector for public relations

In 2003, Governor Ehrlich followed through with his campaign promise to resurrect the Intercounty Connector study,[49] and he was allowed a fast-track review process by the United States Secretary of Transportation, Norman Mineta. In addition to the election of Ehrlich, the Montgomery County Council that was seated at the end of 2002 had a 6-3 majority of members in favor of the project. Prior to the 2002 election, a majority had been skeptical, if not outright opposed, to the project.[50] The Montgomery County Council and County Executive Douglas M. Duncan issued a resolution endorsing the Intercounty Connector in December 2002.[13]

On April 21, 2004, the Transportation Planning Board voted to include the Intercounty Connector in future networks of the Washington region's transportation system for purposes of forecasting changes in air quality.[51] On November 17, 2004, the Transportation Planning Board endorsed regional transportation plans which included the Intercounty Connector, determining that the proposed plans met air quality goals and that funding for the project was adequate.[52]

On July 11, 2005, Governor Ehrlich announced the state's preference to build the Intercounty Connector along Corridor 1. Corridor 1 (approximately 80% of which is the Master Plan Alignment) has been on the books for decades; Corridor 2, also known as the Northern Alignment, was designed to reduce Corridor 1's impact on the environment. While the EPA gave Corridor 2 a higher environmental rating,[53] it was eventually rejected by the state due to the increased number of homes and businesses that would have to be removed for its construction, because of negative environmental impacts on the Washington Suburban Sanitary Commission's Rocky Gorge Reservoir on the Patuxent River[54] (which is a source of drinking water for much of the WSSC service area),[55][56] and because it was not consistent with several approved and adopted Maryland-National Capital Park and Planning Commission master plans in Montgomery and Prince George's Counties.

On August 31, 2005, the Board of Public Works gave its approval to the Corridor 1 alternative, which allowed state funding of the project[57] in accordance with Maryland's provisions (established by statute) for funding a "growth-related project" that is not entirely within Priority Funding Areas.[58]

In December 2005, controversy arose over the Intercounty Connector's proposed toll rate. At a proposed 17 cents per mile (11 ¢/km), an end-to-end driver would have to pay about $6 a day for a round-trip (about $1,500 per year).[59]

On May 30, 2006, the Federal Highway Administration gave approval to the Corridor 1 plan, meaning that Maryland had satisfied "all environmental, economic and community requirements and that it can build the highway".[60] The Baltimore Business Journal wrote, "Federal approval for the $2.4 billion connector came after Ehrlich made a direct request to President George W. Bush, who named the Intercounty Connector as one of his priority projects. The president's direct attention prompted federal resource agencies to give the project a more timely environmental review."[61]

As approved, the Intercounty Connector would be 18 miles (29 km) long, running from I-370 in Gaithersburg to I-95 in Beltsville. It would be a controlled access toll-highway with eight interchanges, and two park-and-ride lots would be built as well.[13] The project included $370 million for mitigation and environmental stewardship activities in order to address the impact of communities, wetlands, streams, wildlife, forests, air quality, historic resources, and parklands.[13]

Construction

Construction of the ICC in Redland

The SHA constructed the ICC using separate design-build contracts for five phases.[62]

  • A. I-270/I-370 to east of MD 97 (completed)
  • B. East of MD 97 to west of US 29 (completed)
  • C. West of US 29 to east of I-95 interchange, and I-95 collector/distributor road improvements along I-95 from MD 212 to just north of the ICC (completed)
  • D. Collector/distributor road improvements along I-95 from just north of the ICC to north of MD 198 (completed)
  • E. East of I-95 interchange to US 1 (completed)

The first of the five contracts was awarded on March 27, 2007. The contract, worth $478.7 million, was awarded to Intercounty Constructors, a joint venture of Granite Construction Company, Corman Construction Inc. and G.A. & F.C. Wagman, Inc. Construction on the seven-mile (11 km) section between I-370 and MD 97 began in November 2007.[63] Contracts for three other phases are completed and the fifth phase involving collector-distributor lanes along I-95 has been completed.[64]

Requests for statements of qualification were issued for Phase A in December 2005,[65] for Phase D in August 2006,[66] and for Phase B in August 2007.[67]

The selection of the second of the five contracts was announced on November 20, 2007. The contract, worth $513.9 million, was awarded to IC3, a joint venture of Shirley Contracting Company, LLC; Clark Construction Group, LLC; Guy F. Atkinson Construction, LLC; Facchina Construction Company, Inc. and Trumbull Corporation. This work includes the ICC from a point west of US 29 to I-95, and interchanges with those routes.[68]

On September 4, 2008, The Washington Post reported that the Contract B construction contract had been awarded on July 22, 2008, to a joint venture of Kiewit, Corman Construction, and G.A. & F.C. Wagman, at a total cost of about $559.7 million—reportedly 22% higher than previous estimates. The Post story went on to say that a protest of this contract award was filed on July 30, 2008 by a joint venture that was not selected, though the bid price from the rejected group was lower. This protest may have delayed the start of construction on Contract B.[69] On October 15, 2008, the Post reported that the protest was denied by state procurement officer Robert P. Gay and that the losing proposer would file an appeal with the Maryland State Board of Contract Appeals.[70]

On September 12, 2008, the Post reported that Contract D ran into funding issues which had delayed its construction.[71] Contract D is associated with the proposed new interchange of I-95 and Contee Road (not part of the ICC). SHA Former Administrator Neil J. Pedersen stated that the "service roads can be delayed until the I-95 interchange has been built at Contee Road."

The first segment opened on February 23, 2011,[7] ahead of its projected spring 2011 opening.[72] No tolls were charged on the date of opening to March 6, 2011.[73] On the opening morning, over 10,000 vehicles used the highway,[7] and it went on to draw in 30,000 vehicles per day. During the first week of May, the tollway drew 11,490 vehicles per day, which is much less than the 21,000 projected (though by 2014, this section of highway was averaging almost 40,000 vehicles per day on average[74]). As a result, the state launched a $1.4 million advertising campaign to promote the new highway.[75] The second segment of the highway, from MD 97 to I-95 opened on November 22, 2011.[76] The highway was opened between I-95 and US 1 on November 7, 2014.[77]

Funding

The $2.56 billion project was being financed from several sources, including the Maryland Transportation Authority (MdTA) revenue bonds, $1,232,500,000 (50.39%), GARVEE bonds $750,000,000 (30.66%), Maryland General Fund $264,910,000 (10.83%), Maryland Transportation Trust Fund $180,000,000 (7.36%), and Special Federal Funds $18,500,000 (0.76%)[78][79]

Opposition

MD 200 has gained opposition from several groups, including the Maryland General Assembly and the Prince George's County Council. Proponents of the highway have claimed that it will improve the flow of interregional traffic, relieving traffic congestion on local roads. Opponents of the highway have claimed that the road will (with a few limited exceptions) harm significant traffic flow characteristics (such as increasing drive times, congestion, and costs in the form of tolls), will harm the environment (with air, sea and land impacts), and will disrupt established communities through which it passes.[3]

Government

Members of the Maryland General Assembly stated opposition in the Spring 2008[80] and Spring 2009 sessions, the 1998 session,[81] and back to 1979, when a bill introduced in the General Assembly by Delegate Robin Ficker proposed to eliminate funding for a study of the ICC and the never-built Rockville Facility highway project.[82] In 1980, a bill proposed by Delegate Idamae Garrott to forbid the Maryland Department of Transportation from even studying the matter of new highways running east and west between Montgomery and Prince George's Counties was tabled by the Montgomery County Delegation.[83]

In the 1998 session, House Bill 817 was introduced to prohibit MDOT from spending funds or granting approvals to the ICC project, and House Bill 905 was intended to stop the operation of a toll highway altogether.[84][85] Both bills failed to pass. In 2004, House Bill 732 proposed a similar statement to House Bill 817, extended to include the MdTA.[86] The 2007 Special Session saw the offering of House Bill 37 to prevent construction of the road. Both of these bills also failed to pass.[87] In the 2008 session, two bills proposing to cancel or delay the project were introduced—House Bill 1416 and House Bill 1471.[88][89] House Bill 1471 proposed to eliminate funding for the road, and, if it had passed, would trigger "liquidated damage clauses that would require it to pay the contractors an estimated $80.0 million upon cancellation of the contracts," according to the Fiscal Note prepared by the state's Department of Legislative Services.[90] Both bills failed.

In the 2009 session, a bill proposing to cancel funding for the ICC was pre-filed by Delegate Barbara A. Frush—House Bill 27.[91] This bill had not attracted any co-sponsors nor had it been scheduled for a hearing.[92] A similar bill, Senate Bill 753, was filed in the Maryland Senate by Sen. E. J. Pipkin and others.[93] The Maryland Politics Watch blog opined that Pipkin's co-sponsorship of SB 753 may be related to his possible desire to run again for the U.S. House of Representatives Maryland District 1 seat.[94] Both bills failed in the 2009 session. House Bill 27 received an unfavorable report from the House of Delegates Appropriations Committee on March 28, 2009; and no action was taken on Senate Bill 753 prior to adjournment on April 13, 2009, though a hearing was scheduled on March 18, 2009 before the Senate Budget and Taxation Committee.

The position of the County Council of Prince George's County in opposition to the ICC has been repeatedly cited by opposition groups, and its 2003 resolution on the subject, CR-32-2003, was adopted on June 10, 2003, where it called for alternatives to the road.[95] In 2007, the Prince George's County Council passed resolution CR-59-2007,[96] which repeats much of what was stated in CR-32-2003, including the language endorsing the ICC in Prince George's County.

Environmental groups

In November 2006, environmental groups announced that they were preparing to file suit in order to delay or stop the project,[97] and lawsuits aimed at halting construction[98][99] were filed by environmental groups and affected residents, assisted in part by pro bono legal counsel from the Institute for Public Representation of the Georgetown University Law Center.[100][101] One of those lawsuits was originally filed in the U.S. District Court for the District of Columbia (possibly as part of a forum shopping effort to avoid having the Fourth Circuit Court of Appeals hear the case on appeal[102] - though the United States Court of Appeals for the District of Columbia Circuit, which would have heard any appeals from the D.C. federal court, had ruled against the Sierra Club and allied groups[103] on similar legal issues in reversing a lower court on a case involving the proposal to reconstruct and widen the Woodrow Wilson Bridge in 1999)[104] but Judge Gladys Kessler of the D.C. federal court ordered the matter transferred to federal court in Maryland on May 17, 2007 and the suits were consolidated. After hearings in October 2007,[105] both lawsuits were dismissed in their entirety on November 8, 2007 by Judge Alexander Williams, Jr. of the U.S. District Court for the District of Maryland in a 105-page memorandum opinion.[106][107][108][109][110][111][112][113]

The Baltimore Sun described the decision handed down by the court as a "victory for both Governor Martin O'Malley, who backs construction of the road, and a measure of vindication for former Governor Robert L. Ehrlich, who made it the top transportation priority of his administration."[114] After the opinion was released, environmental groups opposed to the ICC stated that they would "consider their legal options before deciding whether to continue their battle"[115] and some homeowners near the selected route expressed disagreement with the ruling of the court.[116] On January 7, 2008, it was announced that Environmental Defense and the Sierra Club would appeal Judge Williams' decision to the United States Court of Appeals for the Fourth Circuit in Richmond, Virginia.[117][118][119][120][121] In April 2008, persons and groups opposed to the ICC held an "Irish wake" to draw attention to the impact of the ICC,[122][123] and an op-ed in The Diamondback was printed which raised objections to the ICC.[124]

In June 2008, protests against the ICC were held at Dr. Charles R. Drew Elementary School in Silver Spring. The participants claimed that ICC construction should be halted because of air pollution impacts on pupils at the school, though it was reported that Governor O'Malley has no plans to do so.[125] In August 2008, The Baltimore Sun published a letter to the editor from the executive director of the Coalition for Smarter Growth calling on the Maryland Department of Transportation to "cancel the ICC."[126] In September 2008, The Sun's columnist Dan Rodricks wrote an anti-ICC opinion piece[127] asserting that the ICC was the "Intercounty Anachronism". Rodricks' column was first rebutted by a letter to the editor by Montgomery County Councilmember Nancy Floreen (D-At Large)[128] and then in a longer op-ed by SHA Administrator Neil Pedersen.[129] Also in September 2008, The Gazette published an op-ed by state delegate Heather R. Mizeur (D-District 20) suggesting that the ICC be canceled.[130] The Mizeur op-ed was rebutted in a response (also published by The Gazette) by Neil Pedersen in October 2008.[131]

In November 2008, it was announced that Environmental Defense had dropped its appeal with the Fourth Circuit of the decision handed down by Judge Williams of the U.S. District Court for Maryland about a year earlier. In exchange for dropping the suit, the State Highway Administration agreed to fund new emissions-reduction technology used by public school buses in Montgomery County; and the SHA will also "sponsor a three-year study that involves installing air quality monitors along a major highway selected for its similar characteristics to the ICC and I-95."[132][133] Press releases were issued by the State Highway Administration[134] and Environmental Defense[135] discussing the details of the legal settlement.

Environmental mitigation

Lua error in package.lua at line 80: module 'strict' not found. A major component of the ICC is environmental mitigation[136] and aesthetics.[137] In addition to work taking place near and in the right-of-way of the ICC, there are over 50 "off-site environmental and community improvement projects" that will be funded as part of the ICC engineering and construction budget.[138][139]

In a letter to the editor of The Baltimore Sun, David Marks, a former official with the Maryland Department of Transportation, wrote that the SHA project team "...had the foresight to require substantial environmental improvements as part of the project, and they insisted on broad public input..."[140]

One component of the mitigation is the replacement of parkland taken for the ICC with new land.[141] Replacement lands intended to compensate for these losses include a large parcel of land in the Boyds area of Montgomery County owned by the Eugene B. Casey Foundation. However, the trustees of the Casey Foundation did not agree to the purchase of this parcel,[142] so the State Highway Administration acquired the land by condemnation and the matter was reported as resolved in June 2008.[143] In July 2008, controversy was reported on a similar subject. A 118-acre (0.48 km2) parcel of land near the intersection of MD 198 and Peach Orchard Road which had been condemned by the SHA in 1997 for possible use as the so-called Northern Alignment (Corridor 2) was conveyed to the Maryland-National Capital Park and Planning Commission to compensate for parkland which will be taken by the ICC. The former owner, Winchester Homes, filed a lawsuit contending that the SHA must offer to sell this land back to Winchester, and in May 2008, Judge S. Michael Pincus of the Montgomery County Circuit Court ruled that "the SHA was contractually obligated to offer Winchester Homes the chance to buy back the property." It was further reported that the state filed an appeal in June 2008.[144]

In the February 2008 edition of the Successes in Stewardship newsletter, the Federal Highway Administration stated:[145]

Since environmental impacts were the major barrier to prior ICC planning efforts, the third EIS team redefined the project-development approach to explicitly include environmental stewardship as part of the project's stated purpose and need. In order to fulfill the ICC's stated purpose "to help restore the natural, human, and cultural environments in the project area from the adverse effects of past development," lead-agency staff used context-sensitive design approaches to minimize or altogether avoid adverse impacts to wetlands and streams in the development of project alternatives.

At least one section of the ICC was re-routed from the master-planned route to reduce environmental impact, though the re-routing led to additional residences having to be condemned as a result.[146]

Eastern box turtles (Terrapene carolina carolina) in the path of the ICC will be located with the aid of dogs trained to find them by scent[147] and moved to other locations in Montgomery County near Boyds and Brookeville.[148]

In a letter to the editor of The Gazette, SHA Administrator Neil Pedersen enumerated a list of environmental mitigation and community enhancements that SHA is funding as part of constructing the ICC.[149]

The ICC is likely to force changes to the 14th hole of the Cross Creek Golf Club, which straddles the border between Montgomery County and Prince George's County. However, it was reported that the 14th hole was surveyed incorrectly, and part of it was mistakenly located on land set aside for the ICC.[150]

In January 2009, it was reported that Eyes of Paint Branch (a group that has opposed the ICC[151]) had recently demanded of the SHA that the contractors working to build the ICC comply with Montgomery County's regulations for the Upper Paint Branch Special Protection Area, which the State of Maryland has no legal obligation to follow.[152]

Construction of the ICC has forced the National Capital Trolley Museum to relocate its car barns, shops, visitors center, and part of its track a short distance to the north. In 2006, the museum's development director made a public plea for relocation help and coordination in a Washington Post op-ed column.[153] The museum suspended operations for relocation in December 2008 and resumed trolley rides in January 2010.[154] In August 2009, the SHA held a public forum at the new and relocated trolley museum to describe the environmental mitigation aspects of the ongoing ICC construction project.[155][156][157]

A major environmental concern along the entire ICC project is the impact of stormwater runoff on creeks and streams, during and after construction. Techniques and technologies to treat such water are known as best management practices (BMPs). State-of-the-art BMPs used along the ICC's construction project were described in an article in Land and Water magazine.[158] Some of the methods being used to control runoff were described in a The Baltimore Sun "On the Outdoors" column, published after the writer toured several work areas along the ICC's right-of-way:

The ICC project employs teams of "stormbusters" to put down straw and grass seed and erect plastic silt fences in construction areas before it rains to prevent erosion. Solar-powered stream monitors give Baker and enforcement personnel a real-time reading of water conditions. Paved storm-water ditches in older neighborhoods abutting the highway will be replaced by grass-lined swales that will filter and cool the water before it enters tributaries.

The Sun column went on to describe financial incentives that will be paid to construction contractors that meet environmental goals and requirements.[159]

As part of construction work, several archaeological sites have been found in the path of the ICC, including a Native American site near Georgia Avenue and Norbeck Road that contains artifacts dating to the Stone Age.[160] and near US 29, the 19th century homestead of a freed slave, Melinda Jackson, containing numerous artifacts.[161]

Associated construction projects

ICC Trail

A bicycle trail has long been planned to run parallel to the highway,[162] both in Montgomery County[163] and Prince George's County.[164]

However, in 2004, the SHA announced that it was dropping the ICC bike trail from its own plans due to cost and environmental footprint.[165] Since then, there have been proposals to re-route some sections of the trail over existing surface streets,[166] and to cut back or eliminate the trail for reasons of environmental impact[167] and cost.[168]

This move was harshly criticized by several groups, notably the bicycling community, who as The Washington Post states "have been promised much and given little" pertaining to the bicycle trail; however, it also believes that the county planners are assessing the situation seriously and will make the best decision.[169] Eventually, on September 18, 2008, the Montgomery County Planning Board voted to endorse a trail following a route not adjacent to the ICC's route.[170]

The Planning Board's proposal has been submitted to the Montgomery County Council for consideration as a master plan amendment. Bicycle advocates have stated their opposition to the proposal to remove parts of the bike trail immediately adjacent to the ICC.[171] Later, in March 2009, the Montgomery County Council effectively endorsed both approaches, one being a route that did not follow the ICC (in particular, along the route crossing the Paint Branch) but also keeping in place plans for a path essentially parallel to the highway.[172]

View of the trail at Muncaster Mill Road

Currently, the ICC Trail is open in three distinct segments. The westernmost segment, from Needwood Road to MD 28 (Norbeck Road), primarily following the MD 200 right-of-way except for a section which follows Emory Lane to Georgia Avenue, opened on July 30, 2011;[173] this section was later extended to MD 182 (Layhill Road). The second segment runs from Notley Road to MD 650 (New Hampshire Avenue), behind the southern sound wall of the highway. The third segment begins by running alongside US 29 from Fairland Road north to Briggs Chaney Road, passing underneath its interchange with MD 200. The segment then turns east to run along the south side of Briggs Chaney Road, then turns east at the road's interchange with MD 200, running along the freeway's south side until crossing the Little Paint Branch and terminating at the Paint Branch Trail. A fourth section was completed in 2015, running along the easternmost section of MD 200 from Konterra Drive to US 1 (Baltimore Avenue). Future segments of the trail have been left to county governments to plan and build.

Exit list

Exit numbers and mile markers are a continuation of those along I-370.

County Location mi[1] km Exit Destinations Notes
Montgomery Gaithersburg 2.540 4.088 I-370 west to I-270 Western terminus of MD 200; eastern terminus of I-370
2.540 4.088 3 WMATA Metro Logo small.svg Shady Grove Road – Metro Station Metro Access Road is officially MD 200A but is signed as I-370; split into exits 3A (Shady Grove Road) and 3B (Metro Station) on eastbound I-370
Norbeck 8.204 13.203 8 MD 97 (Georgia Avenue) – Olney, Wheaton Originally signed as exits 9A (south) and 9B (north), but was renumbered as exits 8A (south) and 8B (north) when the second segment opened on November 22, 2011
Aspen Hill 10.445 16.810 10 MD 182 (Layhill Road) – Norwood, Glenmont
Colesville 13.245 21.316 13 MD 650 (New Hampshire Avenue) – Ashton, White Oak
Fairland 15.978 25.714 16 US 29 (Columbia Pike) – Silver Spring, Columbia Also includes access for Briggs Chaney Road eastbound
16.747 26.952 17 Briggs Chaney Road Westbound exit and eastbound entrance
Prince George's Laurel 18.607 29.945 19 I-95 – Baltimore, Washington Signed as exits 19A (north) and 19B (south)
19C MD 198 (Sandy Spring Road) / Konterra Drive Direct access from eastbound MD 200 to the Konterra Drive interchange and the I-95 collector-distributor lanes between MD 200 and MD 198
Konterra Drive Eastbound exit and westbound entrance
20.008 32.200 20 US 1 (Baltimore Avenue) – Laurel, Beltsville Eastern terminus; continuous-flow intersection[174]
1.000 mi = 1.609 km; 1.000 km = 0.621 mi

See also

References

Footnotes

  1. 1.0 1.1 1.2 Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. 3.0 3.1 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.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. 7.0 7.1 7.2 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. 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.00 13.01 13.02 13.03 13.04 13.05 13.06 13.07 13.08 13.09 13.10 13.11 Lua error in package.lua at line 80: module 'strict' not found.
  14. 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. Lua error in package.lua at line 80: module 'strict' not found.
  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. Transportation Solutions Group (1999), p. i.
  27. Transportation Solutions Group (1999), p. 48, figure A2.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Transportation Solutions Group (1999), p. 37.
  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. Lua error in package.lua at line 80: module 'strict' not found.
  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. Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.
  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. Lua error in package.lua at line 80: module 'strict' not found.
  45. 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. 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. Lua error in package.lua at line 80: module 'strict' not found.
  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. Lua error in package.lua at line 80: module 'strict' not found.
  64. Lua error in package.lua at line 80: module 'strict' not found.
  65. Lua error in package.lua at line 80: module 'strict' not found.
  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. Lua error in package.lua at line 80: module 'strict' not found.
  69. Lua error in package.lua at line 80: module 'strict' not found.
  70. Lua error in package.lua at line 80: module 'strict' not found.
  71. Lua error in package.lua at line 80: module 'strict' not found.
  72. Lua error in package.lua at line 80: module 'strict' not found.
  73. Lua error in package.lua at line 80: module 'strict' not found.
  74. 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. Lua error in package.lua at line 80: module 'strict' not found.
  82. Lua error in package.lua at line 80: module 'strict' not found.
  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. 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. Lua error in package.lua at line 80: module 'strict' not found.
  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. Lua error in package.lua at line 80: module 'strict' not found.
  95. Not directly available on the Web, but the resolution (in Microsoft Word format), can be found through a search of the Prince George's County Government Legislative Information System for Resoution CR-32-2003
  96. Also not directly available on the Web, but the resolution (in Microsoft Word format), can be found through a search of the Prince George's County Government Legislative Information System for Resoution CR-59-2007
  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.[dead link]
  103. The City of Alexandria, Virginia had been the lead plaintiff in this case, but settled out of court on March 1, 1999, leaving the Sierra Club and several allied groups as the plaintiffs/appellees, see the settlement agreement here: http://www.wilsonbridge.com/pdfs/rodReport/Attachment%204%20-%20Settlement%20Agreement.pdf.
  104. City of Alexandria, Virginia, et al., Appellees v. Rodney E. Slater, Secretary, U.S. Department of Transportation, et al., Appellants, 198 F.3d 862 (United States Court of Appeals for the D.C. Circuit 1999).
  105. Lua error in package.lua at line 80: module 'strict' not found.
  106. Audubon Naturalist Society of the Central Atlantic States, Inc., Environmental Defense, et al. v. United States Department of Transportation, et al., AW-06-3386 and AW-07-1480 (Consolidated) (U.S. District Court for the District of Maryland November 8, 2007).
  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. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  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.[dead link]
  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. Lua error in package.lua at line 80: module 'strict' not found.
  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.[dead link]
  127. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  128. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  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. 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. Lua error in package.lua at line 80: module 'strict' not found.
  134. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  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. 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. Lua error in package.lua at line 80: module 'strict' not found.[dead link]
  141. Lua error in package.lua at line 80: module 'strict' not found.
  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.
  146. Lua error in package.lua at line 80: module 'strict' not found.
  147. Lua error in package.lua at line 80: module 'strict' not found.
  148. Lua error in package.lua at line 80: module 'strict' not found.
  149. Lua error in package.lua at line 80: module 'strict' not found.
  150. Lua error in package.lua at line 80: module 'strict' not found.
  151. Lua error in package.lua at line 80: module 'strict' not found.
  152. Lua error in package.lua at line 80: module 'strict' not found.
  153. Lua error in package.lua at line 80: module 'strict' not found.
  154. Lua error in package.lua at line 80: module 'strict' not found.
  155. Lua error in package.lua at line 80: module 'strict' not found.
  156. Lua error in package.lua at line 80: module 'strict' not found.
  157. Lua error in package.lua at line 80: module 'strict' not found.
  158. Lua error in package.lua at line 80: module 'strict' not found.
  159. Lua error in package.lua at line 80: module 'strict' not found.
  160. Lua error in package.lua at line 80: module 'strict' not found.
  161. Lua error in package.lua at line 80: module 'strict' not found.
  162. Lua error in package.lua at line 80: module 'strict' not found.
  163. Lua error in package.lua at line 80: module 'strict' not found.
  164. Lua error in package.lua at line 80: module 'strict' not found.
  165. Lua error in package.lua at line 80: module 'strict' not found.
  166. Lua error in package.lua at line 80: module 'strict' not found.
  167. Lua error in package.lua at line 80: module 'strict' not found.
  168. Lua error in package.lua at line 80: module 'strict' not found.
  169. Lua error in package.lua at line 80: module 'strict' not found.
  170. Lua error in package.lua at line 80: module 'strict' not found.
  171. Lua error in package.lua at line 80: module 'strict' not found.
  172. Lua error in package.lua at line 80: module 'strict' not found.
  173. Lua error in package.lua at line 80: module 'strict' not found.
  174. Lua error in package.lua at line 80: module 'strict' not found.

Works cited

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

External links

Script error: No such module "Attached KML".