FEMA Deployments

Data Source

All KHSM data are from the OHSS Statistical System of Record (SSOR). The SSOR is the authoritative source of DHS statistical data and undergoes rigorous validation. SSOR data for emergency management deployments are constructed from administrative data stored in the Deployment Tracking System (DTS). FEMA assigns and tracks personnel deployed in response to a disaster in DTS.

Data Lineage

FEMA extracts data from DTS. They provide us this extract as a comma-separated values (CSV) file. We clean the data as described below and then create an active deployments dataset. This includes a row of data for each deployment that is active during a given period (such as by day, week, or month). We use the date-on-site and departure date variables in the source data to define when the deployment was active. We calculate this KHSM from the active deployments dataset.

Units of Measure and Descriptive Variables

Units of Measure

Deployment

A deployment occurs when an individual is assigned to an event for a defined period. This KHSM counts the number of active deployments during a given month or year. We count long deployments once during each month or year they were active. If an individual deploys more than once in a period, we count each deployment separately. The average length of deployments to events starting in Fiscal Year 2024 was 26 days.

Descriptive Variables

Event Type

Deployments support specific events. There are 5 event types captured in the report.

• Pre-Declaration: Initiated by FEMA. These events conduct preliminary damage assessments (PDAs) when a declaration request seems imminent. Sometimes, a pre-declaration deployment is not followed by a declaration. For example, FEMA may deploy in preparation for a hurricane, but if the hurricane does not make landfall, there is no declaration.
• Emergency Declaration: Initiated by a request from a governor or tribal chief executive and declared by the president. These events provide federal resources to supplement state and local governments to save lives and protect people and property. These events have an immediate funding limit of $5 million. These events can be paired with a Major Disaster declaration to get immediate funds.
• Major Disaster Declaration: Initiated by a request from a governor or tribal chief executive and declared by the president. These events provide resources for natural catastrophes that cause severe damage beyond state or local capabilities. They have no funding limit and open up federal assistance programs, but have a delayed processing time.
• Fire Management: Initiated by a request from a state and FEMA decides to provide support. These events mostly consist of providing Fire Management Assistance Grants. A fire that exceeds state and local resources can be declared an emergency or major disaster.
• Post-Joint Field Office (JFO): Initiated by FEMA. These events provide federal resources after initial declaration response efforts are complete. A JFO is a temporary central location for coordination of field-level incident management activities. These events happen after JFO deactivation.

This report excludes Activation and Long-Term Recovery events. These aren’t generally associated with a specific Stafford Act declaration or funded by the Disaster Relief Fund.

Event Region

FEMA Regional Office responsible for the event.

Event Location

The duty station in the state or territory the deployment is in.

Hazard

A hazard is the source or cause of harm or difficulty. All events are associated with a single hazard. Hazards can be natural (acts of nature), technological (accidents or failures of systems or structures), or human-caused (the intentional actions of an adversary).

• Biological: When material of biological origin causes damage to people, animals, plants, natural resources, or infrastructure
• Chemical/Toxic Substances: Poisonous vapors, aerosols, liquids, and solids. These have toxic effects on people, animals, or plants.
• Civil Unrest: A mass action that challenges public safety. Includes riots, acts of violence, unlawful obstructions or assemblages, or other actions against public law and order.
• Coastal Storm: A violent atmospheric disturbance to the local maritime conditions. For example, waves or water levels or both.
• Dam/Levee Break: The failure of a barrier used to regulate the level or flow of water Results in an increase in the risk of water causing damage or injuries.
• Drought: An occurrence in which the amount of water available in an area falls short of expected or required levels. Caused by meteorological, hydrological, agricultural, or socioeconomic conditions.
• Earthquake: Ground shaking and radiated seismic energy caused by a slip on a tectonic fault. Caused by volcanic or magmatic activity, or by other sudden stress changes in the earth.
• Flood: The overflow of water onto normally dry surfaces causing damage or injuries.
• Human Cause: A harm or difficulty caused by the intentional actions of an adversary.
• Hurricane/Typhoon: A tropical cyclone, formed in the atmosphere over warm ocean areas. Wind speeds must reach 74 miles per hour or more and blow in a large spiral around a center or “eye.”
• Mud/Landslide: An occurrence in which masses of rock, earth, or debris travel down a slope under the influence of gravity. Debris includes combinations of loose mud, sand, soil, water, and air.
• National Special Security Event: An event designated by the secretary of homeland security. The Secret Service leads security operations for these events. Examples include Presidential Inaugurations, State of the Union Addresses, United Nations General Assemblies, Republican National Conventions, and Democratic National Conventions.
• Other: Water shortage, building collapse, etc.
• Severe Storm: A violent atmospheric disturbance characterized by a combination of impacts. These impacts often include lightning, strong winds, extensive rain, and hail.
• Tornado: A violently rotating column of air touching the ground, usually attached to the base of a thunderstorm.
• Tropical Storm: A tropical cyclone, like a hurricane/typhoon. Maximum sustained wind speeds are 39 to 73 miles per hour.
• Tsunami: Large, destructive waves typically caused by underwater earthquakes or volcanic eruptions.
• Volcano: An opening in the Earth’s crust that allows molten rock, gases, and debris to escape to the surface
• Wildfire/Fire: Combustion or burning and the accompanying light, heat, and smoke.
• Winter Storm/Snow/Severe Ice Storm: A destructive, low temperature storm. The main types of precipitation are snow, sleet, or freezing rain.

