Collision Risk Analysis for Wind Farms: A Practical Pre-Construction Guide from Field Data to Final Risk

by | Dec 16, 2025 | Blog, News | 0 comments

Wind energy has become one of the cornerstones of modern energy systems. It is renewable, scalable, and plays a critical role in reducing greenhouse gas emissions and dependence on fossil fuels. For many regions, wind farms are no longer an exception but a standard part of energy infrastructure planning.

At the same time, wind farms are built in open landscapes—ridges, plains, coastal zones—precisely because these areas offer strong and consistent wind. These landscapes are also used by birds for flight, foraging, migration, and dispersal. As a result, wind energy and bird ecology sometimes intersect in physical space.

This intersection does not automatically imply a problem.

Most birds avoid turbines successfully, and many wind farms operate with minimal or negligible impacts on bird populations. However, for certain species, under specific conditions, wind turbines can pose a collision risk. Whether that risk is relevant or insignificant cannot be assumed—it needs to be quantified.

Gyps fulvus

This is where Collision Risk Analysis (CRA) comes in.

Collision Risk Analysis is a pre-construction assessment used to estimate how often birds may collide with turbine blades once a wind farm is operational. Its purpose is not to argue for or against wind energy, but to provide an evidence-based evaluation that allows developers, regulators, and conservation authorities to make informed decisions.

CRA is carried out before construction, when turbine layouts can still be adjusted, mitigation measures planned, and uncertainties addressed. It translates field observations of bird flight behaviour into a predictive framework that estimates collision risk under realistic operating conditions.

Importantly, CRA acknowledges two key facts at the same time:

  • Wind farms are an essential component of sustainable energy systems.

  • Wildlife impacts, where they exist, should be identified, assessed, and managed responsibly.

Rather than relying on assumptions or general statements, CRA provides a standardized way to answer a practical question:

How often are birds expected to enter the rotor-swept area of turbines, and what is the likelihood that this results in a collision?

To answer that, CRA combines ecological data (such as bird flight activity and height) with technical information about turbines (such as rotor size and rotation speed). The result is a quantitative estimate of collision risk, usually expressed on a monthly and annual basis for individual species.

This approach allows potential impacts to be:

  • compared between species,

  • evaluated across seasons,

  • and placed into a broader ecological and regulatory context.

Once the rationale for Collision Risk Analysis is clear, the methodology itself becomes much easier to understand. What follows is not a checklist, but a structured way of thinking about how birds move through space—and how wind turbines operate within that same space.

Wind farms

The Practical Guide: How to Do Collision Risk Analysis Step by Step (Pre-Construction)

You’ve got the “why.” Now you want the “how.”

Here’s the good news: pre-construction collision risk analysis is not magic. It’s a repeatable process that turns field observations into a quantitative estimate of risk.

Here’s the other good news: you don’t need a PhD to follow it. You just need to be disciplined about units, and consistent about what each number represents.

Think of CRA like cooking: if you measure ingredients correctly, the recipe works. If you eyeball the salt, you might ruin dinner.

Let’s walk through it.


Step 0: Define your turbine geometry (because it controls “the danger zone”)

Before you touch bird data, define the rotor-swept height band. This is the vertical slice of air where collisions can happen.

You need:

  • Hub height (H) = height of the rotor center above ground

  • Rotor radius (R) = half the rotor diameter

The rotor-swept band is:

Lower tip height = H − R
Upper tip height = H + R

Everything else in the analysis depends on this, because birds flying outside that band cannot collide with blades.


Step 1: Collect flight activity data (Vantage Point surveys)

The basic idea of a vantage point (VP) survey is simple:

  • you sit at a fixed location,

  • you scan a defined area (of construction site),

  • and you record every relevant flight you observe.

But CRA requires one specific type of VP output:

time spent flying (not just “number of birds”).

That’s why CRA loves bird-seconds:

  • one bird flying for 60 seconds = 60 bird-seconds

  • three birds flying for 20 seconds each = also 60 bird-seconds

This is the best way to capture “how much airspace use” is happening.

For each observation you typically need:

  • species

  • flight duration (seconds)

  • flight height band (or estimate)

  • where it occurred (inside your study area)

  • which VP recorded it

  • time spent observing (effort)


Step 2: Decide how you’ll treat multiple VPs (this matters a lot)

Take time to plan how to set up Vantage Points during the planning phase, and your life will be easier during analysis!

