You take an intake from a former overseas security contractor injured at a remote forward operating base in 2013. The work history checks out. The injury is documented. You run the employer name and find the prime contract, the task order, even the project location. Then you go looking for the carrier and hit a wall. No coverage record. No policy number. No third-party administrator. Nothing.
Most attorneys assume this means they searched wrong. Sometimes they are right. But sometimes the answer is the one nobody wants to confront: the employer carried no Defense Base Act insurance at all. When that happens, your case does not get easier or harder. It gets different. Your target shifts from an insurance carrier to the employer itself, and behind the employer, the federal Special Fund.
This is one of the most misunderstood corners of DBA practice. The uninsured DBA employer Special Fund Section 18 no carrier scenario sends attorneys chasing a policy that never existed, while the statutory remedy sits unused. The Longshore and Harbor Workers' Compensation Act, which the DBA incorporates wholesale, built specific machinery for exactly this gap. Direct employer liability. Default judgment procedures. And in defined circumstances, payment from the Special Fund administered by the Department of Labor.
The hard part is not the law. The hard part is proving the negative. You cannot simply assert that an employer was uninsured. You have to document the absence of coverage on the specific date of injury, rule out every layer where a carrier could be hiding, and then pursue the correct statutory party. This guide walks the entire path, from confirming the coverage gap to choosing your target.
What does it mean when a DBA employer was uninsured?
The Defense Base Act requires every covered employer to secure insurance for its overseas workforce, or to obtain formal authorization to self-insure. That obligation comes straight from Section 4 of the Longshore Act, applied to DBA work through 42 U.S.C. 1651. An employer that ignores it is not relieved of liability. It is exposed to far worse.
An uninsured employer is not the same thing as an employer you cannot find a carrier for. Those are two distinct situations, and conflating them is the most common error we see. A missing carrier record can mean the policy was written under a parent company name, placed through a third-party administrator that obscures the true insurer, or filed under an employer alias your search never matched.
True non-coverage means no policy existed on the date the injury occurred. That distinction matters because the remedies diverge sharply. If a carrier existed but is merely hidden, your job is identification. If no carrier existed, your job is to invoke direct employer liability and, where applicable, the Special Fund.
Coverage also has a temporal dimension that traps the unwary. An employer can be insured in 2012, uninsured for a lapse window in 2013, and insured again in 2014 under a different carrier entirely. The only date that matters is the date of injury. We have written before about why DBA carriers change over time, and the same temporal logic governs whether coverage existed at all on any given day.
So before you ever utter the word "uninsured" in a filing, you need to establish three things. First, the correct legal name of the employer on the injury date. Second, the absence of any policy across every layer where one could exist. Third, that the injury falls within DBA jurisdiction in the first place. Skip any of these and you risk arguing non-coverage against an insurer who will appear the moment you file.
How does direct employer liability work under the Longshore Act?
When a DBA employer fails to secure insurance, the Longshore Act strips away the protections that normally shield it. This is the consequence most uninsured employers never anticipated. The statute is built to make non-coverage a catastrophic choice, not a cost-saving one.
The first hammer is Section 5. An employer that fails to secure compensation loses the exclusive-remedy bar. The injured worker, or the survivors in a death case, can elect to sue the employer at law for damages. In that suit, the employer is barred from raising the classic common-law defenses: it cannot claim the worker assumed the risk, cannot blame a fellow servant, and cannot assert contributory negligence. The worker gets a tort claim with the defenses gutted.
The second hammer is direct liability for compensation itself. The uninsured employer is personally responsible for the full benefit stream that a carrier would otherwise have paid. Medical costs, indemnity, the works. There is no insurer to negotiate with because the employer became its own insurer by default, whether it meant to or not.
The third hammer is personal. Under Section 38 of the Longshore Act, failure to secure payment of compensation is a misdemeanor, and the president, secretary, and treasurer of a corporate employer can be held individually liable alongside the company. That provision exists to defeat the shell-company maneuver, where an undercapitalized entity is left holding the obligation while its principals walk away.
For your investigation, this means the universe of viable targets expands the moment non-coverage is confirmed. You are no longer limited to a carrier. You are looking at the corporate employer, its officers, and any parent that exercised control. The challenge is that uninsured employers are frequently the smallest and least solvent players, which is precisely why they skipped coverage. That is where the Special Fund enters.
When does the Special Fund step in for an uninsured DBA employer?
The Special Fund is established under Section 44 of the Longshore Act and administered by the Department of Labor. It is financed by assessments on carriers and self-insured employers, plus certain penalty payments. Attorneys often hear "Section 18" and assume it is the fund's authority. Section 18 is actually the enforcement and default-order mechanism; Section 44 creates the fund itself, and Section 18(b) authorizes payment from it in specific default situations.
Here is the critical limitation. The Special Fund is not a general guarantor for every uninsured employer. It is a backstop of last resort, available only after you have exhausted the statutory steps against the employer and obtained the proper default order. The fund pays where an employer defaults on a compensation order and the deputy commissioner determines the employer is insolvent or otherwise unable to pay.
The path runs through Section 18(a) first. Once compensation is due and payable under an award and the employer fails to pay for 30 days, you can apply to the deputy commissioner for a supplementary order declaring the amount of the default. That supplementary order is enforceable in federal district court like a judgment. Section 18(b) then authorizes the Secretary, in the Secretary's discretion, to make payment from the Special Fund where judgment cannot be satisfied by reason of the employer's insolvency or other circumstances precluding payment.
The fund's exposure is also constrained. Under Section 44, neither the United States nor the Secretary is liable in respect of fund payments in an amount greater than the money or property deposited in or belonging to the fund, and the Secretary retains discretion to consider current fund commitments before approving payments. This means catastrophic and death claims may not receive full make-whole recovery if the fund's resources are strained. You cannot promise a client full make-whole recovery from the fund. You can promise a structured path that ends in some recovery when the employer is judgment-proof.
The fund is the same mechanism that absorbs certain obligations when a carrier collapses rather than an employer. The mechanics differ, but the safety-net logic is identical, and we cover the carrier side in detail in our breakdown of what happens to open claims when a carrier becomes insolvent. Whether the failure is at the carrier layer or the employer layer, the Special Fund is the statutory floor.
How do you actually prove a DBA employer was uninsured?
Proving the absence of coverage is harder than proving its presence. You are documenting a negative, and a default order built on a sloppy negative will collapse the moment an insurer surfaces. The standard we apply is simple: rule out every layer where a policy could exist before you conclude none did.
Start with the direct carrier layer. Public DOL records and FOIA database results can show coverage filings tied to an employer. But absence from one source is not proof of non-coverage. Carriers and policies get recorded inconsistently, and a gap in one dataset may simply mean the record lives elsewhere. You need corroboration across sources before the gap means anything.
Next, rule out the parent and affiliate layer. Many overseas contractors operate through a web of related entities, and a policy written for the parent may cover a subsidiary that appears uninsured on its own name. This is where alias resolution across employer name variations becomes decisive. The same operating company can appear under a dozen legal names, and missing one of them produces a false non-coverage finding.
Then rule out the administrator layer. A third-party administrator handling claims for an employer is a strong signal that a real carrier sits behind it, even if the carrier's name never appears in your first search. If a TPA was processing claims, an insurer almost certainly existed, and your "uninsured" theory is probably wrong.
Finally, treat any inconsistency as a stop-and-dig signal. A genuine coverage gap usually leaves a fingerprint: a policy that lapsed and was reinstated, an employer that vanished from filings for a defined window, a contract that named a carrier the records never confirm. Those same fingerprints appear on our list of DBA investigation red flags, and they are exactly the patterns that distinguish a real coverage gap from a search you simply did not finish.
This is precisely the kind of cross-source confirmation that breaks down when done by hand across disconnected DOL pages and spreadsheets. ClaimTrove runs the employer through prime and subcontract award data, coverage filings, case summaries, and decision text in one pass, so a coverage gap shows up as a documented absence across every layer rather than a hole in one tab. Run a sample investigation to see how the layers resolve.
What should attorneys do once non-coverage is confirmed?
Confirming non-coverage changes your entire litigation posture, and your next moves should follow a deliberate sequence. The goal is to preserve every remedy the statute gives you while building the record that a default order will require.
First, decide between the compensation track and the tort election. A worker facing an uninsured employer can pursue Longshore benefits through OWCP or elect to sue at law under Section 5 with the common-law defenses stripped. The right choice depends on solvency, damages, and venue. A solvent uninsured employer may be a better tort target; a judgment-proof one points you toward the compensation track and the Special Fund.
Second, build the corporate-officer record early. Because Section 38 reaches the officers personally, identifying the president, secretary, and treasurer on the injury date can convert a worthless corporate defendant into a collectible one. Do this while the trail is warm, before the entity dissolves.
Third, drive toward a final compensation order. The Special Fund path under Section 18 does not open until you have a final order, a 30-day default, and a supplementary order declaring it. Every step you take should advance that sequence, because nothing reaches the fund without it. If the matter is contested, it will likely run through the OWCP and OALJ machinery, and our guide to the DBA claims process step by step maps that full route.
Fourth, document everything contemporaneously. A default order built on a clean, dated, multi-source coverage gap survives challenge. One built on a single missing record does not. The strength of your eventual fund application is set the day you confirm non-coverage, not the day you file.
The single decision that drives all four steps is whether coverage truly existed on the injury date. Get that wrong and you either chase a phantom carrier or wrongly accuse a solvent insurer of non-coverage. ClaimTrove was built to settle that one question fast, by confirming whether an employer was insured on a specific date across every data layer at once. Start an investigation and find out which target your case actually has.