Your Client Worked for "ITT Systems" in 2010. Good Luck Finding the Right Carrier.
A paralegal lands a new DBA case. The claimant says he worked for "ITT" on a base operations contract in Kuwait. He was injured in 2010. The claimant remembers the company name on his badge. He does not remember the insurance carrier. He does not have his LS-1 notice.
The paralegal searches DOL records for "ITT" and finds nothing useful. Too many results, too many unrelated companies. She narrows to "ITT Corporation, Systems Division" and finds case data from FY2009 through FY2012. But the carrier listed in the OALJ records from that era differs from the one listed in a 2016 filing under "Vectrus Systems Corporation." A 2023 filing under "V2X" shows yet another carrier.
The same corporate entity. Three different names. At least three different carriers across a 15-year span. This is the Vectrus/V2X carrier identification problem, and it affects over 10,800 cumulative DBA claims filed between 2001 and 2024 under 13 distinct employer name variations in DOL records alone. ClaimTrove tracks every variation across 18 federal data sources, connecting each name to the carrier that held the DBA policy during that period.
How Did One Company End Up With 13 Different Names in Federal Records?
The answer is four corporate transactions in 13 years, each generating new legal entity names while leaving the old ones embedded in DOL filings that never get updated.
The lineage starts with ITT Corporation, Systems Division. ITT's defense services arm operated base support contracts across the Middle East and Europe through the 2000s. In 2011, ITT split into three companies. The defense services business became Exelis Inc., which operated as Exelis Systems Corporation for DBA purposes. DOL records from FY2012 and FY2013 show claims filed under both "ITT Corporation, Systems Division" and "Exelis Systems Corp." simultaneously, because legacy cases kept the old employer name while new injuries used the new one.
In September 2014, Exelis spun off its logistics and base operations business as Vectrus Inc. The publicly traded company started filing DBA claims under "Vectrus Systems Corporation" beginning in FY2015. But transitional cases still appeared under "Exelis Systems Corp." and hybrid names like "Vectrus Systems Corp-f/k/a Exelis Systems Corp." and "Vectrus/Exelis Systems Corp." showed up in filings through FY2023. The DOL does not enforce naming consistency.
Then in July 2022, Vectrus merged with Vertex Aerospace to form V2X Inc. This created yet another split in the records. FY2023 shows 675 cases under "Vectrus Systems Corporation" and 344 under "V2X" for the same corporate entity. By FY2024, V2X filings jumped to 972 cases, but "Vectrus Systems Corporation" still appeared with 228 cases. The old names never fully disappear. Each corporate event fractures the claims trail further, making carrier identification progressively harder for practitioners handling injuries that span these transitions.
Why Does Each Name Change Create a Carrier Identification Gap?
Corporate name changes do not just create a search problem. They create a carrier temporal shift problem. When a company restructures, it frequently rebids its DBA insurance. New corporate entities negotiate new policies. The carrier that covered ITT Corporation in 2009 is not necessarily the carrier that covered Vectrus in 2016 or V2X in 2024.
ClaimTrove's employer-carrier mapping data confirms this pattern. Across the ITT/Exelis/Vectrus/V2X lineage, at least five distinct insurance carriers appear in OALJ case records and DOL filings. The carrier shifts do not align cleanly with the name changes. A claimant injured under "Exelis Systems Corp." in FY2013 might have been covered by a completely different carrier than one injured under "Vectrus Systems Corporation" in FY2015, even though Vectrus was the direct successor entity.
The problem compounds when third-party administrators enter the picture. Several filings in this lineage reference TPAs like Gallagher Bassett and Broadspire. Practitioners who mistake the TPA for the carrier file against the wrong entity and lose months. The TPA administers the claim. The carrier underwrites the policy. They are different companies with different legal obligations. For this employer family, the TPA-to-carrier relationship has also shifted over time.
Understanding which carrier held the policy on the specific date of injury requires tracing both the employer name and the carrier timeline simultaneously. A search for "Vectrus" alone misses injuries filed under ITT, Exelis, or V2X. A search for the carrier name alone misses the temporal boundaries of that carrier's policy period.
What Does the Contract Award Data Reveal About V2X Operations?
USAspending data shows Vectrus Systems LLC holding over $17 billion in prime contract awards from the Department of Defense. The company also operates through Vectrus Federal Services GmbH, a German subsidiary with over $894 million in DoD awards and 1,131 contract actions, primarily supporting U.S. military installations across Europe.
The geographic footprint matters for DBA practitioners because it determines which carrier investigation workflow applies. V2X and its predecessor entities operate across multiple CENTCOM and AFRICOM theaters. ClaimTrove's contract award data shows performance locations in Afghanistan, Kuwait, Qatar, Bahrain, Cuba, Romania, and Germany, among others. Germany alone accounts for over 340 contract actions across both Vectrus Systems LLC and the GmbH subsidiary.
V2X's core service lines, base operations support, IT and network services, and logistics management, generate high volumes of DBA claims because they place large workforces at overseas military installations. The company inherited the LOGCAP and similar base support work that ITT Systems Division performed in Iraq and Afghanistan during the peak conflict years. That legacy means thousands of open or recently closed claims still reference ITT or Exelis as the employer, even though the responsible corporate entity is now V2X.
The January 2024 merger of V2X into Amentum Holdings adds another layer. Amentum's acquisition of V2X means the alias chain now extends to five corporate parents: ITT, Exelis, Vectrus, V2X, and Amentum. Each acquisition absorbs the predecessor's DBA liabilities but does not retroactively update the employer name on existing DOL filings.
How Does the Alias Problem Compare to Other Defense Contractor Mergers?
The Vectrus/V2X lineage is not unique. Defense contractor consolidation has created similar alias chains across the industry. DynCorp became DynCorp International, then was absorbed into Amentum. PAE Incorporated merged into Amentum through a separate path. Blackwater became Xe Services, then Academi, then folded into Constellis.
What makes the V2X lineage particularly challenging is the volume. With 10,805 cumulative claims across the family, this is one of the largest DBA employer groups in federal records. The 13 name variations in DOL case summaries alone do not capture the full picture. Employer-carrier mapping records show additional variations like "VECTRUS SYSTEM CORP." (missing the S), "VECTRUS/EXELIS SYS. CORP." (abbreviated), and "ITT CORPORATION / EXELIS" (slash-separated hybrid). Each abbreviation and typo creates another search dead end for practitioners using exact-match queries.
The employer alias resolution problem is why keyword searches against DOL databases fail for companies with complex corporate histories. Searching "Vectrus" misses ITT-era claims. Searching "ITT" returns thousands of irrelevant results from ITT's other divisions. Searching "V2X" only captures post-merger filings. No single search term covers the full lineage. Practitioners need a system that maps all variations to a unified employer profile and connects each variation to the carrier that held the DBA policy during that specific period.
What Should Practitioners Do When They Get a V2X or Vectrus Case?
Start with the date of injury. That single data point determines which corporate name was active, which carrier held the policy, and which TPA administered the claim. A 2009 injury falls under ITT Corporation. A 2013 injury could be either ITT or Exelis depending on the specific contract. A 2015 injury is likely Vectrus. A 2023 injury could be Vectrus or V2X. A 2025 injury is V2X under the Amentum umbrella.
Next, identify the specific contract. V2X operates multiple contracts simultaneously across different theaters. The carrier may vary by contract, not just by time period. A base operations support contract in Kuwait might carry a different DBA policy than an IT services contract in Germany. The contract number, if the claimant has it, narrows the carrier search significantly.
Third, do not assume the carrier you find in one OALJ case applies to your client's situation. The DynCorp/Amentum coverage history shows how carriers shift every few years for large defense contractors. The same pattern applies to V2X. A carrier identified in a 2019 Vectrus case may have been replaced by the time your client was injured in 2022.
Finally, check for the LS-1 notice. The employer is required to post the carrier's name and policy number at the worksite. If your client photographed the notice or retained a copy, that is the fastest path to carrier identification. If not, you need a tool that resolves all 13+ name variations, cross-references carrier mappings across multiple federal data sources, and accounts for temporal shifts in coverage.
ClaimTrove's investigation engine does exactly this. Enter any name in the V2X lineage, from "ITT Corporation" to "V2X Inc." to "Vectrus/Exelis Systems Corp." The engine resolves aliases, searches across 18 federal databases, and returns carrier matches scored by confidence and date relevance. Run your V2X carrier investigation now and get answers in minutes instead of weeks.