Your Client Worked for Blackwater. Or Was It Academi? Or Constellis?
A veteran walks into your office with a traumatic brain injury from a 2012 convoy ambush in Helmand Province. He says he worked for "Blackwater." But Blackwater became Xe Services in 2009, then Academi in 2011, then merged into Constellis in 2014. His DOL coverage card might list any of those names. His OALJ case file might reference yet another. And the carrier that wrote his DBA policy in 2012 may have been replaced twice since then.
This is not a hypothetical. Private security contractors (PSCs) generate some of the highest injury and death volumes in the entire DBA system. ClaimTrove data shows over 30,000 DBA claims tied to private security employers across DOL case summaries alone. Among those, more than 500 death claims are recorded for the top PSC employer families. Yet the industry's constant corporate restructuring means these claims scatter across dozens of employer name variants in federal databases.
For attorneys handling PSC injury cases, the core problem is not just identifying the right carrier. The problem starts with identifying the right employer. A single corporate family like Constellis maps to 16 distinct name variants in DOL records. GardaWorld maps to 15. Without resolving those aliases first, you are searching a fraction of the available evidence.
How Do PSC Injury Patterns Differ from Other DBA-Covered Occupations?
Most DBA-covered contractors work in construction, logistics, or base support. Their injury profiles look like domestic workers' compensation claims: falls, equipment injuries, repetitive stress, vehicle accidents. Private security contractors face a fundamentally different risk profile.
PSC injuries cluster around three categories that rarely appear in other DBA occupational groups. First, hostile-action injuries: gunshot wounds, blast injuries, IED attacks, and ambush-related trauma. Second, psychological injuries: PTSD, anxiety disorders, and other combat-zone stress conditions. Third, death claims at rates that dwarf every other DBA employer category.
The numbers are stark. Across DOL case summaries, Compass Security alone reported 447 death claims out of 1,375 total cases. That is a 32% death-to-claim ratio. Triple Canopy and Constellis combined for over 14,000 claims with 71 recorded deaths under the Triple Canopy name alone. When you add the Blackwater-era filings (1,250 cases, 30 deaths), the Constellis corporate family exceeds 16,000 total DBA claims across all name variants.
PTSD claims present a particular challenge in the PSC context. Unlike a construction worker who falls from scaffolding, a security contractor's psychological injury may not manifest until years after the triggering events. The lag between exposure and filing means these claims often surface long after the original DBA carrier has been replaced. Attorneys handling DBA PTSD claims for PSC employees frequently discover that the carrier on the policy during deployment differs from the carrier when the claim is filed.
Which Private Security Employers Generate the Most DBA Claims?
ClaimTrove's database tracks DBA claims across 4,983 DOL case summary records, 5,022 OALJ decisions, and 154,886 FOIA-obtained coverage records. Within this data, private security employers consistently rank among the highest-volume claim generators.
The top PSC employer families by total DBA case volume, aggregated across all known name variants:
- DynCorp International family: Over 28,000 cases across DynCorp International, DynCorp, and DynCorp Technical Services. While DynCorp is primarily a logistics and aviation services contractor, its protective services division generated substantial PSC-related claims. DynCorp recorded 287 death claims across its name variants.
- Constellis family: Over 16,000 cases spanning Blackwater Security Consulting, Xe Services, Academi, Triple Canopy, Constellis Group, Constellis Holdings, and Olive Group. This family maps to 16 distinct employer names in DOL records.
- SOC LLC: Over 9,000 cases under SOC LLC, SOC-SMG, and Special Operations Consulting variants. SOC recorded 16 death claims.
- GardaWorld/Aegis family: Over 3,700 cases across GardaWorld Federal Services, Aegis Defense Services, Aegis Defence Services Limited, ArmorGroup North America, and 15 other name variants.
These four employer families alone account for a significant share of all security-related DBA claims. Yet because their claims are fragmented across dozens of employer name spellings, a simple DOL search for "Blackwater" misses over 90% of the relevant Constellis-family data.
Why Does Industry Consolidation Make Carrier Tracing So Difficult?
The private security industry underwent rapid consolidation between 2009 and 2020. The Blackwater-to-Constellis transformation alone involved four corporate renamings, multiple subsidiary acquisitions (Triple Canopy, Olive Group), and at least three different DBA insurance carriers across the timeline.
Each corporate change creates a new employer record in federal databases. USAspending.gov tracks the contract under the entity name at time of award. DOL case summaries record the employer name at time of filing. OALJ decisions reference the employer name at time of adjudication. A single worker's claim might appear under three different employer names depending on which database you search.
ClaimTrove's employer alias system maps 55 distinct name variants for PSC employers across four major corporate families. The GardaWorld and Aegis merger alone created a web of 15 employer name variants including "AEGIS Defense Services (BVI)," "AEGIS/FSI Worldwide," "Armorgroup North America," and "GardaWorld Federal Services LLC." An attorney searching DOL records for "GardaWorld" will find approximately 1,500 cases. Searching the full alias chain reveals over 3,700.
Carrier changes compound the problem. When an employer changes its name, the DBA policy often continues under the old name until renewal. When the employer is acquired, the acquiring company may bring its own carrier. The historical carrier for Blackwater-era claims differs from the Academi-era carrier, which differs from the Constellis-era carrier. Without temporal mapping, you cannot determine which carrier was on the policy when your client was injured.
What Does OALJ Decision Data Tell Us About PSC Litigation?
ClaimTrove's database contains 61 OALJ decisions directly involving private security contractor employers. These decisions reveal patterns specific to the PSC industry that do not appear in standard DBA litigation.
PSC cases disproportionately involve disputed causation. Carriers contest whether injuries resulted from "work-related" hostile action versus off-duty incidents. In the security contractor context, the line between on-duty and off-duty barely exists. A contractor living on a forward operating base in Afghanistan is arguably "at work" 24 hours a day. OALJ judges have addressed this in multiple published decisions, generally applying a broad interpretation of employment scope in combat zones.
Death claim adjudication follows a distinct pattern for PSCs. Because many PSC fatalities result from hostile action (ambush, IED, rocket attack), the War Hazards Compensation Act (42 U.S.C. 1701) often applies. WHCA allows the DBA carrier to seek reimbursement from the U.S. Treasury for benefits paid on war-hazard claims. This reimbursement mechanism can influence how aggressively carriers contest PSC death claims versus non-hostile fatalities.
The historical trend data shows PSC claim volumes peaked between 2008 and 2014, corresponding to the surge periods in Iraq and Afghanistan. As troop drawdowns reduced the private security footprint, new claim filings declined. But legacy claims from the surge era continue to generate OALJ activity, particularly for PTSD and delayed-onset conditions.
How Should Attorneys Approach PSC Employer Investigations?
Investigating a private security contractor's DBA carrier requires a different workflow than a standard employer investigation. Three factors make PSC cases uniquely complex.
First, resolve the full corporate family before searching. If your client says they worked for "Triple Canopy" in 2016, you need to know that Triple Canopy was already part of Constellis Group by then. The DBA policy may be under the Constellis name, the Triple Canopy name, or a hybrid like "Constellis Group / Triple Canopy Inc." All three appear as distinct employer entries in DOL records. Searching only one misses critical claims history and carrier data.
Second, check for temporal carrier shifts. PSC employers change carriers more frequently than most DBA-covered contractors. The high-risk profile of security work means carriers periodically exit the PSC market segment or reprice coverage dramatically. An employer that used one carrier for its State Department WPPS contract may use a different carrier for its USAID protective services contract running simultaneously.
Third, look for WHCA applicability. If the injury resulted from hostile action in a designated war-hazard zone, the WHCA reimbursement mechanism changes the claims dynamics. Carriers have less financial incentive to aggressively contest claims they can pass to the Treasury. Document the hostile-action nexus early in your investigation.
ClaimTrove automates the alias resolution and temporal carrier mapping that makes PSC investigations so time-consuming. The platform's 214 employer alias mappings and 2,454 carrier-employer records span the full consolidation timeline for every major private security contractor family. Run your security contractor employer investigation through ClaimTrove to see the complete carrier history across all corporate name changes.