Your Claimant Worked for AECOM. Which AECOM?
An electrician gets injured on a military base in Qatar. His badge says "AECOM." His W-2 says "AECOM Technical Services, Inc." The contract award in USAspending lists "AECOM International Inc." His supervisor works for something called "AC First." A colleague on the same project was hired through "GSS Ltd."
All of these names trace back to the same corporate family. But in DBA insurance terms, they are not the same entity. Each subsidiary may carry a different insurance policy. Each acquisition-era predecessor may have used a different carrier. Each joint venture partner adds another layer of confusion.
ClaimTrove data shows 19 distinct AECOM-related employer names across carrier mapping records and 37 entity name variations across federal contract awards. The company has generated over 6,600 OWCP case filings. With $2.7 billion in overseas federal contract awards in our database, AECOM is one of the largest DBA employers in the world. It is also one of the hardest to trace.
This article explains how AECOM's corporate history created this complexity, which subsidiaries generate the most DBA claims, and what you need before you can identify the right carrier.
How Did AECOM Become So Complex for DBA Purposes?
AECOM Technology Corporation was already a major engineering and construction firm when it acquired URS Corporation in 2014 for $6 billion. That single transaction doubled the complexity of every DBA investigation involving either company.
URS had its own web of subsidiaries. Federal contract records in ClaimTrove show awards under URS Group, Inc., URS Federal Services, Inc., URS Federal Services International, Inc., and URS Corporation. Each entity had its own DBA insurance arrangements. Those arrangements did not vanish when AECOM closed the acquisition. Claims arising from URS-era employment still fall under whatever carrier URS used at the time of injury.
Then came the management services spin-off. AECOM separated its management services business, which eventually became part of the Amentum portfolio. This created yet another fork in the carrier trail. Records now show hybrid names like "AC First LLC / AECOM a/k/a AMENTUM" and "AC FIRST, LLC, AECOM KNA AMETNUM" in OALJ docket filings. Those are real employer names from real DBA cases, not hypotheticals.
The timeline matters for your investigation. A worker injured under URS in 2013 has a different carrier than one injured under AECOM Technical Services in 2018, which is different again from one injured under AC First/Amentum in 2023. When defense contractor consolidation reshapes the DBA coverage landscape, the carrier history fractures along every corporate transaction boundary.
Which AECOM Subsidiaries Generate the Most DBA Claims?
Not all AECOM entities are equal in DBA terms. ClaimTrove's OWCP case data reveals where the volume concentrates.
The parent "AECOM" name dominates. In FY2024, DOL reported 495 cases under the plain "AECOM" employer name. That number alone would make AECOM one of the top five DBA employers by claims volume. But it masks the subsidiary breakdown.
Below that top-line figure, separate filings appear under "AECOM/AC First/GSS" (51 cases in FY2024), "AC First/AECOM" (40 cases), "AECOM / GSS LTD" (30 cases), and "AECOM AC First" (16 cases). Going back to FY2017, records show "AECOm" (a capitalization variant with 251 cases) and "AECOM/URs" (11 cases). Even "Aecom/URS" appears separately in FY2020 with 9 cases.
These are not duplicates that DOL cleaned up. They appear as separate employer entries in separate fiscal year reports. A paralegal searching only for "AECOM" in DOL records will miss hundreds of cases filed under AC First, GSS Ltd, or URS variants. Understanding why alias resolution matters when the same employer has 20 different names is the difference between a complete investigation and a partial one.
On the federal contract side, the fragmentation is even worse. USAspending records show 490 awards under "AECOM International Inc.," 255 under "AECOM Technical Services, Inc.," 135 under "URS Group, Inc.," and smaller counts across dozens of joint venture entities like "Baker-AECOM JV" and "RQ-AECOM JV." Each of those 37 distinct recipient names could carry a different DBA policy.
Where Does AECOM Operate Overseas, and Why Does Theater Matter?
AECOM's overseas footprint spans every major U.S. military theater command. That geographic spread directly affects DBA carrier identification because different contracts in different regions may use different insurance arrangements.
In ClaimTrove's contract award data, AECOM Technical Services holds awards for work in Iraq ($67M in a single award), Qatar ($36M), and the West Bank ($42M through USAID). URS Group shows awards for Afghanistan ($41M and $36M in separate contracts) and South Korea ($74M). URS Federal Services International holds a $312M Department of Energy award for work in Russia.
The awarding agency shapes the carrier question. That USAID contract in the West Bank falls under USAID's mandatory carrier arrangement during the performance period. The DoD contracts in Iraq and Qatar leave carrier selection to AECOM. The Department of Energy contract in Russia operates under yet another procurement framework. If you are investigating a DBA claim and you need to understand how overseas construction contracts trigger DBA insurance requirements, the awarding agency is the first variable to nail down.
Construction and engineering services also carry higher injury rates than desk-based contract work. AECOM employees build infrastructure, operate heavy equipment, and perform electrical and mechanical work in austere environments. That risk profile affects which carriers will underwrite the DBA exposure and what premiums they charge, creating carrier turnover over time.
How Many Carriers Has the AECOM Family Used?
ClaimTrove's carrier mapping data shows the AECOM corporate family connected to multiple carrier names across different subsidiaries and time periods. The carrier trail is not a straight line. It branches with every acquisition, subsidiary, and contract vehicle.
What makes this particularly challenging is the presence of third-party administrators in the records. A TPA name on a claims filing is not the carrier. TPAs handle claims processing but do not carry the insurance risk. Confusing a TPA for the actual carrier is one of the most common errors in DBA investigations. When you see a claims administrator name on AECOM-related filings, you need to trace through to the underwriting carrier behind that TPA.
The temporal dimension adds another layer. Carriers that appear in AECOM records from 2010 may not appear in records from 2020. Large construction contractors renegotiate DBA policies regularly, driven by premium costs, claims experience, and market conditions. Understanding why DBA carriers change over time helps you avoid assuming that a confirmed carrier from one period still applies to your claimant's injury date.
The URS acquisition compounds this problem. Pre-2014 URS claims involve URS-era carriers. Post-2014 claims may have migrated to AECOM's carrier, but the timing of that migration depends on when specific contracts were novated or re-awarded under the AECOM umbrella. Some URS contracts continued under URS entity names for years after the acquisition closed.
What Makes AECOM Different from Other Large DBA Employers?
Compare AECOM to a company like Fluor Corporation, another major overseas construction contractor with DBA complexity. Fluor has seven known name variations in ClaimTrove data. AECOM has 19 in carrier records alone and 37 across contract awards. Fluor's complexity comes from subsidiary proliferation. AECOM's comes from subsidiary proliferation plus a major acquisition plus a corporate spin-off, all within a single decade.
The AC First and GSS Ltd connection creates a particularly tangled thread. These entities appear both independently and in combination with AECOM across OALJ docket filings. The variations are remarkable: "AC First/AECOM/GSS Ltd./AGS," "GSS Ltd.(Subcontractor)/AC First/AECOM," "Global Sourcing Solitions (subcontractor)/AC First/AECOM" (note the misspelling of "Solutions" in the actual federal record). Each of these compound names represents a different contractual relationship in a different case filing.
AECOM National Security Programs, Inc. is another subsidiary that appears with a completely different carrier than the parent entity in ClaimTrove data. National security work operates under specialized contracts with unique insurance requirements. An attorney who finds the carrier for "AECOM" and assumes it covers the national security subsidiary will file against the wrong insurer.
The 6,600+ OWCP cases across the AECOM family also reflect the company's sheer workforce scale. AECOM employs approximately 50,000 people globally. In peak years of OCONUS operations, thousands of those employees were covered under DBA policies. FY2024 alone shows 632 combined cases across all AECOM-related entity names. That volume means your claimant's case is not unusual, but identifying the specific carrier for that specific claimant still requires pinpoint accuracy.
What Do You Need Before Investigating an AECOM DBA Claim?
Three data points will dramatically narrow your carrier search for any AECOM-related claim.
First, get the exact legal entity name from employment documents. "AECOM" is not sufficient. Check the W-2, the offer letter, and the site badge. Was it AECOM Technical Services? AECOM International? AC First? URS Federal Services? GSS Ltd? The entity name determines which branch of the corporate family you are tracing.
Second, identify the awarding agency and contract program. AECOM holds contracts with DoD, USAID, Department of Energy, and State Department. Agency-level mandatory carrier programs applied during certain periods for some of these agencies. A USAID contract has different carrier implications than a DoD contract, even when the same AECOM subsidiary performs the work.
Third, establish the fiscal year of injury. Federal fiscal years run October through September. An injury in March 2015 falls in FY2015. Carrier arrangements shift across fiscal years, and the pre- versus post-URS-acquisition timeline (2014) is a critical boundary. Pre-2014 URS employees have a fundamentally different carrier trail than post-acquisition AECOM employees.
With those three inputs, a targeted investigation replaces a blind search across two decades of records under 37 entity names.
ClaimTrove's investigation engine searches across 18 federal data sources simultaneously, resolves all 19 known AECOM alias variations automatically, and applies temporal scoring to rank carrier matches by proximity to your claimant's injury date. For a corporate family this complex, automated alias resolution and temporal scoring are not optional. They are the difference between hours of manual research and a 60-second answer.
Run an AECOM carrier investigation on ClaimTrove and get carrier identification with confidence scoring, source citations, and OALJ decision links.