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

California State Route 905

From Infogalactic: the planetary knowledge core
(Redirected from SR 905 (CA))
Jump to: navigation, search

State Route 905 marker

State Route 905
Otay Mesa Freeway
<mapframe frameless="1" width="290" height="290" align="center">{{Wikipedia:Map data/Wikipedia KML/California State Route 905}}</mapframe>
SR 905 highlighted in red
Route information
Defined by Streets and Highways Code § 632
Maintained by Caltrans
Length: 8.964 mi[2] (14.426 km)
Existed: 1986 (from SR 117)[1] – present
Major junctions
West end: Oro Vista Road / Tocayo Avenue in San Diego
  <templatestyles src="Plainlist/styles.css"/>
East end: Boulevard Garita de Otay at the Mexican border near Otay Mesa
Location
Counties: San Diego
Highway system
I-880 I-980

State Route 905 (SR 905), also known as the Otay Mesa Freeway, is an 8.964-mile-long (14.426 km) state highway in San Diego, in the southwestern part of the U.S. state of California. It connects I-5 and I-805 in San Ysidro to the Mexican border at Otay Mesa. The entire highway from I-5 to the international border is a freeway with a few exits that continues east from the I-805 interchange before turning southeast and reaching the border.

SR 905 formerly followed Otay Mesa Road, which had been in existence since at least 1927. Before it was SR 905, the route was first designated as part of SR 75, before it was redesignated as SR 117. The freeway was completed between I-5 and Otay Mesa Road in 1976. The border crossing opened in 1985 after several delays in obtaining funding for construction on what would become SR 905. After becoming SR 905 in 1986, the highway was converted to first an expressway in 2000 and then a freeway in 2010 and 2011. Plans are for this highway to eventually become known as I-905.

Route description

SR 905 begins at the intersection of Tocayo Avenue and Oro Vista Road in Nestor. It begins as a freeway, intersecting with I-5 at a partial cloverleaf interchange. After interchanges with Beyer Boulevard and Picador Boulevard, the freeway then intersects I-805. Following this, SR 905 veers southeast to parallel Otay Mesa Road, with interchanges at Caliente Avenue (in Pacific Gateway Park), Britannia Boulevard, and La Media Road. Following those interchanges, SR 905 also interchanges with the SR 125 toll road[3] and the SR 11 freeway, which is planned to be a toll facility that will serve a new border crossing east of Otay Mesa.[4] Immediately after, SR 905 turns south to its final interchange at Siempre Viva Road before the route ends at the Otay Mesa Port of Entry,[5] which traffic of large trucks must use to cross the border.[6]

SR 905 is part of the California Freeway and Expressway System[7] and part of the National Highway System,[8] a network of highways that are considered essential to the country's economy, defense, and mobility by the Federal Highway Administration.[9] In 2013, SR 905 had an annual average daily traffic (AADT) of 58,000 between Beyer Boulevard and I-805, and 18,400 around the I-5 junction, the former of which was the highest AADT for the freeway.[10]

History

I-805 northbound at the SR 905 interchange

What was known as the "Otay Mesa Road" existed as a dirt road by 1927.[11] A paved road connected San Ysidro to Brown Field and the easternmost ranches in the Otay Mesa area by 1935.[12] Discussions were held between San Diego County and National City over the maintenance of the road in 1950, since it was used by trucks travelling to the landfill.[13] The majority of SR 905, running in parallel with Otay Mesa Road from I-5 to SR 125, was added to the state highway system and the California Freeway and Expressway System in 1959 as Legislative Route 281,[14] and became part of SR 75 in the 1964 renumbering.[15]

Planning was underway for the extension of SR 75 east to the then-proposed SR 125 by 1963.[16] The California Highway Commission endorsed the routing for SR 75 in 1965 along Otay Mesa Road, away from future residential developments.[17] There were plans as early as 1970 to have a highway heading southwest to a new border crossing that would bypass the Tijuana area.[18] The next year, James Moe, the state public works director, subsequently asked the California State Legislature to lengthen SR 75 to connect to this new crossing, rather than using I-5 to make the connection.[19]

State Route 117
Location: San Diego
Existed: 1972–1986

