Patterns of Bat Fatalities at Wind Energy Facilities in North America
Bibliographic record
Abstract
Abstract Wind has become one of the fastest growing sources of renewable energy worldwide, but widespread and often extensive fatalities of bats have increased concern regarding the impacts of wind energy development on bats and other wildlife. We synthesized available information on patterns of bat fatalities from a review of 21 postconstruction fatality studies conducted at 19 facilities in 5 United States regions and one Canadian province. Dominance of migratory, foliage‐ and tree‐roosting lasiurine species (e.g., hoary bat [ Lasiurus cinereus ]) killed by turbines was consistent among studies. Bat fatalities, although highly variable and periodic, consistently peaked in late summer and fall, coinciding with migration of lasiurines and other species. A notable exception was documented fatalities of pregnant female Brazilian freetailed bats ( Tadarida brasiliensis ) in May and June at a facility in Oklahoma, USA, and female silver‐haired bats ( Lasionycteris noctivagans ) during spring in Tennessee, USA, and Alberta, Canada. Most studies reported that fatalities were distributed randomly across turbines at a site, although the highest number of fatalities was often found near the end of turbine strings. Two studies conducted simultaneously in the same region documented similar timing of fatalities between sites, which suggests broader patterns of collisions dictated by weather, prey abundance, or other factors. None of the studies found differences in bat fatalities between turbines equipped with lighting required by the Federal Aviation Administration and turbines that were unlit. All studies that addressed relationships between bat fatalities and weather patterns found that most bats were killed on nights with low wind speed (<6 m/sec) and that fatalities increased immediately before and after passage of storm fronts. Weather patterns may be predictors of bat activity and fatality; thus, mitigation efforts that focus on these high‐risk periods could reduce bat fatality substantially. We caution that estimates of bat fatality are conditioned by length of study and search interval and that they are biased in relation to how searcher efficiency, scavenger removal, and habitat differences were or were not accounted for. Our review will assist managers, biologists, and decision‐makers with understanding unifying and unique patterns of bat fatality, biases, and limitations of existing efforts, and it will aid in designing future research needed to develop mitigation strategies for minimizing or eliminating bat fatality at wind facilities.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.002 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.003 | 0.003 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".