Your client was hurt by a defective generator on a forward operating base in Iraq. The manufacturer offers a $90,000 settlement to make the third-party product liability case disappear. Your client signs, takes the check, and pays off the credit cards. Three months later, the DBA carrier files a motion claiming the entire DBA claim is now forfeited. Not reduced. Not offset. Forfeited. Permanently.
This is the Section 33(g) trap, and it is one of the few mistakes in Defense Base Act practice that cannot be undone. Section 33(g) of the Longshore and Harbor Workers' Compensation Act, which the DBA incorporates by reference, requires written carrier consent before a claimant settles a third-party case for less than the compensation owed. Settle without that consent and the worker can lose every dollar of future DBA benefits.
The cruelty of the provision is that it punishes the act most injured workers want to take. A wounded contractor in financial distress sees a settlement offer and grabs it. No one tells them a one-paragraph consent letter stands between that check and total forfeiture of their workers' compensation claim. The DBA Section 33(g) third-party settlement carrier consent forfeiture rule has ended more claims than most attorneys realize, and the decisions that interpret it are scattered across decades of Benefits Review Board and federal appellate rulings.
This guide walks through how the consent requirement actually works, the precise mechanics of lien and credit recovery, the small set of situations where forfeiture does not apply, and how to research which carrier litigated a 33(g) defense before you draft your settlement strategy.
What does Section 33(g) actually require?
Section 33(g) lives inside 33 U.S.C. 933, the statute governing what happens when a third party, someone other than the employer, causes the injury. In DBA cases that third party is often an equipment manufacturer, a host-nation vehicle operator, a base contractor your client did not work for, or a security subcontractor.
The statute creates two distinct duties. First, the consent duty: if the claimant settles a third-party claim for an amount less than the DBA compensation the carrier would owe, the claimant must obtain the carrier's written approval before settling. Second, the notice duty: the claimant must notify the carrier of any third-party settlement regardless of amount.
Miss the consent requirement on a below-compensation settlement and the consequence is forfeiture of all future DBA benefits, including medical. The forfeiture is not discretionary. Once a court finds the elements met, the judge has no equitable power to soften it. The Supreme Court confirmed this harsh reading in Estate of Cowart, holding that the plain language controls even when the result feels punitive.
Three elements drive the analysis. The settlement must be with a third party, not the employer or its carrier. The settlement amount must be less than the total DBA compensation owed. And the claimant must have failed to get prior written consent. If all three are present, the door closes.
Notice the second element carefully. If the third-party settlement exceeds the total DBA compensation owed, consent is not required because there is nothing left for the carrier to pay. This is why valuation matters so much. You cannot know whether you need consent until you know what the claim is worth, and DBA claim valuation involves variables that state-side comp attorneys rarely confront. Our breakdown of the six valuation factors state workers comp attorneys never encounter explains why a wrong number here is so dangerous.
Why is the consent requirement such a trap for claimant attorneys?
The 33(g) trap punishes timing and silence more than bad faith. Most forfeitures do not involve attorneys hiding settlements. They involve attorneys who handled the third-party case and the DBA case as separate matters, or who never knew a DBA claim existed at the time of the third-party deal.
Consider the common fact pattern. A contractor is injured by a defective product overseas. A personal injury firm takes the product liability case. A separate firm, or no firm, handles the DBA claim. The PI firm settles the product case for a reasonable amount without ever asking whether DBA compensation exceeds the settlement. No consent is sought because the PI lawyer does not practice Longshore law and never saw the issue.
That coordination gap is where claims die. The PI attorney is not thinking about a federal workers' comp statute. The DBA attorney may not even know the third-party case is moving. By the time anyone connects the two, the settlement is signed and the consent window has closed.
A second trap is the assumption that a large settlement is automatically safe. It is only safe if it exceeds total DBA compensation owed. A $150,000 product settlement looks generous until you realize a permanent total disability claim for a 40-year-old contractor can carry a present value well into seven figures. When you understand why permanent total disability triggers the most aggressive carrier defense, you see why carriers eagerly raise 33(g) when a below-value settlement slips through.
A third trap is the credit doctrine masquerading as a non-issue. Some attorneys assume the worst case is just an offset, that the carrier will simply credit the third-party money against what it owes. That is the result when consent is obtained or not required. Without consent on a below-compensation deal, the result is not a credit, it is forfeiture. The distinction between a credit and a forfeiture is the difference between losing some money and losing the entire claim.
How do liens and credits work in a third-party DBA case?
When the third-party recovery is handled correctly, Section 33 creates an orderly distribution. Understanding it clarifies why the carrier cares so much about consent and notice.
The carrier holds a lien on the third-party recovery for compensation and medical benefits it has already paid. After the claimant's attorney fees and litigation costs come off the top, the carrier is reimbursed for its prior payments out of the net recovery. This prevents a double recovery, the worker collecting both DBA benefits and tort damages for the same harm.
What remains after the lien is satisfied becomes the carrier's future credit. The carrier does not have to resume paying DBA benefits until the claimant's net third-party recovery is exhausted. If a worker nets $200,000 after fees and lien, the carrier may suspend ongoing payments until benefits that would otherwise accrue equal that $200,000.
This credit structure is why consent matters even when a settlement is reasonable. The carrier wants visibility and control because the deal directly shapes its future exposure. A low settlement with consent simply reduces the credit; the claimant keeps the DBA claim alive. The same low settlement without consent destroys the claim entirely.
The math also explains the carrier's incentive to litigate. If a carrier can prove a 33(g) forfeiture, it eliminates all future liability in one motion, often worth far more than any lien. That asymmetry, modest lien versus total forfeiture, is exactly why responsible carriers pursue these defenses so hard. The same aggressive posture shows up across benefit categories whenever a carrier sees a chance to cap its exposure in a single ruling.
One practical note on net versus gross. The credit and lien calculations turn on net recovery after attorney fees and costs, not the gross settlement number. Getting the accounting right protects both the fee and the client's remaining benefits. Sloppy math here invites a carrier challenge even when consent was properly handled.
When does Section 33(g) forfeiture NOT apply?
The forfeiture rule is harsh, but it is not unlimited. A handful of escape routes exist, and knowing them can save a claim that looks lost.
- The settlement exceeds total compensation owed. If the third-party recovery is greater than the full value of the DBA claim, consent was never required. There is nothing for the carrier to pay, so the consent precondition never triggers.
- Consent was actually obtained. Written carrier approval before settlement defeats forfeiture entirely. The consent does not need to be elaborate; it needs to be in writing and before the settlement is executed.
- No third party at all. A settlement with the employer or its own carrier is not a third-party settlement. Section 33(g) governs recoveries from someone other than the employer.
- The claim was not yet a claim. Courts have wrestled with whether 33(g) applies before a formal DBA claim exists. The answer has shifted, and circuit splits have appeared on the timing of when the duty attaches.
Courts and the Benefits Review Board have disagreed about when the consent duty crystallizes, producing conflicting rulings on whether the duty attaches before a formal DBA claim is filed or only once compensation liability has been established. That uncertainty is precisely why you should never treat 33(g) as settled in your jurisdiction without checking the controlling decisions. The administrative law judges who decide these motions leave a detailed record of their reasoning, and reading that record is the fastest way to predict your outcome. Our guide to what attorneys can learn from administrative law judge decisions shows how to mine those rulings.
There is also the interaction with exclusive remedy. Some attorneys confuse a third-party tort claim with a direct suit against the employer, which the DBA generally bars. The two are different animals, and conflating them creates strategic errors. If you are unsure whether a defendant counts as a third party or a barred employer target, our explanation of the exclusive remedy bar under the Defense Base Act draws the line.
How should you structure a third-party settlement to protect the DBA claim?
Prevention beats litigation. Once the check clears without consent, your options shrink to arguing the escape routes above. A disciplined process keeps you out of that fight.
Start every overseas injury intake by asking whether any non-employer party may bear fault. Defective equipment, host-nation drivers, base operators, and security subcontractors all create third-party exposure. Flag these at intake so the third-party and DBA tracks never drift apart.
Before any third-party settlement, value the DBA claim. You cannot judge whether the settlement falls below compensation owed without a defensible number. Build that valuation on present value of future indemnity plus projected lifetime medical, the categories carriers scrutinize hardest.
If the settlement may fall below DBA value, obtain written consent before signing anything. Send the carrier the proposed settlement terms and request approval in writing. Document the request and the response. A short paper trail defeats most forfeiture motions.
Coordinate the two firms. If a separate personal injury firm handles the tort case, put the 33(g) consent obligation in writing to that firm and confirm they understand the forfeiture risk. Many catastrophic 33(g) losses trace to a handoff where neither firm owned the consent step.
Finally, identify the carrier early. The consent letter has to go to the right entity, and DBA carriers shift across contract years and task orders. Sending a consent request to last year's carrier, or to a third-party administrator that no longer handles the file, is functionally the same as sending nothing. Knowing who actually carries the risk at the moment of settlement is not a clerical detail; it is the difference between valid consent and an empty letter in the wrong inbox.
ClaimTrove maps the carrier, prime contractor, and subcontractor behind an overseas injury across more than one million federal records, including 5,022 indexed OALJ decisions and thousands of contract awards. When you need to know who must sign the consent letter and how that carrier has litigated 33(g) before, run the investigation before you draft the settlement, not after.
How do you research a carrier's 33(g) litigation history?
Carriers are not interchangeable on Section 33(g). Some raise forfeiture aggressively in every below-value settlement. Others negotiate credits and rarely push for total forfeiture. Knowing your carrier's pattern changes how you approach consent and settlement timing.
That history lives in the decisional record. Across 5,022 indexed OALJ decisions and the broader Benefits Review Board case law, you can trace which carriers litigated 33(g), how administrative law judges ruled, and which arguments succeeded. The patterns are not obvious from any single decision; they emerge only when you read across many.
The hard part is connecting the carrier name in a decision to the employer and contract in your case. Carrier names change, third-party administrators muddy the picture, and the same insurer appears under multiple corporate identities. Our work on how DBA carrier disputes get resolved through the OALJ process shows why this resolution step is where most independent research stalls.
ClaimTrove indexes those decisions and links them to the carriers and employers behind each contract, so you can search Section 33(g) forfeiture decisions and identify the responsible carrier in one place. Start an investigation, pull the carrier's 33(g) history, and walk into your settlement negotiation knowing exactly who you are dealing with and how they have litigated this defense before.