A paralegal opens a file for a diesel mechanic who spent 2010 and 2011 turning wrenches on a dusty forward operating base in southern Afghanistan. The intake sheet says "Camp Leatherneck, Helmand Province." It does not name the employer's insurance carrier. It does not even name the prime contractor. That single line is where thousands of Defense Base Act investigations begin, and it is where most of them stall.
Camp Leatherneck was the largest United States Marine Corps base in Helmand Province. It shared a perimeter with the United Kingdom's Camp Bastion, and together the two formed the logistics heart of the 2009 to 2011 troop surge. At its peak the complex housed tens of thousands of personnel, and behind every one of them stood contractors. Cooks, mechanics, security staff, translators, and construction crews all worked there under federal contracts that carry DBA obligations.
The problem for attorneys is that public records rarely tie an injury to a specific base. They tie it to a country. This article walks through what ClaimTrove data reveals about the Leatherneck and Bastion contractor footprint. It covers the injury numbers and why the base name on an intake form is only the first clue in a much longer chain.
What Were Camp Leatherneck and Camp Bastion?
Camp Leatherneck opened in 2009 as the Marine Corps expanded operations into Helmand. It became the main American installation in the province. Camp Bastion, the adjoining British base, hosted a major airfield and a field hospital that treated coalition casualties from across the region.
The two bases operated as a joint complex. Contractors moved between them, and support work often spanned both perimeters. During the surge the footprint grew fast, then shrank just as fast as the drawdown began. The United States formally handed Camp Leatherneck to Afghan National Army forces in October 2014.
That short life span matters for DBA work. A contractor injury at Leatherneck almost always falls between 2009 and 2014. The carrier that covered a payroll in 2010 may not be the carrier that covered the same employer in 2013. Coverage shifts over time, which is one reason the base name alone never answers the carrier question. If you want the mechanics of that problem, our breakdown of why DBA carriers change over time lays out how a single employer can rotate through several underwriters.
How Many DBA Claims Came Out of Helmand Province?
Here is the first hard limitation every DBA researcher hits. The Department of Labor publishes Defense Base Act case summaries by nation, not by base. There is no official "Camp Leatherneck" claim count. There is only an Afghanistan number.
That Afghanistan number is large. ClaimTrove's DOL case summary data records 76,922 cumulative DBA cases for Afghanistan across the 2001 to 2024 reporting period, including 1,865 death cases. Those totals cover every base, contract, and employer in the country. Leatherneck and Bastion injuries live somewhere inside that figure, but the data does not carve them out.
The year by year pattern tells the surge story clearly. Afghanistan DBA cases climbed from 3,122 in fiscal year 2010 to 3,605 in fiscal year 2011, then kept rising to a surge-era peak of 7,350 cases in fiscal year 2013. Death cases tracked the fighting even more sharply. They hit 357 in fiscal year 2010 and 374 in fiscal year 2011, the two years when the Helmand surge was at its most intense.
Those death peaks line up with the exact window when Leatherneck and Bastion were most heavily populated. The nation level data cannot prove that any single fatality happened at the base. It can show that the deadliest years for Afghanistan contractors were the years when this complex was the busiest place in the country. For the broader picture, our analysis of IED blast injury claims in Afghanistan and Iraq covers the injury types that drove those surge era numbers.
What Do Federal Contract Records Show About Leatherneck and Bastion?
Contract data is where the base finally comes into focus, and it is surprisingly thin. ClaimTrove holds 1,251 Afghanistan contract awards. Of those, only two name Camp Leatherneck directly in the award description.
The first is a General Services Administration vehicle fleet award to AMS Integrated Solutions FZ-LLC, valued at roughly $29.5 million and running from 2011 into 2019. Its description activates service at four forward operating bases at once, listing Bagram Airfield, Kandahar Airfield, Camp Leatherneck, and the Kabul base cluster together. The second is a Department of Defense award to KBR Wyle Services worth about $4.1 million. Titled "Camp Leatherneck Retrograde," it covered teardown work during 2013 and 2014 as the base closed.
Camp Bastion appears in four Afghanistan awards, and every one of them went to AECOM Technical Services. They cover design and engineering support for a medical facility expansion, a parallel taxiway and refueler apron, and command and control construction at the adjoining Tombstone Bastion site. A broader search for Helmand Province across the same contract corpus returns just ten awards.
These counts are not a census of every contractor who worked there. They are what surfaces when you search award descriptions for the base name. Most contracts describe the work by task, agency, or contract vehicle, not by the base where crews actually stood. That gap is exactly why searching a single keyword misses the employers you need. Learning to read USAspending contract data for DBA investigations is the difference between finding two contractors and finding the dozens who really operated there.
Why Is Legal Precedent So Scarce for These Bases?
You might expect a base this large to generate a stack of published decisions. It did not. Across ClaimTrove's corpus of administrative law judge and Benefits Review Board decisions, exactly one references Camp Leatherneck by name. Not a single decision references Camp Bastion.
This scarcity is not evidence that injuries were rare. It reflects how the DBA system works. The overwhelming majority of DBA claims settle or resolve informally, long before a judge writes an opinion. Only contested claims that run the full adjudication route leave a searchable decision behind.
For an attorney, the lesson is that base name alone will not pull useful case law. The productive search runs on the employer, the carrier, and the contract vehicle, then cross checks the injury date. A Leatherneck injury in 2011 and a Leatherneck injury in 2013 may involve different primes, different subs, and different carriers even for the identical worksite.
Why Does the 2009 to 2011 Surge Still Drive DBA Claims Today?
Many Helmand injuries were not one time events. Blast exposure, hearing loss, musculoskeletal damage, and psychological trauma often surface years after the contractor leaves the theater. A worker who rotated through Leatherneck in 2010 may file a claim well into the following decade.
The Afghanistan case data reflects this long tail. Even after combat operations wound down, annual DBA case counts stayed high and then climbed again, reaching 9,812 in fiscal year 2024. Late filed occupational disease and cumulative trauma claims keep the pipeline full.
For the practitioner, a delayed claim compounds the carrier problem. The employer may have merged, rebranded, or dissolved. The carrier that wrote the policy during the surge may have exited the DBA market entirely. Reconstructing coverage for a 2010 injury reported in 2024 means rebuilding a paper trail that is more than a decade cold. Camp Leatherneck sat at the same logistical crossroads that made staging hubs like Kuwait's Camp Arifjan so contractor heavy, and both share this same delayed claim challenge.
How Do You Trace a Carrier for a Leatherneck or Bastion Injury?
The base name gets you to Afghanistan. It does not get you to a carrier. To close that gap you have to move from location to employer to carrier, and each step needs its own records.
Start with the contract data to identify the primes and subs that operated in Helmand during the injury window. Resolve the employer's corporate aliases, because the name on the badge is often not the name on the DBA policy. Then layer in adjudicated decisions, DOL coverage records, and agency mandate rules to narrow the actual underwriter. A single Marine base can touch federal contract awards, subcontract chains, legal decisions, and insurance filings all at once, and no free public tool joins those sources for you.
ClaimTrove runs that entire chain in one investigation. It searches federal contract data, resolves aliases, checks agency mandates, and surfaces the DOL and legal records behind each carrier candidate. Then it ranks the results by how close they sit to your injury date. Run a location first investigation on Afghanistan and your injury window inside ClaimTrove to see the primes, subs, and carrier candidates that public keyword searches never reveal.
What Should Attorneys Take Away From the Helmand Data?
Camp Leatherneck and Camp Bastion were enormous, but they leave a faint trail in the exact records attorneys reach for first. The DOL reports Afghanistan claims by nation, so the base disappears into a country total of 76,922 cases. Federal contract descriptions name Leatherneck only twice and Bastion only four times. Published legal decisions barely mention either.
None of that means the claims are weak. It means the evidence is scattered across sources that do not talk to each other. The winning approach treats the base name as a starting coordinate, not an answer, and then rebuilds the employer and carrier chain around the injury date. Point your next Helmand file at ClaimTrove and let the investigation engine assemble the contract, corporate, and coverage records into a single carrier answer.
This tool provides information from public DOL records. It is not legal advice. Always verify with primary sources.