Skip to content

Bombing / Explosive Package / Suspicious Package

Threat in Public Safety, arrives with intent

An intent-driven threat whose response, evacuation, cordons, bomb squads, disrupts a site even when the device is a hoax.

Plans also call it: bomb threat, improvised explosive device, IED, VBIED, explosive device, mail bomb

See a sample briefBook a walkthroughAll 31 hazards →

Sample brief

The first page of a Bombing / Explosive Package / Suspicious Package brief: likelihood, impact and readiness on your own scale, with each figure sourced.

Evidence brief for Cedar Ridge County (example)

September 14, 2026

Bombing / Explosive Package / Suspicious Package

Threat in Public Safety, on the established threats & hazards list

Impact
5432112345

Likelihood

Likelihood
2

Unlikely — Possible but infrequent — roughly once in 50 to 100 years (1–2% chance in any year).

Impact
2

Minor — Limited effects — few injuries, damage confined to a small area, brief localized disruption of services.

Readiness
4

High — The organization has a well-developed capability to manage this threat or hazard. Plans, personnel, resources, and skills are largely in place, and the capability has been meaningfully tested or demonstrated. Remaining gaps are unlikely to significantly impair performance.

  • 2source documents
  • 58verified mentions
  • —federal declarations
  • —NRI risk score
Worked example: Cedar Ridge County is fictional. The scores illustrate the format and are nobody's decision. Open a full sample brief →

The national record

FEMA’s National Risk Index doesn’t model Bombing / Explosive Package / Suspicious Package. Your team fills it with local evidence, and Hazzard shows the gap rather than a zero.

How it maps

The same hazard in the vocabularies your plan and FEMA already use.

FEMA National Risk Index
Not covered
FEMA declaration incident type
Not covered
NOAA Storm Events type
Not covered
Hazzard category
Public Safety, human-caused

The national record

What the federal data says about Bombing / Explosive Package / Suspicious Package: nothing yet

No federal dataset scores Bombing / Explosive Package / Suspicious Package or files declarations under it. That's common for threats and emerging hazards, and it's why a brief for Bombing / Explosive Package / Suspicious Package is built from your own plans, exercises and records. Hazzard shows the gap instead of inventing a number.

In your plan

What a Bombing / Explosive Package / Suspicious Package profile needs, and where each part comes from

A local hazard mitigation plan profiles each hazard the same way (44 CFR 201.6). Here is how Hazzard fills each part for Bombing / Explosive Package / Suspicious Package.

  1. Location

    44 CFR 201.6(c)(2)(i)

    Your documents

    No national layer maps Bombing / Explosive Package / Suspicious Package. We draw the geographic extent from your plans, studies and annexes, cited to the page.

  2. Extent

    44 CFR 201.6(c)(2)(i)

    Your documents

    The magnitude your plans use for Bombing / Explosive Package / Suspicious Package (a scale, a depth, an acreage, a duration), read from your documents and cited, so the profile states the strength you plan for.

  3. Previous occurrences

    44 CFR 201.6(c)(2)(i)

    Your documents

    FEMA files no declaration type for Bombing / Explosive Package / Suspicious Package. The history comes from your after-action reports, incident records and plans.

  4. Probability of future events

    44 CFR 201.6(c)(2)(i)

    Your team decides

    No national dataset gives a frequency for Bombing / Explosive Package / Suspicious Package. Your team scores likelihood on your scale from the evidence we organize.

  5. Vulnerability and impacts

    44 CFR 201.6(c)(2)(ii)

    Your documents

    The Census population profile and HHS emPOWER counts for context; the consequences themselves come from your plans and exercises.

  6. The assessment itself

    Your team decides

    Likelihood, impact and readiness for Bombing / Explosive Package / Suspicious Package are drafted with every source attached, and a person on your team accepts each one. Hazzard never records a score on its own.

How we can help

How we’d help you prepare for Bombing / Explosive Package / Suspicious Package

  1. 1

    We start from what you own

    Your EOP, threat assessments and after-action reports, filed so each statement about Bombing / Explosive Package / Suspicious Package points to its page.

  2. 2

    We mark the gaps

    Where federal data is silent, the brief says so. Your team's local evidence carries the score instead of a zero.

  3. 3

    You leave with a cited brief

    Likelihood, impact and readiness for Bombing / Explosive Package / Suspicious Package on your own scale, with each figure tied to its source. It is ready for your planning team or council.

Also in Public Safety

Preparing for Bombing / Explosive Package / Suspicious Package

Assess Bombing / Explosive Package / Suspicious Package from the evidence you already hold.

No federal dataset scores targeted violence for your county. We build the assessment from your own plans, exercises and after-action reports. We reply within one business day.

Book a walkthrough

Takes about two minutes. A person reads each request.

Or start by marking your area on the map