Why public turbine registries lag behind commissioning dates

Pull up a public wind turbine registry for almost any state and you'll find turbines missing that you can plainly see standing in satellite basemaps from eighteen months ago. That's structural, and it's worth understanding if you're scoping a competitor site or doing a wake-loss study on assumptions you can't verify.
Where the delay comes from
Commissioning a turbine and reporting it are two separate workflows run by two separate parties, usually on two separate timelines.
The turbine itself goes commercial the day it passes performance testing and starts delivering to the grid. That date is set by the owner, the EPC contractor, and whoever's buying the power. None of them owe the public a registry update on that schedule.
Federal and state registries, by contrast, depend on voluntary or semi-voluntary disclosure. The USWTDB, for instance, pulls from FAA obstruction filings, state siting board records, and operator-submitted data, then reconciles those against aerial imagery on its own update cycle. Each of those upstream sources has its own lag:
- FAA filings get submitted for airspace clearance, sometimes a year or more before steel goes in the ground, and don't always get closed out once the project is built.
- State siting board dockets close when permits are approved, not when turbines spin up. An approved project can sit for two or three years before it's built, and the docket doesn't reopen to confirm completion.
- Operators self-report fleet counts on their own cadence, often tied to annual reporting obligations rather than commissioning events. A developer with no near-term SEC or FERC filing due has no particular reason to update a public list the week turbines go live.
Stack those three gaps together and a registry can run a full reporting cycle, sometimes two, behind what's standing in a field right now. For a project commissioned in Q1, it's not unusual for that turbine to show up in public data the following year, if it shows up on schedule at all.
What the gap costs a siting team
For wake-loss modeling, a missing turbine upstream of your site is a missing wake deficit in the model. You'll size turbine spacing and hub heights off a fleet count that understates density, and the error doesn't show up until operational data starts coming back short of forecast.
For competitive density scoping, the registry gap cuts the other way. You're trying to read how saturated a county already is before committing to a lease position, and the public count tells you less than what's been built. Developers who've been burned by this tend to default to manually tracing turbines off recent basemap imagery, counting towers and pads by eye, project by project. It works, but it's slow, and it has to be redone every time a new imagery pass comes in or a new project files.
There's also a quieter cost: registries don't distinguish well between "permitted," "under construction," and "operating." A project that stalled at financing can sit in a dataset looking identical to one that's spinning. Without a way to check which turbines are physically standing right now, a density read built on registry data alone carries that ambiguity forward into your site plan.
Closing the gap without waiting on disclosure
Wind Turbine Mapping locates every turbine in an area of interest directly from its rotor shadow and pad geometry in current imagery, and resolves each hub's position into a point layer, refreshed quarterly, so a fleet count reflects what's physically built rather than what's made it through a reporting cycle. For a density read on a candidate site, or a wake-loss study where turbine positions carry real weight, that's a meaningfully tighter cycle than waiting on the next USWTDB release or an operator's annual filing.
If you're tired of reconciling three outdated sources before you can trust a turbine count, take a look at what quarterly imagery-derived mapping gets you instead.