Loading...
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.
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.
Supreme Group fed armies across Afghanistan through 8+ named entities, each splintering DBA coverage. Here is why tracing its carrier is so hard.
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.
Searching DBA records for CACI International and finding gaps? That absence may mean self-insurance. Here is how the investigation actually works.
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.
PAE built a sprawling overseas footprint before the Amentum merger, scattering its DBA carrier records across dozens of names, contracts, and years.
Raytheon's mergers, subsidiaries, and self-insurance make its DBA carrier hard to trace. Here is how federal records reveal the responsible party.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
