Pool 2 Hazard

  • mile832
    MN
    Posts: 565
    #1315238

    Just FYI for anyone boating on Pool 2. I have reason to believe there is a submerged channel marker a couple feet below the surface on the upstream tip of the second wingdam south of the 494 launch on the east side (this is the wingdam across the river from the big water outlet). The hazard is upstream roughly 40-50 feet from the visible red bouy and 40-50 feet towards the east bank. In other words, if youre looking upstream, the hazard is upstream and to the right of the red marker 60-70 feet at about 45 degrees to the current. Watch out!

    I smacked into it today and chewed up my prop and bent my skeg. I couldnt figure out what I could have hit in 16 feet of water until I saw the red bouy paint on my prop.

    Good luck and be careful.
    Tim

    Mike W
    MN/Anoka/Ham lake
    Posts: 13294
    #563820

    Think that may be a log that has been hanging out there for awhile. If we dont get some water again soon it should be out of water. Sorry to hear about your prop. Bet that log must have a couple hundred dollars worth of jigs on it.

    mplspug
    Palmetto, Florida
    Posts: 25026
    #563821

    Sorry to here that man, that is a bummer. Nice heads up thread for your fellow IDAers.

    mile832
    MN
    Posts: 565
    #563838

    Whatever it is, it has red paint on it…

    My guess is a big tree pulled it under from upstream. I think there used to be a bouy by the next wingdam upstream and its not there anymore. I’m guessing thats the one.

    clarence_chapman
    Hastings, MN Lake Isabel activist
    Posts: 1345
    #563873

    Would notifing the Coast Gaurd of the boey be appopriete?

    Mike W
    MN/Anoka/Ham lake
    Posts: 13294
    #563918

    Maybe one got hung up on the root ball of that tree. That log usually pops up about 40′ to the eaast of that cone and just a little down stream. Good to know as that area is a popular wing dam to fish and a lot of people anchor there. Im heading there right now.

    Im heading down there right now. If anyone wants to jump in give me a call.

    jon_jordan
    St. Paul, Mn
    Posts: 10908
    #563940

    It’s the red can under water. I have a pretty good idea why too. About a 50 foot section (maybe more)of that yellow raft floating tubing stuff to collect run off from the bridge construction broke free and floated down on the marker. Once it hit it, took the can down. It’s not coming up until that junk gets cut loose. It’s not too far under water. If you go by it slowly you can see the marker and the yellow raft stuff about a foot down.

    Always need to be careful in the spring down there.

    -J.

    DeeZee
    Champlin, Mn
    Posts: 2128
    #564680

    Quote:


    I have reason to believe there is a submerged channel marker a couple feet below the surface on the upstream tip of the second wingdam south of the 494 launch


    Thats where having a River Pro jet boat comes in handy!!!
    Thanks Tim for the heads up. I know that area pretty well, there is some significant timber lying on the bottom in that area that has alot of very big limbs hanging off them.

    Correct me if I am wrong, I believe the Coast Guard does a spring cleanup every year to retrieve some of the buoys markers. I have seen alot of “stray” buoys already the past several weeks.

    sippiriverrat
    Andover MN.
    Posts: 390
    #568304

    I was just through there yesterday and got luck to not hit it, I will try to find it and get a GPS ready and call it in to the coast guard.

    Steve Root
    South St. Paul, MN
    Posts: 5623
    #569935

    Quote:


    I know that area pretty well, there is some significant timber lying on the bottom in that area that has alot of very big limbs hanging off them.


    Not to mention about 75 of my jigs

    Rootski

    Mike W
    MN/Anoka/Ham lake
    Posts: 13294
    #570565

    Steve. You need to take a page from BrianK’s book and start cat fishing. Then you will start catching more walleyes.

Viewing 11 posts - 1 through 11 (of 11 total)

You must be logged in to reply to this topic.