Your client was permanently and totally disabled in a 2014 IED blast outside Kandahar. The compensation order set his weekly rate years ago, and the carrier has paid the same dollar figure every two weeks since. The client calls to ask why his check has not moved while rent, groceries, and medical copays climb. You pull the file and realize nobody ever raised LHWCA Section 10(f). That oversight could be costing him hundreds of dollars a month, and the back-due amount may run into five figures.
This is the quiet failure point in long-running Defense Base Act claims. The headline fight is usually average weekly wage, causation, or the carrier's identity. Section 10 gets treated as a formula you run once and forget. It is not. Section 10 governs how the compensation rate is built at the start and, through subsection (f), how that rate grows over time for permanently disabled workers and certain survivors.
Across the 5,022 OALJ decisions and 4,983 case summary records in ClaimTrove, disputes over the initial wage figure dominate the published record. The cost-of-living adjustment piece shows up far less often, which tells you it is under-litigated, not unimportant. Attorneys who understand Section 10 in full recover more for clients on permanent awards and catch carrier underpayments that would otherwise compound silently for a decade.
What does LHWCA Section 10 actually cover?
The Defense Base Act borrows its benefit machinery from the Longshore and Harbor Workers' Compensation Act. When DBA practitioners say "Section 10," they mean 33 U.S.C. 910, incorporated into the DBA at 42 U.S.C. 1651. Section 10 does two distinct jobs, and conflating them is where money gets left on the table.
The first job is fixing the average weekly wage at the moment of injury. Section 10 lays out three methods, labeled (a), (b), and (c). Method (a) applies to workers who held the job substantially the whole year before injury. Method (b) covers comparable workers when the claimant's own history is too thin. Method (c) is the catch-all for everyone whose earnings do not fit (a) or (b), which describes most overseas contractors on short rotations.
The second job lives in subsection (f). It directs annual cost-of-living adjustments for workers receiving permanent total disability compensation and for death benefit recipients. This is the supplementary benefit that compounds, and it is the part most often missed in DBA files.
Why the (a), (b), (c) distinction drives the COLA later
The wage method you establish at the front end sets the base on which every future Section 10(f) increase is calculated. A wrong or low base does not just shrink the first check. It shrinks every annual adjustment that follows, because each year's increase is a percentage applied to the running rate. Getting the wage method right is therefore the foundation for the supplementary benefit, not a separate fight. We break down the underlying wage mechanics in our analysis of average weekly wage calculation for overseas contractors, which is essential reading before you touch the COLA piece.
How do Section 10(f) cost-of-living adjustments work?
Section 10(f) ties annual increases to the percentage change in the national average weekly wage, the same NAWW figure the Department of Labor publishes each year. The adjustment applies on October 1, the start of the federal fiscal year. It is capped: the statutory ceiling on the annual increase is 5 percent, even when the NAWW jumps higher.
Here is the part that surprises attorneys new to permanent claims. The 10(f) adjustment is not automatic in practice, even though it is mandatory in law. Carriers are supposed to apply it. Many do for the workers who are actively paid through a well-run claims shop. Others let the rate sit flat, especially on older files transferred between third-party administrators where the original compensation order is buried.
The mechanics matter for back-pay math. If a permanently disabled client has gone five years without a single adjustment, you are not asking for one increase. You are reconstructing five compounding steps, each layered on the last, then summing the shortfall across every payment period. The arithmetic is unforgiving and easy to get wrong by hand.
Who qualifies for the Section 10(f) supplement?
Two groups get the annual bump. First, workers on permanent total disability. Second, eligible survivors receiving death benefits under Section 9. Notably, permanent partial disability awards do not get the 10(f) treatment, which is one reason the scheduled-versus-unscheduled classification carries such long-term weight. We explore that lifetime-value gap in our piece on scheduled versus unscheduled awards and body-part specificity.
The permanent total threshold is exactly why carriers fight so hard to keep a claim classified as temporary or partial. Permanent total status triggers lifetime benefits and the compounding COLA, which is the entire defense incentive behind contesting that classification.
Why is the Section 10(f) supplement so often missed?
The supplement gets missed because nothing in the system actively flags it. A compensation order states a dollar figure. The carrier's payment system pays that figure. Unless someone with the statute in front of them audits the rate each fiscal year, the flat number persists. There is no automatic alert when October 1 passes and the rate fails to move.
Three structural problems make this worse on DBA files specifically.
- Carrier and administrator turnover. DBA coverage shifts between carriers and third-party administrators frequently. When a file moves, the institutional memory of the original award and its adjustment history often does not move with it. The new administrator pays what the screen shows.
- Geographic distance. Many permanently disabled DBA claimants are foreign nationals or repatriated workers living far from any U.S. attorney. Nobody is auditing their checks against the published NAWW each year.
- Rate base confusion. If the original award was itself disputed or modified, figuring out which base the 10(f) increases attach to requires reading the full procedural history, not just the final order.
The carrier-identity layer compounds all of this. Before you can even ask a carrier to fix an unadjusted rate, you have to know which entity currently holds the obligation, which is rarely the original carrier on a decade-old claim. That identification problem is the core of what ClaimTrove was built to solve, and it sits upstream of any Section 10 recovery.
How do you audit a permanent DBA award for missed COLA?
The audit is methodical. You are comparing what the client actually received against what Section 10(f) required, year by year, from the date permanent total status attached.
Start by fixing three anchors. The date permanent total disability began. The compensation rate set by the order on that date. And the published national average weekly wage figures for each fiscal year since. The DOL publishes the NAWW history, and we track the maximum-rate progression in our reference on the LHWCA national average weekly wage and maximum rate history.
Then reconstruct the rate ladder. For each October 1, apply the lesser of the NAWW percentage change or the 5 percent cap to the then-current rate. Carry the result forward as the new base for the following year. Each step compounds on the last, so the gap between the correct rate and the flat rate the carrier paid widens every year.
Finally, total the shortfall. For each payment period, subtract what the carrier paid from what the ladder says they owed, then sum across the entire span. On a claim that has gone unadjusted for several years, the cumulative figure is frequently large enough to change how the client thinks about the entire case.
Where the dispute usually lands
Carriers rarely contest that 10(f) exists. They contest the base, the start date of permanent total status, or whether earlier informal adjustments already captured the increases. These are evidentiary fights, and they often route through the same dispute channels as any other DBA disagreement. If the carrier digs in, you may end up before an administrative law judge, the same forum that decides wage-method disputes. Our guide to the OALJ carrier dispute resolution process walks through what that path looks like.
What does the case record tell us about Section 10 litigation?
The published OALJ and Benefits Review Board record skews heavily toward the front-end wage question. In the body of DBA decisions ClaimTrove indexes, fights over which method applies, what comparable earnings look like, and how to value overseas pay packages with hazard differentials are common. Pure Section 10(f) adjustment disputes are comparatively rare in the published decisions.
Read that scarcity correctly. A low volume of litigated 10(f) cases does not mean the adjustments are being paid. It more likely means the failures go uncaught because the claimants are not represented at the moment the adjustment should have triggered. Unlitigated is not the same as uncontested. It often means undiscovered.
This is why the supplement is best understood as an audit opportunity rather than a litigation specialty. The money is recovered by attorneys who proactively check the rate ladder on every permanent file they inherit, not by attorneys waiting for a 10(f) issue to surface on its own. The same diligence applies to the broader benefit structure, which we map across compensation types in our overview of LHWCA benefits and compensation calculation methods.
Run the carrier identification before you run the math
Every Section 10(f) recovery has a precondition: knowing exactly which carrier or administrator is on the hook today. On a permanent claim that began a decade ago, that is almost never the carrier named in the original file. Coverage shifts, administrators change hands, and the obligation can be hard to trace through the paper trail alone.
ClaimTrove resolves that question fast. We cross-reference federal contracting records, FOIA database results, and authorized-carrier filings to show which carrier was responsible for a given employer at a given time, including how that responsibility shifted across the life of a long claim. That is the foundation you need before you can credibly demand a corrected rate and back pay.
Start an investigation in ClaimTrove, pin down the responsible carrier across your client's full claim timeline, and then run the Section 10(f) audit with confidence that your demand is going to the right party. Stop letting compounding underpayments hide inside flat compensation checks.