A paralegal pulls a DBA file for a contractor injured supporting an Army intelligence mission in Afghanistan in 2017. The injured worker's pay stub says "Engility." The claim was never adjudicated, so there is no Office of Administrative Law Judges decision naming the carrier. The paralegal searches the Department of Labor coverage records for "Engility" and finds a handful of filings. Then she searches the same period under "TASC," and "L-3 Services," and "International Resources Group," and the results change again. Same contractor. Same overseas work. Four different legal names, and the insurance carrier on file is not the same across all of them.
This is the Engility problem. Between 2012 and 2019, Engility was spun out of L-3 Communications, rolled up at least four federal-services firms, and then disappeared entirely into Science Applications International Corporation (SAIC). Each of those events touched the corporate structure that determines who actually wrote the Defense Base Act policy. When you research Engility DBA insurance carrier history SAIC connections, you are not tracing one company. You are tracing a corporate family tree where the branches keep getting grafted onto new trunks.
The carrier on a DBA claim follows the legal entity that held the contract, not the brand on the badge. When the legal entity changes through a spin-off, acquisition, or subsidiary reorganization, the carrier record can change with it, or it can stay frozen under a name nobody uses anymore. This article walks through Engility's corporate path, explains why each transition fractures the carrier trail, and shows you the search surface you have to cover before you can answer one question: who insured this worker on the date of injury?
Where Did Engility Come From, and Why Does Its Origin Complicate Carrier Identification?
Engility did not start as a standalone company. It was spun off from L-3 Communications in July 2012 as a separate, publicly traded government-services contractor. The spin-off carried with it pieces of L-3's services business, which themselves traced back to earlier acquisitions including Titan Corporation and MPRI. So the very first day Engility existed as its own company, its operating history already ran backward through at least two other corporate names.
That origin matters for DBA work because overseas contracts and the injuries under them often predate the spin-off. A worker injured in 2011 was employed by an L-3 entity. The same program, the same base, the same supervisor, but the claim sits under "L-3 Services" or "L-3 Communications" in the records, not "Engility." A 2013 injury on the continued program might sit under "Engility." The carrier serving that program may or may not have changed when the contract novated to the new entity.
Spin-offs create a specific trap. The new company inherits ongoing contracts through novation agreements, but it negotiates its own insurance program. There is no rule that says the spun-off entity keeps the parent's DBA carrier. Sometimes coverage carries over for continuity. Sometimes the new company's broker places it elsewhere on renewal. You cannot assume either way, which is exactly why this resembles the multi-name carrier trail created by Blackwater's evolution into Academi and Constellis, where each corporate rename sat on top of a different insurance arrangement.
The practical consequence: an Engility-origin claim from 2011 to 2013 requires you to search the L-3 family, the Engility name, and the specific subsidiary that held the relevant contract. Searching one name returns a fraction of the picture.
What Companies Did Engility Absorb Before SAIC Bought It?
Engility grew by acquisition, and every acquisition imported another company's contract base, another set of legal entities, and another DBA insurance history. The two largest were TASC, Inc., a systems-engineering firm Engility merged with in 2015, and the broader rollup of federal-services businesses that followed. Smaller acquisitions added more overseas-capable units, including firms with USAID and State Department reconstruction work.
Each absorbed company had its own carrier relationships at the time of acquisition. When Engility bought them, the contracts continued, but the insurance did not automatically consolidate onto a single Engility-wide DBA policy on day one. Insurance programs renew on their own cycles. A TASC overseas contract might have run on TASC's existing carrier for a full policy year after the merger before any consolidation happened.
For an attorney, this means the relevant legal name on a claim depends on three things at once: which underlying company originally held the contract, what date the injury occurred, and whether the insurance had been consolidated yet by that date. A 2015 injury on a former-TASC program is a different carrier-research problem than a 2017 injury on the same program after integration.
This temporal layering is the core reason acquisition-heavy contractors defeat simple lookups. The carrier is not a property of the company. It is a property of the company-on-a-specific-date. Our investigation engine handles this by weighting every carrier signal by its distance from the injury date, because a coverage record from the wrong policy period is worse than no record at all. Understanding how DBA carriers map across Afghanistan contractors shows why date-scoped evidence beats name-matching every time.
How Does the SAIC Acquisition Change the Carrier Picture?
In January 2019, SAIC completed its acquisition of Engility in an all-stock deal. Engility ceased to exist as an independent company. Its contracts, its people, and its overseas obligations moved under the SAIC corporate umbrella. From that point forward, work that would once have been billed and insured under Engility runs under SAIC.
This is where the research gets genuinely difficult, because SAIC has its own complicated identity. The SAIC that bought Engility is not the original SAIC. In 2013, the legacy Science Applications International Corporation split into two public companies: a new, smaller SAIC focused on government services, and Leidos, which took the larger science and technology business. So the company that absorbed Engility in 2019 is itself a 2013-vintage entity carved out of a much older firm.
Stack those events and a single overseas worker's coverage history can run through Engility, then SAIC, while the "SAIC" brand points back through a 2013 corporate split. This is the same structural problem we describe in why the SAIC and Leidos split makes carrier identification so difficult, except Engility adds an additional layer on the SAIC side.
The acquisition date is the hinge. An injury before January 2019 belongs to the Engility-era insurance program. An injury after belongs to SAIC's program. Those are different policies, potentially different carriers, and almost certainly different policy numbers. The brand on the worker's old paystub tells you nothing about which side of the hinge the claim falls on until you fix the date.
Why Do Acquisitions Fracture the DBA Carrier Trail So Badly?
Three mechanics make corporate-history contractors like Engility so hard to resolve. Understanding them tells you where to look and why a single search fails.
First, legal-entity drift. DBA policies name a specific insured legal entity, often a subsidiary, not the parent brand. Engility-era overseas work might have been written under a services subsidiary whose name shares nothing obvious with "Engility." After the SAIC deal, the insured entity name changes again. The policy follows the entity, and the entity name is not the brand.
Second, FEIN and registration scatter. Each corporate entity carries its own Federal Employer Identification Number and its own federal contractor registration. When entities merge or get absorbed, registrations expire, get superseded, or get re-issued under the acquiring company. A search keyed to one identifier misses the others. This is why working from the carrier's NAIC number rather than its name matters once you have a candidate carrier: the identifier is stable even when the corporate names around it are not.
Third, contract-vehicle continuity. Most Engility overseas work ran under large indefinite-delivery vehicles and task orders. The vehicle can survive the acquisition while the carrier on individual task orders shifts. Knowing the company is not enough; you have to know which task order controlled the work, because on an IDIQ contract the specific task order can determine the carrier. A program that novated from Engility to SAIC may keep the same vehicle number while the insurance underneath it turns over.
Put together, these three mechanics mean the answer to "who covered Engility" is never a single carrier name. It is a carrier-by-period table, indexed to legal entity, FEIN, contract vehicle, and date. Building that table from scattered public records by hand is the work ClaimTrove automates.
What Search Surface Do You Have to Cover for an Engility Claim?
To resolve an Engility-era DBA claim correctly, you cannot search one name in one database. You have to cover an entire surface of names across multiple record types, then reconcile them by date.
The name set alone includes the Engility brand, the L-3 predecessor entities it spun out of, the acquired companies it absorbed such as TASC, the SAIC entity that took over in 2019, and any overseas services subsidiaries that actually appeared as the insured on the policy. Miss one and you miss the filings tied to it.
Then the record types. Coverage filing records from DOL FOIA releases give the most direct evidence: an actual insurance filing tying an employer name to a carrier at a specific date. Adjudicated decisions name carriers in their party headers when a claim was litigated. Federal contract award data ties the entity to specific overseas task orders and agencies, which matters when an awarding agency carried a mandatory carrier program. Federal entity registrations link the brand to its FEIN and UEI so you can confirm you are searching the right legal entity. Each source covers a different slice; no single one covers an acquisition-fractured contractor completely.
The reconciliation step is where attorneys lose the most time. Once you have hits across five name variations and four record types, you still have to align them to the injury date and discard the ones from the wrong policy period. A coverage filing under a TASC entity in 2014 is irrelevant to a 2018 injury on a consolidated SAIC-era program, even though both legitimately involve "Engility." This is the same agency-mandate sensitivity that makes State Department contract carrier tracing so date-dependent, where the mandated carrier changed across distinct contract periods.
ClaimTrove runs that entire surface at once. It resolves Engility's aliases and subsidiaries to a single canonical entity, searches every record type in parallel, and ranks the carrier candidates by how close each piece of evidence sits to your injury date. Instead of five manual searches and a spreadsheet, you get a carrier-by-period answer with the source documents attached. Run the Engility name through ClaimTrove and let it resolve the aliases, subsidiaries, and carrier-by-period that the SAIC acquisition buried.
How Should You Verify an Engility-Era Carrier Once You Have a Candidate?
Even after a tool surfaces a likely carrier, verification is non-negotiable, because acquisition-era records are exactly where errors hide. Start by confirming the injury date sits inside the policy period of the candidate carrier, not just somewhere in the company's history. A carrier that covered an Engility subsidiary in 2014 is not your answer for a 2018 loss unless the coverage genuinely continued.
Next, confirm the legal entity. The carrier wrote a policy for a named insured. Match that named insured to the entity that actually held the contract the worker was performing, using the FEIN and the contract vehicle, not the brand. If the named insured is a subsidiary you have never heard of, that is normal for this contractor, not a red flag.
Finally, check whether the awarding agency ran a mandatory DBA program during the contract period. Some federal agencies required all their overseas contractors to use a single designated carrier for defined windows. If Engility's work fell under such a program on the injury date, the mandated carrier overrides whatever the company's commercial program would otherwise suggest. That single check can resolve an otherwise ambiguous file in one step.
The discipline is the same one good DBA investigators apply everywhere: never trust a carrier name without a date, an entity, and a source document behind it. For a contractor like Engility, where the corporate history did most of the obscuring, that discipline is the difference between filing against the right policy and chasing a carrier that stopped covering the work years before the injury.