CIGNA to ACE to Chubb: The DBA Carrier Lineage That Still Controls Decades-Old Claims

Why does a CIGNA insurance card from 2003 now point to Chubb?

You pull an old OWCP coverage filing on a contractor injured in Iraq in 2004. The carrier line reads CIGNA. You call CIGNA. They tell you they do not write workers' compensation anymore and have not for two decades. The claim is still open. The contractor is still owed money. So who pays?

The answer lives in a corporate chain that most attorneys never trace. CIGNA's property and casualty book, including its Defense Base Act policies, was sold to ACE Limited in 1999. ACE then bought Chubb in 2016 and took the Chubb name for the combined company. That single CIGNA-era policy did not disappear. The obligation followed the book of business through two corporate transitions and now sits with a Chubb entity.

This is the core problem with the CIGNA ACE Chubb DBA insurance carrier lineage history. The name on the document is frozen at the moment the policy was written. The responsible party keeps moving. DBA death and permanent disability claims routinely span decades. Over that span, the carrier of record and the carrier that actually pays become two different things. Years of mergers separate them.

ClaimTrove tracks 637 authorized DBA carriers and maps them against decades of federal records. The corporate genealogy that turns a CIGNA card into a Chubb obligation is exactly the kind of buried connection that derails carrier identification. This article explains the lineage, why it matters for old claims, and where the tracing actually breaks down.

What happened when CIGNA sold its property and casualty book?

CIGNA Corporation spent most of the 1990s as a diversified insurer writing both health coverage and property and casualty lines. The property and casualty side included commercial workers' compensation, which is the legal vehicle Defense Base Act coverage rides on. DBA policies are workers' compensation policies extended to overseas federal contract employees under the Longshore and Harbor Workers' Compensation Act framework.

In 1999, CIGNA sold its entire domestic property and casualty operation to ACE Limited, a Bermuda-based insurer. The deal moved the active policies, the renewal rights, and critically the runoff liabilities. Runoff means the open claims on policies already written. A DBA claim from a 1997 contract did not stay with CIGNA. It transferred to ACE as part of the acquired book.

This is the first link attorneys miss. CIGNA continued to exist as a major health insurer, so calling CIGNA gets you a real company that genuinely has no record of your DBA file. The company is not stonewalling. The book of business left the building in 1999. Understanding who actually holds a legacy policy requires reading the carrier name as a historical snapshot, not a current fact.

The mechanics of how a single corporate name can hide multiple underwriting entities is its own discipline. We cover the broader pattern in our analysis of the hidden carrier families where multiple names mean one company. The CIGNA transition is just one instance of a much larger structural problem in DBA insurance.

How did ACE become Chubb, and why does it matter for old claims?

ACE Limited spent the 2000s and early 2010s building one of the largest commercial insurance platforms in the world, partly by absorbing other carriers' books. The CIGNA property and casualty operation became part of that platform. ACE American Insurance Company emerged as one of the principal underwriting entities, and it carried forward DBA obligations that traced back to the CIGNA era.

In January 2016, ACE completed its acquisition of The Chubb Corporation for approximately $29.5 billion. In a move that confuses nearly everyone, ACE adopted the Chubb name for the merged enterprise. So the company that bought Chubb is now called Chubb. The legacy ACE American entity continues to operate underneath the Chubb brand.

For a decades-old DBA claim, the carrier of record might read CIGNA. The runoff might have moved through ACE American. The current responsible parent is a Chubb company. Three names, one continuous chain of obligation. We break down the entity structure in detail in our piece on how the ACE American and Chubb subsidiary structure confuses carrier identification.

Why does the lineage matter beyond trivia? Because service of process, claim correspondence, and settlement authority all depend on naming the correct legal entity. A demand letter addressed to CIGNA for a 2002 injury may never reach the desk that controls the file. The claim does not become uncollectible. It becomes mistargeted.

Why are old DBA claims uniquely exposed to carrier lineage problems?

Defense Base Act claims have unusually long tails. A permanent total disability award can pay for the rest of a claimant's life. A death claim supports survivors for years. Medical benefits for a traumatic injury can reopen decades after the original event. ClaimTrove holds 5,022 OALJ decisions, and the timeline of disputed claims regularly stretches ten, fifteen, or twenty years from injury to final resolution.

Over a twenty-year claim life, the insurance industry consolidates relentlessly. The carrier that wrote the policy may merge twice, sell its runoff once, and rebrand once more before the file closes. Each transaction breaks the link between the name on the original document and the entity that holds the checkbook today.

This is not unique to the CIGNA chain. The same dynamic drives the broader trend we document in our analysis of how defense contractor consolidation reshapes DBA coverage. Both the contractor side and the carrier side consolidate over the same twenty years. As a result, a single claim can carry four or five legacy names across federal records.

The practical consequence is that the oldest claims, the ones with the most accrued value, are the hardest to trace. A fresh 2024 claim names a current carrier. A 2003 claim names a carrier that has since changed identity at least once. The carrier identification work scales inversely with claim age, and the dollar value scales directly with it.

What is the difference between a carrier of record and the responsible entity?

This distinction sits at the heart of every legacy carrier problem, and the CIGNA chain illustrates it cleanly. The carrier of record is the name printed on the policy and the coverage filing. The responsible entity is the legal party that actually holds the obligation today. For a fresh claim, these are the same. For an old claim that has survived two corporate transitions, they diverge.