Data Processing

We produce this KHSM from a single data extract from. We perform several data quality checks to ensure the accuracy of the source data. The date on site and departure data variables in the DTS data define the period the deployment was active.

Data Cleaning

We validate data input to identify anomalous data entries. We work with FEMA to correct the source data when we find anomalies. We exclude anomalous data entries until they are resolved.

• Event Identifiers: We cross tabulate the numeric event identifier and string event name variables for all deployments. Each event identifier should have only one associated event name. We identify string event names that do not follow the expected format, such as containing ‘XXXX’ in the name, as anomalous.
• Event Types: We compare the event type encoded in the event name to the event type variable. These event types should always match. We also check the data to ensure they are in the 5 Stafford Act event types within the KHSM scope. For example, activation and long-term recover events are not within scope.
• Personnel Types: We check that the personnel types are within the FEMA and DHS Surge Capacity Force personnel within the KHSM scope. For example, other federal agency deployments are not within scope.
• Event Locations: We compare the event location encoded in the event to the location variable. These event locations should always match.
• Hazard Types: We check that the hazard types are within the Stafford Act hazard types within the KHSM scope. For example, training exercises are not within scope.
• Days Deployed: Deployments must be for a positive duration. Small negative amounts (0, -1, -2) can appear in the data for administrative reasons. We exclude these from the KHSM. Longer negative durations indicate data entry error and the source data needs correction.
• Dates: Any deployment with a date on site or event start date before Fiscal Year 2016 is identified as anomalous. This means that deployments that started prior to Fiscal Year 2016 but continued into Fiscal Year 2016 are excluded from the KHSM.

We transform state or territory abbreviations in the source data to their full name in string format for Event Location.

Integration

A single data source is used to produce the Deployments KHSM.

Imputation

We don’t substitute any missing data for the Deployments KHSM.

Limitations

Undercount and Overcount

We don’t count anomalous data identified during data cleaning that FEMA hasn’t resolved in this KHSM. Currently, FEMA has resolved all anomalous data.

We use the event start date, event type, hazard type, and personnel type to query only Stafford Act deployments of FEMA and DHS Surge Capacity Force personnel during the defined period.

Undercount can occur if a deployment is not captured in the data provided by FEMA due to a gap in their system query. This potential under coverage is currently unknown.

Overcount can occur if data that don’t meet the KHSM scope are captured in the data provided by FEMA due to an error in the system query. To eliminate potential overcount, we conduct input validation when we receive the data from.

Over coverage can also occur if data is inaccurately inputted in the source system. We can’t identify this potential over coverage with our input validation and is currently unknown.

Accuracy

We extract data from live systems that are subject to change. Statistical information is subject to change due to corrections, systems changes, or changes in data definition.

We don’t count anomalous data identified during data cleaning that FEMA hasn’t yet resolved. This ensures the data counted in the KHSM is accurate, but may result in undercount. Currently, FEMA has resolved all anomalous data.

We round each row of data to the nearest 10 to protect privacy and security. As a result, the actual totals and the totals of the rounded rows can vary.

Timeliness

We extract data from the source system no more than 30 days before the release of the report. We release data are released on a quarterly basis within 60 days of the end of the fiscal year.

Linkage Error

There is no linkage performed in producing the deployments KHSM.

Reporting Period

Data reported covers Fiscal Years 2016-2024.

Changes from Previous Releases

The current release is the first iteration of the Emergency Management Deployments KHSM. As such, there are no changes to note from previous releases.

Related Data and Information

• Emergency and Disaster Deployments: Anonymized deployments microdata and a narrative report that contains additional detail to support the underlying data.
• OpenFEMA | FEMA.gov: FEMA’s data delivery platform. Provides datasets to the public in open, industry standard, machine-readable formats.