If you have more than one VP, you have two common situations:

  1. VPs observed simultaneously
    You need to avoid double-counting the same flight.

  2. VPs observed at different times (not simultaneous)
    This is simpler: you can combine them as independent samples of the same site.

In pre-construction work, the second case is very common. In that case, you typically produce one final monthly dataset by aggregating across VPs.

The key principle: combine VPs in a way that respects effort (how long you watched) and the area you covered (how much space you could see). YOu also need to be aware if any of the VPs view areas overlap, for the calculation of visibility area.


Step 3: Calculate DA (bird density in the air)

This is where CRA becomes “a model” and not just “a survey summary.”

The Band approach wants a measure called:

DA_birds_km² = average instantaneous density of flying birds (birds per km²), at any height.

Here’s the cleanest way to compute it from VP data:

DA = total bird-seconds / (observation seconds × visible area in km²)

*there are other ways of calculating DA, but I am just talking how we do it in BIOTA.

Let’s translate that:

  • total bird-seconds = sum of all flight durations for that species in that month

  • observation seconds = total time you spent watching during that month

  • visible area (km²) = the area of airspace you were effectively sampling from VPs

This produces something intuitive:

“At a random moment, how many birds of this species are typically in the sky above one square kilometre?”

If you only remember one “don’t mess this up” rule, it’s this:

***DA divides by area.
It does not multiply by area.


Step 4: Calculate Q2R (the fraction of activity inside rotor height)

DA tells you “birds are in the air.”
Q2R tells you “how much of that air use is inside the rotor height.”

Q2R is simply the proportion of your recorded flight time that falls inside the rotor band:

Q2R = bird-seconds inside (H−R to H+R) / total bird-seconds (all heights)

If your VP data is stored by height bands, this is easy:

  • sum the time in bins that fall inside rotor heights

  • divide by total time across all height bins

If a height band overlaps the rotor boundary, you can approximate by splitting proportionally by bin width. For most pre-construction assessments, a reasonable approximation is acceptable as long as you document it.

Step 5: Choose v (flight speed) for each species

Flight speed is needed because faster birds pass through the rotor plane differently than slow ones.

You usually do not measure this on site in EIAs. Instead you use:

  • literature values,

  • standard CRM defaults,

  • or expert-accepted typical speeds.

The key is consistency:

  • use one defensible mean speed per species,

  • document the source,

  • don’t mix random numbers from different websites.

Wind farms

Step 6: Decide if night activity matters (for most raptors, it doesn’t)

CRA often works in monthly time steps, and the model needs to know how many “active seconds” exist in the month.

For many species, night flight is real (migrants, seabirds, etc.).
For most diurnal raptors, it’s effectively zero.

In practice, you create:

Active hours = daylight hours + (night hours × nocturnal fraction)

Nocturnal fraction might be:

  • 0.0 for strictly diurnal

  • 0.25 for slight crepuscular

  • higher for truly nocturnal or nocturnal migrants

If you have a nocturnal rank table, you just map it to a fraction and apply it consistently.


Step 7: Calculate “transits” through the rotor disc (how often birds pass through)

Now we’re ready for the first big modeled output.

A “transit” is one bird passing through the rotor-swept airspace once.

The Band basic model estimates transits using:

  • bird density in the air (DA)

  • rotor area

  • flight speed

  • proportion at rotor height (Q2R)

  • active time

  • number of turbines

  • operational fraction (if included)

If you’ve set up DA and Q2R correctly, the transit calculation becomes straightforward.

This step answers:

“How many opportunities for collision exist, before considering blade rotation and avoidance?”


Step 8: Compute single-transit collision probability (the “one pass” risk)

This is the part called “Stage C” in many templates.

Here you estimate:

“If a bird passes through the rotor disc once, what is the chance it gets hit?”

This depends on turbine mechanics and bird size:

  • rotor speed (rpm)

  • blade width profile (chord)

  • number of blades

  • pitch / blade angle

  • bird length and wingspan

  • relative wind direction (upwind vs downwind)

And here’s a practical reality of pre-construction work:

You often don’t have perfect blade profile data.

When that happens, you use:

  • a standard generic blade profile for the turbine class,

  • a reasonable rpm range,

  • and document assumptions clearly.

If your spreadsheet shows blanks in Stage C, the culprit is usually:

  • missing blade profile values,

  • broken references,

  • or macros disabled.


Step 9: Apply avoidance (because birds aren’t dumb)

If you stop at “collision probability,” you’ll overestimate impacts.

