You pull a coverage record on an older overseas injury and see a carrier you do not recognize: Eagle Pacific Insurance Company. You check the current Department of Labor list of authorized DBA carriers. The name is not there. You search a modern carrier directory. Nothing. The claim is real, the injury date is real, but the carrier appears to have vanished.
This is one of the most common walls attorneys hit on legacy Defense Base Act claims. The name on the paper does not match anything in circulation today. That does not mean the coverage was fake. It usually means the record is old enough that the carrier has since merged, rebranded, exited the workers' compensation market, or wound down entirely.
Legacy carrier names are not trivia. Think of a long-tail occupational claim. Hearing loss, a repetitive-strain condition, or a disease with delayed onset. The injury date can sit years or decades before the claim is filed. The responsible carrier is the one that held the policy on the date of injury, not the carrier the employer uses now. So the old name on the record is the answer, even when it looks like a dead end.
Eagle Pacific Insurance is a useful teaching case because the name checks every box that makes legacy identification hard. It is a real workers' compensation insurer. It is easy to confuse with a near-mirror-image name. And it is no longer a name you will find writing new business. Getting from that name to a payable carrier is exactly the problem this article walks through.
Who Was Eagle Pacific Insurance Company?
Eagle Pacific Insurance Company was a Seattle-based specialty workers' compensation insurer. It wrote specialty comp coverage and, by the early 2000s, had been in the business for close to two decades. It was one of two operating companies inside a broader Eagle insurance group, paired with a similarly named sister company.
That group ownership shifted over time, which is typical for mid-size comp writers. Corporate parents change, senior management turns over, and books of business get moved. The important point for a DBA researcher is simpler. The Eagle Pacific name belongs to a specific carrier that operated in a specific window, then stopped appearing on new policies.
Eagle Pacific also surfaced in federal workers' compensation litigation. It appeared as the carrier in a published Ninth Circuit case involving the Office of Workers' Compensation Programs. That matters because it confirms the name was not purely a state comp brand. It touched the same federal claims machinery that governs Longshore and Defense Base Act cases.
Here is the honest limit. The precise corporate lineage, ownership dates, and final regulatory status of Eagle Pacific are details to confirm against primary sources before you rely on them. The general shape is clear. The exact chain deserves verification, and that verification is part of the work.
Why Do Legacy Carrier Names Like Eagle Pacific Still Matter in DBA Claims?
The Defense Base Act follows the same core rule as the Longshore Act it extends. Liability attaches to the carrier that insured the employer on the date the injury occurred. Not the date of the claim. Not today.
That single rule is why old names keep mattering. A contractor injured overseas years ago may only now be pursuing benefits for a condition that took time to develop or worsen. The policy in force back then is the policy that responds. If Eagle Pacific held that risk on that date, Eagle Pacific, or whoever now stands in its shoes, is the party in the chain.
Injury date drives the entire analysis. That is why carriers shift across a single employer's coverage timeline, and a name that was correct in one period is wrong in the next. An employer that used one insurer a decade ago may use a completely different one now. You cannot ask the employer who they use today and assume that answers a claim rooted in an older injury.
Legacy names also cluster in older filings and thin out in recent ones. Some carriers dominated a book of coverage in one era, then faded. The same pattern shows up with names like carriers that dominate old coverage filings but vanish from modern claims. Recognizing that a name belongs to a past era is half the identification.
How Do You Recognize a Legacy Carrier Name in Coverage Records?
Start with three signals. Any one of them tells you the name in front of you is probably legacy rather than current.
First, the name is absent from the current authorized carrier list. The Department of Labor maintains a list of roughly 637 carriers and self-insured employers authorized to write DBA coverage. If a name is not on it, the carrier either never wrote DBA business or no longer does. Both point you toward historical research.
Second, the name only appears attached to old policy periods. Coverage records carry dates. When a name shows up only on filings from an earlier window, and never on anything recent, you are looking at a carrier that exited or changed form.
Third, the name is easy to confuse with a look-alike. Eagle Pacific Insurance Company and its sister company sit one word-order flip apart. Records get transcribed, abbreviated, and rekeyed, and near-identical names get swapped. A clerk who reverses two words turns one insurer into another. Treat any mirror-image pair as a flag to slow down and confirm which entity actually held the policy.
Decades of DOL coverage filings make this recognition possible. Even very old DBA claims leave a traceable carrier trail in the historical filing record. The name you cannot place today was documented when the policy was active.
What Happens When a Legacy DBA Carrier Is Defunct or Insolvent?
A legacy name can be dormant for several reasons, and they are not the same. Some carriers simply stopped writing new business but continued paying old claims. Some were absorbed by an acquirer that took on the liabilities. Some were placed into liquidation because they could not meet their obligations.
The distinction changes who actually pays. If a carrier merged upward, the successor is generally on the hook. If a carrier was liquidated, a guaranty mechanism may step in, and the process becomes slower and more procedural. Either way, the underlying claim does not evaporate because the original insurer's name went dark.
Insolvency in particular reshapes an open claim. Deadlines, proof-of-claim procedures, and the identity of the paying entity all change once a carrier enters wind-down. The mechanics of what happens to open claims when a carrier exits the market are their own analysis. They hinge on which of these paths the legacy carrier took.
One caution specific to DBA. The Defense Base Act is a federal program, and the interaction between state guaranty associations and federal Longshore obligations is not automatic or uniform. Do not assume a state fund backstops a federal DBA liability the way it would a state comp claim. Confirm the actual mechanism before you tell a client who will pay.
If you are staring at a legacy name and cannot tell which path it took, that ambiguity is exactly what a structured investigation resolves. Run the employer and date of injury through ClaimTrove to see the carrier that held the risk in that period. It also traces the corporate path from a defunct name to the party responsible today.
How Do You Match an Old Employer and Injury Date to the Right Legacy Carrier?
Legacy identification is a matching problem, not a lookup. You have an employer, a location, and a date. You need the carrier that connected all three at the moment of injury.
Begin with the employer under every name it has used. Contractors operate through subsidiaries, joint ventures, and rebrands, so the entity on the DBA filing may not read like the household name. Resolving those variations is its own discipline, and it feeds directly into carrier matching.
Then anchor everything to the injury date. Pull the coverage that was active in that specific window, not the coverage that exists now. Historical filing records are the strongest evidence here. That is why coverage filing records help pin a carrier to a date instead of leaving you to guess from a current directory.
Finally, follow the corporate trail forward from the legacy name. A name like Eagle Pacific is a starting point, not a stopping point. The question is what happened to that book of business, and which entity now answers for policies written under the old name. That forward walk, from a dead name to a live obligation, is the whole game on legacy claims.
Doing this by hand across scattered records is slow and error-prone, and a single mis-keyed name can send you to the wrong carrier entirely. Search a specific employer and injury date in ClaimTrove to surface the responsible carrier, the confidence behind it, and the citations that back it up. A legacy name stops being a dead end.