Military Airfields / Wildlife / BASH
Wildlife / BASH
Sightings, strikes, and a live BASH heatmap across 270+ species.
The problem
Identifying what you just saw is half the report
A sighting is only as useful as the species on it. Guessing at "some kind of hawk" makes the record weaker the moment it's logged. A strike is an entirely different report: what was hit, how bad the damage was, whether it was ingested, whether remains were recovered. That's detail a sighting never asks for and a strike can't do without.
And logged one at a time, neither tells you much. The question that actually matters (where on the airfield the risk is concentrated, and whether it's getting better or worse) only shows up once enough of them sit on the same map.
How it works
From the species picker to the heatmap
- 01
A picker built to get the species right
Search or browse over 270 species with a photo next to each one, so identifying what you saw doesn't come down to a guess.
- 02
A sighting and a strike ask for different things
A sighting logs species, count, behavior, and location. A strike adds what was hit, the damage and its effect on the flight, phase of flight, and whether remains were collected, so the report matches what actually happened.
- 03
Every entry lands on the same map
Sightings and strikes both plot to a live heatmap, filterable to one, the other, or both together, so concentration by area is visible instead of remembered.
- 04
The trend lines are already built
Sightings by month, top species, strikes by species group, and BWC history over time: the analytics behind the log are ready without exporting anything to build them separately.
Built on the regulation
The citation, implemented
- DAFMAN 91-212
Sightings, strikes, and the heatmap that surfaces concentration by area implement the reporting and hazard-tracking this instruction requires, logged the same way for every species.
The benefit
What it automates
Species ID stops being a guess
A photo next to every species in a 270-plus entry picker means the record starts with the right animal, not an approximation.
A strike report captures what a sighting can't
Damage, phase of flight, parts struck, remains collected: the fields that make a strike report useful for finding a pattern are there because the form knows it isn't a sighting.
Concentration shows up on the map, not by memory
The heatmap draws from every sighting and strike logged, so where risk actually concentrates on the airfield is visible without anyone having to remember where the trouble spot is.
Related
Works alongside
FAQ
Straight answers
How many species does the picker cover?
Over 270, each with a photo to check an identification against, searchable by name rather than scrolled through blind.
What's the difference between logging a sighting and logging a strike?
A sighting captures species, count, behavior, and location. A strike adds what was hit, the damage and its effect on the flight, phase of flight, and whether remains were recovered, fields a sighting never needs.
What does the heatmap actually show?
Every sighting and strike plotted on the same map, filterable to one, the other, or both, so where risk concentrates on the airfield is visible at a glance, not something inferred from memory.
Is there anything beyond the raw log, like trends and breakdowns?
Yes: sightings by month, the top species by count, strikes broken out by species group, and BWC history over time, all built from the same log without a separate export.