ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

The Santa Monica Offshore Causeway Never Built

Updated on August 21, 2013

Had the Santa Monica Causeway highway project been completed, it would have looked similar to that of Clearwater, Florida, today, except bigger. Clearwater is 10 miles west of Tampa, it sits smack on the Gulf of Mexico with its 80-degree water. The town, itself, is not large, but it is connected by a causeway over the Tampa Bay. Beaches line the coastal road once off the causeway and the boardwalk goes on for miles and miles of white sand beaches.

Back in 1961 or so, there was a plan proposed by some in Santa Monica and supported by the Army Corps of Engineers in 1963, to build a series of man-made islands connected by a causeway to link downtown Santa Monica. The Interstate 10 was relatively new and took direct aim towards the city. The city was eager to have a new highway to carry dense auto traffic, even then, and even paid $50,000 for feasibility plans. Located 4,000 feet from shore, the 30,000-foot long causeway would run parallel to the coastline from Santa Monica beach all the way north. In the middle of this artificial island complex would stretch a 200-foot wide freeway called “Sunset Seaway.” The plan would also provide an additional 2.5 million square feet of public beach facing the ocean that could accompany 50,000. The causeway itself would span a six-mile strip of land atop the Pacific Ocean.

However, Santa Monica, was only worth 21 million then, and could not afford it without help. That is where Los Angeles County joined in. Los Angeles County had an assessed value of $13 billion in 1963. Against this figure, the County could acquire bonds totaling $670 million. Santa Monica needed only a fraction of that amount. LA was eager about the project. So, funding seemed to have been resolved.

The causeway would have been made a mile from the current shoreline, hopping over a series of man-made islands. It would have ran from the Santa Monica Pier to just north of Topanga Canyon and enclose 3200 acres. To get the rock and landfill, rock would come from the Santa Monica Mountains to create a protective reef. Once in place, the initial landfill for the causeway would come from terracing the mountains.

The islands created would be 65% residential and would have been the largest earth moving project in the world, at that time. The Corps' estimated that over 200 million cubic yards of earth would need to be moved to create the islands at a cost of $90,000,000. This is in addition to the 2.5 tons of rock for the reef. Los Angeles was also in support, however, by 1965, Jerry Brown's father, Gov. Pat Brown, vetoed the whole plan when over 10,000 local resident signatures opposing it reached Sacramento.

This could be said it was the first environmental opposition by young activists, surfers, movie stars and local residents.




Comments

    0 of 8192 characters used
    Post Comment

    No comments yet.

    working

    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://hubpages.com/privacy-policy#gdpr

    Show Details
    Necessary
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
    Features
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Marketing
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Statistics
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)