Kootenay Lake Ferry Terminal Issues – Overview

March 26, 2018 – Brian Moffat of Riondel, BC presents this overview for perusal regarding issues around the Kootenay Lake Ferry and terminal. The perspective and research follows below, along with contact info for writing your own letters of concern or feedback.

This entry was posted in Uncategorized by ingrid. Bookmark the permalink.

About ingrid

Ingrid has been the owner and editor of The East Shore Mainstreet newspaper for more than twelve years since 2002. She lives and works out of her home in Gray Creek alongside her husband Juergen and children Zoe and Luka.

One thought on “Kootenay Lake Ferry Terminal Issues – Overview

  1. In this case the SNC Lavalin study was extremely flawed, and the criteria for superiority for a Queens Bay location was severely restricted. Things not considered in the study included economic, environmental and social issues effected by a move.

    • the proposed new site is at the bottom of a mud slide and millions and millions more dollars would be required to secure the mountainside
    • the proposed site is where several thousand residents intake their potable drinking water, and relocation of the water intake would again costs millions of dollars.
    • There was no back up plan for when the ferry went down.
    • With hourly sailings they did not budget for longer hours. Thus there would be only 11 hours of service in the winter. 6 plus hours of service would be lost for almost 10 months of the year.
    • environmentally the site is home to an endangered lizard species
    • it is one of the few shallow bays for fish habitat on Kootenay Lake
    • Indigenous people’s concerns were not addressed.
    • Economic impact was not addressed
    • Community Value interests were not addressed.

    When one so severely limits their evaluation criteria, one can make any project look “unequivocally” more desirable.

Leave a Reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload the CAPTCHA.