Where Does the Defense Base Act Actually Apply?
The Defense Base Act extends workers' compensation coverage to civilian employees working overseas on U.S. military bases, under contracts with the U.S. government for public works or national defense, or on contracts approved and funded by the U.S. under the Foreign Assistance Act. That description sounds comprehensive. In practice, its boundaries generate constant litigation.
The geographic reach of the DBA is both its greatest strength and its most contested feature. Unlike domestic workers' compensation statutes that apply within a state's borders, the DBA applies extraterritorially. It reaches any country where U.S. government contract work is being performed. But the statute does not cover every injury that happens to every American worker overseas. The connection between the injury, the employment, and the government contract must be established.
ClaimTrove's analysis of 5,022 OALJ decisions and 244 court opinions shows that jurisdictional challenges appear in roughly one-fifth of contested DBA cases. These challenges take many forms, but they frequently center on the location of injury, the nature of the employment relationship, and the scope of the government contract.
What Makes the DBA's Geographic Scope Different from Domestic Workers' Comp?
Domestic workers' compensation operates on a straightforward territorial model. If you are injured in Texas while working for a Texas employer, Texas workers' comp applies. There are complications at the margins (traveling employees, multi-state employers), but the basic framework is geographic.
The DBA operates differently. It does not apply to a defined territory. It applies to a defined relationship: the relationship between a worker, an employer, and a U.S. government contract for overseas work. This means the same worker, doing the same job, in the same location, might be covered by the DBA or might not be, depending on whether their employer holds the right kind of government contract.
This contract-based jurisdiction creates situations where two workers standing side by side at the same overseas facility have different legal protections. The worker employed by a prime contractor with a direct DoD contract is covered. The worker employed by a local subcontractor three tiers down may face questions about whether the DBA extends to their employment relationship.
The BRB and federal courts have generally interpreted the DBA's scope broadly, consistent with its remedial purpose. But broad interpretation does not eliminate the need to establish the jurisdictional facts. Attorneys must still prove that the employer had a qualifying contract, that the work was performed outside the United States, and that the injury arose out of and in the course of employment.
How Does Location Affect Which Carrier Applies?
DBA insurance policies can be written with geographic limitations. A carrier may insure an employer's operations in Afghanistan but not Iraq. A policy may cover "worldwide" operations or may be limited to specific countries or regions. When a worker is injured in a location not explicitly covered by the employer's DBA policy, a coverage dispute erupts.
These disputes are more common than many practitioners realize. Large defense contractors operate across multiple theaters simultaneously. A contractor with active projects in Afghanistan, Iraq, Kuwait, and Djibouti may have different DBA carriers for different locations, or a single carrier with location-specific endorsements. A worker who deploys from one country to another mid-assignment can inadvertently cross a policy boundary.
The evidence needed to resolve these disputes is specific: the policy declarations page showing geographic coverage, the employee's travel and deployment records, and proof of where the injury actually occurred. In conflict zones, this last element can be surprisingly difficult to establish. Base locations are often classified or described in vague terms. Medical evacuation records may list a treatment facility rather than the injury location. Incident reports may reference grid coordinates or FOB names that do not correspond to clear country designations.
For attorneys investigating DBA claims, establishing the exact injury location is a foundational step. ClaimTrove's database of 43,298 contract awards includes place-of-performance data that helps map employers to specific overseas locations. Cross-referencing the employer's contract location with the claimed injury location can either confirm or challenge the jurisdictional basis of the claim.
What Happens with Third-Country Nationals Under the DBA?
Third-country nationals (TCNs) represent one of the most litigated categories of DBA claimants. A TCN is a worker who is neither a U.S. citizen nor a citizen of the country where the work is performed. A Filipina worker employed by a Kuwaiti subcontractor on a U.S. military base in Afghanistan is a TCN. A Bangladeshi worker doing laundry services at a base in Iraq under a U.S. government contract is a TCN.
The DBA covers TCNs, and the BRB has affirmed this repeatedly. The statute does not limit coverage to U.S. citizens. It covers "employees" of qualifying contractors, regardless of nationality. But TCN cases raise unique jurisdictional issues that do not arise with U.S. citizen workers.
First, the employment chain is often longer and more opaque. A U.S. prime contractor hires a regional subcontractor, which hires a local labor broker, which recruits workers from a third country. Each link in this chain creates questions about who the "employer" is for DBA purposes and whether the DBA extends to workers at the end of a long subcontracting chain.
Second, TCN workers often have limited documentation. Work permits, employment contracts, and pay records may be in different languages, governed by different local labor laws, and held by intermediaries rather than the worker. Reconstructing the employment relationship to establish DBA jurisdiction requires navigating these documentary challenges.
Third, the BRB has addressed whether a TCN must have a "substantial connection" to the United States for DBA jurisdiction to attach. Some carriers have argued that the DBA should not cover a foreign worker employed by a foreign subcontractor, even if the ultimate contract is with the U.S. government. The BRB has generally rejected these narrow interpretations, holding that the statutory text covers all employees of qualifying contractors without a citizenship requirement.
TCN cases also raise practical challenges for carrier identification. As explained in our guide to tracing prime vs. subcontractor DBA insurance, the subcontractor employing the TCN may or may not carry its own DBA insurance. If it does not, the prime contractor's carrier may be implicated. Determining the insurance chain requires tracing the subcontracting relationships and identifying which entity at each tier carried DBA coverage.
What Is the "Floating Situs" Problem in DBA Cases?
The Longshore Act (which the DBA incorporates) applies to injuries occurring on "navigable waters" or in an adjoining area. This "situs" requirement creates interesting jurisdictional questions when DBA workers are injured on vessels, offshore platforms, or during maritime transport.
In the DBA context, the floating situs issue most commonly arises with workers who perform duties on military vessels or at port facilities overseas. A civilian contractor working on a Navy ship in the Persian Gulf is covered by both the DBA (overseas government contract work) and potentially the Longshore Act directly (injury on navigable waters). The interplay between these two statutes can affect which procedural rules apply and how benefits are calculated.
More practically, the floating situs problem arises when workers are injured during transport between locations. Helicopter flights between bases, convoy travel between provinces, and boat transfers between port facilities all create moments when the worker is "between" defined locations. If the worker is injured during transport, the question of where the injury occurred may determine jurisdictional issues.
The BRB has addressed these transport injuries under the zone of special danger doctrine, as discussed in our analysis of key BRB decisions that define DBA coverage, generally finding that injuries during required travel in a conflict zone are compensable regardless of the precise location. But the carrier coverage question can still depend on where the transport started or where it was headed, if the employer's policy has geographic limitations.
Defense contractors with maritime operations face particular complexity here. A worker based in Kuwait who regularly travels by boat to offshore facilities in the Persian Gulf may be covered by different insurance arrangements depending on whether the injury occurs on land in Kuwait, on the vessel, or at the offshore facility. The floating situs adds a dimension that purely land-based DBA cases do not have.
How Do Afghanistan, Iraq, and Other Theaters Differ in DBA Practice?
While the DBA applies uniformly as a matter of law, the practical realities of different overseas theaters create different patterns in how cases develop. Afghanistan and Iraq have generated the vast majority of DBA claims since 2001, but other theaters have their own characteristics.
Afghanistan cases, which dominated the DBA claims landscape for over a decade, are distinguished by the remote and austere conditions of many worksites. Forward Operating Bases (FOBs) in provinces like Helmand, Kandahar, and Paktia were often isolated, dangerous, and poorly documented. Workers at these locations faced blast injuries, vehicle accidents, attacks, and the psychological toll of constant threat. Medical evacuation paths were complex, with injured workers moving through multiple facilities before reaching definitive care. This creates evidentiary challenges for establishing exact injury dates and locations.
Iraq cases from the peak deployment years (2003-2011) involved larger, more established bases with better documentation. Injuries at major installations like Camp Victory, Balad Air Base, or the Green Zone are generally easier to document than injuries at remote Afghan FOBs. However, Iraq cases have their own complications, particularly around the transition periods when bases were closed or handed over to Iraqi forces.
Other theaters present different issues. DBA cases from Africa (particularly AFRICOM-related operations in Djibouti, Niger, and Somalia) are growing. Cases from the Pacific region, Europe, and South America each have their own characteristics related to the types of contracts, the nature of the work, and the available documentation.
For carrier identification purposes, the theater matters because different contracts cover different regions. ClaimTrove's contract database includes place-of-performance data across all theaters, helping attorneys identify which prime contractors operated where and during which periods. This data becomes the starting point for tracing the subcontractor and carrier chain specific to the theater where the injury occurred.
How Do Recent BRB Decisions Address Location Disputes?
The BRB continues to refine its jurisdictional jurisprudence. Recent decisions have addressed several recurring location disputes that DBA practitioners should track.
One line of cases addresses the scope of "adjoining areas" for workers who split time between U.S. military installations and off-base locations. When a worker spends mornings on a military base and afternoons at an off-base contractor facility, an injury at the off-base location raises questions about whether the DBA's military base coverage extends to that site. The BRB has generally taken a functional approach, asking whether the off-base work was integral to the government contract rather than focusing solely on the physical location.
Another line of cases addresses workers who perform short-term assignments in multiple countries. A contractor who spends two weeks in Afghanistan, then three weeks in Kuwait, then returns to Afghanistan may be injured during the Kuwait segment. If the employer's DBA policy covers Afghanistan but not Kuwait, the carrier may argue that the Kuwait injury falls outside the policy. The BRB has examined whether these multi-country assignments constitute a single continuous deployment or separate assignments, with different results depending on the facts.
A third category involves injuries during rest and recuperation (R&R) leave. When a worker is injured during authorized R&R in a third country (such as Qatar or Dubai), the question arises whether the DBA covers injuries that occur outside the primary work location. The zone of special danger doctrine often applies to these situations, but the carrier coverage question depends on the policy's geographic terms.
What Should DBA Attorneys Do When Jurisdiction Is Contested?
When a carrier raises a jurisdictional challenge, the burden falls on the claimant to establish the facts that bring the claim within the DBA's scope. This means proving three elements: a qualifying contract, overseas employment, and an injury arising from that employment.
Start with the contract. Obtain the contract number, the contracting agency, and the period of performance. ClaimTrove's database of 43,298 contract awards and 4,315 subaward records provides a starting point for identifying the contract under which the claimant worked. The contract's terms will specify the geographic scope and nature of the work.
Next, document the employment relationship. If the claimant worked for a subcontractor, trace the chain from the sub to the prime to the government contract. Each link must be documented. Employment records, pay stubs, deployment orders, and badge records all establish the worker's presence at the overseas location.
Then, establish the injury location. Medical records, incident reports, witness statements, and military records can all place the injury at a specific location. The more precisely you can establish where the injury occurred, the stronger your jurisdictional position.
For complex multi-theater or multi-employer cases, investigative tools that cross-reference contract data, employer data, and carrier data save significant time. ClaimTrove aggregates over 1 million records from 18+ public sources specifically to help DBA practitioners build the factual foundation for jurisdiction. When a carrier argues your client was not covered, you need data, not assumptions.
Build your jurisdictional case on solid evidence. Search ClaimTrove's database of contract awards, carrier mappings, and case precedent to establish the facts before the hearing.