Mohegan Lake Legal Defense Fund

History of this site

This site was originally set up to fight 3 of 5 zoning variances proposed by the FBC development at Sagamore Trail and Mohegan Ave that eliminates two single family homes while nearly quadrupling the parking and occupancy loads of the old Lakeland Jewish Center. That effort failed and the application is currently before the Planning Board.

While Save Mohegan Lake will continue to update you on that issue, we are moving on to all issues affecting the lake, such as Mohegan Lake Improvement District (MLID) meetings, agenda and budget. This site is not an official mouthpiece for MLID, but some updates will be provided on this site; the official site is located here.

We do it all here, so long as it's Mohegan Lake related. Feel free to submit comments, content, garage sale notices, police blotters, PSA's, essays on the virtues of our 105 acre ice rink, rants, raves, etc... We love it all.


Monday, June 8, 2015

The Most Important News For Mohegan Lake In Some Time

We got approval for a copper sulfate treatment to control the flaming algae bloom we get every year.  On to aluminum sulfate, hopefully.  Looking forward to a full season of swimming.  No pool pass for us this year. 

Here's a note from MLID president Ken Belfer:

Thanks to the hard work of Laura Kosbar, who prepared the application and handled the follow up, we have received the permit from NYS DEC to apply copper sulfate this season to Mohegan Lake.  The first application date has not yet been set, but will be in June.  Notices will be posted at all of the beaches, as well as an email notification sent to spread the word.  The application will be done during the week, and there will be no swimming allowed for 24 hours after the application.  Let's hope this will allow us to have a swimmable lake for the entire summer this season.
Yay!  And a big thanks to the dedication of a very few number of people in our community on this matter.  They know who they are.  Are you involved with MLID?  Should you be?

No comments: