A paralegal opens a new file. The client spent 2008 running a fuel yard at Joint Base Balad, north of Baghdad. He now has a chronic respiratory condition and a stack of medical records. The employer name on his old badge means nothing to the current corporate directory. The question on the desk is simple to ask and hard to answer. Who was the DBA insurance carrier, and which prime did his company work under?
Balad Air Base sits at the center of this problem. It was one of the largest American installations in Iraq. Also known as Logistics Support Area Anaconda, it functioned as a sprawling logistics, aviation, and medical hub roughly 40 miles north of Baghdad. Thousands of contractors passed through it across the war. Very few of them can name their insurance carrier a decade later.
Public records exist, but they are scattered across contract databases, legal decisions, and claim statistics that do not talk to each other. A contract award tells you a prime was there. A claim summary tells you injuries happened in-country. Neither one hands you the carrier. This article walks through what the Balad contractor footprint looks like in hard numbers, using live ClaimTrove data, and where the gaps sit. Every figure below comes from a query you could run yourself.
What made Joint Base Balad a contractor hub?
Balad was built for scale. At its peak it ran one of the busiest airfields in the world by traffic volume. It housed the Air Force Theater Hospital, the primary trauma center for wounded service members and contractors across Iraq. It staged troops, aircraft, fuel, food, and equipment for operations across the country.
That mission required a deep contractor bench. Base operations, dining facilities, laundry, power generation, vehicle maintenance, and construction were all outsourced. The Army's LOGCAP program supplied much of this support. Under LOGCAP, a single logistics prime coordinates a web of subcontractors delivering life support on the base.
The nickname troops gave Balad tells you about the risk environment. They called it Mortaritaville, a reference to the frequency of indirect fire that landed inside the wire. Contractors working the flight line, the fuel points, and the perimeter were exposed to that risk alongside uniformed personnel. When a mortar round or a rocket caused injury to a covered contractor employee, the Defense Base Act applied.
Understanding this mission matters for claims work. The type of contract shapes which prime was responsible, and the prime often shapes which carrier wrote the policy. A logistics support role and an aviation training role at the same base can trace back to entirely different insurance chains. That is why base identity alone never resolves the carrier question.
What does the contract record show for Balad?
ClaimTrove holds 1,312 federal contract awards with a place of performance in Iraq. Of those, 13 name Balad Air Base directly in the contract description. That is a small slice, and it reflects a real limitation of federal contract data. Most awards describe the work and the country, not the specific installation.
The 13 Balad-specific awards cluster around two very different missions. One cluster is construction and logistics from 2006 through 2010. These awards went to KBR Services, LLC, and cover work like a counter-IED parking apron, expeditionary fabric hangars, a medevac helicopter compound, and a reception and staging facility. The award values run from roughly $1.7 million to $34.7 million each.
The second cluster is aviation training from 2015 through 2021. These awards went to Lockheed Martin Corporation for Iraqi Air Force F-16 advanced pilot training conducted at Balad. This is a useful reminder that the base did not go quiet after the 2011 drawdown. Contractor activity continued under a different mission and a different prime.
KBR's central role at Balad is visible in the data, and it mirrors what the broader record shows about that company. If you are tracing a KBR-linked file, the carrier history behind the largest defense contractor is a necessary starting point rather than an endpoint. One prime can shift carriers across contract periods.
The LOGCAP structure adds another layer. A worker employed by a dining or fuel subcontractor at Balad may never appear in a prime award at all. Tracing that chain means understanding how Army logistics contract transitions create carrier coverage gaps. The prime you find in a contract search is frequently not the entity that actually employed your client.
How many DBA claims came out of Iraq?
The Department of Labor does not publish DBA claim counts by base. It publishes them by nation. So the honest answer to "how many Balad claims exist" is that no public dataset isolates that number. What you can see is the Iraq-wide picture, and it is large.
ClaimTrove's case summary records count 92,952 total DBA cases tied to Iraq across the cumulative 2001 to 2024 reporting period. That figure includes 1,765 death cases. Balad, as one of the largest and longest-running bases, sits inside that total, but the records do not carve out its share.
The year-by-year trend tracks the war. Iraq recorded 7,075 DBA cases in FY2009 and 7,394 in FY2010, two of the highest-volume years of the war. Death cases peaked at 176 in FY2009. Volume fell through the drawdown years, then rose again to 4,393 cases in FY2020 as activity shifted. These are national totals, not base totals, and any responsible claim analysis has to keep that distinction sharp.
This is where the surge, drawdown, and later ISIS-era phases matter for carrier work. Coverage answers change with the timeline, because primes and their policies changed with the timeline. Reading Iraq claims through those three distinct coverage eras is more useful than treating the war as one undifferentiated period. A 2007 injury and a 2019 injury at the same base can point to different carriers.
Why are Balad burn pit claims a DBA problem?
Balad ran one of the most notorious open-air burn pits of the entire war. The pit covered roughly 10 acres and burned waste continuously for years. Everything from plastics and medical waste to vehicle parts went into it. The smoke plume drifted across living and working areas of the base. This is well-documented public history, not a contested claim.
For DBA purposes, burn pit exposure creates an occupational disease problem rather than a single-incident injury. A contractor does not always know at the time that the exposure will later cause illness. Respiratory disease, certain cancers, and other conditions can surface years after the person left Iraq. The claim clock and the responsible carrier both depend on when the disease is tied to the exposure.
That timing question is genuinely difficult. The controlling date is not the day the pit was burning. It turns on when the condition manifests and the worker becomes aware of the work connection. Get that date wrong and you can point at the wrong policy period entirely.
The carrier liability piece is equally tangled. A disease diagnosed in 2020 may trace to exposure during a 2006 to 2010 contract period, under a prime whose carrier has since changed. The framework for sorting slow-fuse carrier liability for 2003 to 2011 base operations applies directly to Balad files. The base was a heavy-exposure site during exactly that window.
Balad is not unique in this pattern, but its scale makes it a frequent source of these claims. Comparing it to a staging hub like Camp Arifjan in Kuwait shows how mission and geography change the contractor mix and the resulting claim profile. Each base leaves a different fingerprint in the data.
How do you identify the carrier for a Balad contractor?
Start with the honest constraint. The legal record on Balad is thin at the decision level. Only three decisions in ClaimTrove's OALJ corpus reference Balad by name. A base that hosted thousands of contractors produced very few published rulings that name it. That is normal, and it is why contract data and claim statistics have to fill the gap.
The workable method layers sources. You resolve the employer's real corporate name and its aliases first, because badge names and legal filing names rarely match. Then you connect that employer to a prime and a contract period. Then you match that period against carrier evidence drawn from legal decisions, industry reports, and FOIA database results. No single source answers the question. The layers together narrow it.
Sequencing those sources correctly is the whole game, and it is easy to do out of order. A clear investigation timeline showing which database reveals what keeps you from anchoring on a prime that never employed your client. Balad files reward that discipline because the direct evidence is so sparse.
ClaimTrove runs this layered search for you across contract awards, claim summaries, legal decisions, and carrier evidence in one pass. Instead of hand-checking 1,312 Iraq awards and cross-referencing corporate aliases, you enter the employer and dates and get a ranked carrier answer with its sources attached. Run a Balad-linked employer through ClaimTrove and pull the underlying contract, claim, and carrier records in one investigation.
The Balad footprint is real, it is documented, and it is recoverable. What it is not is sitting in one tidy table. The contractor mission was enormous, the exposure history is well established, and the claim volume for Iraq as a whole is among the highest of the war. The work is connecting a specific employee to a specific carrier. Start that investigation in ClaimTrove and let the engine trace the chain your client cannot recall.
This tool provides information from public DOL records. It is not legal advice. Always verify with primary sources.