A claimant walks into your office with an injury from a logistics yard at a forward operating base in Kuwait. The DBA-7 they hand you names "Vectrus." Simple, you think. One employer, one carrier, one filing. Then you pull the DOL case summary records and the picture fractures. Vectrus Systems Corporation. Vectrus Systems Corporation (formerly Exelis). Vectrus/Exelis Systems Corp. Vectrus Systems Corp-f/k/a Exelis Systems Corp. Four spellings of the same company in a single cumulative report, and that is before you account for the V2X merger that swallowed the entire entity in 2022.
This is the trap base-operations primes set for DBA practitioners. These are not flashy security contractors. They run dining facilities, fuel depots, vehicle maintenance bays, and base infrastructure across CENTCOM. The work is unglamorous, the injuries are constant, and the corporate structure changes faster than the claims close.
ClaimTrove data shows Vectrus Systems Corporation alone accounts for 7,243 cumulative DBA cases from 2001 through 2024, including 41 death claims. That is not a fringe employer. That is one of the most frequent DBA defendants in the entire dataset. And the carrier behind those 7,243 cases is not constant. It shifts with the corporate entity, the contract vehicle, and the policy year.
The "vectrus v2x dba insurance base operations contractor" question looks like a name lookup. It is actually a corporate genealogy problem layered on top of a carrier-by-period problem. Get either layer wrong and you file against the wrong policy.
Why are base-operations primes like Vectrus recurring DBA defendants?
Security contractors get the headlines, but base-operations and logistics primes generate far more claim volume. The reason is exposure. A private security detail might field a few hundred shooters. A base-ops prime employs thousands of cooks, mechanics, electricians, fuel handlers, and warehouse staff, every one of them performing physically demanding work in austere conditions.
The case summary data makes this concrete. Vectrus claim volume by fiscal year is not flat. It surges with contract activity. FY2022 shows 2,297 cases. FY2021 shows 2,092. FY2019 shows 328. The earlier years run in the low hundreds. When a contractor wins a large LOGCAP-style base-support task order, the headcount jumps, and so does the DBA claim curve roughly 18 to 36 months behind it.
This pattern matters for two reasons. First, it tells you the company was running heavy operations during specific windows, which helps you anchor the injury date to an active contract. Second, it tells you the carrier you are hunting is a workers' compensation underwriter writing a high-frequency, high-severity book, not a boutique policy. These are the carriers that show up again and again across the base-ops sector.
Vectrus is not unique here. The same dynamic drives claim volume for other overseas logistics and engineering primes. We walk through a parallel example in our analysis of why 19 name variations make AECOM the hardest carrier trace in construction, where contract-driven headcount and corporate restructuring combine to scramble the carrier trail in much the same way.
The takeaway for your file: a base-ops prime with thousands of claims is a moving target, not a fixed defendant. The volume itself is a signal that the carrier relationship is structured around large contract vehicles, and those vehicles change carriers when they re-compete.
What is the Vectrus to V2X merger and why does it matter for old claims?
In 2022, Vectrus merged with the Vertex Aerospace business and rebranded the combined company as V2X. ClaimTrove's alias records capture this lineage directly: Vectrus is the canonical entity, "V2X" is tagged as the successor, and "Vertex Aerospace" is tagged as the predecessor partner in the combination. The records also flag V2X as the surviving legal name in the post-merger structure.
Here is why a corporate event from 2022 controls a claim from 2016. DBA liability follows the policy, not the brand. When you file, you need the entity that held the workers' compensation coverage on the date of injury, and the carrier that wrote that policy for that entity. A merger does not retroactively rewrite who insured a worker in 2016. It does, however, change which legal name appears on current filings, who responds to your correspondence, and which corporate counsel picks up the phone.
The Exelis layer makes this worse. Before it was Vectrus, the company operated under Exelis Systems Corporation. That is why the case summary data carries "formerly Exelis" and "f/k/a Exelis" variants. A claimant injured in the early 2010s may have a DBA-1 naming Exelis, a medical record naming Vectrus, and a current entity named V2X, all for the same continuous operation at the same base.
Mergers are the single most reliable way to lose a carrier trail. We document the mechanism in detail in our breakdown of why mergers and joint ventures hide the overseas contractor carrier, and the same logic applies to the technology-sector splits we cover in the Leidos and SAIC carrier identification analysis. Each corporate event creates a new name, and each new name can sit on a different policy.
The practical danger is filing against V2X today for an injury that occurred under Exelis or pre-merger Vectrus, assuming the current entity's carrier applies. It may not. The carrier on a 2016 base-support contract can differ from the carrier on the 2023 V2X book. You have to resolve the entity for the injury date first, then the carrier for that entity and period.
How many names does this one company actually use?
Count them. In the DOL case summary data alone, Vectrus appears as at least four distinct entity strings. Add the corporate lineage and you get Exelis Systems Corporation, Vectrus Systems Corporation, Vertex Aerospace, and V2X. ClaimTrove's contract award records return roughly 1,895 awards tied to Vectrus naming, and the Afghanistan FOIA contractor database returns 224 records under Vectrus and Exelis prime-contractor names.
Each of those name forms is a separate search key. If you query DOL records for "V2X" you miss the 7,000-plus cases filed under Vectrus and Exelis. If you query "Vectrus" you miss current filings under V2X. If you query neither Exelis variant, you lose the early-decade claims entirely. A single missed alias can hide the exact decision or coverage record that names your carrier.
This is the alias resolution problem at the heart of DBA carrier work. The hardest version of it involves serial name changes that compound across a decade. Our deep dive on how five name changes created the most complex DBA carrier trail in history shows where this pattern reaches its extreme, and the same investigative discipline applies to Vectrus on a smaller scale.
The corporate genealogy is not trivia. It is the map that connects a claimant's injury to a carrier of record. Without it, you are searching a fraction of the available evidence and calling the result a complete investigation.
Where does Vectrus and V2X work, and why does location change the carrier?
Vectrus built its DBA exposure on CENTCOM base operations. The contract award and Afghanistan FOIA records place the company across Kuwait, Afghanistan, Iraq, and the broader Gulf theater, performing base life support, logistics, and infrastructure maintenance. This geography is not incidental to carrier identification. It is central to it.
Some overseas contracts carry agency-mandated DBA carriers. When a specific awarding agency runs a mandatory insurance program during a defined window, every contractor under that agency uses the same carrier for that period, regardless of the company's normal commercial relationship. A base-support task order awarded through one vehicle can therefore sit on a completely different carrier than a task order the same company holds elsewhere.
That is why two Vectrus injuries in the same year, at different bases, under different contract vehicles, can point to different carriers. The company's "usual" carrier is not the whole answer. The contract vehicle and the awarding agency's insurance rules can override it. This is the same licensing-and-coverage paper trail we trace in our piece on how ITAR registration creates a carrier paper trail, where the federal contracting structure, not the corporate logo, determines the coverage.
For your investigation, location plus date plus contract vehicle is the real query. Vectrus at Bagram in FY2016 is a different carrier question than Vectrus in Kuwait in FY2022. ClaimTrove resolves each as a distinct carrier-by-period lookup rather than a single company-wide answer.
Who is the DBA carrier for Vectrus and V2X?
This is the question every reader actually wants answered, and it is exactly the question a blog post cannot responsibly answer in the abstract. There is no single Vectrus carrier. There is no single V2X carrier. There is a carrier for a specific entity, on a specific contract vehicle, in a specific policy year, and that answer moves across the company's history.
What we can tell you is how the answer is structured. The carrier of record depends on three variables stacked together. First, which entity held coverage on the injury date: Exelis, pre-merger Vectrus, or V2X. Second, whether the contract ran under an agency with a mandatory carrier program during that window. Third, the policy year, because base-ops books re-compete and carriers rotate as contracts turn over. Our data on base-ops primes generally shows carrier relationships shifting on a multi-year cadence rather than holding steady across a decade.
Getting this wrong has consequences. File against the current V2X carrier for a 2015 Exelis injury and you may name a carrier that never insured that risk. The claim stalls, the statute runs, and you are reconstructing the carrier history under deadline pressure.
ClaimTrove was built to collapse this into a single investigation. You enter the employer, the location, and the injury date. The engine resolves the Exelis-Vectrus-V2X lineage, checks every name variation against DOL case summaries, coverage records, OALJ decisions, contract awards, and the Afghanistan FOIA database, then runs the carrier waterfall, including agency-mandate checks, to return a carrier ranked by confidence and dated to the period that matters. Run a Vectrus or V2X investigation in ClaimTrove and resolve the entity, the aliases, and the carrier-by-period in one pass instead of stitching four name variations together by hand.
What should you verify before you file a Vectrus or V2X DBA claim?
Start with the entity for the injury date, not the entity on today's letterhead. Confirm whether your claimant worked under Exelis, pre-merger Vectrus, or post-2022 V2X. The badge, the paystub, and the contract number each carry clues, and they will not always agree because the operation was continuous while the corporate name changed underneath it.
Next, identify the contract vehicle and the awarding agency. A base-support task order tells you whether an agency-mandated carrier program might control. This single fact can override the company's usual carrier relationship, and it is the variable attorneys miss most often.
Then run every name variation against the records, not just the one on the claim form. The 7,243 cumulative cases are split across multiple entity strings. The decision or coverage record that names your carrier might be filed under a spelling you have not searched. ClaimTrove handles this expansion automatically, but if you are working by hand, search all four forms at minimum.
Finally, treat the carrier answer as period-specific. Do not assume the FY2022 carrier covers an FY2016 injury. Anchor the carrier to the policy year and the entity, and document why. That is the difference between a filing that survives a coverage dispute and one that gets bounced to the wrong adjuster.
The bottom line for DBA practitioners
Vectrus and V2X are a textbook case of why base-operations primes are hard. High claim volume, a multi-decade corporate lineage from Exelis through V2X, contract-vehicle-dependent carriers, and at least four name variations in the DOL data alone. The "vectrus v2x dba insurance base operations contractor" question is never a one-line lookup. It is a layered investigation where the entity, the contract, and the policy year each move the carrier answer.
You can reconstruct this by hand across DOL case summaries, OALJ decisions, and contract databases, accepting that one missed alias hides the carrier. Or you can let the investigation engine resolve the entire lineage and return a dated, confidence-ranked carrier in seconds.