Avoidance rate reflects that birds typically detect and avoid turbines.

Final collision estimate:

Collisions = (Transits × single-transit probability) × (1 − avoidance rate)

Avoidance is often the biggest uncertainty, so best practice is to:

  • use standard defaults (by species group)

  • and/or run sensitivity cases (e.g., 0.95, 0.98, 0.99)

This makes your report more honest and more defensible.

Wind farms

Step 10: Summarize results the way authorities expect

Decision-makers (Ministry, Agencies) want results that are:

  • species-specific

  • monthly (seasonal pattern)

  • annual totals

  • transparent assumptions

A typical output includes:

  • a table of monthly transits / collisions (before & after avoidance)

  • annual totals

  • a short explanation of assumptions

  • a clear statement of uncertainty (especially blade profile and operational time)

This is our recipe — a practical, transparent way to turn bird flight data into a defensible collision risk assessment before a wind farm is built. We use it in different types of Nature Impact Assessements for wind and solar developers.
If you follow these steps, you’re now equipped to carry out a Collision Risk Analysis that regulators can understand and projects can stand behind.
And if you do it differently, improve a step, or challenge an assumption — even better.
That’s how good methods evolve, and we’re always happy to hear about it.

Zamenis situla

Zamenis situla lives a life that is almost perfectly optimized to avoid detection. It is active during short and often unpredictable windows. It prefers complex, three-dimensional microhabitats like stone walls, rocky crevices, and dense vegetation where visibility is minimal. It does not bask conspicuously. It does not flee dramatically. More often than not, it freezes, disappears, or never emerges in the first place. From an evolutionary perspective, this makes perfect sense. From a monitoring perspective, it is a nightmare.

And this is where a fundamental mismatch appears between how conservation monitoring is designed and how some species actually live.

Most monitoring frameworks, especially those linked to Natura 2000 obligations, are built on a quiet assumption: that with sufficient effort, you will eventually detect the species. That presence can be confirmed repeatedly. That population size can be estimated. That trends can be calculated. On paper, this sounds reasonable. In reality, for species like Zamenis situla, it often turns into a multi-year exercise in disciplined failure.

We tried everything we were supposed to try. Capture–mark–recapture, the gold standard of population estimation, was implemented carefully and consistently. After three years, recaptures were still too rare to produce any meaningful population estimates. The statistics simply refused to cooperate, not because the method was flawed, but because the species never appeared often enough to close the loops that the models require.

We walked line transects (for Distance methodology), again and again, knowing full well that the probability of encountering such a cryptic snake on an imaginary line through the landscape was low, but hoping that repetition would eventually tip the balance. It didn’t. Common, active snake species showed up. Zamenis situla almost never did. The transects were clean, the data sheets were tidy, and the result was silence.

We set up permanent plots and applied the Occupancy models, accepting that absolute counts might be unrealistic and that presence–absence could be a more honest goal. But even here, detection probability became the limiting factor. Entire predefined squares remained empty year after year, not because the species was absent, but because its lifestyle simply didn’t intersect with our sampling windows often enough to leave a detectable signal.

At the end we also tried to add environmental DNA detecton to the occupancy model to increase the number of records, but eben this yielded a very low detectability, as it seems that besids being elusive, leopard snake is also rare (low number/area) compared to other species and also quite unselective in habitat type (present in low number in variety of habitats). 

Ironically, the most consistent records we obtained came from places no one wants to rely on: roads. Dead-on-road individuals. Road transects. Asphalt cutting through stone-rich landscapes. It’s uncomfortable to admit, but roads are often the places where elusive animals briefly become visible, precisely because movement — not habitat — is what exposes them. These records don’t represent healthy systems, but they do represent reality. Ignoring them would have meant ignoring the majority of what the species was willing to show us.

At some point, we had to stop asking a question that clearly wasn’t working. “How many individuals are there?” sounds like the right question, but for species like this, it may simply be the wrong one. So we shifted our thinking. Instead of chasing absolute population size, we focused on something more modest, but far more robust: relative abundance based on effort – CPUE (Catch Per Unit Effort) methodology.

How many individuals do we detect per person-hour of fieldwork? How many per kilometer surveyed? These numbers don’t pretend to tell us how many snakes exist in total. What they do tell us is whether our interaction with the species is changing over time, under comparable conditions and comparable effort. They give us a baseline. A reference point. A way to compare years, sites, and methods without forcing the data to say something it cannot support.

