A paralegal opens a DBA file. The injured worker did signals-intelligence support at a forward site in 2012. The retainer names the employer as Six3 Systems. She searches federal contract databases for that name and finds a thin, frozen trail that stops around 2013. No recent awards. No obvious carrier. The company seems to have vanished.
It did not vanish. Six3 Systems was acquired, and its overseas work, its contract vehicles, and its Defense Base Act exposure were absorbed into a much larger parent. The claim is still very much alive. The evidence just lives under a different corporate name now.
This is the recurring trap with intelligence-services contractors. They grow through acquisition, get folded into a prime, and then the original employer name goes quiet in the public record. The Defense Base Act, codified at 42 U.S.C. sections 1651 through 1654, still applies to that overseas injury. But finding the responsible carrier means tracing a corporate history most attorneys never think to run.
Six3 Systems is a clean example of the problem. A young intelligence contractor, built through its own roll-up of smaller firms, then swallowed by a defense prime at the peak of the post-surge intelligence market. Every layer of that history changes where a DBA claim's records sit today. This profile walks through what happened, why it matters for carrier identification, and how a disciplined investigation recovers the trail that a plain name search misses.
Who Was Six3 Systems Before the CACI Acquisition?
Six3 Systems was a Virginia-based intelligence and cyber services contractor. It focused on the kind of work that puts people overseas: signals intelligence, surveillance support, cyber operations, and biometrics and identity-intelligence services for defense and intelligence customers. That mission profile is exactly the sort of work that triggers Defense Base Act coverage when it happens abroad.
The company was itself a roll-up. It grew by acquiring smaller specialty firms and stitching them into one intelligence-services brand. That matters for a claims investigator. It means the name on a 2011 or 2012 injury may trace back to a predecessor entity that Six3 had absorbed only a year or two earlier. The employer history has layers inside layers.
Intelligence contractors also work under contract structures that hide the customer. Task orders route through prime vehicles. Classified programs do not advertise the place of performance. So the public footprint of a company like Six3 is thinner than a logistics or construction prime of the same size. There are fewer visible awards, and the ones that exist often omit the overseas location that makes DBA apply.
ClaimTrove tracks these corporate name families precisely because a single legal name rarely tells the whole story. The same challenge drives the broader problem of resolving one employer across many name variations. Predecessor firms, subsidiaries, and DBA trade names all point back to a single canonical entity that controls the claim.
What Happened When CACI Acquired Six3 Systems?
In 2013, CACI International acquired Six3 Systems for a reported price near 820 million dollars. The deal moved Six3's intelligence, surveillance, and cyber business into CACI's national-security portfolio. Over time, the Six3 brand faded and its programs continued under CACI.
For a DBA claim, the acquisition date is the hinge. An injury before the deal happened while Six3 was an independent employer with its own insurance arrangements. An injury after the deal happened inside CACI's corporate structure. The two scenarios can point to entirely different places in the record, even for the same program at the same overseas site.
This is where a name search fails. If you search only for Six3 Systems, you capture the pre-acquisition slice and nothing after. If you search only for CACI, you may miss the legacy Six3 contract that the injury actually arose under. The correct answer requires holding both names in view and letting the injury date decide which era controls.
Corporate consolidation like this is not a rare edge case in defense contracting. It is the norm. Primes buying specialty firms and absorbing their overseas exposure is the same force behind how defense-contractor consolidation reshapes DBA coverage. It reaches the entire market, not just one intelligence firm.
How Does an Acquisition Fold Legacy Intel Claims Into a Parent's Records?
When a parent buys a subsidiary, the acquired company's assets, contracts, and liabilities generally travel with the deal. Open contracts get novated or assigned. Ongoing programs continue under new ownership. And insurance obligations, including Defense Base Act coverage duties written into federal contracts under FAR 52.228-3, follow the work.
That means a Six3 injury does not lose its coverage because Six3 stopped being an independent company. The obligation to insure the worker attached at the time of the contract and the injury. The question is which policy and which carrier stood behind that specific contract at that specific time. Acquisition does not erase that answer. It just relocates the paper.
Legacy claims fold into the parent in several ways. The parent may assume administration of open claims. Old policies from the subsidiary's era may still control injuries that predate the deal. And federal databases begin attributing the subsidiary's contract activity to the parent, so the historical trail gets rewritten under the new name.
Running the corporate lineage is not optional here. It is the investigation. Attorneys who want a repeatable method should study how to trace an employer's corporate history for DBA claims. The acquisition timeline tells you whether the subsidiary's carrier or the parent's arrangement controls a given injury date.
Why Is Carrier Identification Harder for Intelligence Contractors?
Intelligence-services work adds friction that ordinary contractor investigations do not face. The programs are often classified, so the place of performance is redacted or generic. The contract vehicles are frequently indefinite-delivery task orders, where the controlling insurance can change from one order to the next. And the workers themselves may be linguists, analysts, or technical specialists whose job titles do not scream overseas deployment.
The result is a public record that undercounts the real overseas exposure. A search may return domestic-looking awards and miss the forward-deployed task order where the injury actually happened. Attorneys who take the visible contract list at face value can conclude, wrongly, that DBA does not apply.
This same opacity affects other intelligence-adjacent firms. The carrier trail for linguist and intelligence-support work is among the hardest in the DBA space. The analysis of why linguist and intelligence-support contractors resist a routine carrier search reads as a near mirror of the Six3 problem. Thin public awards, classified programs, and specialist job titles combine to break the usual shortcuts.
Add the acquisition layer on top of that opacity and the difficulty compounds. You are now tracing a hard-to-see overseas footprint across a corporate boundary. Neither the old name nor the new name alone gives you a complete picture. You need the union of both, filtered by the date the injury occurred.
How Do You Trace a Six3 Systems Claim Across Federal Databases?
Start with the injury date and the corporate timeline. Fix when the worker was hurt, then place that date relative to the 2013 acquisition. That single comparison tells you whether you are investigating the independent Six3 era or the CACI-owned era, and it narrows every search that follows.
Next, run both names in parallel. Search the predecessor name and the parent name, and include the smaller firms Six3 itself absorbed. Federal identifiers help here. A UEI or CAGE code can survive a name change and tie the old entity to the new one. These federal registry identifiers so often unlock a stalled trace.
Then layer the sources. Contract award records show the program and, sometimes, the overseas place of performance. Personnel-location records can corroborate contractor presence at a specific site during a specific period. Legal decision records and coverage filings can surface the carrier that actually stood behind a contract. No single source answers the question. The answer emerges from the overlap.
Finally, resolve the parent's coverage posture separately. Some large defense primes carry commercial DBA policies. Others self-insure, which changes who you pursue entirely. Rather than assume, verify the parent's structure directly. The companion profile on how CACI's coverage structure changes a carrier search walks through why the parent's posture, not the subsidiary's old name, often decides where a modern claim lands.
What Should Attorneys Do Before Naming a Carrier on a Six3 Claim?
Do not name a carrier from a single database hit. The Six3 fact pattern is exactly the kind that produces a confident wrong answer. A frozen name, a thin award list, and a missing overseas location all push an investigator toward the wrong conclusion.
Build the timeline first, confirm the corporate lineage second, and only then match the injury date to a coverage source. If the parent self-insures, there may be no third-party carrier to pursue at all, and your strategy shifts to the employer directly. If a commercial policy controlled the legacy contract, the date of injury tells you which one.
ClaimTrove was built for exactly this problem. Running Six3 Systems through the investigation engine resolves the aliases and surfaces the predecessor and parent entities. It cross-references contract data, personnel-location records, legal decisions, and coverage filings in one pass. It shows you the corporate boundary and where the claim's records sit on each side of it. Run this employer through ClaimTrove to recover the trail a plain name search leaves behind.
The intelligence-services sector will keep consolidating. Every acquisition folds another legacy contractor's overseas exposure into a bigger parent. The attorneys who win these claims are the ones who trace the history instead of trusting the name on the retainer.