Showing posts sorted by date for query vermont. Sort by relevance Show all posts
Showing posts sorted by date for query vermont. Sort by relevance Show all posts

October 9, 2014

Sorry, your health care coverage can't actually be used.

=================================

Subject: Important Information About Your Health Coverage
Date: Fri, 6 Dec 2013
From: vthealthconnect@state.vt.us
To: [ ]@[ ].net

Dear [ ],

Hello! We are writing to let you know that you have a new notice regarding your bill for health care benefits from Vermont Health Connect. To view your notice, please click on the link below and log in to your account.

Your notice is: Premium Invoice

www.vermonthealthconnect.gov

After logging into your account, click on ‘My Account’ and select the ‘My Profile’ tab. Once there, click on ‘View Documents’ from the ‘Quick Links’ box. If you have any questions regarding this notice, please call Vermont Health Connect Customer Support toll-free at 1-855-899-9600, Monday-Friday 8am-8pm and Saturdays 8am-1pm (except holidays and holiday weekends).

Thank you,

Vermont Health Connect

=================================

Subject: Re: Important Information About Your Health Coverage
Date: Fri, 06 Dec 2013
From: [ ] <[ ]@[ ].net>
To: vthealthconnect@state.vt.us

There doesn't appear to be a way to log in. There is a "logout" button, which remains "logout" after clicking it. No "login" button or pane.

In fact, because of the consequent inability to check my account and the lack of reply by telephone [since applying on line], I just sent in a paper application today. Which I guess is now unnecessary as far as setting up an account.

I think I would like a paper notice/statement/bill.

Thanks.

=================================

Subject: RE: Important Information About Your Health Coverage
Date: Mon, 9 Dec 2013
From: AHS - VT Health Connect
To: '[ ]' <[ ]@[ ].net>

Dear [ ],

Thank you for writing.

To log in to your account, please go to https://portal.healthconnect.vermont.gov/ and click on “Start Here” found next to where you see “Are you looking for coverage for yourself or your family?” On the next page, please click either on “Login to your Account” or “Apply Now” as either will bring you to the log-in screen. Once you are logged into your account, you will be able to access your invoice using the directions in your original e-mail.

[Makes sense? Even if you have an account, you have to illogically click "Are you looking for coverage for yourself or your family?" to get to it. But perhaps that was an admission of the truth recorded here.]

As you've requested, we'll send a paper invoice to you in the mail. You can expect to receive this invoice within a week.

Please let us know if we can help you with anything else.

Kind regards,
Rebecca

Vermont Health Connect
Customer Support – 855-899-9600

Check out our website for updated information!

Links:
Vermont Health Connect: http://info.healthconnect.vermont.gov/
YouTube Channel: http://www.youtube.com/vthealthconnect

=================================

Subject: Your Vermont Health Connect Invoice
Date: Tue, 17 Dec 2013
From: Vermont Health Connect
To: [ ] <[ ]@[ ].net>

Dear [ ],

Thank you for completing your application for health insurance coverage through Vermont Health Connect. You may have received two invoices this month – one for your new (2014) Vermont Health Connect health plan, which begins January 1, 2014, and one for your former (2013) health plan, which was recently given the option of extending up to March 31, 2104.

You only need to pay the bill for the plan you wish to have effective on January 1. You do not need to pay the other bill. If you want help making the choice of which bill to pay, please call our Customer Support Center toll-free at 1-855-899-9600 and reference the code “VHC1215.” A customer service representative will then talk you through your options. Please note that our call volume is high at this time. We thank you in advance for your patience. If you applied through a Navigator, you could consult him or her as well.

Please note that you do not need to take any additional steps to cancel your former plan. Your 2013 health plan will automatically expire after you pay your premium and your 2014 plan takes effect.

We are open from 8:00 a.m. to 8:00 p.m. Mondays-Fridays and 8:00 a.m. to 1:00 p.m. on Saturdays.

Sincerely,

Vermont Health Connect Customer Service

=================================

Subject: Starting coverage in February
Date: Sat, 11 Jan 2014
From: [ ] <[ ]@[ ].net>
To: vthealthconnect@state.vt.us

I set up my account and selected a plan very early and received an invoice by mail (as requested) in December. However, I had already paid my Catamount Care premium for January, so I did not pay the premium for the new plan.

Now I need to make sure that I will get another invoice (by mail, please) for the new plans, to start coverage in February.

=================================

Subject: RE: Starting coverage in February
Date: Mon, 20 Jan 2014
From: AHS - VT Health Connect
To: '[ ]' <[ ]@[ ].net>

Dear [ ],

Thank you for writing. We're so sorry for the delay in replying to your email.

I've reviewed your account and see that you also called and spoke with someone about this last week. As they told you, it is fine for you to just pay your premium for February. Your account has been marked so that your policy will start in February.

Please let us know if we can help you with anything else.

Kind regards,
Rebecca

Vermont Health Connect

=================================

Subject: Important Information About Your Health Coverage
Date: Wed, 5 Feb 2014
From: vthealthconnect@state.vt.us
To: [ ]@[ ].net

Dear [ ],

Hello! We are writing to let you know that you have a new notice regarding your bill for health care benefits from Vermont Health Connect. To view your notice, please click on the link below and log in to your account.

Your notice is: Premium Invoice

www.vermonthealthconnect.gov

After logging into your account, click on ‘My Account’ and select the ‘My Profile’ tab. Once there, click on ‘View Documents’ from the ‘Quick Links’ box. If you have any questions regarding this notice, please call Vermont Health Connect Customer Support toll-free at 1-855-899-9600, Monday-Friday 8am-8pm and Saturdays 8am-1pm (except holidays and holiday weekends).

[Steps to view invoice:
• Click "Are you looking for coverage for yourself or your family?"
• Click "Log in"
• Click "My Account"
• Click "My Profile"
• Find the "Quick Links" box and Click "View Documents"
• Click the listed documents until you reveal the current invoice]

Thank you,

Vermont Health Connect

=================================

Subject: Re: Starting coverage in February
Date: Mon, 10 Mar 2014
From: [ ] <[ ]@[ ].net>
To: AHS - VT Health Connect

Today I received a "Payment past due/Termination Notice" from BCBS [Blue Cross/Blue Shield]. As noted below, this is because I was assured that it was OK to ignore the January premium and that the new policy was to begin in February. This was necessary because the invoice for January coverage under Catamount Care was due (and paid) before the invoice for the new BCBS policy under VHC was available.

According to the BCBS notice, "Vermont Health Connect has reported that full payment has not been received for your health insurance."

Please resolve this.

=================================

Subject: RE: Starting coverage in February
Date: Thu, 13 Mar 2014
From: AHS - VT Health Connect
To: '[ ]' <[ ]@[ ].net>

Dear [ ],

Thank you for contacting us. We're very sorry that you received the past due notice from BCBS. I see that you have paid each of your invoices well in advance of the due dates, and as you noted, the fault is entirely ours for not yet making that change to your coverage start date. Unfortunately, we don't have that functionality to make the change once your plan is in force, but we are working on it and will correct your account as soon as we are able.

You actually have a 90 day grace period, so there is no danger of your plan being terminated as long as you keep paying your monthly premiums as you have been doing.

Please let us know if we can be of any further assistance.

Kind regards,
Ellen

Vermont Health Connect

=================================

And so I have been paying the monthly premium to Vermont Health Connect, ignoring the monthly "PAST DUE/NOTICE OF TERMINATION" notices from BCBS.

Secure in the knowledge that we do indeed have continuing "affordable health insurance" (which Vermont was already providing for almost everybody, effectively and without major problems: the "Catamount Care" referred to above). Secure, that is, as long as we would never need it, as it turned out.

I had an annual check-up scheduled in early October and was told by the doctor's office that a check of insurance status revealed it to be "pending". For that reason, they would not be able to submit the bill. I learned from a call to BCBS on Oct. 1 that "pending" in this case meant that I was behind in payments, because they still considered my coverage to have begun on Jan. 1 instead of Feb. 1, and therefore still expected an extra month of payment. In other words, despite the reassurance from Vermont Health Connect 8 months before that "we are working on it and will correct your account as soon as we are able", they still had not. Furthermore, the reassurance that "there is no danger of your plan being terminated as long as you keep paying your monthly premiums as you have been doing" turned out to be meaningless, since my regular doctor wouldn't risk billing to a "pending" insurance account. The person I talked with at BCBS helpfully transfered me to Vermont Health Connect, noting that she had heard that they may be "a few months" behind.

