Is L3Harris Technologies self-insured for Defense Base Act claims?

Yes. L3Harris holds DOL-approved self-insurer status and administers DBA claims internally rather than through a commercial carrier. The company posts a security deposit with the Department of Labor and pays indemnity and medical benefits directly from corporate funds. There is no external carrier to identify for claims administered under the post-2019 merger program.

What was L3Harris called before the 2019 merger?

L3Harris Technologies was formed on June 29, 2019 from the merger of L3 Technologies and Harris Corporation. L3 Technologies was previously known as L-3 Communications Holdings, and earlier L-3 Communications, with roots going back to a 1997 spinoff from Lockheed Martin. Harris Corporation operated under that name for more than a century before the merger. Employment records may show any of these names.

Where do I send an LS-203 for a self-insured employer like L3Harris?

The LS-203 claim form goes to the DOL district office with jurisdiction over the claim, but claim correspondence and controverted notices go to the employer's risk management department rather than to a commercial carrier intake address. If L3Harris uses a third-party administrator for day-to-day claim handling, you need to confirm whether service on the TPA satisfies statutory notice requirements.

How do I verify an employer's self-insured status under the DBA?

The DOL Division of Longshore and Harbor Workers' Compensation maintains records of authorized self-insurers, including the effective period of the authorization and the security deposit posted. You can also infer self-insured status when federal contract data shows a large overseas footprint for an employer with no corresponding commercial DBA policy activity. ClaimTrove flags self-insured employers in the first screen of the investigation report.

Does self-insured status change the statute of limitations or notice deadlines?

No. The one-year statute of limitations for filing a DBA claim and the 30-day employee notice requirement apply identically to self-insured employers and commercially insured employers. What changes is the address for notices and the identity of the respondent in any formal proceeding. The procedural deadlines do not move.

Can a self-insured employer use a third-party administrator?

Yes, and many large self-insured employers do. A TPA handles day-to-day claim intake, adjustment, and payment, but the employer retains the underwriting risk and remains the legally responsible party. The TPA services agreement defines the scope of delegated authority, and that agreement is typically discoverable in claim proceedings.

Are reserves discoverable in a self-insured DBA case?

Reserve information is often more accessible in self-insured cases than in commercial carrier cases because the reserves are internal corporate records rather than carrier work product subject to insurer privilege objections. Practice varies by jurisdiction and by the specific employer's litigation posture, but attorneys pursuing self-insured claims should request reserve history as part of standard discovery.

What other major defense contractors are self-insured for DBA?

ClaimTrove tracks a short list that includes L3Harris, Huntington Ingalls Industries, CACI International, and ManTech International, among others. The exact composition changes as DOL authorizations are granted, renewed, or revoked. Self-insured employers concentrate in the top tier of defense contractors because the financial requirements for authorization exclude smaller firms.

If L3Harris denies my claim, who do I litigate against?

The employer itself is the named respondent in formal DBA proceedings involving a self-insured employer. There is no carrier co-respondent. Depositions, subpoenas, and settlement authority all flow through the employer's legal and risk management functions rather than through an external insurance carrier's defense counsel.

Does self-insured status affect how the claim gets paid if the employer goes bankrupt?

This is one of the key differences between self-insured and commercially insured DBA claims. A commercial carrier's obligation survives the employer's bankruptcy. A self-insured employer's security deposit with the DOL provides a backstop, but the deposit is calibrated to expected exposure and may not cover catastrophic claim volume in a worst-case scenario. This is why the DOL monitors self-insurer financial condition closely and can revoke authorization when warranted.

L3Harris DBA Self-Insured Status: Why There's No Carrier to Find

You have a claimant who worked overseas on an ISR mission, got injured in 2022, and now needs DBA benefits. The employer listed on the paystub is L3Harris Technologies. You run the standard playbook. You search WHCA databases. You pull OWCP coverage records. You check every carrier directory you know. And you find nothing. No policy number. No Gallagher Bassett intake file. No ESIS adjuster assigned. The reason is simple and most attorneys miss it: L3Harris does not buy DBA insurance from anyone. It is its own carrier.

Self-insured employers represent one of the most disruptive variables in a DBA investigation. The standard workflow assumes a commercial insurance carrier sits behind every employer, issuing policies, receiving LS-202 notices, and cutting benefit checks. That assumption fails for L3Harris, and it fails for a growing list of large defense contractors that have received DOL approval to hold the risk internally. When an attorney misses the self-insured flag, the claim stalls. Notices go to the wrong place. Adjusters who do not exist get called. Deadlines get missed.

