Amentum Standalone Spinoff and Base-Operations Prime DBA Profile: Why the Name on the Retainer Is Not the Entity That Owns the Claim

Why does naming Amentum as the employer not tell you who owns the DBA claim?

A new retainer crosses your desk. The injured worker names Amentum as his employer. The accident happened at an overseas base-operations site in 2016, on a logistics-support contract. You open a claim under 42 U.S.C. 1651 and start hunting for the carrier.

There is one problem. In 2016, Amentum did not exist as a standalone company. The name on your client's paperwork was created years after his injury. The entity that owed him Defense Base Act benefits on the day he was hurt may be a different corporation entirely.

This is the trap that base-operations primes set for DBA attorneys. Amentum is one of the largest players in overseas base support, life support, and logistics. Much of that work was once performed under other corporate names. A contractor may honestly believe he worked for Amentum, because that is the name on his badge today.

Getting the responsible entity right is not academic. It decides which policy answers, which carrier you serve, and whether your Section 33(g) consent request reaches the correct party. Name the wrong entity and you can blow a filing deadline, serve a defunct policy, or chase a carrier that never wrote the risk. That gap is the heart of the Amentum standalone spinoff base operations prime DBA profile.

The DBA incorporates the Longshore Act, so the claim attaches to the insurance in force for the employing entity on the date of injury. The DBA sits at 42 U.S.C. 1651 through 1654 and pulls in the Longshore Act at 33 U.S.C. 901 through 950. The employer of record is the legal entity that employed the worker under the contract at that time.

A memory, a badge, or a current corporate logo is not proof of that entity. Learning how to trace an employer's corporate history is the first defense against naming the wrong party. The current brand is the answer to a different question than the one your claim asks.

How did Amentum's spinoff from AECOM reshuffle DBA liability?

Amentum did not grow from a startup. It began as AECOM's government Management Services business. In early 2020, AECOM divested that unit to private-equity ownership, and it launched as a standalone company under the Amentum name.

That single event splits the timeline for coverage purposes. Work performed before the 2020 divestiture ran under AECOM legal entities and AECOM-era insurance. Work performed after the spinoff runs under Amentum entities and their policies. The corporate boundary in 2020 is a boundary in the coverage record too.

A successor company can assume a predecessor's liabilities by contract. Whether it did, and to what extent, is a factual and contractual question, not a default. Even where liabilities transfer, the DBA claim still looks to the insurance policy that was in force for the employing entity on the date of injury. Successor branding does not rewrite which carrier was on the risk that day.

So a worker hurt in 2018 on AECOM-era base-operations work presents a different coverage question than a worker hurt in 2022 under Amentum. Same job site, same type of contract, potentially two different carriers and two different corporate defendants. The name on the retainer flattens that distinction and hides it.

The spinoff also matters for how you read older records. A coverage filing or a decision from 2017 will name an AECOM-era entity, not Amentum, even though the work later moved under the new brand. If you dismiss those records because they do not say Amentum, you throw away the exact evidence you need. Read the pre-2020 records as the predecessor's story, because that is what they are.

The insurance obligation is written into the contract itself. FAR 52.228-3 requires the DBA workers' compensation clause on covered overseas contracts, and it is the paper trail that ties a contract to a carrier for a period. When the corporate owner changes, the contract and its insurance clause do not automatically follow into the new parent's master policy. Each vehicle carries its own coverage story.

This is not unique to one company. It is the recurring pattern in this corner of federal contracting, and it is worth understanding how defense-contractor consolidation reshuffles DBA coverage across the whole market. Spinoffs, carve-outs, and private-equity deals each create a new seam where the responsible entity and the responsible carrier can change without the worker ever noticing.

What happens to a DBA claim when Amentum absorbs PAE, DynCorp, and Jacobs' business?

The spinoff was only the beginning. After it became standalone, Amentum grew by absorbing other overseas contractors. It acquired DynCorp International in 2020. It acquired PAE in 2022. In 2024, it combined with Jacobs' Critical Mission Solutions and Cyber and Intelligence business and became the publicly traded Amentum Holdings.

Each of those predecessors carried its own long DBA history. Each had its own carriers, its own alias variations, and its own claims footprint across Iraq, Afghanistan, Kuwait, and dozens of base-support locations. When Amentum absorbed them, those histories did not merge into one clean carrier answer. They stacked underneath a single brand.

Consider a worker hurt on a DynCorp base-operations task order in 2015. The current corporate name is Amentum, but the coverage question runs against DynCorp's entity and DynCorp's policy for that period. The same logic applies to a PAE injury before the 2022 acquisition. The predecessor owns the claim.

DynCorp alone illustrates the depth of the problem, and DynCorp's DBA coverage history shows how many carrier shifts sit beneath one now-absorbed name. A single legacy prime can hold a decade of rotating carriers before the acquisition ever happened.

PAE compounds it further, because PAE itself was assembled from earlier acquisitions before Amentum bought it. Following the PAE-to-Amentum carrier trail means peeling back two layers of consolidation, not one. You are tracing a predecessor of a predecessor, each with its own policies in force at different dates.

The Jacobs combination adds yet another layer. Amentum absorbed a slice of Jacobs, not the whole company, so only certain Jacobs government programs came across. A claim tied to a program that moved into Amentum reads differently than one tied to work Jacobs kept. Sorting which programs migrated is its own factual question in the file.

