A paralegal opens a new file. The client was a heavy-equipment operator hurt on a flight-line project at Andersen Air Force Base on Guam. The supervising attorney asks the first question bluntly. Does the Defense Base Act even apply here? Guam flies the US flag. It uses US currency. Its residents are US citizens. On paper it looks domestic. That instinct is exactly what trips up attorneys handling a Pacific staging claim for the first time.
Guam is not a foreign country. It is a US territory. That single distinction controls how a contractor injury there gets covered, filed, and paid. The Defense Base Act was written for work outside the continental United States, and Guam sits squarely in that category. Public Department of Labor records already show a steady stream of DBA claims tied to the island.
This article walks through what those public records reveal about contractor injuries at Andersen and Naval Base Guam. You will see the claim volumes, the recent surge tied to the Marine Corps buildup, and the rule that makes DBA coverage apply on US soil. You will also see why the federal contract databases most attorneys rely on quietly hide the Guam picture. Every number here comes from ClaimTrove data drawn from public DOL and federal sources. What those numbers cannot tell you, on their own, is which carrier insured a specific contractor on a specific date. That answer takes a full investigation.
Does the Defense Base Act apply on Guam if Guam is US soil?
The short answer is yes for most base and public-work contracts. The Defense Base Act extends Longshore Act coverage to work performed outside the continental United States. The statute is specific about what that phrase means. Under 42 U.S.C. 1651(b)(4), the continental United States means the States and the District of Columbia. Guam is neither. It is a US territory sitting several thousand miles west of Hawaii.
Two categories of the coverage statute reach Guam directly. Section 1651(a)(2) covers lands used by the United States for military or naval purposes in any territory or possession outside the continental United States. Section 1651(a)(3) covers any public work in that same territory or possession. Andersen Air Force Base and Naval Base Guam both fit the first category. Construction, base support, and public-work contracts on the island fit the second. Coverage does not turn on the worker's nationality, so US citizens and local hires can both fall within the Act.
There is a maritime wrinkle worth flagging. Guam has navigable US waters, so a harbor or waterfront worker injured over the water may fall under the Longshore Act directly rather than through the DBA extension. Land-based base-support and construction workers generally travel the DBA path. The line between the two turns on the specific job and injury site, which is why the CONUS versus OCONUS coverage question deserves careful analysis on every file.
What do public records show about DBA claims on Guam?
ClaimTrove pulls DBA case counts by nation from published DOL case summaries. Guam appears as its own reporting entity. Across the cumulative 2001 to 2024 period, the records show 157 DBA claims tied to Guam. That is a modest figure next to combat theaters, but it is far from zero.
The mix of claims matters as much as the count. Of those 157 cumulative claims, 80 are logged as no-lost-time filings. More than half of the Guam caseload involves injuries that did not keep the worker off the job for an extended stretch. The records show zero death claims across every Guam reporting period. That injury profile looks nothing like Iraq or Afghanistan.
Year to year, the volume stayed low through the 2010s. Guam logged single digits in most fiscal years from 2009 through 2020, with a high of 10 claims in FY2014. Then the pattern broke. Something changed on the island after 2020, and the claim data captured it.
Why did Guam DBA claims jump after 2021?
The recent numbers tell a clear story. Guam recorded 30 DBA claims in FY2022, 25 in FY2023, and 28 in FY2024. Those three years alone account for 83 claims. That is more than half the entire cumulative total, packed into the most recent window.
The driver is construction. Guam sits in the middle of a major military buildup. The Marine Corps is relocating thousands of personnel from Okinawa to the new Marine Corps Base Camp Blaz. The associated construction has pulled contractors onto the island in large numbers. More workers and more heavy equipment on active jobsites means more injuries, and the DBA claim curve followed.
That Okinawa connection is not incidental. The same relocation that raised Guam's contractor footprint is reshaping the workload at Japanese bases too. Attorneys who track the Pacific posture should read the Guam surge alongside the parallel contractor picture at Okinawa and mainland Japan bases. The two theaters are moving in tandem.
Which bases and contractors drive the Guam footprint?
Two installations anchor the Pacific staging posture on Guam. Andersen Air Force Base on the northern end hosts the 36th Wing and a rotating bomber and tanker presence. Naval Base Guam on the southern end supports submarines and Pacific fleet operations. Both run on contractor labor for construction, logistics, and day-to-day base support.
Base operating support contracts generate a steady share of the claims. Public DOL records show DZSP 21, a base operating support prime at Naval Base Guam, with 14 recorded DBA claims across the cumulative period. That total includes 11 claims in a single recent fiscal year. That one employer illustrates how a long-running support contract concentrates injury exposure at a single site over many years.
The public records name the employer, the claim counts, and the fiscal years. They do not name the insurance carrier behind that contractor, and they do not tell you whether coverage changed when the contract was recompeted. That gap is the hard part of every Guam file. It is where a name in a spreadsheet stops being useful and a real investigation begins.
Why will federal contract databases hide the Guam picture?
Here is a trap that catches careful investigators. Most DBA contract research leans on federal spending databases filtered by overseas place of performance. Guam breaks that filter. Because Guam is a US territory, federal systems often code it as domestic or route it under an outlying-islands label rather than a foreign country code.
In ClaimTrove data, the overseas contract award set that spans 193 countries returns almost nothing for Guam by country code. A single award surfaces at all, and only because a reviewer wrote Guam into the project description. An attorney who searches by the usual foreign-country filter would conclude, wrongly, that no contract activity exists on the island.
The lesson is that Guam demands a different search path. You cannot rely on the foreign place-of-performance shortcut, and you have to reconcile contract data against the DBA claim record, the base assignment, and the employer name. Reading federal spending data correctly is a skill in itself, and Guam is one of the sharpest examples of why.
ClaimTrove reconciles those sources for you. Run a Guam location investigation and the engine pulls the contractors, the DBA claim history, and the OALJ decisions tied to the island into one report. It then traces each contractor toward its likely carrier.
How does Guam compare with other Pacific and territory bases?
Guam is one of several US positions where the territory question controls DBA coverage. The cleanest parallel is Guantanamo Bay, which the coverage statute names by hand as covered ground. Contractors there face the same jurisdictional logic even though the base sits on land the United States does not own outright.
Across the wider Pacific, the peacetime staging bases share Guam's injury profile. Slip-and-fall, equipment, and construction injuries dominate, and death claims stay rare. The steady contractor presence at forward bases produces claims that look far more like Guam than like a combat theater. The record at Korea's largest Army garrison shows the same pattern.
The through-line is that a US flag overhead does not remove DBA coverage. Territory status, base assignment, and contract type decide the question. Guam simply makes that principle unusually visible, because the island reads as domestic while the law treats the work as overseas.
What should you verify before you file a Guam DBA claim?
Start with jurisdiction. Confirm the injury site sits on a covered military installation or public work, and note whether any maritime exposure could pull the claim toward the Longshore Act directly. Pin the injury date, because the carrier on risk can change when a base support contract is recompeted.
Then build the evidence chain. ClaimTrove holds 16 OALJ and BRB decisions that reference Guam, 10 of them classified as DBA, with rulings spanning 2002 through 2022. Those decisions, the contract record, and the employer history are the raw material for identifying the responsible carrier.
Guam looks simple from the outside. A US territory, a familiar flag, a short list of bases. The coverage answer is straightforward once you apply the statute, but the carrier answer never is. ClaimTrove is built to close that gap. Enter the base, the contractor, and the injury date, then pull the underlying employer, carrier, and decision data in one place.