Can You Sue Your Employer Under the Defense Base Act? Exclusive Remedy Explained

Why Do Injured Contractors Ask About Suing Their Employer?

Your client was injured at a forward operating base in Afghanistan. Medical bills are mounting. The employer's third-party administrator is dragging its feet on the claim. Your client wants to know one thing: can they sue?

The short answer is almost always no. The Defense Base Act operates as the exclusive remedy for most workplace injuries sustained by civilian contractors working overseas on U.S. government contracts. This means the DBA replaces the right to file a tort lawsuit against the employer in exchange for a no-fault compensation system.

But the exclusive remedy doctrine is not absolute. Specific factual circumstances can open the door to civil litigation. Understanding where the line falls is critical for DBA practitioners who need to advise clients accurately at intake. The wrong answer, in either direction, costs money and time.

Across the federal system, the exclusive remedy question generates contested litigation at the administrative law judge level, at the Benefits Review Board, and in federal circuit courts. The doctrine touches carrier identification, employer liability, and damages theory. If you handle DBA claims, you will encounter this question repeatedly.

What Is the Exclusive Remedy Doctrine Under the DBA?

The Defense Base Act incorporates the Longshore and Harbor Workers' Compensation Act by reference. Section 5(a) of the LHWCA, codified at 33 U.S.C. section 905(a), provides the exclusive remedy rule. The employer's liability under the Act is "exclusive and in place of all other liability of such employer to the employee."

This language is deliberately broad. It bars negligence claims, strict liability claims, and intentional tort claims in most circumstances. The rationale mirrors domestic workers' compensation: the employer gives up the right to assert defenses like contributory negligence, and the employee gives up the right to sue for full tort damages. Both sides trade something.

For DBA cases, the exclusive remedy provision extends extraterritorially. A contractor injured in Iraq, Afghanistan, Kuwait, or any other overseas location covered by the DBA cannot bring a tort suit against the employer for that injury. The compensation system administered by the Department of Labor's Office of Workers' Compensation Programs is the sole path to recovery against the employer.

This is fundamentally different from what many attorneys encounter in domestic practice. In state workers' compensation, the exclusive remedy doctrine varies by jurisdiction, and some states have carved significant exceptions. The federal system under the LHWCA and DBA is more restrictive. Getting the jurisdictional classification right at the outset shapes every decision that follows, from the claims process itself to the damages theory you pursue.

Does the Exclusive Remedy Bar Apply to Every Employer in the Contracting Chain?

Here is where the doctrine gets complicated. The DBA contracting chain often includes a prime contractor, one or more subcontractors, staffing intermediaries, and joint ventures. The exclusive remedy bar protects the "employer," but identifying which entity qualifies as the employer is frequently contested.

Section 4 of the LHWCA, at 33 U.S.C. section 904, imposes liability on the employer to secure DBA insurance coverage. Section 5(a) then grants that employer immunity from tort suits. The two provisions work together: the obligation to provide coverage and the shield from lawsuits are two sides of the same coin.

For subcontractors, Section 4(a) creates a chain of liability. If a subcontractor fails to secure DBA coverage, the prime contractor becomes liable for compensation benefits. This statutory liability also carries the exclusive remedy shield. A prime contractor who pays compensation benefits under this provision gains tort immunity, even if the prime was not the direct employer.

The complexity multiplies in practice. ClaimTrove's database includes 43,298 prime contract awards and 4,315 subcontract awards from USAspending data. Many of these contracts involve layered subcontracting arrangements where multiple entities could argue they are, or are not, the employer for exclusive remedy purposes. Determining the correct employer in the chain is essential before you can assess whether the exclusive remedy applies or whether a tort claim is viable against a particular entity.

What Are the Recognized Exceptions to the Exclusive Remedy Bar?

Three categories of exceptions to the DBA exclusive remedy have been recognized by courts and administrative tribunals. Each requires specific factual showings that go beyond ordinary workplace negligence.

The Intentional Tort Exception. Section 5(a) of the LHWCA preserves the employee's right to sue when the employer has "intentionally and deliberately" caused the injury. Courts have interpreted this narrowly. Ordinary negligence, gross negligence, and even reckless disregard for safety do not satisfy the standard. The employer must have acted with actual intent to injure. In overseas DBA contexts, this exception is rarely successful, but it surfaces in cases involving egregious safety failures at construction sites in war zones.

The Dual Capacity Doctrine. Under this theory, an employer who occupies a second legal relationship with the employee, such as product manufacturer, property owner, or medical provider, may lose the exclusive remedy shield with respect to that second capacity. If a defense contractor both employs a worker and manufactures the defective equipment that caused the injury, the worker may have a tort claim against the employer in its capacity as manufacturer. Federal courts have recognized this doctrine in limited circumstances under the LHWCA framework.