If your client's injury predates any of these deals, do not investigate Amentum. Investigate the entity that employed the worker on the contract at the time, and find that entity's carrier for that period. Running the current parent name through any database returns the wrong footprint. ClaimTrove resolves the aliases and predecessor names first, then maps the carrier by period, so you start from the right entity instead of the brand on today's letterhead.

Why does the injury date, not the current corporate name, decide which carrier pays?

The Amentum standalone spinoff base operations prime DBA profile turns on one date: the day your client was hurt. The DBA follows Longshore Act principles, and coverage is tested at the time of injury. Whatever the employer is called now, the carrier that answers is the one that insured the employing entity then.

Base-operations contracts make this harder than a single-carrier employer would. These are long-running support contracts that get re-competed, renewed, and re-priced. Carriers rotate at those inflection points. A prime can sit with one underwriter for a few years, then move to another when the contract is rebid or the policy renews.

That is why two injuries at the same base, two years apart, can point to two different carriers for the same employer. The contract vehicle changed, or the policy year turned, or the corporate entity shifted. Understanding why the carrier on a base-operations contract changes over time keeps you from assuming last year's carrier is this year's carrier.

Federal records make the injury date usable. ClaimTrove holds 43,298 prime contract award records and 637 authorized DBA carriers, so contract awards can show which vehicle was active in a given period. FOIA coverage filings, spanning back decades to the 1940s, tie an employer to a carrier at a specific date. Legal decisions from the more than 5,000 adjudicated records name the carrier that actually litigated a claim from that era.

None of that helps if you search the current brand instead of the entity that held the risk. The date also matters for deadlines. The DBA statute of limitations under Section 913 runs from the injury or from awareness of the work connection. Naming the wrong entity early can burn months you cannot get back. Fixing the date first protects both the carrier answer and the clock.

Temporal proximity also drives which carrier record is the best match. Litigated DBA claims are often filed around three years after the injury, so a decision docketed in one year usually reflects an injury a few years earlier. A carrier record from the wrong window may belong to a different policy period entirely. Weighting records by their distance from the injury date separates the live answer from stale noise.

The practical rule is simple. Fix the injury date first. Then identify the employing entity and any predecessor as of that date. Only then ask which carrier was on the risk. Skip those steps and the current corporate name will quietly point you at the wrong policy.

What corporate-history evidence proves the responsible entity in an Amentum claim?

You cannot argue the responsible entity from a badge photo. You prove it with federal records that tie a legal name to a contract, a location, and a date. That evidence trail is what survives a carrier's challenge to the named party.

Start with entity registration data. Federal registries hold legal business names, DBA names, and unique identifiers like the CAGE code and UEI for hundreds of thousands of contractors. These identifiers cut through name confusion, because a legal entity keeps its identifier even when the marketing name changes above it.

Alias evidence comes next. Amentum and its predecessors appear under many surface names, subsidiaries, and misspellings across records. ClaimTrove maintains 214 curated employer alias mappings and more than 2,400 employer-to-carrier mappings, so the search runs on every name the entity used, not just the parent. One surface name almost never tells the whole story for a company assembled from this many acquisitions.

Contract records anchor the entity to the work. An award or task order names the awarding agency, the place of performance, and the period. Together those place a specific legal entity on a specific base at a specific time. That is the backbone of a defensible responsible-entity argument, and it doubles as proof the DBA applied at all.

Adjudicated decisions close the loop. When a predecessor litigated a DBA claim from the relevant period, the decision names the employer entity and the carrier that appeared. That is the strongest single record you can put in front of an ALJ to fix both the party and the policy. Assemble those four record types and the responsible entity stops being a guess.

How do you run an Amentum base-operations DBA investigation the right way?

Building the Amentum standalone spinoff base operations prime DBA profile for your specific claim takes four steps, in order. Rush them and you inherit the same wrong-entity error the retainer already contains.

Step one is entity and alias resolution. Amentum, its predecessors, and their subsidiaries appear under many names across federal records. You need every legal name and DBA variation the employing entity used during the relevant period, not just the parent brand.

Step two is fixing the employing entity to the injury date. If the injury predates the 2020 spinoff or a later acquisition, the predecessor is your target, not Amentum. This is where the spinoff and merger timeline does real work in the file.

Step three is the contract vehicle and awarding agency. Base-operations work runs on identifiable contracts, and some awarding agencies have carried mandatory-carrier arrangements during defined windows. The vehicle and the agency both narrow the carrier field before you ever look at a policy.

Step four is carrier by period. With the right entity, the right date, and the right contract, you match the carrier that was actually on the risk. That answer decides your Section 33(g) letter, your notice to the carrier, and your posture at the informal conference. It is also the step this article deliberately does not shortcut for you, because it depends on facts unique to your claim.

The cost of skipping this order is concrete. A misnamed party can force an amended claim, hand the carrier a defense on the pleadings, and delay the first compensation payment your client needs. On a base-operations prime with this much corporate history, the wrong-entity error is the default outcome, not the rare one. The four-step sequence exists to keep you out of it.

This is exactly the work ClaimTrove is built to do. Run your employer, injury date, and location through a ClaimTrove investigation. The engine resolves the aliases and predecessors, ties the contract vehicle to the period, and surfaces carrier records by date. You start with the entity that owed the benefits, not the name on the badge, and the rest of the file falls into place.