A paralegal opens a new file. The injured worker is a security contractor who worked on a federal contract. The injury happened on a US Army installation. The intake form says "military base," and the attorney assumes the Defense Base Act applies. Then a detail surfaces: the base was Fort Bragg in North Carolina, not a forward operating base in Kandahar. Suddenly the entire coverage theory is wrong, and the carrier the team spent two days hunting may not be a DBA carrier at all.
This is the CONUS versus OCONUS problem, and it sinks more DBA intake decisions than any other single fact pattern. The phrase "US military base" tells you almost nothing about jurisdiction. A base inside the continental United States and a base in Bahrain trigger completely different compensation regimes. Get the geography wrong and you file under the wrong act, chase the wrong insurer, and waste the statute of limitations window doing it.
This guide explains how DBA coverage actually works on military bases, why CONUS and OCONUS are not interchangeable, and where the real exceptions live. Understanding DBA coverage on a US military base, domestic CONUS vs OCONUS, is the first jurisdictional question any DBA team should resolve before it touches carrier research. The location determines the act. The act determines the carrier. The carrier determines the claim.
What Does CONUS vs OCONUS Mean for DBA Coverage?
CONUS stands for the continental United States. OCONUS means outside the continental United States. The military uses these terms constantly, but for DBA purposes the distinction is not a logistics label. It is a jurisdictional fault line.
The Defense Base Act was written to cover civilian employees working on US military bases and public works projects outside the United States. The statutory hook is overseas employment. When the work happens abroad, on a foreign base or under a foreign-performed contract, the DBA is the controlling compensation scheme for covered employees.
CONUS work is different. A civilian injured while working on a domestic military installation in Texas, Georgia, or Virginia is generally not a DBA claimant. That worker typically falls under state workers' compensation law, or in maritime and certain federal-enclave situations, under the Longshore and Harbor Workers' Compensation Act. The DBA simply was not designed for stateside work.
This matters because the carrier universe is different. A DBA carrier is one of a limited set of insurers authorized by the Department of Labor to write Defense Base Act coverage. ClaimTrove tracks 637 authorized DBA carriers. A domestic workers' comp policy on a CONUS contract may be written by an insurer that has never touched a DBA filing. Searching DBA records for a CONUS injury can return nothing, not because the data is missing, but because the claim never belonged in the DBA system.
When Does DBA Coverage Apply on an Overseas Military Base?
OCONUS is where the DBA does its heaviest lifting. The act reaches civilian employees of government contractors performing work on US military bases overseas, on public works contracts abroad, and under contracts approved or funded by US agencies for overseas performance.
The geography behind these claims is concentrated. ClaimTrove data covers 43,298 prime contract awards and tracks where the work was performed. Combat-theater countries like Afghanistan and Iraq dominate the historical DBA caseload, but the footprint is far broader. Permanent overseas installations generate steady DBA exposure even in peacetime, which is why claims from places like Germany and Japan look structurally different from claims out of Kandahar.
The country a worker was injured in shapes everything downstream. We break down that geography in detail in our look at defense contractor workforce size overseas by country, which shows where the 43,298 awards actually place the risk. A peacetime base in a NATO host nation carries different coverage and dispute patterns than a wartime forward operating base, even when both are technically "US military bases."
One trap deserves attention. Not every OCONUS contract requires DBA insurance, and not every overseas worker is a covered DBA employee. The contract type, the funding agency, and the nature of the work all factor in. We map those distinctions in our breakdown of which OCONUS contract types actually require DBA insurance coverage. Assuming "overseas equals DBA" is almost as dangerous as assuming "military base equals DBA."
Are There Exceptions Where CONUS Work Triggers the DBA?
Yes, and this is where confident attorneys get burned. The CONUS-equals-no-DBA rule is a strong default, not an absolute wall. A handful of fact patterns can pull domestic work under the act or its companion statutes.
Consider a contractor whose work is performed partly in the United States but is integrally tied to an overseas military contract. Consider a worker injured during US-based training or staging that is part of an overseas deployment pipeline. Consider mixed contracts where the same employee rotates between a CONUS support role and OCONUS field work within a single coverage period. The injury date and physical location interact with the contract scope in ways that are not always obvious from an intake form.
The companion-statute problem compounds this. The Longshore and Harbor Workers' Compensation Act underlies the DBA and can independently apply to certain federal and maritime work performed stateside. Determining whether a claim sits under state comp, the LHWCA, or the DBA is a real legal analysis, not a checkbox. Location disputes are common enough that we devoted a full article to how injury location disputes complicate DBA jurisdiction.
The practical takeaway: do not let a CONUS injury location close the file automatically. Read the contract scope. Identify the funding agency. Determine where the controlling work was performed and what the employee was actually doing when injured. A domestic address on a police report is a starting hypothesis, not a verdict.
Why Does Getting the Jurisdiction Wrong Break Carrier Identification?
Carrier identification is the core of DBA practice, and it is entirely downstream of jurisdiction. If you misclassify a claim, every search you run afterward is pointed at the wrong dataset.
Picture the failure cascade. The team assumes DBA based on "military base." It searches DBA carrier records for the employer. The contractor used multiple corporate names, so even a correct DBA search is hard, which is exactly why we wrote about why DBA carriers change over time through temporal shifts in coverage. Now layer a jurisdictional error on top. The team is searching the right database with the wrong premise, or the wrong database entirely. The result looks like missing data when it is really a misframed question.
The opposite error is just as costly. A team assumes a CONUS injury is plain state comp, never checks the contract scope, and misses that the worker was on an overseas-staging assignment covered by the DBA. The claim gets filed under state law, the DBA limitations clock runs, and a viable federal claim quietly expires.
This is why ClaimTrove starts investigations with location and contract context, not just an employer name. Across more than one million federal records and 18 data sources, the system cross-references where work was performed, which agency funded it, and which authorized DBA carriers appear in the relevant filings. Correct jurisdiction is the precondition for a correct carrier answer.
Stop guessing whether a base is CONUS or OCONUS for coverage purposes. Run a ClaimTrove investigation to see how location, contract, and carrier data line up before you file.
How Should You Triage a Military Base Injury at Intake?
A repeatable intake sequence prevents the most expensive mistakes. Work the geography and the contract before you commit to a compensation theory.
- Pin the exact installation. Not "a military base," but the named installation and its country. Fort, camp, and post names repeat across CONUS and OCONUS, so confirm the actual location.
- Confirm CONUS or OCONUS. A domestic installation points toward state comp or the LHWCA. An overseas installation points toward the DBA, subject to contract review.
- Read the contract scope. Identify the prime contract, the funding agency, and whether the work was tied to overseas performance even if the injury happened stateside.
- Check for mixed assignments. Rotating, staging, and training roles can cross the CONUS-OCONUS line within one coverage period.
- Resolve the employer's identity. Contractors operate under multiple legal names and subsidiaries, which is the same identity problem that makes carrier tracing hard everywhere in DBA work.
- Only then search for the carrier. Once jurisdiction is settled, the carrier question becomes answerable.
This ordering reflects how experienced DBA teams actually work. Subcontracting adds another layer, because the responsible carrier is not always the prime's carrier. We cover that wrinkle in our guide to who is responsible when a subcontractor's employee is injured. Settle the location, settle the act, settle the employer identity, and the carrier search stops feeling like guesswork.
The fastest way to compress this entire sequence is to let the data do the cross-referencing for you. ClaimTrove pulls location, contract award, and carrier filings into one view so your team confirms jurisdiction and identifies the authorized DBA carrier in the same investigation, instead of running three separate manual searches.
This article provides information from public DOL records and is not legal advice. Always verify coverage and jurisdiction with primary sources.