Your client was a heavy-equipment mechanic on an atoll most Americans cannot find on a map. He was paid in US dollars, deployed from a US staging point, and injured servicing a fuel system on a runway that launches US strategic bombers. Then he learns the island is sovereign British territory. His first question, and yours, is whether US workers' compensation law reaches a coral speck in the middle of the Indian Ocean.
It does. Diego Garcia is one of the cleanest Defense Base Act jurisdictional questions in the entire overseas-contractor universe, and yet it generates real confusion because the geography fights the law. The island belongs to the United Kingdom. The base on it belongs, operationally, to the United States. That split is exactly the situation Congress wrote the DBA to cover.
This piece walks through why a remote British possession triggers US coverage, what makes Diego Garcia logistically unique among DBA worksites, and where the hard problems actually live. The hard problem is almost never jurisdiction. It is identifying which carrier insured which contractor during which staffing period. That answer is not public, and it shifts over time. We will show you how the identification process works without handing over mappings that took years of records work to assemble.
If you handle overseas contractor injuries, Diego Garcia is worth understanding cold. The base has operated continuously since the 1970s, the contractor population is small and specialized, and the claims that come out of it tend to involve serious mechanical, maritime, and logistics injuries rather than the combat-adjacent profile of Iraq or Afghanistan work. The legal questions are different, and the carrier puzzle is its own animal.
What is Diego Garcia and why does the US military operate there?
Diego Garcia is the largest atoll in the Chagos Archipelago, in the central Indian Ocean. It is British territory, designated the British Indian Ocean Territory (BIOT) in 1965. There is no native civilian population on the island today. The only people there are military personnel and the contractors who keep the base running.
The United States operates a major naval support facility on the island under a long-running agreement with the United Kingdom. The base hosts a deep-water harbor, a runway long enough for B-52 and B-2 bombers, prepositioned equipment ships, and communications and tracking infrastructure. For decades it has functioned as the central logistics hub for US operations across the Middle East, East Africa, and the Indian Ocean.
That mission profile drives the contractor work. Diego Garcia needs base operations support, fuel handling, port and harbor services, aircraft ground support, water and power, food service, and heavy maintenance. Almost none of that is done by uniformed personnel. It is done by civilian contractors working under US government contracts, which is the precise population the DBA was designed to protect.
The island's isolation shapes everything about the work. The nearest major landmass is roughly 1,000 miles away. Resupply comes by ship and by air on a fixed schedule. There is no walking off the job and driving home. A worker who is injured cannot reach a Level I trauma center in an hour. Medical evacuation often means a flight to Singapore or another regional hub, and that logistics reality has direct consequences for how serious injuries are managed and how DBA medical benefits get spent.
For a workforce this small and this remote, the contractor roster is correspondingly narrow. A handful of large base-operations primes have held the work over the decades, with specialized subcontractors layered underneath them for fuel, marine, and aviation services. That concentration is good news for identification in theory and a trap in practice, because the same physical job can change corporate hands without any visible signal to a claimant.
Does the Defense Base Act cover injuries on British territory?
Yes, and the statute does not blink at the British flag. The Defense Base Act, codified at 42 U.S.C. 1651, extends the Longshore and Harbor Workers' Compensation Act to civilian employees working on US military bases and under US government contracts outside the continental United States. The triggering facts are the contract and the worksite's relationship to US operations, not the sovereignty of the dirt underneath.
The DBA was built precisely for overseas bases on foreign soil. Congress did not assume the United States would own every base where contractors work. It assumed the opposite. A base operated by the US military on territory leased or shared with an allied government is the textbook DBA scenario, and Diego Garcia is as clean an example as exists. The contract is a US government contract. The worksite supports US military operations. Coverage follows.
What makes Diego Garcia simpler than many theaters is the absence of competing legal regimes that muddy other claims. There is no NATO contracting layer to untangle, which on European or Mediterranean bases can defeat DBA coverage when the work was actually performed under a NATO contract rather than a US one. There is no host-nation workers' compensation scheme competing for the worker, because there is effectively no host-nation civilian economy on the island.
The jurisdictional clarity does not mean the claim runs itself. Concurrent and successive employment is common in the contractor world, and a worker who rotated through Diego Garcia, Kuwait, and a domestic shipyard within a single benefit period can present a genuinely difficult average weekly wage and responsible-employer analysis. If your client stacked overseas assignments, the principles in our breakdown of concurrent employment and DBA claims across multiple overseas employers apply directly.
Off-duty injury questions also surface more on Diego Garcia than people expect. The island is a closed environment where workers live, eat, exercise, and recreate within the base footprint. When the entire life of the worker happens on the employer's controlled site, the line between compensable and non-compensable injury blurs. Our analysis of recreational injury coverage for off-duty overseas contractors is squarely on point for a base like this one.
What makes Diego Garcia contractor work logistically unique?
The island runs on three tightly coupled functions: the airfield, the port, and base life support. Each generates a distinct injury profile, and each is staffed by a distinct slice of the contractor population.
The airfield work centers on fuel and ground support for strategic and tanker aircraft. That means jet fuel handling, hydrant systems, refueling vehicles, and flight-line operations. The injury risk skews toward burns, chemical exposure, falls from height on aircraft, and equipment-strike incidents. These are mechanical and process injuries, not the blast and small-arms exposures that dominate war-zone claims.
The port and harbor work is maritime in character. Diego Garcia hosts prepositioning ships and a working deep-water harbor, so contractors handle cargo, small craft, mooring operations, and marine maintenance. This is where the line between DBA and pure Longshore coverage can get interesting, because some maritime work on the island looks a lot like the harbor work the LHWCA was originally written for. The status-and-situs analysis still resolves to DBA on a US overseas base, but the factual record reads like a longshore file.
Base life support covers everything else: power generation, water treatment, food service, billeting, and the heavy equipment that keeps it all moving. These workers face the broad industrial injury spectrum plus the compounding factor of isolation. A crush injury that is survivable in San Diego becomes a medevac-dependent emergency 1,000 miles from a trauma center.
That medevac reality is the single most important practical feature of Diego Garcia DBA claims. Serious injuries trigger long, expensive evacuation chains, often through Singapore. DBA medical benefits cover reasonable and necessary treatment, and the necessary treatment for a remote-island injury can include international air ambulance, regional hospitalization, and repatriation. The medical record on these files is geographically scattered, which matters when you are assembling proof and tracing the carrier who paid, or should have paid, for the evacuation.
The work also frequently involves contractor-supplied heavy equipment and machinery. When the injury was caused by a machine the employer itself built, supplied, or modified, a second theory of liability can open up alongside the DBA claim. That is the terrain covered in our discussion of the dual capacity doctrine when the employer is also the equipment manufacturer, and it comes up more on heavy-logistics sites than most practitioners expect.
Why is identifying the Diego Garcia carrier so difficult?
Here is the part that surprises attorneys. The jurisdiction is easy and the carrier is hard. You can be certain the DBA applies and still have no idea which insurance company is on the hook.
The first reason is contract structure. Base operations support at a site like Diego Garcia typically runs through large, multi-year vehicles where the controlling document is not the umbrella contract but the specific task order in force on the date of injury. The carrier obligation can ride on the task order, not the parent contract, and the same prime can carry different coverage arrangements across different task orders. We unpack this in detail in our piece on which task order controls the carrier under an IDIQ contract, and it is the single most common reason a confident carrier guess turns out wrong.
The second reason is temporal shift. Across our records, DBA carriers for a given contractor change every three to five years for most overseas work, driven by contract recompetes, broker changes, and market cycling. A worker injured in one year and a worker injured at the same site four years later may have entirely different carriers, even if the prime contractor name on the badge never changed. A carrier answer without a date attached is close to meaningless.
The third reason is the third-party administrator problem. The name on the claim correspondence is very often a TPA, not the actual underwriter. A claimant who sees a familiar claims-administration company on a letter assumes that company is the insurer. It usually is not. Resolving the administrator back to the carrier that actually carries the risk is its own analytical step, and getting it wrong sends a lien notice or a controversion to the wrong entity.
The fourth reason is corporate identity. The legal employer named on the DBA filing is frequently a subsidiary or a contract-specific entity, not the household-name prime. The badge says one thing, the contract says another, and the insurance card a third. Resolving those names to a single corporate family is a prerequisite to even asking the carrier question correctly.
Diego Garcia compounds all four problems because the contractor population is small and the work is long-running. The same physical job has been performed by different corporate entities under different vehicles across five decades, with carriers shifting underneath each transition. Identifying the carrier means pinning the specific employer, the specific contract or task order, and the specific date, then tracing that combination to an underwriter through records that were never designed to be searched together.
How does ClaimTrove surface the carriers active on Diego Garcia?
ClaimTrove was built for exactly this problem: the worksite where the law is settled but the carrier is buried. The platform cross-references federal contract award records, FOIA-released contractor databases, DOL coverage filings, OALJ and BRB decision parties, and SME-confirmed carrier mappings to reconstruct which contractors operated at a location during a given period and which carriers stood behind them.
For a location-first investigation, you enter the place and the date. The engine discovers the prime contractors that held work at that location during that window, traces each to its likely carrier, resolves third-party administrators back to underwriters, and accounts for the temporal proximity between the carrier evidence and your client's injury date. It also flags whether a US government contract was actually in force, which is the foundation of DBA coverage in the first place.
The output is not a guess. Each carrier candidate carries a confidence level and a stated source, so you can see whether the answer rests on a direct coverage record, a legal-decision party, or a statistical inference that you should verify independently. That transparency is the difference between a name you can act on and a name you have to re-investigate.
Run a Diego Garcia investigation in ClaimTrove and surface the contractors and carriers active on the island for your client's exact period. The jurisdiction is the easy part. Let the platform handle the part that actually decides where your client's benefits come from.
What injury patterns should attorneys expect from Diego Garcia claims?
Because the workforce is concentrated in fuel, marine, aviation, and heavy-logistics roles, the claims skew toward severe single-incident industrial injuries rather than the cumulative-trauma and psychological profiles that dominate war-zone files. Crush injuries, falls, burns, chemical exposures, and machinery strikes are the recurring patterns.
This profile resembles high-hazard logistics and base-support work more than security contracting. If you want a sense of how injury severity and carrier exposure correlate across different overseas contractor roles, our analysis of what DBA data reveals about the highest-risk employers provides useful comparative context, even though Diego Garcia's workforce is logistics-heavy rather than security-heavy.
The isolation factor also reshapes the damages picture. A back injury that resolves with outpatient care in the continental United States can require evacuation, regional hospitalization, and weeks of repatriation logistics from Diego Garcia. The medical benefit exposure on a serious claim is therefore higher and more complex than the same injury domestically, and the records are scattered across multiple jurisdictions and providers.
Finally, expect documentation gaps. Remote sites generate incomplete incident records, delayed reporting, and witness populations that rotate off the island before a claim matures. Building these files is records-intensive, which is precisely why identifying the responsible carrier early, before witnesses scatter and contracts get archived, pays off more here than almost anywhere else in the DBA world.