Was ANHAM FCZO a LOGCAP contractor?

No. ANHAM's Iraq contracts were primarily awarded through the Defense Logistics Agency Troop Support Subsistence Prime Vendor program and separate task orders, not LOGCAP. This means ANHAM's DBA carrier history does not align to LOGCAP III or LOGCAP IV carrier transitions, and investigators should not assume the LOGCAP prime's carrier applies to ANHAM employees.

Why is ANHAM sometimes not listed in SAM.gov for the relevant period?

ANHAM was registered in the UAE as a Free Zone Company (FZCO), and its SAM.gov registration status varied across contract periods. Some U.S.-registered affiliates carried their own CAGE codes, while the Emirati parent was tracked separately. Searching only the current ANHAM FCZO spelling in SAM.gov will miss historical filings under Anham FZCO or affiliate entities.

If my client worked at an ANHAM dining facility, does that mean ANHAM's carrier covers the claim?

Not necessarily. ANHAM operated with a large subcontractor workforce, including Third Country National labor brokers and local Iraqi firms. If the claimant was on a subcontractor payroll, the carrier is the subcontractor's DBA insurer, not ANHAM's. Prime-level liability may still attach on a secondary theory if the subcontractor was uninsured, but the primary carrier analysis starts with the actual employer of record.

How do I figure out if my client worked directly for ANHAM or for a subcontractor?

Ask five questions during intake: what the uniform or badge said, which base and deployment window, who issued the paycheck, what currency and country appeared on the check, and whose logo appeared in safety briefings. These data points almost always identify direct-versus-subcontractor status before you touch any public records.

What records should I pull first for an ANHAM DBA claim?

Start with USAspending prime award records filtered by all ANHAM name variants, then cross-reference FOIA-derived coverage card data by employer name, then check OALJ decisions for any prior ANHAM claims that named the carrier. If the claim involves a subcontractor, you will also need subaward reporting, which is less complete.

Did ANHAM's carrier change over time?

For open-market Iraq primes that operated outside mandatory agency carrier contracts, carriers typically shift every three to five years due to contract recompetitions, insurer repricing of theater risk, and broker changes. ANHAM's long contracting run in Iraq spans multiple such windows, so the carrier for a 2009 injury is unlikely to be the same as the carrier for a 2015 injury even for the same employer.

Is ANHAM's DBA coverage different for TCN employees versus U.S. citizens?

DBA applies regardless of employee nationality for work performed overseas under a covered U.S. government contract. However, TCN employees were frequently hired through foreign labor brokers rather than directly by ANHAM, which means their employer of record, and therefore their DBA carrier, may be a non-U.S. staffing company that never appeared in SAM.gov or USAspending at all.

What happens if I cannot find ANHAM's carrier in any public record?

Coverage card FOIA results often surface carrier attachments that never appeared in contract filings. If those also come back empty, the next steps are targeted FOIA requests to the contracting agency, outreach to known ANHAM brokers, and review of any OALJ decisions where ANHAM appears as a named party. ClaimTrove's carrier scoring engine combines these sources and returns ranked candidates even when no single record gives a definitive answer.

Does the base of assignment really change the carrier analysis?

Yes. ANHAM operated under multiple task orders covering different theater zones and base clusters. Different task orders can have different insurance arrangements, so narrowing the claim to a specific base combined with the injury date often isolates the relevant task order and, by extension, the likely carrier.

ANHAM FCZO DBA Insurance: Tracing Iraq's Largest Food Service Prime Across Contract Periods

A paralegal opens a file with an injury date of August 2014, a claimant who worked as a cook at Joint Base Balad, and an employer listed as "ANHAM." No carrier is named. No LS-201 is in the file. The claimant cannot remember which ANHAM entity hired him, whether he worked for the prime or a sub, or what the patch on his uniform said. The paralegal pulls up SAM.gov and finds nothing current. She pulls USAspending and finds dozens of task orders across multiple contract vehicles, with ANHAM listed under at least three name variants.