Following this, in 1972, the legislature added a new SR 117, which extended this part of SR 75 southwest to the Mexican border near Border Field State Park, to the state highway system, and a southerly extension of SR 125 to the border at Otay Mesa to the state highway and Freeway and Expressway systems.[20] Two years later, planning began for the construction of the Otay Mesa crossing and the construction of SR 75 to connect it to I-5 and I-805.[21] Later, the Comprehensive Planning Organization (CPO), the local association of municipal governments, recommended using $4 million of federal funding for the construction of SR 75.[22][23] The CPO later endorsed expediting construction of the freeway before completion of the border crossing, so that the freeway would primarily serve border traffic, thus preventing land speculation in Otay Mesa.[24] While Mexican authorities wanted the crossing constructed in 1975, the CPO indicated that the funding for SR 75 would not be available until at least 1980, or even 1985.[25] Following this, Representative Lionel Van Deerlin attempted to accelerate the construction of the crossing, even though there was no funding for the highway.[26]

Construction began on the southern portion of SR 75 in mid-1974. In January 1976, the part of SR 75 between I-805 and Otay Mesa Road was opened to traffic.[27] On April 6, the next portion of the freeway opened. However, there were concerns about what to call the freeway, citing confusion with the northern portion of SR 75. The entire cost of the project was $6.3 million.[28] SR 117 was extended east to SR 125, replacing the southerly segment of SR 75, by the Legislature in 1976;[29] this took effect at the beginning of 1977.[30] Estimates for completing the freeway ran from $13.8 million to $28.5 million.[31]

In late 1977, the CPO made plans to push for adding SR 117 to the Interstate Highway System, to obtain additional federal funding.[32] By 1979, both San Diego city and county had allocated $6 million to construct a temporary way to access the border crossing along Otay Mesa and Harvest Roads.[33] Two years later, the City of San Diego indicated that the upgrade of Otay Mesa Road to a four-lane road would be the preferred option;[34] the state agreed to allocate $2 million towards the $10 million project, with the city contributing $6.4 million and the county adding $2.3 million.[35] The Federal Highway Administration approved the continuous roadway via SR 117 and SR 125 from I-5 to the border at Otay Mesa as a non-chargeable (not eligible for federal Interstate Highway construction dollars) part of the Interstate Highway System in October 1984.[36] The Otay Mesa border crossing opened on January 24, 1985.[37] The route number was legislatively changed to 905 in 1986,[1] and signs were updated in 1988. This change was to apply for other federal funding.[38] The original piece of SR 117, west of I-5, also became SR 905 with the rest of SR 117,[1] but the California Department of Transportation (Caltrans) has not constructed it.[5]

Efforts were underway in 1997 to secure federal funding for the highway and other infrastructure near the Mexican border, largely supported by Senator Barbara Boxer and Representative Bob Filner,[39] and Representative Bud Schuster, the chairman of the House Transportation and Infrastructure Committee, visited the region before giving informal approval to the proposal.[6] In 1999, Governor Gray Davis approved allocating $27 million in federal funding to complete the freeway.[40] Concerns were expressed by local residents and municipal officials regarding the apparent priority of SR 125 over SR 905 in terms of funding, especially since SR 125 was to be constructed as a toll road, and SR 905 would compete with the toll road enterprise.[41] In May 1998, Congress approved $54 million in funding for the completion of SR 905.[42]

Otay Mesa Road was widened to six lanes in 2000 for $20.5 million. Before, it had 50 percent more traffic than it was designed to handle;[43] it was considered by the San Diego Union-Tribune as "California's busiest trade route with Mexico." Traffic had increased by ten times, with the number of people dying in traffic accidents approaching five times the state average. The widening of Otay Mesa Road was considered a temporary fix for the problem.[44] The next year, the California Transportation Commission allocated $25 million of state funding towards completing the freeway.[45] The interchange with Siempre Viva Road opened on December 8, 2004.[46] Delays in the U.S. Congress approving federal funding in 2005 resulted in a delayed start to construction for the rest of SR 905.[47]

Construction began on the part of SR 905 between Britannia Boulevard and Siempre Viva Road in April 2008, and from Brittania Boulevard to I-805 in July 2009.[48] Efforts were made to keep construction going despite a shortfall in funding from state bonds in 2009.[49] The part between Britannia Boulevard and Siempre Viva Road opened in December 2010.[48] The interchange with I-805 began to be upgraded in April 2011,[50] and the construction, which used $20 million in federal funding,[51] finished in February 2012.[48] The final freeway segment of SR 905 between I-805 and Britannia Boulevard opened on July 30, 2012. The entire cost of the project connecting I-805 to the border crossing was $441 million.[52]