This article explains what L3Harris's self-insured status means in practice, why the company's merger history makes alias resolution difficult, and how your records requests must change the moment you confirm an employer administers its own DBA program. By the end, you will know exactly where to direct your LS-203, which DOL office approved the self-insurer authorization, and what to do when the risk management department stops returning calls.

What does it mean for L3Harris to be self-insured under the DBA?

The Defense Base Act extends Longshore and Harbor Workers' Compensation Act coverage to civilian employees of US government contractors working overseas. Most contractors satisfy their DBA obligation by purchasing a commercial policy from one of the seven or eight major carriers that write this line of business. L3Harris does not. Instead, the company operates under DOL-approved self-insurer status, which allows it to retain the underwriting risk, administer claims through an internal team, and pay indemnity and medical benefits directly from corporate funds.

Self-insurance in the DBA context is not informal. It requires an application to the Department of Labor's Office of Workers' Compensation Programs, annual financial disclosures, and a security deposit in the form of a surety bond, letter of credit, or negotiable securities. The deposit amount is calibrated to the employer's expected claim exposure. A contractor with thousands of overseas employees posts significantly more than one with a handful. Approval is renewed periodically, and the DOL can revoke the authorization if the employer's financial condition deteriorates or if claims handling falls below acceptable standards.

For a practicing attorney, the operational consequences are immediate. There is no third-party adjuster who will call you back within 48 hours because of contractual service level agreements. There is no commercial carrier with a compliance department monitoring LS-208 payment timeliness. Everything flows through the employer's own risk management function. That changes who you serve, who you depose, and who authorizes settlement. If you are still learning the basics of who qualifies for benefits under this statute, our overview of what the Defense Base Act covers and who qualifies is worth a quick read before you go further.

Why does the L3Harris merger history complicate alias resolution?

L3Harris Technologies is a relatively young corporate entity. It was formed on June 29, 2019 through the merger of L3 Technologies and Harris Corporation. L3 Technologies itself was a rebrand of L-3 Communications Holdings, which had operated under that name since the late 1990s after spinning off from Lockheed Martin's former Loral business units. Harris Corporation traces back more than a century as a communications and electronics manufacturer. The combined entity now sits among the top defense contractors by revenue and employs tens of thousands of personnel, many of them deployed to overseas contract sites.

This matters for DBA investigation because the same injured worker's employment record might legitimately show any of the following employer names across a multi-year tenure: L-3 Communications, L-3 Services, L3 Technologies, Harris Corporation, Harris Communications, L3Harris Technologies, or one of several dozen subsidiary and division names. Each predecessor had its own DBA arrangement. Some Harris Corporation divisions historically purchased commercial DBA coverage. L-3 Communications operated with a mix of commercial and self-insured arrangements at different times. The post-merger L3Harris consolidated under a unified self-insured program, but claims with dates of injury before 2019 may still be administered under a legacy structure.

This is exactly the kind of situation where defense contractor consolidation reshapes DBA coverage in ways that are invisible from the outside. ClaimTrove's alias resolution layer maps predecessor names, merger dates, and self-insured effective periods so that a search for any legacy entity surfaces the current administrator. Without that mapping, an attorney working from a 2017 paystub for L-3 Services can easily conclude the employer is defunct when in fact the liability rolled forward into L3Harris.

How do you know an employer is self-insured before you waste weeks searching?

The standard carrier identification workflow assumes an external carrier exists. When it does not, every step in the workflow returns a null result, and the investigator often misreads those nulls as incomplete data rather than as a positive signal that the employer is self-insured. That misread is the single most common reason self-insured claims get mishandled in the first 30 days.

There are a handful of reliable indicators. First, the DOL publishes a list of authorized self-insured employers under the LHWCA and DBA, though the list is not always current and does not capture effective date changes cleanly. Second, federal contract award data from USAspending shows prime contracts valued in the billions for a parent entity with no corresponding commercial DBA policy traffic across multiple years. When a top-tier contractor has heavy overseas deployment but produces zero commercial carrier hits in federal records, self-insurance is the most likely explanation. Third, the Longshore case docket itself tells you. In OALJ decisions involving self-insured employers, the employer appears as the named respondent without a carrier co-respondent.

The broader framework for reading these signals lives in our breakdown of red flags to watch for during DBA investigations, which covers self-insured detection alongside six other patterns that routinely derail carrier identification. ClaimTrove flags self-insured employers at the top of the investigation report so that you never spend time chasing a carrier that does not exist. The product surfaces this flag in the first screen of output, along with the risk management contact pathway and the relevant DOL district office.

