How We Build the Incident Database
HoneyBeeAwareness.org maintains a working incident database to help document serious bee-related public-safety events involving people, pets, livestock, workers, responders, schools, and communities.
The database is built from public records, news reports, official statements, legal references, field reports, and submitted incident information. Not every record is perfect, and not every detail is always available. For that reason, we label source strength, bee identification status, severity, and verification notes as clearly as possible.
Working Transparency Statement
Our goal is not to claim that every date, county, or detail is final on day one. Our goal is to document credible incidents honestly, preserve leads for future review, and show broader patterns that may help prevent future injuries and losses.
Why the Database Exists
Serious bee incidents are often scattered across local news stories, public-safety posts, legal references, agency notes, archived articles, family reports, and field observations. Many are difficult to find later, and many are never placed into a larger public-safety context.
HBA organizes these records so patterns can be seen more clearly: mowing and weed-eating incidents, outdoor-worker exposure, animal losses, responder involvement, public-location hazards, school-related incidents, hidden colonies, and other recurring situations.
Where Records Come From
Incident records may come from several types of sources. Each source type has different strengths and limits.
- Official agency reports, public-safety releases, fire department reports, police reports, EMS references, state records, and county records.
- Established news reports that include dates, locations, official statements, injuries, animal impacts, or response details.
- University, Extension, agency, and research references used for background and regional context.
- Legal filings or court references, carefully labeled as allegations or legal records when appropriate.
- Public submissions to Honey Bee Awareness, reviewed before any public use.
- Field reports, beekeeper observations, animal-owner reports, worker reports, or community leads retained for follow-up when documentation is incomplete.
How Records Are Classified
HBA separates several issues that are often mixed together in casual conversation. Severity, bee identification, source strength, trigger, and verification status are not the same thing.
| Field | What It Helps Explain |
|---|---|
| Source Strength | Whether the record is supported by an official source, established news report, partial documentation, direct field report, or unverified lead. |
| Bee ID Status | Whether bees were confirmed Africanized, reported Africanized, suspected Africanized, unknown, managed honey bees, feral honey bees, or unspecified. |
| Severity | Whether the incident involved fatality, hospitalization, severe injury, animal fatality, responder involvement, or another public-safety concern. |
| Trigger / Activity | What activity or setting may have been involved, such as mowing, weed-eating, chainsaw work, livestock care, tree trimming, utility work, or public-location exposure. |
| Date Precision | Whether the date is exact, inferred, approximate, month-level, year-level, or still unknown. |
| Review Notes | What needs later confirmation, such as county, date, duplicate status, original source, bee ID wording, or source conflict. |
Source Strength
Honey Bee Awareness does not treat every source as equal. A public news story quoting fire officials is not the same as a social-media lead. A direct field report is valuable, but it may still need documentation before becoming a public record.
- A: Official report, government record, agency release, or direct documentation.
- B: Established news source or public report that quotes officials or includes strong details.
- C: Local source, partial documentation, field report, or record needing additional review.
- D: Lead, unverified reference, or item retained for follow-up but not yet treated as a strong public record.
Bee Identification Status
A serious incident is not automatically an Africanized bee incident. Some sources confirm Africanized bees, some report or suspect Africanized bees, and many do not identify the bees at all.
HBA tracks bee identification separately from severity so readers can understand what is documented and what is not documented. This helps avoid both exaggeration and minimization.
Why Some Records Are Preliminary
A real incident may still have incomplete details. Older reports may have missing dates, county uncertainty, unavailable original sources, conflicting location wording, or incomplete bee identification. When an event appears credible but details need more work, HBA may keep the record as preliminary or retain it in a candidate-review file.
This is intentional. Preserving a credible lead is different from pretending every detail is final. The database can improve over time as stronger sources, witness reports, official records, or submitted information become available.
What the Database Is Not
The HBA database is not a complete official government registry. It is not a claim that every serious bee incident has been found. It is not anti-bee, anti-beekeeper, or intended to sensationalize attacks.
It is a working public-safety documentation project designed to organize credible information, identify patterns, support education, and encourage responsible stewardship of gentle, manageable honey bees.
How the Process Is Evolving
The database began with state-by-state searches in southern and Africanized-risk regions. As records accumulated, HBA added pattern-based sweeps focused on recurring public-safety situations, including mowing and weed-eating, farm and ranch work, pets and livestock, elderly victims, children and school incidents, legal/liability cases, responder involvement, and show-animal concerns.
Future work will include source strengthening, duplicate review, submitted incident review, case studies, maps, regional summaries, misconceptions, glossary terms, and educational pages connected back to real documented patterns.
Every Record Represents a Real Event
Every record represents more than a data point. These incidents affected real people, families, animals, workers, responders, and communities. The purpose of this database is to learn from those events, improve public awareness, support responsible beekeeping, and help reduce preventable harm.