Third-Party Claims Under Section 33. While not technically an exception to the exclusive remedy against the employer, Section 33 of the LHWCA preserves the employee's right to sue third parties who are not the employer. This is the most frequently used avenue for tort recovery in DBA cases. If a different contractor's negligence caused the injury, or if a vehicle manufacturer's defect contributed to it, the injured worker can pursue a third-party tort claim while simultaneously receiving DBA benefits.

Section 33 also creates a lien mechanism. The DBA carrier has a right to reimbursement from any third-party tort recovery, up to the amount of compensation benefits paid. Managing this lien correctly requires knowing which carrier paid the benefits, a question that sounds simple but often requires tracing through multiple federal compensation programs to answer definitively.

How Do Third-Party Tort Claims Interact with DBA Benefits?

Section 33 of the LHWCA creates a detailed framework for coordinating DBA compensation with third-party tort recoveries. The mechanics matter for practitioners because missteps can forfeit your client's DBA benefits entirely.

When an employee receives DBA compensation and also has a viable tort claim against a third party, the employee must provide written notice to the employer and carrier before settling or proceeding to judgment. The employer and carrier have the right to approve or disapprove the settlement. If the employee settles without the employer's written approval, the employee may forfeit all future DBA compensation benefits.

The offset formula works as follows. From the net third-party recovery, the employer and carrier are entitled to reimbursement for all compensation benefits paid and for their share of legal expenses. Any excess goes to the employee. If the third-party recovery exceeds total compensation liability, the employer's obligation terminates.

This creates a strategic calculation for DBA attorneys. A large third-party settlement may eliminate future DBA benefits. A small settlement may leave DBA benefits intact but fail to maximize the client's total recovery. Evaluating these tradeoffs requires knowing the exact DBA benefits paid, the projected future benefits, and the carrier on the hook for ongoing payments.

The carrier's identity is not always obvious. In DBA cases involving overseas contractors, carriers change over time. The carrier responsible at the date of injury may differ from the carrier providing coverage when the third-party settlement occurs. Temporal carrier shifts are common across the major DBA employers. ClaimTrove's investigation engine searches 18 federal data sources to trace carrier history over time, which is critical when third-party recoveries and DBA liens need to be coordinated across coverage periods.

When Does the Zone of Special Danger Doctrine Expand DBA Coverage Beyond the Workplace?

One doctrine that indirectly affects the exclusive remedy analysis is the zone of special danger. Under this doctrine, injuries sustained off-duty in overseas locations can still fall within the scope of DBA coverage. If the injury is covered by the DBA, the exclusive remedy bar applies. If it is not covered, a tort claim may be the only option.

The zone of special danger doctrine recognizes that overseas contract workers face risks that do not exist in domestic employment. A contractor living on a military base in a hostile territory faces elevated danger 24 hours a day. Injuries from rocket attacks during off-duty hours, motor vehicle accidents during recreational travel in-country, and even some off-base social activities have been held compensable under the DBA because the overseas conditions created the danger.

For the exclusive remedy analysis, the doctrine cuts both ways. If the zone of special danger brings an injury within DBA coverage, the employer gains tort immunity. The injured worker receives compensation benefits but cannot sue for full tort damages. Conversely, if an injury falls outside the zone, no DBA benefits may be available, but a tort claim could theoretically proceed.

This creates a paradox for claimants. Arguing that an injury falls within the zone of special danger secures DBA benefits but locks out tort recovery. Arguing it falls outside the zone preserves tort rights but eliminates the no-fault compensation safety net. Advising the client correctly requires evaluating both paths before committing to a litigation strategy.

How Does the Exclusive Remedy Affect Your Carrier Investigation Strategy?

The exclusive remedy doctrine has direct implications for how you investigate a DBA case. If the employer is shielded by the exclusive remedy, your client's recovery depends entirely on the DBA compensation system. That means identifying the correct carrier is not just helpful. It is the case.

When third-party claims are viable under Section 33, carrier identification still matters. The carrier's lien rights mean you need to know exactly who paid benefits, when coverage started and ended, and whether carrier changes during the claim period create gaps or overlaps. A third-party settlement negotiated without accurate carrier information can leave money on the table or trigger forfeiture of future benefits.

For employers in the DBA contracting chain, the exclusive remedy question often turns on insurance coverage itself. Under Section 4(a), an employer that fails to secure DBA insurance loses the exclusive remedy protection. An uninsured employer can be sued in tort by the injured worker. This creates a powerful incentive structure, and it means that verifying whether an employer actually maintained DBA coverage at the time of injury is a threshold factual question.

ClaimTrove's database tracks 637 authorized DBA carriers, 2,454 employer-carrier mappings confirmed across multiple federal sources, and coverage history spanning fiscal years 2009 through 2024. Carrier changes are common. The same employer may have been covered by one carrier during your client's injury year and a different carrier two years later. Missing the correct temporal match means pursuing the wrong party. Run a carrier investigation on ClaimTrove to trace the full coverage timeline before you commit to a claims strategy.