What does the investigation workflow look like for a self-insured employer?

When you confirm self-insured status, the standard five-step carrier workflow compresses into something different. You are no longer trying to match an employer to a carrier. You are trying to identify the specific internal risk management group, the claims administrator (which may be a third-party administrator retained by L3Harris even though L3Harris holds the risk), and the correct address for statutory notices.

Notices change first. The LS-202 employer's first report of injury still gets filed with the DOL district office that has jurisdiction, but the LS-203 claim form and any controverted notice traffic flows to the employer's risk management department rather than to a commercial carrier's claims intake address. If L3Harris uses a TPA to handle day-to-day claim administration, you need to identify that TPA and confirm whether service on the TPA constitutes service on the self-insured employer. This is a subtle but important distinction. TPAs are not carriers, and service rules differ.

Discovery changes next. A subpoena duces tecum to a commercial carrier typically produces a tidy claim file with adjuster notes, reserves, and reinsurance correspondence. A subpoena to a self-insured employer produces corporate claim files that may or may not separate DBA reserves from other self-insured lines. Privilege logs look different. Reserve disclosures may trigger different objections. The employer's risk management policies become discoverable in a way that commercial carrier practices rarely are. Our step-by-step guide to identifying the correct DBA insurance carrier for your claim walks through the commercial carrier version of this workflow, and the contrast with the self-insured version is instructive.

How does L3Harris fit into the broader self-insured landscape?

L3Harris is not alone. ClaimTrove tracks a short list of top-tier defense contractors that have received DOL approval to self-insure their DBA exposure. A small number of top-tier defense contractors have received DOL approval to self-insure their DBA exposure, and they appear in federal contract data with significant overseas footprints but no commercial DBA policy traffic.

Among the top 10 DBA-exposed contractors, self-insured entities punch above their weight in claim volume because their overseas deployment is concentrated in high-risk environments. A commercial carrier like AIG or Allied World may write hundreds of DBA policies across mid-tier contractors, but a single self-insured entity like L3Harris can generate as many claims as several of those mid-tier employers combined. Our analysis of the top 10 DBA insurance carriers and their market share excludes self-insured employers by design, which means the commercial carrier market share numbers systematically understate total DBA claim volume.

The practical implication is that any attorney with a mixed book of DBA claims will eventually encounter a self-insured employer. If your practice focuses on a specific contract type (LOGCAP, State Department security, USACE construction) you may encounter them more often because those programs attract the larger primes that qualify for self-insurance. Knowing the self-insured shortlist in advance changes how you read intake data.

What records should you request when the employer is self-insured?

Records requests for self-insured DBA claims look different from commercial carrier requests in four specific ways. Understanding these differences up front prevents the common problem of receiving a partial production and not realizing what is missing.

First, request the DOL self-insurer authorization file. This is a public record held by the DOL Division of Longshore and Harbor Workers' Compensation. It shows the effective period of the authorization, the security deposit amount and form, and any conditions attached to the approval. If the authorization lapsed or was conditioned during the relevant period, that fact matters for liability allocation. Second, request the internal claims handling procedures manual. Self-insured employers maintain written procedures for DBA claim administration, and those procedures are discoverable in a way that commercial carrier best practices documents often are not. Third, request the TPA services agreement if a TPA is involved. This document defines the scope of delegated authority and tells you whether the TPA can settle, whether it has reserve-setting authority, and what the employer's oversight role looks like.

Fourth, request reserve history. Self-insured reserves are set internally without the external actuarial discipline that a commercial carrier applies. Reserve movements can tell you a great deal about how the employer assessed the claim over time, and they are often produced in discovery in self-insured cases in ways they would not be in commercial carrier cases. The 5-step DBA carrier investigation workflow covers the commercial records request baseline, and the self-insured variant substitutes or supplements at each step.

Look up L3Harris self-insured DBA claims administration history

Every claim involving L3Harris, a predecessor entity, or any subsidiary rolled up under the post-2019 merger needs to start with a self-insured flag check. ClaimTrove surfaces that flag in the first screen of the investigation report, along with the relevant alias history covering L-3 Communications, L-3 Services, L3 Technologies, Harris Corporation, and the combined L3Harris Technologies entity. The report tells you whether the date of injury falls within a legacy commercial coverage period or the post-merger self-insured period, and it routes you to the correct administrative contact.

Run a L3Harris investigation in ClaimTrove to see the full alias map, the DOL self-insurer authorization record, and the claims administration pathway for your specific date of injury. Stop chasing policy numbers that do not exist.