This is the ANHAM investigation problem. The company fed tens of thousands of U.S. personnel across Iraq under contracts worth billions, yet its DBA carrier history is scattered across foreign corporate registrations, multi-year subsistence prime contracts, and a layered subcontractor chain. The direct employees on the ANHAM payroll were a fraction of the people working under its dining facility operations. Each contract period potentially carried a different insurance arrangement. Each subcontractor potentially carried its own.

This article walks through why ANHAM FCZO (originally registered as Anham FZCO in the United Arab Emirates) creates an identification challenge unlike domestic primes, what public records exist for tracing coverage, and how the subcontractor workforce complicates the liability analysis. If you are handling an ANHAM-related DBA claim, the goal here is to map the investigative terrain before you burn billable hours on dead ends.

Who is ANHAM FCZO and why does the name keep shifting?

ANHAM is an Emirati-registered logistics and food service contractor that became one of the largest subsistence primes in Iraq during the occupation and drawdown periods. The company operated under the Subsistence Prime Vendor (SPV) program administered through the Defense Logistics Agency, delivering food to U.S. forces across forward operating bases. At its peak ANHAM managed a supply chain running from Jordan, Turkey, and Kuwait into hundreds of dining facilities across Iraq.

The company appears in federal records under several variants: Anham FZCO, ANHAM FCZO, ANHAM LLC, Anham USA, and related affiliates. The FZCO suffix refers to a Free Zone Company designation under UAE corporate law. The entity was not always registered in SAM.gov during its active contracting years, and where it was registered, CAGE codes and DUNS numbers did not always cross-reference cleanly to the Emirati parent. This is the first trap. If you search only for "ANHAM FCZO" in SAM.gov you will miss contract records filed under the older Anham FZCO spelling or under U.S.-registered affiliates.

Our alias resolution database includes 214 employer alias mappings for exactly this type of scenario, and ANHAM is a textbook case of why federal contract data reveals DBA carrier information only when you can tie all the name variants back to a single operating entity. Search one spelling and you get a partial picture. Search all of them together and the contract history finally lines up.

What contracts did ANHAM hold and why does the vehicle matter?

ANHAM was not a LOGCAP contractor. This is important because DBA investigators often assume that any large logistics prime in Iraq fell under LOGCAP, inherited the LOGCAP insurance structure, and therefore defaulted to whichever carrier was attached to the prime for that task order period. That shortcut does not work for ANHAM.

ANHAM held contracts primarily through the Defense Logistics Agency Troop Support (DLA) and, separately, through task orders issued by various command elements for base support services. The DLA subsistence contracts were structured as indefinite-delivery, indefinite-quantity vehicles with separate task orders for different theater zones. Each contract and task order potentially had its own DBA insurance arrangement because DBA coverage attaches to the employer, not to a blanket mandatory contract like the State Department or USAID programs.

Because ANHAM operated outside the mandatory carrier structures that govern some agencies, its carrier was selected on the open market for each contract period. That means the carrier could change when contracts recompeted, when insurers repriced Iraq risk, or when ANHAM switched brokers. Our data shows that for open-market Iraq primes the carrier typically shifts every three to five years, and ANHAM's long run of active contracting spans multiple such windows. If you are learning how to read USAspending data for DBA investigations, the key insight for ANHAM is that you must align the injury date to the specific task order active on that date, not to a single master contract.

Why does the subcontractor workforce create the biggest problem?

ANHAM's direct employees were the tip of a much larger workforce. Dining facility operations, base support services, and in-theater logistics under ANHAM prime contracts were executed largely through a chain of subcontractors, including Third Country National (TCN) labor brokers based in the Middle East and South Asia, local Iraqi firms, and specialty service subs for things like ice production, laundry, and transportation.

For DBA purposes, this creates two parallel tracks. If the claimant was a direct ANHAM hire, the carrier is the one ANHAM itself maintained for that contract period. If the claimant worked for a subcontractor performing work under the ANHAM prime, the carrier is the subcontractor's own DBA policy, which may or may not exist, may or may not have been active on the injury date, and may or may not be traceable through public records. ANHAM's prime status does not automatically make ANHAM's carrier liable for the sub's employees, although the prime can be pulled in on a secondary liability theory if the sub is uninsured.