Once we accepted this shift, something important happened. Monitoring stopped feeling like failure. The data, sparse as it was, started to make sense within its own limits. We could finally talk about trends, not in absolute terms, but in relative ones. And for elusive species, relative trends are often the only trends that exist.

Another realization followed naturally. You cannot interpret Zamenis situla in isolation. Its signals are too faint. Its numbers too low. So we began looking at other snake species within the same system, especially those that are more detectable and respond more visibly to environmental change. Their relative abundance became a contextual reference — a way to understand whether changes observed in Zamenis situla reflect species-specific dynamics or broader ecological shifts affecting the entire snake community.

CPUE_snake_comparison_Telascica

What the numbers actually show

When survey effort is standardized using CPUE (detections per person-hour), a clear pattern emerges. Our example is calculated for Telašćica Nature Park (Croatia): some snake species, like Malpolon insignitus, are detected frequently and predictably, while others appear far less often despite the same level of field effort. Zamenis situla falls into this second group with just 0.105 detections per person-hour. Its detection rate is low, but importantly, it is not an outlier — it aligns closely with other elusive snake species such as Elaphe quatuorlineata. In practical terms, this means the species is present, but encounters are rare by nature, not necessarily because populations are collapsing. The value of CPUE lies precisely here: it allows us to compare species fairly under equal effort and to track changes over time, even when absolute population counts are impossible.

Slowly, a clearer picture emerged. Not a precise one. Not a comfortable one. But an honest one.

The real challenge of monitoring rare and elusive species is not technical. It’s philosophical. It requires accepting uncertainty, resisting the urge to over-quantify, and designing monitoring systems that respect biological reality rather than forcing it into predefined statistical boxes. Some species will never give us neat datasets. Some will always exist at the edge of detectability. That does not make them unsuitable for monitoring — it makes them unsuitable for rigid expectations.

In the end, working with species like Zamenis situla teaches you humility. It reminds you that absence of data is not data of absence, that rarity is not always decline, and that conservation is as much about listening carefully as it is about counting. Some species don’t want to be measured. They don’t announce themselves. They don’t make things easy.

And what is next for us? We plan to further test the CPUE methodology and fine-tune it at our most effort-intensive site, the BIOTA research center in Krka National Park, where snake research averages about 4,500 person-hours per year. It’s the only site where even Zamenis situla recapture rates reach around 10%, allowing us to calculate survival, density, detectability, and absolute population size for comparison with CPUE relative estimates.

Zamenis situla

Practical guide: how we actually calculated CPUE (Catch Per Unit Effort)

1. Defining the problem correctly

Before any method was selected, the problem was reframed.

We explicitly accepted that:

  • absolute population size estimation was unlikely to be achievable

  • detection probability was extremely low and variable

  • zero detections could not be interpreted as absence

  • standard outputs (N, density, occupancy probability per grid) were unrealistic goals

The primary objective therefore became:

To establish a repeatable, effort-standardized system that allows comparison through time and space, even when detections are rare.

This single decision guided everything that followed.

2. Field effort standardization (the non-negotiable foundation)

Relative abundance metrics are meaningless without strict effort control.

For every field activity, we recorded:

  • number of observers

  • active survey time (in hours)

  • distance covered (in kilometers)

  • survey type (active search, road transect, incidental)

  • weather conditions and time of day

Only surveys that met predefined comparability criteria were included in calculations (similar season, similar time window, similar survey intent).

This allowed us to later express detections per unit of effort, not as raw counts.

3. Survey types used (and how they were treated analytically)

We did not exclude methods that performed poorly in isolation.
Instead, we treated each method as a filter with its own bias, then decided which outputs were usable.

a) Active visual search (time-based)

This included:

  • slow searches of stone walls, rocky slopes, and vegetation

  • targeted microhabitat inspection

  • surveys conducted during biologically plausible activity windows

Output used:

  • detections per person-hour

Even when detections were rare, time-based standardization allowed comparison between years.

b) Line transects (distance-based)

Transects were walked repeatedly in the same areas.

Outcome:

  • detection probability for Zamenis situla was near zero

Decision:

  • transects were not abandoned

  • but their outputs were not used as standalone indicators for the target species

  • they remained useful for other snake species, which later became reference indicators

c) Permanent plots and occupancy framework

Permanent plots were surveyed repeatedly.

Outcome:

  • insufficient detections to parameterize occupancy models for the target species