When CIGNA sold its book in 1999, the carrier of record on existing policies stayed CIGNA, frozen in the documents. The responsible entity became ACE. When ACE rebranded as Chubb in 2016, the responsible entity shifted again on those same legacy policies. The record never changed. The obligation moved twice. An attorney who treats the carrier of record as the responsible party is chasing a company that exited the business decades ago.

The gap matters most at three moments in a claim. It matters when you send the initial demand, because a misaddressed notice can sit unanswered. It matters at settlement, because only the responsible entity can bind a release. And it matters on appeal, because naming the wrong carrier in a filing can produce procedural challenges that delay relief to your client. None of these failures mean the claim is weak. They mean the claim is pointed at a ghost.

ClaimTrove's investigation engine is built to close this gap. It reads the carrier of record from the filing, walks the corporate genealogy, and returns the current responsible entity with a confidence level drawn from 2,454 SME-confirmed mappings. The point is not to memorize that CIGNA became Chubb. The point is to resolve your specific claim, in its specific year, to the live entity that can actually pay it.

Where does the CIGNA to Chubb trace actually break down?

The lineage looks clean on paper. CIGNA to ACE in 1999, ACE to Chubb branding in 2016. In practice, three things break the trail for attorneys working real files.

First, the carrier name on the OWCP filing is whatever was true at policy inception. A policy bound in 1998 reads CIGNA. A policy bound in 2005 might read ACE American. A policy bound in 2018 reads Chubb. The same underlying obligation chain produces three different document names depending on the year. Reading these as three separate carriers is the most common mistake.

Second, third-party administrators sit between you and the carrier. The entity handling correspondence on a legacy DBA claim is often a TPA, not the carrier itself. The TPA name on the letterhead tells you nothing about which carrier in the CIGNA ACE Chubb chain actually carries the risk. We explain how to separate these layers in our guide on how to spot a TPA versus an actual DBA carrier.

Third, the federal records themselves are inconsistent. Across our 154,886 OWCP coverage card filings, the same carrier can appear under slightly different spellings, abbreviations, and entity suffixes. Matching a CIGNA-era filing to a current Chubb entity requires resolving those name variants, not just reading the field at face value. Our coverage of how OWCP coverage cards help identify DBA carriers walks through what these filings do and do not tell you.

Stack these three breakpoints and the picture is clear. The lineage is knowable, but it is not visible from any single document. You need the document, the corporate genealogy, the TPA mapping, and the name-variant resolution working together.

What does the CIGNA ACE Chubb DBA insurance carrier lineage history timeline look like?

Carrier identification gets easier when you anchor it to dates. The lineage breaks into clean segments, and the policy inception year tells you which segment a given DBA claim belongs to. Walking the timeline removes most of the guesswork.

Through the 1990s, CIGNA wrote commercial workers' compensation, and DBA coverage rode on those policies. Any DBA policy bound in this window names CIGNA on the federal record. In 1999, CIGNA sold the entire property and casualty book to ACE Limited, transferring both active policies and runoff liability. From that point forward, no new DBA policy was written under the CIGNA name on the property and casualty side.

From 1999 through 2015, ACE wrote and serviced this business, frequently through ACE American Insurance Company as the underwriting entity. A DBA policy bound in this window often names an ACE entity, even though the obligation traces back to the same book CIGNA originated. In January 2016, ACE acquired Chubb and rebranded the combined company as Chubb. Policies from 2016 forward carry the Chubb name from inception.

So three date bands map to three document names that all sit on one chain. Pre-1999 reads CIGNA. 1999 to 2015 often reads ACE American. 2016 forward reads Chubb. When you see any of those three names on a DBA filing, the inception date confirms where you are and what the current entity should be. This temporal logic is the same pattern that drives carrier turnover across the industry, applied here to one specific corporate chain.

How do you confirm a CIGNA-era policy is now a Chubb obligation?

The confirmation work follows a sequence. Start with the carrier name and the policy inception date from the coverage filing. The date tells you which segment of the lineage you are in. Pre-1999 and you are firmly in CIGNA legacy territory that transferred to ACE. Between 1999 and 2016 and you are likely looking at an ACE American entity. After 2016 and the Chubb branding is already in place.

Next, match the named entity against the authorized carrier list. Not every CIGNA-branded insurance subsidiary went to ACE, and not every ACE entity is a Chubb company today. The specific underwriting entity matters more than the brand name. ClaimTrove maps these entities against 2,454 SME-confirmed employer-carrier mappings so the trace lands on a verified responsible party rather than a guess.

Then cross-reference the employer. The employer on a DBA claim was covered under a specific contract with a specific carrier in a specific year. If the employer's known carrier history runs through the CIGNA ACE Chubb chain in that year, the lineage trace is corroborated by the contract side, not just the carrier side. This two-sided confirmation is what separates a defensible identification from an assumption.

This is the work ClaimTrove was built to compress. You no longer trace corporate genealogy, resolve name variants across 154,886 coverage filings, and cross-check employer history one at a time. You run one investigation. It returns the current responsible entity with its confidence level. Trace a CIGNA-era policy to its current carrier with ClaimTrove and stop calling companies that sold the book in 1999.

The CIGNA ACE Chubb DBA insurance carrier lineage history is one of several long chains that control who pays decades-old claims. The same discipline applies to the AIG family, the Zurich subsidiaries, and the mandatory government programs that picked carriers by contract. Knowing the chain exists is the first step. Tracing your specific claim to the live entity is the work that gets your client paid.