Thank goodness we have not been in any emergency situation or in urgent need of a prescription refill.

From Vermont Health Connect I now (!) learned that changing the start date required a new application because it is a "change of status". And so I was transfered to another office to handle that. The woman there, like everyone I have talked with at every step, it should be said, was very helpful and was able to use the original application to make a new one for coverage starting Feb. 1, ie 8 months earlier, to expire Dec. 31, ie in less than 3 months.

Now we were expected to have "new" insurance active in a couple of weeks, a new card in a week after that. Just in time to start the whole charade over again for coverage next year.

We essentially have had no usable insurance coverage since Feb. 1, despite regularly paying monthly premiums for it. What surprises lie in wait for us in the new cycle beginning Jan. 1, 2015, with a promised automatic renewal of coverage? Or in April, when the IRS recalculates everybody's share of their previous year of premiums?

The faster we move to a single payer system the better! Federally, Medicare was supposed to steadily expand in the 1960s to cover everyone, not just the elderly (but then it would have covered draft dodgers and black panthers along with "deserving" citizens like oneself). If the US government can not or will not provide that very basic service to all those who live within its borders, then the states need to go it alone. And I mean not just setting up some mash-up of federal support and state-provided health coverage, although that would be a welcome step despite the likelihood of its being as dysfunctional as the current private-public mash-up — I mean breaking away altogether from the government of Washington. Because health care is just one of its many failures, and war to gain world hegemony seems to be its only goal, war ordnance its only economy, squandering our common wealth as well as our lives, sacrificing them to an end that can only be catastrophic.

