A claimant walks into your office with a single fact: he was injured on a logistics base in Kandahar in 2014, and his pay stub said PAE. That should be enough to find the Defense Base Act carrier. It is not. PAE is now part of Amentum. Before that, PAE was Pacific Architects and Engineers. Before that, it passed through Lockheed Martin, then a private equity owner, then another. Each ownership change rewired the corporate structure, the contract portfolio, and the insurance relationships behind every overseas deployment.
That single pay stub points at a moving target. The entity that hired your client may not exist under that name anymore. The contract he worked on may have been a task order under a vehicle held by a subsidiary you have never heard of. And the carrier that wrote the policy in 2014 may have been replaced twice before the claim was even filed.
This is the core problem with the PAE Amentum DBA insurance carrier overseas contractor history: the company built a sprawling international footprint across two decades, then folded into a larger consolidation that scattered its records across dozens of names and contract vehicles. For attorneys, that footprint is not background trivia. It is the difference between naming the correct carrier in your LS-203 and chasing a respondent that has no obligation to your client.
This article explains why PAE's history makes carrier identification so hard, what its corporate trail actually looks like, and how the Amentum merger compounded an already tangled record. It does not hand you the carrier names for specific contracts. That answer lives in the data, and it changes with the contract and the year.
Who Is PAE and How Did It Become Part of Amentum?
PAE started as Pacific Architects and Engineers, a firm that grew into one of the largest providers of mission support, logistics, and stability operations to the US government overseas. By the height of the Iraq and Afghanistan deployments, PAE was running base operations, training programs, peacekeeping support, and aviation services across multiple continents.
The ownership history is where the trouble begins. PAE passed through Lockheed Martin ownership, then private equity hands, then a public listing through a special purpose acquisition company. In 2022, Amentum acquired PAE outright. Amentum itself was spun out of AECOM's management services business, which means the combined entity carries two separate corporate lineages, each with its own overseas contract record.
Why does this matter for a DBA claim? Because each ownership era operated under different legal entities. A contract awarded to PAE in 2013 may sit under a different corporate parent than a contract awarded in 2019, even though both say PAE on the surface. When you search federal records, you are not searching one company. You are searching a layered stack of entities that share a brand but not a balance sheet.
Amentum has since continued to grow through additional consolidation, which means the brand on your client's pay stub may already be two or three corporate steps removed from the entity that currently holds the liability. We cover the broader pattern in our analysis of how defense contractor consolidation reshapes DBA coverage, and PAE is one of the clearest examples of the phenomenon.
Why Does PAE's Overseas Footprint Complicate Carrier Identification?
Carrier identification under the DBA depends on matching three things: the correct employer entity, the correct contract, and the correct time period. PAE breaks all three at once.
Start with the employer. PAE operated through a web of subsidiaries and affiliated entities to deliver overseas work. ClaimTrove's employer alias records track multiple name variations tied to the PAE family across federal datasets. When a DBA case is filed under one of those variant names, a plain text search for "PAE" will miss it entirely. This is the same trap we describe in our breakdown of why one employer can carry twenty different names.
Now add the contracts. PAE held work across the State Department, the Department of Defense, USAID, and other agencies. Some of that work fell under mandatory carrier programs where the government dictated the insurer. Other work sat on the open market, where the prime chose its own carrier. The carrier answer for a State Department task order can differ completely from the carrier on a DoD logistics contract running in the same year.
Then add time. Carriers do not stay fixed. ClaimTrove data shows that most high-volume overseas contractors rotate carriers every three to five years, and PAE's long history means multiple rotations stacked on top of multiple ownership changes. A claim with a 2011 injury date and a 2016 filing date may involve a carrier that was already off the policy by the time the claim landed.
Layer those three variables and you get a combinatorial problem. The same employer brand, across different entities, on different contracts, in different years, points to different carriers. No single lookup answers it. That is why structured federal data, cross-referenced and time-bounded, is the only reliable path.
What Federal Data Sources Reveal About PAE Contracts?
PAE's footprint is large enough that it surfaces across nearly every federal dataset an investigator can pull. ClaimTrove holds 43,298 prime contract awards and 4,315 subcontract awards from USAspending, and PAE is one of the high-volume employers scraped with a full extraction cap rather than a sample. That depth matters because PAE's contracts are not concentrated in one agency or one country.
Prime award records show you which agency funded the work, the period of performance, and the place of performance. That last field is critical for DBA, because it ties the contract to the country where your client was injured. If you have never used these records before, our guide on how to read USAspending data for DBA investigations walks through the exact fields that carry investigative weight.
Subcontract records add another layer. PAE frequently appeared as both a prime and a teaming partner, which means the same project can show PAE in two different roles depending on the award. When your client worked for a sub under a PAE prime, the carrier obligation flows differently, a problem we unpack in our piece on why tracing subcontractor insurance is so hard.
Beyond contracts, FOIA database results confirm contractor presence in specific theaters during specific periods. For Afghanistan work, ClaimTrove cross-references 29,902 contractor records that document which companies operated where and when. Pair that with 154,886 OWCP coverage filings and 5,022 OALJ decisions, and you can triangulate a carrier picture that no single source produces alone.
How the data sources cross-check each other
The power of these datasets is not any single field. It is the way they constrain each other. A USAspending award gives you a place of performance and a period, but it does not name an insurer. An OWCP coverage filing names an insurer, but you have to confirm it ties to the same entity and period as the contract. Read alone, each source produces a plausible guess. Read together, they narrow the answer to a defensible conclusion.
PAE is a good stress test for this method precisely because it is so large. With contracts spread across agencies and theaters, a careless search returns dozens of awards that have nothing to do with your client's deployment. Filtering by injury date, country, and resolved entity name strips that noise down to the handful of contracts that actually could have employed your client, which is the only set worth tracing a carrier through. For the underlying pattern of why the carrier on a contract shifts over time, see our explainer on temporal shifts in DBA coverage.
None of these sources, on its own, tells you the carrier. The carrier emerges only when you overlay them: the entity from alias resolution, the contract from USAspending, the theater from FOIA records, and the coverage signal from OWCP and OALJ data. That overlay is the engine ClaimTrove runs.
How Did the Amentum Merger Scatter PAE's DBA Records?
The 2022 Amentum acquisition did not consolidate PAE's records into a clean single file. It did the opposite. The merger created a new layer of corporate naming on top of an already fragmented history, and DBA records do not retroactively update when a company is acquired.
Consider what a claims examiner sees. A 2015 injury was insured under a policy tied to a PAE entity that existed at that time. The case may have been filed in 2017, litigated through 2019, and reopened in 2023, well after Amentum took control. The carrier on the original policy did not change because the parent company changed. But anyone searching under "Amentum" today will find nothing tied to that 2015 work, and anyone searching under "PAE" may find only part of it.
This is the same structural problem we documented in DynCorp's DBA coverage history, because DynCorp also flowed into the Amentum family through a separate path. Two large overseas contractors with independent carrier histories now sit under one brand, yet their underlying DBA liabilities remain separate, time-bound, and tied to the entities that existed when the work was performed.
The practical consequence is that a name-based search fails in both directions. Search the old name and you miss work reorganized under the new parent. Search the new name and you miss the historical liabilities that predate it. Only an investigation that resolves the entity to its correct era, then ties that era to the right contract and carrier, survives this kind of consolidation.
For attorneys, the lesson is blunt. The merger headline tells you nothing about who pays your client. Amentum owning PAE today does not mean Amentum's current carrier covers a 2014 Kandahar injury. The coverage question is always anchored to the policy in force on the date of injury, under the entity that held the contract then.
What Should Attorneys Do When a Client Worked for PAE?
Treat the PAE name as a starting clue, not an answer. The goal is to resolve four things in order: the exact entity, the exact contract, the place and date of performance, and the carrier in force at that time.
First, resolve the entity. Run the employer name through alias resolution before you do anything else, because the DBA case may be filed under a subsidiary or a legacy name that does not say PAE. Second, anchor the date. The carrier on a 2012 contract is rarely the carrier on a 2019 contract, so the injury date drives the entire search.
Third, identify the contract and agency. A State Department contract and a DoD logistics contract can carry different carriers in the same year, and mandatory agency programs can override the prime's choice entirely. Our overview of when the government picks your carrier explains where those programs apply. Fourth, verify against coverage and decision records rather than assuming the most common carrier applies.
Doing this by hand across PAE's footprint is punishing. You are searching multiple datasets, reconciling name variants, and time-bounding every result. ClaimTrove automates the overlay. Run a PAE investigation and the engine resolves the entity across its alias set, pulls the matching prime and subcontract awards, cross-references theater presence, and surfaces the carrier signals tied to the period you care about, complete with source citations you can verify against primary records.
One more caution specific to PAE. Because the company carried work under both mandatory and open-market arrangements, do not assume that finding one carrier on one PAE contract tells you the carrier on a different contract. A protective services task order and a base operations contract running in the same fiscal year can sit under entirely different policies. Each contract your client touched must be traced on its own terms, and a worker who moved between PAE projects may have been covered by more than one carrier across a single deployment.
Stop guessing which carrier covered your client's PAE deployment. Run a PAE investigation in ClaimTrove and trace carrier coverage across the Amentum merger, the ownership changes, and the contract record, all in one search. Start your investigation today.