This is the exact scenario covered in our breakdown of why tracing subcontractor DBA insurance is so hard. For ANHAM specifically, the problem is magnified because subcontract awards were often executed through Middle East-based labor brokers who never appeared in U.S. federal registration systems at all. A claimant who says "I worked for ANHAM" may actually have been on the payroll of a Jordanian or Emirati staffing company invisible to SAM.gov, USAspending, and FPDS.

What public records actually exist for ANHAM claims?

Even with the complications above, a meaningful amount of public data does exist. Our investigation engine pulls from 43,298 prime contract awards and 4,315 subcontract awards in USAspending, and ANHAM appears as a named prime in a substantial slice of Iraq-era awards. Subcontract visibility is weaker, as is typical across USAspending, because prime reporting of subawards has historically been incomplete.

FOIA-derived coverage records are another major source. Our FOIA database results often fill the gap where contract records are silent about insurance. For Iraq-era claims in particular, these FOIA database results often fill the gap where contract records are silent about insurance. The 5,022 OALJ decisions in our case law database also occasionally name ANHAM directly, either as employer in a claim or as a reference in a subcontractor dispute.

The harder sources are corporate registrations outside the U.S. and internal broker records. ANHAM's Emirati registration means that some of its operational history lives in UAE free zone records rather than in U.S. systems. Broker-held policy data is almost never public. This is where the tracing gets expensive and where an investigator has to decide whether the cost of primary source pursuit justifies the claim value.

How does the Iraq timeline change the analysis?

ANHAM's active Iraq contracting does not map cleanly onto a single era. It spans the surge, the drawdown to 2011, the advisory period, and the ISIS-era re-engagement. Each of these had different troop footprints, different base configurations, and different carrier market conditions. An injury at Al Asad in 2009 is not the same investigation as an injury at Baghdad Diplomatic Support Center in 2015, even if the employer field reads the same in both case files.

The broader pattern of Iraq DBA claims carrier identification across these three distinct eras applies to ANHAM with particular force. Contract vehicles changed, base lists changed, and subcontractor rosters churned. Our data indicates that for a multi-era prime like ANHAM, the single most important investigative data point after employer name and injury date is the specific base of assignment. That combination narrows the task order and, with it, the likely carrier.

Separately, investigators should not assume ANHAM's coverage followed any LOGCAP pattern. The LOGCAP carrier transition history is a useful reference for understanding how Iraq-era logistics coverage shifts work in general, but ANHAM was on a separate track and its carrier transitions do not align to LOGCAP III to IV boundaries.

What should your intake look like for an ANHAM claim?

Before you burn hours on public records, get the claimant to answer five questions. What exactly did the uniform patch or ID badge say? Which base, and during which deployment window? Was the paycheck issued by ANHAM directly or by a staffing company? Which currency and country was on the check or deposit? Was there a safety briefing, and if so, whose logo was on the slides?

These answers tell you whether you are looking at a direct ANHAM claim, a subcontractor claim, or a TCN labor broker claim. Each path has different carrier identification strategies and different odds of success. For the broader intake structure, the DBA claims process step-by-step guide for attorneys covers how to sequence carrier identification with filing deadlines so that the identification work does not push you past the one-year statute.

Once you have the base, date, and direct-versus-sub classification, you have the three inputs needed to run a targeted carrier investigation rather than a shotgun search.

Run an ANHAM investigation on ClaimTrove

ClaimTrove's employer-carrier mapping engine cross-references 2,468 SME-confirmed carrier attachments, 214 employer alias variants, and FOIA-sourced coverage records to identify the likely carrier for ANHAM employees by contract period and base. For an ANHAM claim, enter the employer name, the injury date, and the base of assignment. The engine returns ranked carrier candidates with confidence scoring, flags whether the claim is more likely a prime or subcontractor matter, and surfaces related OALJ decisions where ANHAM or its carriers appear.

Start an ANHAM investigation, identify the carrier for the specific year and base, and move the file toward filing.