Before being upgraded to a freeway between Britannia Boulevard and Siempre Viva Road, SR 905 directly connected with SR 125 via two at-grade intersections on Otay Mesa Road.[53] When Caltrans opened that segment of the SR 905 freeway in 2010, they omitted the interchange with SR 125, forcing traffic on SR 905 and SR 125 to exit their respective freeways and use Otay Mesa Road (which SR 905 followed at that time) to make the connection. To help fix this problem, a direct freeway-to-freeway interchange was planned, which also included the new SR 11 freeway once it was to be constructed,[54] with construction beginning in late 2015.[55] SR 11 is planned to be a toll facility that will serve a new border crossing east of Otay Mesa.[4] Ramps from SR 905 eastbound to SR 125 northbound, SR 905 westbound to SR 125 northbound, and SR 11 westbound to SR 125 northbound were completed on November 30, 2016, at the cost of over $21 million.[3] Prior to December 16, 2021, traffic on southbound SR 125 was forced to exit onto Otay Mesa Road at that toll road's then southern terminus in order to connect to SR 11 and SR 905.[5] Construction on the ramps for these connections began in 2018,[56] with the ramps from SR 125 southbound to SR 11 eastbound and SR 125 southbound to SR 905 eastbound being completed on December 16, 2021, at the cost of $74 million.[57] The ramp from SR 125 southbound to SR 905 westbound, which was still under construction at the time, was initially scheduled to open to traffic in 2023,[58] but was instead opened to traffic on July 26, 2022, finally completing the interchange.[59] There are no plans to construct the remaining connections from SR 905 westbound to SR 11 eastbound and SR 11 westbound to SR 905 eastbound.

Future

Interstate 905

Interstate 905
Location: San Diego
Length: 8.964 mi (14.426 km)

Plans are for SR 905 to become I-905;[60] however, it could not be constructed with the same federal government funds that were used for constructing the rest of the Interstate Highway System. This is because I-905 was not constructed as of 1978, when the Surface Transportation Assistance Act of 1978 provided that all Interstate construction authorized under previous amendments to the system would be funded by the federal government but additional highway mileage added under 23 U.S.C. § 103(c)(4)(A) would not be funded from the same highway fund.[61][62]

Exit list

Except where prefixed with a letter, postmiles were measured on the road as it was in 1964, based on the alignment that existed at the time, and do not necessarily reflect current mileage. R reflects a realignment in the route since then, M indicates a second realignment, L refers an overlap due to a correction or change, and T indicates postmiles classified as temporary (for a full list of prefixes, see the list of postmile definitions).[2] Segments that remain unconstructed or have been relinquished to local control may be omitted. The entire route is in San Diego, San Diego County.

Postmile Exit
[63]
Destinations Notes
0.00 0.00 Oro Vista Road / Tocayo Avenue At-grade intersection
0.37 0.60 1A–B I-5 (San Diego Freeway) Signed as exits 1A (north) and 1B (south) westbound; signed as exits 1A (south) and 1B (north) eastbound; I-5 exit 3
0.97 1.56 1C Beyer Boulevard Signed as exit 1 eastbound; former US 101
1.56 2.51 2A Picador Boulevard / Smythe Avenue
2.32 3.73 2B I-805 (Jacob Dekema Freeway) Signed as exits 2B (south) and 2C (north) westbound; I-805 exits 1B-C
3.88 6.24 4 Caliente Avenue
4.91 7.90 5 Heritage Road Proposed interchange[64]
5.94 9.56 6 Britannia Boulevard – Tijuana International Airport, Brown Field Municipal Airport Access to Tijuana International Airport via Cross Border Xpress
6.93 11.15 7 La Media Road
7.68–
7.77
12.36–
12.50
8 SR 11 east Eastbound exit and westbound entrance; western terminus of SR 11

SR 125 north (South Bay Expressway)
Southern terminus of SR 125
8.53 13.73 9 Siempre Viva Road Last U.S. exit eastbound
8.89 14.31 Mexico–United States border (Otay Mesa Port of Entry) Continues beyond the international border as Boulevard Garita de Otay
1.000 mi = 1.609 km; 1.000 km = 0.621 mi

See also

References

  1. 1.0 1.1 1.2 Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 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. 4.0 4.1 Lua error in package.lua at line 80: module 'strict' not found.
  5. 5.0 5.1 5.2 Lua error in package.lua at line 80: module 'strict' not found.
  6. 6.0 6.1 Lua error in package.lua at line 80: module 'strict' not found.
  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. 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. 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. 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. California Department of Transportation, State Highway Routes: Selected Information, 1994 with 1995 revisions
  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. 48.0 48.1 48.2 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.[date missing]
  61. Surface Transportation Assistance Act of 1978, Pub.L. 99–599
  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.

External links

Script error: No such module "Attached KML".