Decision:

  • occupancy was rejected as a primary metric for Zamenis situla

  • plots were retained for long-term presence documentation and ancillary species data

This is an important point:
Rejecting a method analytically is not the same as abandoning it operationally.

d) Road transects (distance-based, movement-driven)

Road surveys were conducted systematically:

  • same road sections

  • repeated over years

  • recorded both live and dead individuals

Key insight:
Roads intersect movement, not habitat. For elusive species, this matters more than idealized sampling design.

Output used:

  • detections per kilometer

This became one of the most robust indicators for the target species.

4. The core metrics we calculated

We ultimately focused on two primary metrics, both intentionally simple:

Metric 1: Detections per person-hour

RAtime=Number of detected individualsTotal observer hoursRA_{time} = \frac{\text{Number of detected individuals}}{\text{Total observer hours}}

 

 

Metric 2: Detections per kilometer

RAdistance=Number of detected individualsTotal kilometers surveyedRA_{distance} = \frac{\text{Number of detected individuals}}{\text{Total kilometers surveyed}}

 

 

These metrics were calculated:

  • per year

  • per survey type

  • using only comparable effort blocks

They were never mixed or pooled without clear justification.

5. Why we explicitly avoided “population estimates”

At no point did we extrapolate these metrics to population size.

We did not:

  • convert detections to density

  • scale results to total habitat area

  • infer absolute abundance

Why?

Because doing so would create false precision.
Relative abundance was treated exactly as that — a relative index, not a hidden proxy for population size.

6. Establishing a baseline (the most important output)

The first years of data were treated as baseline calibration, not evaluation.

Instead of asking:

“Is the population increasing or decreasing?”

We asked:

“What does ‘normal detectability’ look like for this species under standardized effort?”

This baseline now functions as:

  • a reference point for future monitoring

  • a conservation target framework

  • a threshold system for detecting change

7. Adding a third dimension: other snake species as context

Because Zamenis situla produces weak signals on its own, we incorporated other snake species into the analytical framework.

For each year, we calculated the same relative metrics for:

  • common, more detectable snakes

  • species with overlapping habitat use

These species were not treated as controls, but as contextual indicators.

Interpretation followed a simple logic:

  • parallel declines → system-level signal

  • divergence → species-specific dynamics

  • stability in common species + change in target species → real biological signal

This step dramatically improved interpretability.

8. What this framework can and cannot do

It can:

  • detect long-term trends

  • provide objective, repeatable indicators

  • support conservation objectives

  • function under extreme detectability constraints

It cannot:

  • estimate population size

  • replace demographic studies where feasible

  • eliminate uncertainty

And that is precisely why it works.

9. Why this approach is transferable

This framework is applicable to:

  • cryptic reptiles

  • nocturnal mammals

  • rare amphibians

  • low-density invertebrates

  • any Natura 2000 species with structurally low detectability

The key is not the species.
The key is the willingness to design monitoring around reality instead of expectation.

Final note for practitioners

If you take only one thing from this guide, let it be this:

When detection is the limiting factor, trend detection beats population estimation.

Once you accept that, monitoring rare and elusive species stops being an exercise in frustration and starts becoming a disciplined, honest form of ecological listening.

And sometimes, that is exactly what conservation needs. 

Written by Dusan Jelic

Related Posts

The Elusiveness Fallacy – how to monitor species that prefer to stay hidden

The Elusiveness Fallacy – how to monitor species that prefer to stay hidden

What do you do when a protected species is present, but almost never seen? Some animals aren’t rare because they’re disappearing — they’re rare because that’s how they live. This article explores why monitoring elusive species like the spotted whip snake breaks traditional conservation methods, and how we learned to listen to faint ecological signals instead of chasing impossible numbers.

read more
Tagging Hope: A Decade of Protecting Croatia’s Last Telestes souffia in the Bregana River

Tagging Hope: A Decade of Protecting Croatia’s Last Telestes souffia in the Bregana River

In 2025, our team completed the latest chapter of a decade-long effort to protect Telestes souffia, tagging 30 adult individuals in the Bregana River using BIOMARK PIT technology. Each fish was gently anesthetised, measured, weighed, and fitted with an 8 mm microchip to enable long-term tracking of survival and movement in its last Croatian habitat. The work builds on earlier studies, including the 2017 research that documented a small and declining population, underscoring the urgency of continued monitoring. With new data now collected, updated 2025 population estimates are on the way — and hope for the species continues to flow with the Bregana.

read more

0 Comments