[Update:  Two and a half weeks later, we've received no notice about the "new" coverage, but instead a series of premium invoices (up to 4 so far), each one different from the last and none of them reflecting a resolution.]

[Update:  Four weeks later, we haven't received a new insurance card or any notice about the "new" coverage.]

[Update:  A month later, BCBS remains uninformed of the change, which Vermont Health Connect says was "finalized" on Oct. 14 (under a different "service request" no. than the "confirmation no." originally provided).]

[Update:  Five weeks later, the "change of circumstance center" has promised to notify BCBS today, which was supposed to have been done on Oct. 14 but was not. The reason another 2 weeks was required in the first place was because there is a child on S-CHIP, and that "start of coverage" (despite being continually covered under the auspices of the state for some 13 years already) was not supposed to change from January to February, so a new "change of circumstance" (the only change being the system's, not ours) had to be created to disinclude the S-CHIP part — it was done, but then someone neglected to tell BCBS. Oh, and a new "master case" number. Could it be more complicated? More counterproductive (unless, of course, prevention of care is precisely the intention)??]

[Update:  Five-and-a-half weeks later, BCBS remains uninformed of the change, which the Vermont Health Connect "change center" now says was "finalized" on Oct. 29 and confirmed that it was sent to "billing" who would then notify BCBS, which process could take 15 days, likely more as they are busy starting enrollment for next year. Vermont Health Connect customer service confirms the change, that the start date has been changed, billing reconciled, and BCBS informed. However, BCBS finds no change -- and it's not on the latest weekly confirmation list from Vermont Health Connect, waiting to be processed. BCBS suggests checking in another week.]

[Update:  A month and a half later, the "last invoice for 2014" has arrived, showing a "balance forward" of 10 times the new premium amount, presumably representing the charges for February through November of our "new" coverage, ignoring the year of payments for our "old" coverage for those same months. Then, inexplicably, the amount due adds only the SCHIP charge, not the next month's premium. Aieee!]

Further notes from 2015: 

May 13:  "Use this updated form [1095-A] when you complete IRS Form 8962 and file your federal income tax return [last month]."

Premiums due:  January 26: $627.52. February 26: $313.76. March 26: ($2.30). April 26: $311.46. May 26: ($238.36). June 26: $75.40. July 26: $313.76.

June 8:  Notice from Blue Cross–Blue Shield: "Payment Past Due." Go to newly launched Vermont Health Connect web site for any information that might be there: My Health Plans: "No current plans found."

June 25:  "A refund has been issued to you in the amount of $20.00."

July 16:  Notice from IRS: "Our records show that you did not file a 2014 tax return to reconcile advance payments of the Premium Tax Credit. … We received a copy of form 1095-A, Health Insurance Marketplace Statement, issued to you by your Health Insurance Marketplace showing … You are required to file a a 2014 federal tax return with Form 8962, Premium Tax Credit, to reconcile …" So it seems that filing Form 8962 with the correct information from one's own records — because the 1095-A form originally provided was obviously incorrect — instead of the updated 1095-A that came a month after the tax filing deadline (and which was still incorrect) [see May 13, above] is not recognized as a possibility, is as good as failing to file at all, and in fact nullifies the 1040 and everything as if never filed at all!

See a new report from 2016:  Vermont Health Connect: “Current wait times are 90 minutes”

October 4, 2014

Wind turbine setback and noise regulations since 2010

These changes in and new wind turbine regulations since 2010 do not include moratoria and bans. See also the list at Windpowergrab and the Renewable Energy Rejection Database (USA). All ordinances in USA: WindExchange (Dept. of Energy) wind energy ordinances database; NREL: Wind Ordinances, Wind Regulations by Region; NCSL: State approaches to wind facility siting (local or state-level).

[note:  1,000 ft = 305 m; 550 m = 1,804 ft; 1,000 m = 1 km = 3,281 ft = 0.62 mi; 1 mi = 1.61 km = 5,280 ft;  about decibels (dB)]

  • Pottawattamie County, Iowa, February 27, 2024:  setbacks 1/2 mi from nonparticipating homes, 1.1× height from participating homes, 1,500 ft from lot lines and public rights of way, 3 mi to incorporated municipalities, airport property, conservation partks, and habitat areas; 412 ft max height; noise limit 40 dBA 1-hour LEq 25 ft outside nonparticipating home; max 30 hours/year shadow flicker at nonparticipating home [link]
  • Slovakia, January 2024:  setback 3 km from inhabited areas [link]
  • New South Wales, Australia, November 2023 [draft]:  noise limit 35 dBA or existing background noise level (LA90(10 min)) plus 5 dBA at residences (whichever is lower) [link]
  • Jefferson County, Nebraska, March 23, 2023:  setback 1 mi from nonparticipating homes, incorporated towns, schools, churches, and state-owned recreation areas [link]
  • Buffalo County, Nebraska, March 14, 2023:  setbacks 3 mi from agriculture residential zoned property, nonparticipating property, church, hospital, pool, or park, 5 mi from villages, cities, and wildlife preservation and management areas, 2 mi from burial sites, Platte River, and South Loup River [link]
  • Poland, March 2023 [effective July 2, 2024]:  setback 700 m [2,300 ft] from houses [link]
  • Iowa, January 9, 2023 [proposed]:  setback from dwelling or nonparticipating property greater of 1.5× height or 5,000 ft [link]
  • Woodbury County, Iowa, August 23, 2022:  setback from residences increased from 1,250 ft to 2,500 ft [link]
  • Stockbridge Township, Michigan, August 2022:  height limit 400 ft [link]
  • Cumberland County, Nova Scotia, June 22, 2022:  setback from dwellings increased from 600 to 1,000 m; 3.2 km from main Wentworth Valley road [link]
  • Grand Forks County, North Dakota, June 2022:  setback increased from 1/4 to 1/2 mi; shadow flicker limited to 30 h/yr [link]
  • Leroy Township, Michigan, May 8, 2022:  height limit 400 ft [link]
  • Gage County, Nebraska, Nov. 17, 2021:  noise limit at residence reduced to 40 dB (from 45) daytime and 37 dBA (from 40) nighttime (10pm–7am), or 3 dBA max 10-minute Leq above ambient [link]
  • Ohio, Oct. 11, 2021:  counties have right to veto, ban, and limit projects; several counties subsequently prohibited wind projects ≥5 MW in 2022 [link]
  • Vermillion County, Indiana, Sep. 28, 2021:  setback 2 mi from property lines and roads; noise limit 32 dBA [link]
  • Ford County, Illinois, Sep. 17, 2021:  setbacks 3,000 ft from property line, 1.5 mi from municipality; noise limit 40 dB (Laeq) 9pm–6am; no shadow flicker at neighboring residence [link]
  • Sidney Township, Michigan, July 5, 2021:  300 ft height limit; setback 3,000 ft or 5× height [sic] from nonparticipating property line or right-of-way, 2.5 mi from lake or pond; noise limits of 40 dBA Leq (1 sec) and 50 dBC Leq (1 sec) and no shadow flicker on nonparticipating property; no radio, TV, or other interference [link]
  • Pierson Township, Michigan, June 15, 2021:  setback 4× height from occupied structures and property lines, 39 dBA limit and no shadow flicker on neighboring property [link]
  • Boone County, Missouri, November 4, 2021:  80 m (~263 ft) hub height limit; setback 1,750 ft from property line or public right-of-way; noise limits at property line 50 dBA daytime (7am–10pm), 40 dBA nighttime (10pm-7am), 45 dBA adjusted total day-night (Ldn; 10 dBA added to nighttime level) [link]
  • Dakota County, Nebraska, July 26, 2021:  change of setbacks from 2,700 ft to 2 mi from neighboring residence, from 600 ft to 2 mi from wetlands and other conservation lands [link]
  • Ellington Township, Michigan, July 2021:  setbacks 5× height from property lines, 3× height from roads; 40 dBA limit and no shadow flicker on neighboring property [link]
  • Worth County, Iowa, approved by Planning and Zoning Commission June 25, 2021:  at nonparticipating property: distance greater of 1,600 ft, 3.75× height, or manufacturer’s safety distance, noise limit greater of ambient or 45 dBA/60 dBC 6am–10pm, 40 dBA/60 dBC 10pm–6am, no shadow flicker; setbacks from eagle nest greater of 1,600 ft, 3.75× height, or manufacturer’s safety distance, 1/2 mi from public recreation area, significant body of water, and habitat >40 acres, 1 mi from public recreation area [link]
  • Clarion County, Pennsylvania, May 25, 2021:  at nonparticipating residence: distance 5× height, noise limit 45 dBA, no shadow flicker [link]
  • Kansas, introduced Feb. 24, 2021:  SB 279: setbacks greater of 7,920 ft (1-1/2 mi) or 12× height from residential property or public building, greater of 3 mi or 12× height from any airport, wildlife refuge, public hunting area, or public park, and greater of 5,280 ft (1 mi) or 10× height from nonparticipating property line [link]
  • Vulcan County, Alberta, Canada, Jan. 27, 2021 [proposed]:  45 dBA noise limit at property line; 800 m setback from nonparticipating residence [link]
  • Burt County, Nebraska, 2020:  setback greater of 3.5× height or 1,800 ft from dwelling [link]
  • Wheeler County, Nebraska, Dec. 9, 2020:  5 mi setback from any dwelling, 1/2 mi distance between turbines, height limit 299 ft [link]
  • Piatt County, Illinois, Dec. 9, 2020:  46 dBA noise limit outside of homes [link]
  • Ireland, Nov. 24, 2020 [Wind Turbine Regulation Bill reintroduced]:  10× height setback from any dwelling, no shadow flicker at dwelling, noise limits per WHO community noise guidelines [link]
  • Reno County, Kansas, Nov. 19, 2020:  setback from residence greater of 2,000 ft or 4× height [link]
  • Edgar County, Illinois, Nov. 4, 2020:  increased setback to 3,250 ft from primary structures [link]
  • Piatt County, Illinois, Oct. 22, 2020 [subject to county board approval]:  increased setback from greater of 1.1× height or 1,600 ft to nonparticipating structure to greater of 1.3× height or 1,600 ft to nonparticipating property line [link]
  • Gage County, Nebraska, Sept. 9, 2020:  increased setback to nonparticipating residence from 3/8 mi to 1 mi [link]
  • Batavia Township, Michigan, Sept. 1, 2020:  height limit 330 ft [link]
  • Reno County, Kansas, Aug. 2020 [proposed]:  40-dB annual average noise limit at any principal building (participating property or not) [link]
  • Hughes County, South Dakota, Aug. 17, 2020:  setback 1/2 mi or 4.9× turbine height from any occupied structure; 45-dB noise limit [link]
  • Brown County, Nebraska, May 2020:  setback 1 mi from property lines and roads [link]
  • North Dakota, Mar. 2020 [subject to Attorney General review and approval of legislative Administrative Rules Committee]:  45 dB noise limit 100 ft from residence [link]
  • Fremont County, Iowa, May 2020 [proposed]:  setbacks 1,500 ft from participating residence, 2,000 ft from nonparticating residence, 1,000 ft from nonparticipating property line, 1 mi from incorporated cities, 3 mi from Mississippi River [link]
  • North Dakota, Mar. 2020 [subject to Attorney General review and approval of legislative Administrative Rules Committee]:  45 dB noise limit 100 ft from residence [link]
  • Honolulu (Oahu), Hawaii, Mar. 2020 [subject to full city council approval]:  setback 5 mi from nonparticipating property lines [link]
  • Matteson Township, Michigan, Mar. 4, 2020:  setbacks 1.25 mi from nonparticipating property line, 4× height to any residence; 328-ft height limit; noise limit 45 dB(A) or 55 db(C) at nonparticipating property line; no shadow flicker on nonparticipating property; allowed only in general agricultural, light agricultural, and research industrial zoning districts [link]
  • Farmersville, New York, Feb. 10, 2020:  height limit 455 ft, setbacks 3,000 ft to property line or well, 2,000 ft to roads, 1 mi to churches and schools including Amish homes and home schools; noise limit lower of 45 dBA at property line and 45 dBA outside dwelling or ambient + 10 dB(A), 10 dB added to nighttime (10pm–7am) levels; noise measurement specified, including C-weighted; shadow flicker on nonparticipating property limited to 8 hours/year and 1 hour/month; property value guarantee and decommissioning provisions [link]
  • Seville Township, Michigan, Jan. 13, 2020:  1,640-ft setback from nonparticipating property line [link]
  • Jefferson Davis Parish, Louisiana, Jan. 13, 2020:  3 mi from business or residence [link]
  • Farmersville and Freedom, New York, Jan. 6, 2020:  2019 law revoked, reverting from 600-ft height limit, 1.3× height setback at property line, and 50-dBA noise limit to 450-ft height limit.  Proposed [approved Jan. 30, 2020, by Cattaraugus County Planning Board]:  height limit 455 ft, setbacks 3,000 ft to property line, 2,000 ft to roads, 1 mi to churches; noise limit lower of 45 dBA at property line and 45 dBA outside dwelling or ambient + 10 dB(A), 10 dB added to nighttime (10pm–7am) levels; noise measurement specified, including C-weighted; shadow flicker on nonparticipating property limited to 8 hours/year and 1 hour/month; property value guarantee and decommissioning provisions [link]
  • Fell Township, Pennsylvania, Jan. 6, 2020:  setback 5× total height to property line, minimum 1,500 ft; noise limit at property line 45–55 dB, 42–52 dB 10pm–7am [link]
  • Mills County, Iowa, 2019:  height limits 80 ft, 150 ft in commercial zones, 200 ft in industrial zones [link]
  • North Rhine–Westphalia, Germany, 2019 [subject to public comment]:  setback 1.5 km from municipalities; banned from forests [link]
  • Ireland, Dec. 12, 2019 [subject to public consultation]:  setback 4× total height to residences, minimum 500 m; noise limit (L90,10 min) outside sensitive properties (e.g., residences) lesser of 5 dBA above existing 30–38 dBA background noise or 43 dBA, with penalties for tonal noise and amplitude modulation and a threshold for low-frequency noise; no shadow flicker at sensitive properties [link]
  • Sanford, New York, Dec. 10, 2019: setbacks 3× height from all permanent structures and off-site property lines, rights of way, easements, public ways, power lines, gas wells, and state lands, greater of 1,500 ft or 3× height from all off-site schools, hospitals, places of worship, places of public assembly, and residential structures; noise limits at nonparticipating property line of 45 dBA Leq (8-hour), 40 dBA average annual nighttime level, no audible prominent tone, no human-perceptible vibrations, 65 dB Leq at full-octave frequency bands of 16, 31.5, and 63 Hz, and 40 dBA (1-hour) from substation equipment; maximum shadow flicker 30 min/day, 30 h/year [link]
  • Sherwood Township, Michigan, Dec. 5, 2019:  height limit 330 ft; setbacks 5× height to nonparticipating property, 1 mi from village, 2 mi from environmentally sensitive areas [link]
  • Posey County, Indiana, Nov. 25, 2019 [subject to town and County Commission approvals]:  noise limit greater of 45 dB or 5 dB over ambient (L₉₀) at nonparticipating property line more than 10% of any hour; no shadow flicker at nonparticipating residence [link]; Jan. 3, 2021:  10 mi distance from Doppler radar site [link]
  • Thomas County, Nebraska, Oct. 2021:  setback 3 mi from property lines, roads, and wetlands; noise limit 35 dbA at residence [link]
  • Hamilton County, Nebraska, Sep. 19, 2021:  setback 2 mi from property line [link]
  • Portland, New York, Aug. 8, 2020:  setbacks 1,600 ft from residences, 1/2 mi from county parks [link]
  • Casnovia Township, Michigan, Oct. 2019:  setback 4× total height to nonparticipating property line; height limit 500 ft; 39 dBA nighttime noise limit and no shadow flicker on nonparticipating property [link]
  • Madison County, Iowa, Aug. 8, 2019:  Board of Health recommendation of 1.5 mi setback from nonparticipating property line, 2,100 ft from participating property line, 40 dBA noise limit at property line [link]; Sept. 8, 2019: County Board approves [link]
  • Montgomery County, Indiana, June 10, 2019:  setbacks greater of 2,640 ft (1/2 mi) or 5× height to property line (Board of Zoning Appeals may increase to 3,200 ft) and 1 mi from towns and schools; 32 dB(A) noise limit at property line; no shadow flicker on nonparticipating property; wells within 1 mi to be tested before and after [link]
  • Jasper County, Indiana, May 7, 2019:  setbacks greater of 2,640 ft (1/2 mi) or 6.5× height to nonparticipating property lines and 1 mi from nonparticipating existing residences, platted subdivisions, “institutional land uses” (e.g., schools), Iroquois and Kankakee Rivers, and confined feed lots; 35 dB(A) noise limit at nonparticipating property line; no shadow flicker on nonparticipating properties [link]
  • Sherwood Township, Michigan, June 13, 2019:  height limit 300 ft; setbacks 5× height to property line, 1/2 mi from water, 1 mi from Village of Sherwood, 2 mi from environmentally sensitive areas [link]
  • Monitor Township, Michigan, effective Apr. 29, 2019:  change of setback from 750 ft to 2,000 ft to nonparticipating or 1,640 ft to participating property line or right-of-way; no shadow flicker or strobe effect on nonparticipating property; no stray voltage; noise limits (Lmax) 45 dBA and 55 dBC at property line or anywhere within neighboring property, no detectable sound pressures of 0.1-20 Hz [link]
  • Worth, New York, Apr. 3, 2019:  setback 5× height to property lines, structures, and roads; 35 dB(A) noise limit during day, 25 dB(A) at night (7pm–7am) [link]
  • Kansas, introduced Feb. 12, 2019:  HB 2273: setbacks greater of 7,920 ft (1-1/2 mi) or 12× height from residential property lines or public building, greater of 3 mi or 12× height from any airport, wildlife refuge, public hunting area, or public park, and minimum 1,500 ft from any property line [link]
  • Nebraska, introduced Jan. 16, 2019 [subject to legislative approval]:  LB373: requires hosting counties to have wind ordinances restricting wind turbines within 3 mi of residence without owner’s permission and addressing noise and decommissioning [link]
  • Saline County, Nebraska, 2018:  setback 1/2 mi from neighboring dwelling; noise limit 40 dBA (10-min average) at any dwelling [link]
  • Redfield, New York, Dec. 11, 2018:  setback 5× height to property lines, structures, and roads; 35 dB(A) noise limit during day, 25 dB(A) at night (7pm–7am) [link]
  • Henry County, Indiana, Nov. 14, 2018:  setback 4 mi from town lines: Blountsville, Cadiz, Greensboro, Kennard, Lewisville, Mount Summit, Springport, Straughn, Sulphur Springs, Mooreland [link]
  • Richland, New York, Nov. 13, 2018:  setback 1 mi from property line; height limit 500 ft; 35 dB(A) (for more than 5 minutes) noise limit at residences [link]
  • Adair County, Iowa, Oct. 24, 2018:  setback 2,000 ft to nonparticipating home, 800 ft to property line [link]
  • Kosciusko County, Indiana, Oct. 16 2018:  setback greater of 3,960 ft or 6.5× height to property line, right-of-way, or power line, 1 mi from community or municipality boundary; 32 dB(A) noise limit at property line; no shadow flicker on nonparticipating property; no detectable vibration in nearby structures or that could damage wells; no interference with TV, radio, GPS, etc.; property value guarantees within 2 mi; notification to all within 5 mi [link]
  • Adams County, Nebraska, Oct. 2, 2018:  setback 2,400 ft to neighboring dwelling, 6,000 ft from turbines not owned by applicant [link]
  • Paint Township, Pennsylvania, Aug. 7, 2018:  height limit 335 ft; setback 1.5× height to buildings and roads, 2,500 ft to property line [link]
  • Greenwood, Maine, Aug. 6, 2018:  added height limit of 250 ft; lowered noise limits at nonparticipating property lines from 55 dB during day and 42 dB at night to, respectively, 35 and 25 dB; increased setback to nonparticipating property lines from 1.5× height to 1 mi per 100 ft height [link]
  • Dekalb County, Illinois, July 12, 2018 [approved by Board, 19-3, Nov. 21, 2018 (link)]:  setback 6× total height to property line, 3 mi to municipality; height limit 500 ft; noise limit of 35 dBA during day (7am–10pm) and 30 dBA at night; no shadow flicker or flash; no radiofrequency or electromagnetic interference [link]
  • North Dakota, July 1, 2018:  decommission and land reclamation plan, cost estimates, and financial assurance required [link]
  • Ingersoll Township, Michigan, May 14, 2018:  [link]
  • Beaver Township, Michigan, May 14, 2018:  setback 4× total height to property line, public roads, and transmission lines; height limit 500 ft; noise limit 45 dBA Lmax or 55 dBC Lmax (or ambient plus 5 dB if greater) at property line [link]
  • Shiawassee County, Michigan, May 8, 2018 [subject to County Board of Commissioners approval]:  setback 3.5× total height to nonparticipating property line (changed from 1.5×); height limit 450 ft (changed from 600 ft); 45 dB noise limit at property line (changed from 55 dB); no shadow flicker on nonparticipating property (changed from 20 hours/year) [link]
  • Almer Township, Michigan, Apr. 2018:  setback 4× total height to nonparticipating property line; height limit 500 ft; 45 dBA noise limit at property line; no shadow flicker on nonparticipating property; no stray voltage; decommissioning bond; all concrete to be removed [link]
  • Tennessee, Apr. 24, 2018:  setback 5× total height to nonparticipating property line; height limit 500 ft [link]
  • Miami County, Indiana, Apr. 11, 2018:  change of setback from 1,000 ft to 2,000 ft to property line [link]
  • DeWitt County, Illinois, Apr. 19, 2018:  change of setback from 1,500 ft to 2,000 ft to houses [link]
  • Pierce County, Nebraska, Mar. 26, 2018:  setback 2,700 ft to houses [link]
  • Maroa, Illinois, Mar. 26, 2018:  setback 1.5 mi from city border [link]
  • Hopkinton, New York, Apr. 26, 2018:  setback 5× total height to property line; 40 dBA noise limit at nonparticipating residence [link]
  • Burnside Township, Michigan, Feb. 26, 2018:  change of sound limit to 45 dBA Lmax (maximum) at property line [link]
  • Yates, New York, Feb. 8, 2018:  change of setback to nonparticipating property line from 3× height to greater of 6× height or 1/2 mi; greater of 6× height or 1/2 mi to residences, public rights of way, and boundaries with other towns; 1 mi to village boundaries, schools, churches, and cemeteries; 3 mi from Lake Ontario shoreline (per US Fish and Wildlife Service recommendation); change of noise limit from 45 dBA during day (7am–8pm) and 40 dBA at night to 42 dBA during day and 39 dBA at night (per Vermont Public Service Board recommendation) [link]
  • Somerset, New York, Jan. 29, 2018:  height limit 150 ft; industrial zones only; setback greater of 1/2 mi or 6× height to public roads, property lines, and residences; 3 mi from Lake Ontario shoreline; 42 dBA limit during day (7am–9pm), 35 dBA at night [link]
  • Wabash County, Indiana, Dec. 18, 2017:  32 dBA limit outside of primary structures; no vibrations detectable on nonparticipant property; no shadow flicker on nonparticipant property; setbacks 3/4 mi to nonparticipant residential structure, 1/2  to nonparticipant business structure, 3/8 mi to participant residence, greater of 1,000 ft or 2× height to public roads [link]
  • Rochester, Indiana, Dec. 4, 2017:  setback 3 mi from city limits [link]
  • Vermont, Nov. 22, 2017:  42 dBA limit 95% of the time 100 ft to nonparticipating residence during day (7am–9pm), 39 dBA at night (9pm–7am; goal to achieve interior sound level of ≤30 dB) [link]
  • Stanton County, Nebraska, Nov. 2017:  setback 2,700 ft from nonparticipating residence [link]
  • Dixfield, Maine, Nov. 7, 2017:  setbacks 2,000 ft to property line, 4,000 ft to occupied building or scenic or special resource; sound limits at property line of 42 dBA at night (7–7), 55 dBA at day within 4,000 ft; 5 dBA added to any average 10-minute sound level in which a tonal sound occurs, 5 dBA added to any average 10-minute sound level in which ≥5 short-duration repetitive sounds occur [link]
  • Clark County, South Dakota, Aug. 14, 2017 [subject to appeal ruling]:  change of setback from 1,000 ft to 3,960 ft (3/4 mi) to residences [link]
  • Antelope County, Nebraska [subject to county commission approval]:  change of setback from 2,000 ft to 2,700 ft to nonparticipating residence; maximum of 2 turbines within 4,000 ft of nonparticipating residence [link]
  • Parishville, New York, June 22, 2017:  setback 5× total height to property line; 45 dBA noise limit at nonparticipating residence during day (7am–7pm), 35 dBA at night (7pm–7am) [link]
  • Bethel, Maine, June 14, 2017:  setback 2 mi to property line; 25 dBA limit at property line 7pm–7am, 35 dBA 7am–7pm; height limit 250 ft [link]
  • Walworth County, South Dakota, May 10, 2017:  setback 2 mi to off-site residence, business, or church [link]
  • Lincoln County, South Dakota, May 2, 2017 [upheld by referendum, July 18, 2017 (link)]:  setback 1/2 mi to homes; 45 dB limit at property line; shadow flicker limits [link]
  • North Dakota, June 5, 2017:  aircraft detection required to minimize lighting at night [link]
  • Clayton County, New York, Apr. 26, 2017:  own use only; setback 5.5× height to property line [link]
  • Livingston County, Illinois, Apr. 20, 2017:  setback to participating homes changed from 1,200 ft to greater of 3,250 ft or 6× height; setback to property line 1,640 ft; state Pollution Control Board noise limits measured at residential property line [link]
  • County Westmeath, Ireland, Jan. 31, 2017:  setbacks from homes 500 m for heights >25 m to 50 m, 1,000 m for heights >50 m to 100 m, 1,500 m for heights >100 m to 150 m, and >2 km for heights ≥150 m [link]
  • Rush County, Indiana, Dec. 16, 2016:  project approved with setback 2,640 ft to nonparticipating property lines and height limit 200 ft; 32 dB limit at propertly line; no shadow flicker on neighboring property [link]
  • Wayne County, Indiana, Dec. 7, 2016:  zoning variance required for every turbine; large turbines not permitted: >100 ft tall, >50 kW, blade sweep >30 ft [link]
  • Hagerstown, Indiana, Nov. 22, 2016:  no structures over 100 ft height within 2 mi of town (extension of airport regulation) [link]
  • Sand Beach Township, Michigan, Oct. 2016 [approved by referendum, 413-80, May 2, 2017 (link)]:  40 dB limit at hosting residences during day, 35 dB at night; 35 dB and 30 dB for nonhosting residences [link]
  • Wabash County, Indiana, Oct. 17, 2016:  32 dBA limit outside of primary structures; shadow flicker at residential and business structures limited to 15 minutes per day, 4 days per year; setback 1/2 mi to nonparticipating residential or business structure [link]
  • Clayton County, New York, Sept. 27, 2016:  setback 1 mi to any structure, roadway, or property line; developers required to pay property owners for any damages or decreases in property value [link]
  • Palo Alto County, Iowa, Sept. 27, 2016:  setback 1,500 ft to dwellings and cemeteries [link]
  • L’Anse Township, Michigan, Aug. 10, 2016:  setback to nonparticipating property line (without easement) changed from 1,000 ft to 2,540 ft; height limit 500 ft [link]
  • County Laois, Ireland, Aug. 5, 2016 [augmented Mar. 29, 2017, by total ban (link)]:  setback 1.5 km to schools, dwellings, community centers, and public roads [link]
  • Newfield, New York, July 24, 2016:  setback 1,760 ft or 3× blade radius to property line without lease or easement [link]
  • Tipton County, Indiana, July 2016:  setbacks 2,640 ft from residences, 1,500 ft from property lines [link]
  • Letcher Township, South Dakota, June 8, 2016; effective July 1, 2016:  setbacks 1 mi to nonparticipating residence and 1,500 ft to property line [link]
  • Poland, May 2016 (revoked to 700 m setback March 2023):  setback 10× total height of turbine to housing [link]
  • Gage County, Nebraska, Mar. 30, 2016:  45 dB limit at nonparticipating properties during day, 40 dB at night (10pm–7am); setback 3/8 mi to nonparticipating residence [link]
  • New Hampshire, Dec. 15, 2015:  sound limits: greater of 45 dBAL90 or 5 dBA above background level during day (8–8), 40 dBA during day, greater of 40 dBAL90 or 5 dBA above background level at night at any temporary or permanent residence; shadow flicker: no more than 8 hours per year at or in any residence, learning space, workplace, health care setting, outdoor or indoor public gathering area, or other occupied building [link]
  • Freedom, Maine, Nov. 17, 2015:  13× height setback to property line, 4× height to public roads, 2,500 ft to special resources; sound limits 5 dBA above preconstruction ambient level, 40 dBA during day, and 35 dBA at night at property line, and 20 dBC above preconstruction ambient dBA level at property line and inside dwellings [link]
  • Lancaster County, Nebraska, Nov. 10, 2015:  sound limits at exterior wall of dwellings 40 dBA and 3 dBA above background (by 10-minute average, Leq,10min) from 7am to 10pm, 37 dBA from 10pm to 7am [link]
  • Boone County, Illinois, Nov. 4, 2015:  change of setback from 1,000 ft to 2,640 ft (1/2 mi) to property line [link]
  • Emmet County, Michigan, Oct. 15, 2015:  change of setback from 1,000 ft to 2,640 ft (1/2 mi) to property line [link]
  • Oklahoma, Aug. 21, 2015:  set back 1.5 mi from public school, hospital, or airport [link]
  • Catlin, New York, July 9, 2015:  height limit 400 ft;, noise limit 40 dBA at property line [link]
  • Rush County, Indiana, July 1, 2015 (upheld by trial court May 27, 2016, appeals court Feb. 14, 2017, and supreme court May 25, 2017 [link]):  project approved with change of setback to 2,300 ft to residences and property line [link]
  • Peru, Massachusetts, June 6, 2015:  height limit [link]
  • Garden Township, Michigan, June 1, 2015:  35 dBA or 50 dBC limit at property line from 10pm to 6am [link]
  • Iroquois County, Illinois, Apr. 14, 2015:  change of setback to property line from 1,500 ft to 12 rotor diameters [link]
  • Cleburne County, Alabama, Feb. 9, 2015 [needs state approval]:  2,500 ft setback to property line, 40 dB sound limit [link]
  • Howard County, Indiana, Jan. 5, 2015:  change of setback from 1,500 ft to 2,000 ft from property line and noise limit at neighboring residence from 50 dBA to 40 dBA [link]
  • Pictou County, Nova Scotia, Jan. 5, 2015:  1,000 m setback, 600 m with consent of homeowner [link]
  • Bavaria, Germany, Nov. 21, 2014:  10× height setback to homes, 800 m to other dwellings [link]
  • Adams Township, Michigan, Oct. 2014, affirmed Apr. 13, 2015 [link]:  3,000 ft setback to lines, roads, and homes [link]
  • Plympton-Wyoming, Ontario, Oct. 8, 2014; repealed under threat of lawsuit May 27, 2015 [link]:  50 dB average, +10 dB peak infrasound limit inside dwellings; 15 dBC or 20 dB infrasound limit over dBA level inside or outside dwellings; amplitude modulation limit indoors of 2 mPa RMS for 10 seconds out of any 40 seconds [link]
  • Mason County, Kentucky, Sept. 30, 2014:  wind turbines >50 kW in already-designated industrial zones only; 1 mi setback of turbines, substations, and maintenance/operation facilities to property line, residences/regularly used buildings, residential zones, rights of way, wetlands, etc.; 30 dBA and 50 dbC limits at property line [link]
  • Buckland, Massachusetts, Sept. 25, 2014:  limits of 250 kW capacity and 120 ft height, setbacks 360 ft to property line and half-mile to off-site residence [link]
  • County Offaly, Ireland, Sept. 15, 2014:  setback 2 km from towns and villages [link]
  • Fairview Township, Pennsylvania, Aug. 4, 2014:  height limit 350 ft, setbacks 1,500 ft to property lines and bodies of water, 1.1× height to roads [link]
  • Dallas County, Iowa, July 29, 2014:  setbacks 2,640 ft from residence, school, hospital, church, or public library, 2 mi from sensitive natural resource areas, wildlife management areas, prairies, wetlands, forested areas, etc.; 30 dBA noise limit at property line of any dwelling, school, hospital, church, or public library [link]
  • County Donegal, Ireland, June 30, 2014 [cancelled by Minister Oct. 6, 2016; reinstated Mar. 27, 2017]:  setback 10× tip height to places of residence or public assembly [link]
  • Ohio, June 16, 2014:  change of setback (1,125 ft from blade tip) to property line (from house) [link]
  • Schoolcraft County, Michigan, June 5, 2014:  setbacks 3,960 ft (3/4-mi) to dwellings and businesses, 1 mi to scenic areas, parks, highways; 35 dB(A) limit at property line, ambient plus 5 dB limit at dwellings [link]
  • Etowah County, Alabama, Mar. 19, 2014:  40 dB limit at property line, 2,500 ft setback from property line [link]
  • Cherokee County, Alabama, Mar. 18, 2014:  40 dB limit at property line, 2,500 ft setback from property line [link]
  • DeKalb County, Alabama:  40 dB limit at property line, 2,500 ft setback from property line [link]
  • Granville, Pennsylvania, May 5, 2014:  setbacks 2,000 ft to property line and participating residence and 2,500 ft to nonparticipating residence, 45 dBA or 45 dBC limit at property line [link]
  • Carteret County, North Carolina, Feb. 26, 2014:  change of setback to 1 mi (from 6× height), plus 275 ft height limit and 35 dB limit (for more than 5 min) at property line [link]
  • Iredell County, North Carolina:  350 ft height limit, 30 dB noise limit at property line [link]
  • Ashe County, North Carolina:  199 ft height limit [link]
  • County Offaly, Ireland, Sept. 15, 2014:  setback 2 km from towns and villages [link]
  • Kentucky, 2014:  setbacks 1,000 ft from property lines, 2,000 ft from residential neighborhood, school, hospital, or nursing home facility [link]
    • Eastern Kings, Prince Edward Island, 2013:  setbacks 4× height to participating dwelling, 3,280 ft (1,000 m) to nonparticipating dwelling [link]
    • Saxony, Germany, July 12, 2013:  setback 1,000 m to residence [link]
    • Noble County, Indiana, May 2013:  3/4 mi to residence [link]
    • Whitley County, Indiana, May 2013:  greater of 1/2 mi or 6.5× height to residence [link]
    • Woodstock, Maine, Mar. 25, 2013:  setback 1 mi to property line; 35 dBA limit at property line 7pm–7am, 45 dBA 7am–7pm [link]
    • Crook County, Wyoming, June 6, 2012:  setbacks greater of 5× height or 1 mi from residence, 1/2 mi from city or town [link]
    • Pratt County, Kansas, May 12, 2012:  3,960 ft to residence [link]
    • Wisconsin, Mar. 15, 2012:  1.1× height to property line, 1,250 ft to any residence [link]
    • Bingham County, Idaho, 2012:  3× height to property line, 1 mi platted Town sites and cities [link]
    • Haut-Saint-Laurent, Montérégie, Québéc, Jan. 9, 2013:  2 km setback [link]
    • Denmark, Dec. 15, 2011:  addition of 20 dB low-frequency (10–160 Hz) limit (day and night) inside homes [link]
    • Frankfort, Maine, Dec. 1, 2011:  1 mi setback to property line, noise limits within 2 mi 35 dB day, 25 dB night [link] [repeal rejected Nov. 4, 2014; link]
    • Victoria, Australia, Aug. 29, 2011:  2 km setback without consent of homeowner [link]; reduced to 1 km Mar. 2015 [link]
    • Umatilla County, Oregon, June 28, 2011:  change of setback to 2 mi from “urban grown boundary”, 1 mi from "unincorporated community" zones (from 3,520 ft) [link]
    • Barnstable County (Cape Cod), Massachusetts, Apr. 20, 2011:  10× rotor diameter to property line [link]
    • Centerville Township, Michigan, Aug. 18, 2010:  height limit 199 ft; setback 10× rotor diameter to property line or road; noise limits at property line 35 dBA or 5 dBA above background during day, 3 dBA above background at night, with low-frequency limits and tonality penalty [link]
    • Klickitat County, Washington, Aug. 17, 2010:  setback 1,600 ft to residences [link]
    • Allegany County, Maryland, Jan. 1, 2010:  setbacks 2,000 ft to homes, 5,000 ft to schools [link]
    • Dixmont, Maine, 2009:  setback 2,500 ft from neighboring residential property line [link]
    • Kearny County, Kansas, 2009:  setback 2,000 ft from property line [link]

    July 16, 2014

    The Oxen at the Intersection: Review

    A Collision (or, Bill and Lou Must Die: A Real-Life Murder Mystery from the Green Mountains of Vermont), by pattrice jones (2014, Lantern Books)


    This book is a page-turner. Jones is an excellent writer. She provides not only a history of the whole fiasco of the plan to kill rather than retire the oxen Bill and Lou, and the efforts to save them, but also a concise overview of the mythologies, intersections of power relationships and prejudice, and psychologies that came into play. It is both a valuable case study for social activists and a good introduction to the holistic anti-oppression perspective of eco-feminism.

    Regarding the case itself, Jones seems to betray some personal rancor over what can well be seen as "hijacking" of the issue by others not directly involved (Jones' sanctuary had been approached by concerned alumni). Critiques of some of those are warranted, but they probably wouldn't have mattered if there was more direct "face-to-face" interaction, which Jones notes as perhaps the biggest shortcoming. However, she doesn't acknowledge the difficulty of direct action in this case: Poultney is rather far from everywhere as well as unfamiliar to almost all of the activists involved. And rights activists in Vermont simply do not go against the farming industry. Even the abuses revealed in late 2009 by HSUS at Bushway Packing, an "Animal Welfare Approved" slaughterhouse where organic dairy farms sent their male calves to be turned into veal, made barely a ripple. In another case in the late 2000's, a jogger in Greensboro noticed a pile of dead and dying animals on a farm, alerted authorities, and – nothing happened. As in these cases, the media, when they paid attention at all, only helped to support the "right-to-farm" viewpoint and discourage questioning of what farmers actually do to their animals.

    One interesting and damning aspect of the Green Mountain College farm program is revealed in the book regarding their treatment of animals. Jones describes Princess, a cow who was given to them from someone who had bought her from an "agricultural college". It was clear that Princess had been abused (beyond the "normal" routines of animal ag), and Jones had written about her just before the Bill and Lou affair began, not knowing what college she had come from. When the campaign to save Bill and Lou began, people at the college recognized Princess and accused Jones of a concerted campaign against them. Jones also describes the visit of a couple of her colleagues during an open house at the college, where they saw a calf with so many burrs around his penis that he couldn't easily urinate. That calf was later sold, no questions asked, on Craig's List, with the stipulation that the buyer never reveal where they got it – which appears to have been a condition for saving Princess as well. As Jones points out, the head of the college farm program is a mathematician. It is an extension of his own hobby farm, with the added inexperience (and callousness) of college students. The animals seem to be neglected and abused and then disposed of, without acknowledgement, when they become too much trouble. As Jones also notes from the visit, the college garden was smaller than the one at their sanctuary. And as satellite pictures show, the college's acres of meadow are far from enough to sustain more than a very few animals (for meat, that is; used for produce, they could in fact feed quite a few humans). In other words, the farm is a sham, but worse, the animals are treated like toys for these very unserious dabblers.


    Princess

    Back to the problem of direct communication, as Jones makes clear, the bottom line was that the college was not at all open to discussion, even within their own walls. They were determined to prove a point, their authority, their "mastery". Closed off as they were, then, it was clearly the chaotic clamor of the social media–fired campaign to save Bill and Lou that at least saved Bill (whose actual fate, however, remains a mystery; for that matter, the actual fate of Lou also remains a mystery). And as Jones notes, it was the uncontrolled barrage of telephone calls to nearby slaughterhouses that stopped the original scheduled plan to turn both of them into hamburgers.

    Jones also mentions her doubts about the effectiveness of gory photos and videos of animal abuse and suffering in the fight for animal rights. I agree. People are already desensitized and, as the "conscious carnivore" pushback shows, actually relish the fact that a life is sacrificed for their passing enjoyment. As the chef in Peter Greenaway's film "The Cook, the Thief, his Wife, and her Lover" observes, people like to feel that they are eating death. Shocking pictures only serve to reinforce the very viewpoint we are attempting to change. As with the picture of the Green Mountain College student grinning maniacally in a hand-scrawled "Death to Chickens" T-shirt holding a dead rooster up by its legs, or the students screaming at protesters that even though they're "vegetarian" they were "excited" to eat Bill and Lou, the people who need to be persuaded away from harming animals are more likely to embrace the imagery, to fling it back defiantly. Disturbing pictures can be effective – if they are used effectively for specific messages and/or to specific audiences, not for indiscriminate shock value.

    Anyhow, this book is a stimulating and inspiring read, an insightful analysis of the mostly failed effort to save these two lives. It is also very nicely typeset.


    Last known photograph of Lou and Bill, Nov. 10, 2012.
    Lou was reportedly killed before dawn of the next day.

    environment, environmentalism, human rights, animal rights, vegetarianism, veganism, Vermont, ecofeminism

    July 2, 2014

    Vermont's Greenhouse Gas Emissions

    According to the Vermont Agency of Natural Resources, in 2011, Vermont’s greenhouse gas (GHG) emissions were approximately 8.11 million metric tons carbon dioxide equivalent. This represents a return to 1990 levels.
    • 46% of those emissions were from transportation
    • 32% from residential / commercial / industrial fuel use
    • 10% from agriculture
    • 5% from electricity consumption
    • 4% from various industrial processes
    • 3% from waste in landfills
    Note that electricity consumption is a very minor contributor (granted, that’s due in large part to the Vermont Yankee nuclear plant in Vernon, which is closing down later this year; but it’s also due to the predominance of hydro, especially that imported from Québec). So it seems all the more stupid to wreck the state’s ridgeline ecosystems to erect strings of giant wind turbines, which at best amount to little more than merely symbolic greenwashing anyway, or to pave acres of open fields with solar panels.


    Wind turbine platform and road, Lowell Mountain - photo by Steve Wright

    Also see: 
    How many cows is wind energy equal to?
    Vermont’s Rumsfeld Strategy [bombing the wrong targets]

    environment, environmentalism, Vermont

    June 17, 2014

    Why Not Wind: an open letter

    To whom it may concern:

    This is a brief representation of the reasons industrial-scale wind is a destructive boondoggle that only fools – or worse – would approve.

    Unlike “conventional” power sources, wind does not follow demand. As the Bonneville Power Authority in the Pacific Northwest of the USA has shown (www.wind-watch.org/pix/493), the relationship between load and wind generation is essentially random. That means that wind can never replace dispatchable sources that are needed to meet actual demand.

    The contribution of wind generation is therefore an illusion, because the grid has to supply steady power in response to demand, and as the wind rises and falls, the grid maintains supply by relying on its already built-in excess capacity.

    That is also why meaningful reductions in carbon emissions are not seen: because fuel continues to be burned in “spinning reserve” plants which are kept active to kick into electricity production when needed for meeting surges in demand or, now, drops in the wind. Denmark’s famously high wind penetration is possible only because it is connected to the large Nordic and German grids – so that Denmark’s wind power actually constitutes a very small fraction of that total system capacity. To make further wind capacity possible (despite a public backlash that has essentially stopped onshore wind development since 2003), Denmark is now building a connection to the Dutch grid.

    Another reason that meaningful reductions in carbon emissions are not seen is that the first source to be modulated to balance wind is usually hydro. This is seen quite clearly in Spain, another country with high wind penetration: The changes in electricity from hydro are an almost exact inverse of those from wind (https://demanda.ree.es/generacion_acumulada.html). This is also seen in the USA’s Pacific Northwest (http://transmission.bpa.gov/business/operations/Wind/baltwg.aspx).

    Finally, on systems with sufficient natural gas–powered generators, which can ramp on and off quickly enough to balance wind’s highly variable infeed, wind forces those generators to operate far less efficiently than they would otherwise. It is like stop-and-go city versus steady highway driving. According to several analyses (e.g., www.wind-watch.org/doc/?p=1568), the carbon emissions from gas + wind are not significantly different from gas alone and in some cases may be more.

    And again, whatever the effect, wind is always an add-on. The grid must be able to operate reliably without it, because very often, and often for very long stretches of time, wind is indeed in the doldrums: It is not there.

    And beware the illusion of “average” output. The fact is that any wind turbine or group of turbines generates at or above its average rate (which is typically 20%–30% of the nameplate capacity, depending on the site) only about 40% of the time. Because of the physics of extracting energy from wind, the rest of the time production approaches zero.

    As an add-on, therefore, its costs are completely unnecessary and wasteful. And even if, by some miracle, it were a reliable, dispatchable, reasonably continuous source, its costs would still be enormous – not only economically, but also environmentally. Wind is a very diffuse resource and therefore requires a massive mechanical system to catch any useful amount. That means ever larger blades on ever taller towers in ever larger groupings. And the only places where that is feasible are the very places we need to preserve as useful agricultural land, scenic landscapes that are so important to our souls (and to tourism), and wild land where the natural world can thrive.

    Besides the obvious damage to the land of heavy-duty roads for construction and continued maintenance, huge concrete platforms, new powerlines, and substations (while making no meaningful contribution to the actual operation of the grid) and the visual intrusion of 150-metre (500-ft) structures with strobe lights and rotating blades, there are serious adverse impacts from the giant airplane-like blades cutting through 6,000–8,000 square metres (1.5–2 acres) of vertical airspace both day and night: pulsating noise (including infrasound which is felt more than heard) that carries great distances and disturbs nearby residents (especially at night, when there is a greater expectation of – and need for – quiet and atmospheric conditions often augment the noise), even threatening their physical health, pressure vortices that kill bats by destroying their lungs, blade tip speeds of 300 km/h that also kill bats as well as birds, particularly raptors, many of which are already endangered, and vibration that carries through the tower into the ground with effects on soil integrity and flora and fauna that have yet to be studied.

    In short, the benefits of industrial-scale wind are minuscule (if that), while its adverse impacts and costs are great. Its only effect is to provide greenwashing (and tax avoidance) for business-as-usual energy producers and lip-service politicians, while opening up to vast industrial development land that has been otherwise fiercely protected – most disturbingly by many of the same groups now clamoring for wind.

    Industrial-scale wind is all the more outrageous for the massive flow of public money into the private bank accounts of developers. It is not surprising to learn that Enron established the package of subsidies and regulatory “innovations” that made the modern wind industry possible. Or that in Italy, the Mafia was an early backer of developers. It is indeed a criminal enterprise: crony capitalism, anti-environment rapaciousness, and hucksterism at its most duplicitous.

    After decades of recorded experience, there is no longer any excuse to fall for it.

     ~~
    Eric Rosenbloom
    President, National Wind Watch, Inc. (www.wind-watch.org)

    Mr Rosenbloom lives in Vermont, USA, where he works as a science editor, writer, and typographer. He has studied and written about wind energy since 2003. He was invited to join the board, and then elected President (a wholly volunteer position), of National Wind Watch in 2006, a year after it was founded by citizens from 10 states who met to share their concerns about the risks and impacts of wind energy development. National Wind Watch is a 501(c)(3) educational charity registered in Massachusetts.

    wind power, wind energy, environment, environmentalism, human rights, animal rights, Vermont, anarchism, ecoanarchism, anarchosyndicalism

    May 18, 2014

    Betraying the Environment

    Suzanna Jones writes at Vt. Digger:

    There is a painful rift among self-described environmentalists in Vermont, a divide that is particularly evident in the debate on industrial wind. In the past, battle lines were usually drawn between business interests wanting to “develop” the land, and environmentalists seeking to protect it. Today, however, the most ardent advocates of industrial buildout in Vermont’s most fragile ecosystems are environmental organizations. So what is happening?

    According to former New York Times foreign correspondent Chris Hedges, this change is symptomatic of a broader shift that has taken shape over many years. In his book “Death of the Liberal Class,” Hedges looks at the failure of the Left to defend the values it espouses – a fundamental disconnect between belief and action that has been corrupting to the Left and disastrous for society as a whole. Among other things, he argues, it has turned liberal establishments into mouthpieces for the power elite.

    Historically, the liberal class acted as watchdog against the abuses of capitalism and its elites. But over the last century, Hedges claims, it has traded that role for a comfortable “seat at the table” and inclusion in “the club.” This Faustian bargain has created a power vacuum – one that has often been filled by right-wing totalitarian elements (think Nazi Germany and fascist Italy) that rise to prominence by ridiculing and betraying the values that liberals claim to champion.

    Caving in to the seduction of careerism, prestige and comforts, the liberal class curtailed its critique of unfettered capitalism, globalization and educational institutions, and silenced the radicals and iconoclasts that gave it moral guidance – “the roots of creative and bold thought that would keep it from being subsumed completely by the power elite.” In other words, “the liberal class sold its soul.”

    From education to labor to agriculture and environmentalism, this moral vacuum continues to grow because the public sphere has been abandoned by those who fear being labeled pariahs. Among the consequences, Hedges says, is an inability to take effective action on climate change. This is because few environmentalists are willing to step out of the mainstream to challenge its root causes – economic growth, the profit system, and the market-driven treadmill of consumption.

    Hedges’ perspective clarifies a lot. It explains why so many environmental organizations push for “renewable” additions to the nation’s energy supply, rather than a reduction of energy use. It explains why they rant and rail against fossil fuel companies, while studiously averting their eyes from the corporate growth machine as a whole. In their thrall to wealthy donors and “green” developers (some of whom sit on their boards), they’ve traded their concern about the natural world for something called “sustainability” – which means keeping the current exploitive system going.

    It also makes clear why Vermont environmental organizations like the Vermont Public Interest Research Group and the Vermont Natural Resources Council – as well as the state’s political leadership – have lobbied so aggressively to prevent residents from having a say regarding energy development in their towns. By denying citizens the ability to defend the ecosystems in which they live, these groups are betraying not only the public, but the natural world they claim to represent. Meanwhile, these purported champions of social justice turn their backs as corporations like Green Mountain Power make Vermonters’ homes unlivable for the sake of “green” energy.

    Hedges’ perspective also explains why environmental celebrity Bill McKibben advocates the buildout of industrial wind in our last natural spaces – energy development that would feed the very economy he once exposed as the source of our environmental problems. Behind the green curtain are what McKibben calls his “friends on Wall Street,” whom he consults for advice on largely empty PR stunts designed to convince the public that something is being accomplished, while leaving the engines of economic “progress” intact. Lauded as the world’s “Most Important Environmental Writer” by Time magazine, McKibben’s seat at the table of the elites is secured.

    In this way the “watchdogs” have been effectively muzzled: now they actually help the powerful maintain control, by blocking the possibility for systemic solutions to emerge.

    Environmentalism has suffered dearly at the hand of this disabled Left. It is no longer about the protection of our wild places from the voracious appetite of industrial capitalism: it is instead about maintaining the comfort levels that Americans feel entitled to without completely devouring the resources needed (at least for now). Based on image, fakery and betrayal, it supports the profit system while allowing those in power to appear “green.” This myopic, empty endeavor may be profitable for a few, but its consequences for the planet as a whole are fatal.

    Despite the platitudes of its corporate and government backers, industrial wind has not reduced Vermont’s carbon emissions. Its intermittent nature makes it dependent on gas-fired power plants that inefficiently ramp up and down with the vicissitudes of the wind. Worse, it has been exposed as a Renewable Energy Credit shell game that disguises and enables the burning of fossil fuels elsewhere. It also destroys the healthy natural places we need as carbon “sinks,” degrades wildlife habitat, kills bats and eagles, pollutes headwaters, fills valuable wetlands, polarizes communities, and makes people sick­ – all so we can continue the meaningless acts of consumption that feed our economic system.

    Advocates for industrial wind say we need to make sacrifices. True enough. But where those sacrifices come from is at the heart of our dilemma. The sacrifices need to come from the bloated human economy and those that profit from it, not from the land base.

    We are often told that we must be “realistic.” In other words, we should accept that the artificial construct of industrial capitalism – with its cars, gadgets, mobility and financial imperatives – is reality. But this, too, is a Faustian bargain: in exchange we lose our ability to experience the sacred in the natural world, and put ourselves on the path to extinction.

    [See also: 
    Exploitation and destruction: some things to know about industrial wind power” (2006)
    Thought for the day: left vs. right

    wind power, wind energy, environment, environmentalism, human rights, animal rights, Vermont, anarchism, ecoanarchism

    February 22, 2014

    The real agenda of school choice opponents: protecting privilege

    Perhaps Steve Nelson should have heeded his feelings of “caution and ambivalence” before submitting his jeremiad against school choice (“Real Agenda of School-Choice Advocates,” Valley News [West Lebanon, N.H.], January 5). It is difficult to imagine a more awkward and inappropriate source of such a lamentation than the head of an expensive private school in Manhattan [The Calhoun School].

    Nelson is rightly concerned about quality, but erroneously states, “The one comprehensive study done to date shows that charters on balance do slightly worse than the public schools they replaced.” Assuming that he is referring to the “National Charter School Study” by the Stanford University Center for Research on Education Outcomes (CREDO), the 2013 report actually states that “charter schools now advance the learning gains of their students more than traditional public schools in reading[, and] academic growth of charter students in math [...] is now comparable to the learning gains in traditional public schools.” CREDO also separately studied Louisiana, which Nelson singled out for condemnation: “The charter school sector in Louisiana has a trend of strong results.”

    Obviously, not all private or charter schools are commendable, voucher systems are far from ideal, and profiteers exploiting a real need are rightly decried. But students who are failed by their public school don’t have time to wait for improvements. They need those alternatives now. It certainly doesn’t help to accuse their parents of tearing apart “the connective tissue of our nation” for trying to do what’s best for their children.

    Since Nelson defended his own alternative school as decidedly not rending “America’s social fabric,” he would have done better to suggest more progressive ways to expand such options for others. As noted by Ginia Bellafante in the same day’s New York Times, Mayor Bill De Blasio’s newly appointed Schools Chancellor, Carmen Fariña, has high praise for a network of charter schools serving the poorest neighborhoods of Brooklyn. And the cover story of the Valley News featured the Ledyard Charter School, which impressively meets the needs of many area students for an alternative to the regular high schools. Not only the schools and students, but society as a whole would clearly benefit from more support for such alternatives.

    A progressive approach to education requires choice for all, not just the rich.

    human rights, Vermont