Loading...
When CACI acquired Six3 Systems in 2013, the intelligence contractor's overseas DBA exposure did not disappear. It moved into a parent's federal records, where most attorneys lose the trail.
The KGL name splits into at least seven federal entities, and its DBA carrier hides behind a subcontractor chain. Here is what its 27 filed cases and driver and yard roles mean for your claim.
Serco appears under at least three separate employer names in DOL cumulative case summaries. Here is where the base and mission support DBA exposure hides and why one lookup never answers the carrier question.
QinetiQ North America put robotics techs, test engineers, and field service reps in DBA jurisdiction, yet its name changes and split divisions scatter the carrier trail across more than 43,000 federal contract awards.
Culmen International deploys logistics and advisory staff to US government missions overseas, yet the DBA carrier behind those workers is rarely printed on any intake sheet. Here is how to trace it.
Aegis Defence Services ran some of the largest private security work of the Iraq war before GardaWorld acquired it in 2015. That lineage is exactly why its DBA carrier is hard to pin down.
Two confusing employer names, one hard DBA search. GIS and Hart each show, in their own separate corporate histories, why private security name changes wreck DBA carrier searches.
Janus Global Operations built its name on demining and EOD abroad, and ClaimTrove records show 406 DBA cases with 54 death claims under a single spelling. Here is why the carrier resists a quick answer.
One employer name, at least six spellings in DOL records, and 35 death claims under a single variation. Reed Incorporated shows why fuel and logistics contractors resist a fast carrier answer.
Torres AES shows up under six name spellings and roughly 289 cumulative DBA case records, yet public data gives no clean carrier answer for its security and linguist field staff.
Cubic runs overseas combat training and simulation programs, and our federal data records places of performance in Jordan and Lebanon. Here is why identifying the DBA carrier is harder than it looks.
MPRI stopped operating under its own name in 2000, and its work later ran through an Engility spinoff and a SAIC acquisition. A legacy MPRI claim can point at three different corporate parents depending on the injury date.
Peraton did not exist before 2017, yet ClaimTrove records already list 13 Defense Base Act cases under the exact name. Here is why intelligence and IT primes hide the carrier.
Amentum was created as a standalone company in 2020, then absorbed DynCorp, PAE, and Jacobs' government business, so a base-operations injury before those deals belongs to a predecessor entity and a different carrier.
IAP Worldwide Services runs base operations and power generation across multiple overseas theaters, and its DBA coverage is bound at the task-order level, so no single carrier lookup works.
A single linguist prime can employ US citizens, third-country nationals, and local nationals on the same contract, and ClaimTrove data tracks 637 authorized DBA carriers before you even reach the alias problem.
A linguist injured on an intelligence-support mission often files under one name while the DBA policy sits under another. Here is why SOSi-type primes bury the carrier and how to dig it out.
Vectrus Systems Corporation carries 7,243 cumulative DBA cases in DOL records, and its 2022 merger into V2X means the name on your claimant's badge may not be the entity that held the policy. Here is why base-ops primes are recurring DBA defendants.
Parsons ran overseas construction across 39 countries and 485 federal contract awards in ClaimTrove data. Its DBA carrier shifts with the contract, not the company, which is why a single-name lookup fails.
Honeywell shows up among the top employers in 15,005 OSHA inspection records, yet most attorneys never connect its overseas technology and logistics work to Defense Base Act coverage. The carrier sits across business units, and that is exactly where claims get lost.
Air-charter contractors like Omni Air International move troops and cargo into combat zones under federal contracts, and every crew member on those missions can trigger Defense Base Act coverage. Identifying the carrier behind those flights is harder than it looks.
Valiant Integrated Services shows up in ClaimTrove under four different legal names across 690 overseas contract awards and 520 cumulative DBA cases. That fragmentation is exactly why pinning this prime to one carrier is harder than it looks.
Chemonics is one of USAID's largest implementing partners, with work across more than 70 countries. Its DBA coverage follows USAID's AIDAR rules, not the defense-contractor playbook, and that distinction changes where you look for the carrier.
Jacobs Engineering holds 443 overseas federal contract awards, yet most of its DBA claim volume now sits inside Amentum after a 2024 spin-merge. Tracing the carrier means tracing the corporate history first.
Engility moved through at least four corporate identities in seven years before SAIC absorbed it in 2019. That path scatters a single contractor's DBA carrier record across multiple legal names, FEINs, and policy periods.
BAE Systems' U.S. work runs through a ring-fenced American subsidiary, not its UK parent. That single structural fact changes carrier tracing, jurisdiction analysis, and where you look for proof of DBA coverage.
PWC Logistics generated 257 DBA cases including 61 death claims before rebranding to Agility, and its affiliate structure now scatters carrier evidence across at least four distinct entity names in our data.
Tetra Tech runs USAID and Defense Department work across 100-plus countries through a web of subsidiaries. That structure is exactly what makes its DBA carrier so hard to pin down.
Bechtel ran some of the largest overseas reconstruction projects of the last two decades, generating DBA claims across at least four countries. Its insurance carrier on any given project is far less obvious than the company's size suggests.
Centerra Group operates under a Constellis corporate umbrella with joint ventures like Centerra-Parsons, and that structure scatters its DBA coverage across at least three name layers and multiple contract periods.
Searching DBA records for CACI International and finding gaps? That absence may mean self-insurance. Here is how the investigation actually works.
Lockheed Martin runs hundreds of overseas programs, and its DBA carrier shifts by contract and year. Here is why one answer never fits, and how to find the right one.
Supreme Group fed armies across Afghanistan through 8+ named entities, each splintering DBA coverage. Here is why tracing its carrier is so hard.
Northrop Grumman files DBA claims under at least four entity names plus a self-insured arm. Here is why the carrier is so hard to trace.
General Dynamics is not one employer in DBA records. Here is why the parent name returns the wrong carrier and how to resolve the right division.
Interpreters are covered by the DBA, but prime-and-sub layering and joint-venture primes hide the carrier behind linguist firms. Here is why.
ManTech runs hundreds of federal contracts across agencies, so its DBA carrier changes by contract and date. Here is how to find the right one.
Raytheon's mergers, subsidiaries, and self-insurance make its DBA carrier hard to trace. Here is how federal records reveal the responsible party.
PAE built a sprawling overseas footprint before the Amentum merger, scattering its DBA carrier records across dozens of names, contracts, and years.
Blackwater USA went through five corporate name changes in under a decade, generating 27 distinct employer identities across DOL records and complicating DBA carrier identification for every claim period from 2003 to present.
With 208 overseas contract awards across 48 countries and over 225 cumulative DBA cases, Booz Allen Hamilton creates a carrier identification challenge that most attorneys never anticipate from a consulting firm.
The ITT-to-Exelis-to-Vectrus-to-V2X corporate lineage has generated over 10,800 DBA claims across 13 distinct employer name variations in DOL records, each potentially tied to a different insurance carrier.
Sallyport Global generated over 1,900 cumulative DBA cases across at least 14 employer name variations, making carrier identification one of the hardest problems in mid-tier PMC investigations.
AECOM appears under 19 distinct employer names across federal DBA records, with over 6,600 OWCP case filings spanning subsidiaries like URS, AC First, and GSS Ltd. Tracing the right carrier requires untangling two decades of acquisitions.
Leidos and SAIC share over 860 cumulative DBA cases across 7 name variations. The 2013 corporate split created a carrier identification puzzle that trips up even experienced practitioners.
ANHAM FCZO fed tens of thousands of U.S. personnel across Iraq for over a decade, yet identifying the DBA carrier for any given ANHAM employee at any given base requires navigating foreign registration gaps, multiple contract vehicles, and a subcontractor workforce that dwarfed direct hires.
AAFES runs 2,400+ retail and food operations on military bases worldwide, yet it is neither a federal agency nor a conventional federal contractor. Here is why its contractor injury claims still fall under the Defense Base Act.
L3Harris Technologies is one of a handful of top-tier defense contractors that handles DBA claims entirely in-house. If you file a notice of injury expecting to track down a commercial carrier, you will waste weeks chasing a policy number that does not exist.
SAIC holds billions in federal IT and intelligence contracts, but its self-insured DBA structure means there is no commercial carrier to contact. Here is what that changes for your claim.
The Constellis family spans at least 6 corporate identities, 18 federal filing name variations, and over 5,200 compound name records across DOL databases. Tracing DBA carrier history through this employer family requires resolving every alias or risking a claim filed against the wrong insurer.
Fluor Corporation operates through at least seven distinct entity names across billions in OCONUS construction contracts. Tracing the correct DBA carrier for a Fluor employee requires understanding which subsidiary held the contract, which program funded it, and when the coverage shifted.
SOC LLC appears under 9 distinct name variations across 25 carrier mapping records in federal DBA data. With over $2 billion in State Department security contracts spanning Iraq, Somalia, and Israel, tracing the correct DBA carrier requires resolving a tangled corporate history that most manual searches miss entirely.
KBR generated more DBA claims than any other single employer during the LOGCAP era. Tracing its carrier history requires navigating the Halliburton split, multiple name variants, and fiscal year carrier shifts across 15+ years.
DynCorp International has changed hands four times in two decades, morphing from a CSC subsidiary into part of Amentum. Each ownership change brought new entity names, new carrier arrangements, and new headaches for DBA practitioners.
KBR is one of the most-searched employers in DBA history. With roots in Halliburton, multiple subsidiaries, and a carrier history that has shifted repeatedly across fiscal years, identifying the correct insurer for a KBR claim requires precise temporal mapping.
GardaWorld's 2015 acquisition of Aegis Defence Services created one of the most complex employer identification challenges in DBA claims. With 25+ name variations scattered across federal records, tracing carrier history requires systematic alias resolution.
