A paralegal opens a new file. The injured worker spent fourteen months on a missile-defense maintenance program at a forward base in the Gulf. The LS-203 names the employer as a Raytheon entity. The claimant remembers a corporate badge, a Raytheon email address, and a chain of command that ran back to a program office in Massachusetts. So who is the Defense Base Act carrier? The instinct is to assume one large defense prime carries one policy across every overseas program. That instinct is wrong, and it costs claims teams weeks.
Raytheon is one of the most complicated employers to trace in the entire DBA universe. The name on the badge rarely matches the name on the contract, and neither matches the name on the OWCP filing. The company has merged, split, rebranded, and reorganized its overseas footprint more than almost any peer. Identifying the right Raytheon DBA insurance carrier for a specific worker on a specific program in a specific year is a research problem, not a lookup.
This article explains why Raytheon is hard, what federal records actually tell you, and how a structured investigation cuts through the corporate maze. It will not hand you a carrier name for a given program, because no honest single answer exists across the company's history. It will show you how to find the right answer for your file.
Why is Raytheon DBA coverage so hard to identify?
Start with the corporate structure. The entity most attorneys call "Raytheon" has not been a single company for years. The 2020 merger with United Technologies created Raytheon Technologies, combining United Technologies' pre-existing aerospace businesses (Collins Aerospace and Pratt and Whitney) with Raytheon's defense segments. The company later rebranded the parent to RTX while keeping Raytheon as a business segment. Each of those moves changed the legal employer name that appears on federal contracts and DOL filings.
That matters because DBA coverage attaches to the contracting legal entity, not the brand. A worker badged "Raytheon" might be employed by a subsidiary, a joint venture, or a program-specific LLC that never used the parent name on its insurance filing. This is the same alias problem that plagues every large prime, and it is why resolving employer name variations is the first step in any serious carrier trace.
Then layer in the program structure. Raytheon overseas work spans missile-defense system support, radar maintenance, training, and integration contracts across multiple combatant commands. Different programs run under different prime contracts. Different prime contracts can carry different DBA policies. A worker on a Patriot maintenance program and a worker on a radar sustainment program may sit under entirely separate insurance arrangements even though both wear the same logo.
Self-insurance adds a final twist. Some large defense technology firms qualify as DOL-authorized self-insured employers rather than buying commercial DBA policies. When that happens, there is no commercial carrier to name at all, and the responsible party is the employer itself through an authorized self-insurance program. Confirming whether a Raytheon entity self-insured for a given period is its own research question.
What federal records reveal about Raytheon overseas contracts?
The fastest way to orient a Raytheon investigation is the federal spending trail. ClaimTrove holds 43,298 prime contract awards and 4,315 subcontract awards drawn from USAspending and related sources. Searching that data for Raytheon legal entities surfaces the actual contracting vehicles behind a worker's program, including award dates, performing locations, and the awarding agency.
This is where the badge-versus-contract gap becomes visible. The spending records show the precise legal entity that won the work, which is frequently a subsidiary name the claimant never heard. Learning to read those records is a skill in itself, and our guide to using federal contract data for carrier identification walks through the mechanics. The contract award is the anchor that ties a worker to a coverage period.
Federal entity records sharpen the picture further. SAM.gov holds 865,232 entity records in ClaimTrove, each tying a CAGE code and UEI to a registered legal name and address. Matching the Raytheon entity from a contract to its SAM.gov registration confirms you are tracing the right corporate body and not a same-named affiliate. For self-insured candidates, the DOL authorized list is the cross-check that tells you whether a commercial policy even exists.
None of these sources, on its own, names the carrier. The spending data names the contract. The entity data names the company. The carrier emerges only when you combine those with coverage-period evidence and DOL claim records. That combination is exactly the problem a structured tool is built to solve.
How does Raytheon compare to other defense technology contractors?
Raytheon is not unique in being hard, but it sits at the difficult end of the spectrum. The pattern repeats across the large defense-technology primes, and seeing the pattern helps you set expectations on a Raytheon file.
Several big technology contractors carry DBA exposure through a mix of commercial policies and self-insurance, and the mix shifts by program and year. The same investigative logic that applies to Raytheon applies to peers like Leidos and its federal technology contracts, where multiple business lines and acquired companies blur the coverage picture. The lesson is consistent: brand size does not equal coverage simplicity.
Self-insurance is especially common at this tier. When you research a firm like SAIC as a self-insured defense contractor, the question flips from "which carrier" to "is the employer the responsible party directly." Raytheon entities sit on both sides of that line depending on the period and program, which is why you cannot assume either answer.
Logistics and sustainment-heavy primes show yet another variation. A worker file at a logistics prime like KBR, with its long DBA carrier history, demonstrates how carriers rotate across the life of a contractor. Raytheon's overseas history is shorter and more technology-focused than KBR's, but the same temporal churn applies. The carrier that covered a 2014 program is not safe to assume for a 2021 program.
Why does the Raytheon carrier change over time?
Even within a single Raytheon program, the responsible carrier can shift between fiscal years. DBA policies are typically annual. When a contract renews, the prime can rebid its insurance, change brokers, or move to a different carrier entirely. ClaimTrove data shows that carrier turnover every few years is the norm across the contractor population, not the exception.
Corporate events accelerate that churn. A merger can consolidate insurance programs onto a new carrier overnight. A divestiture can leave a legacy program on its old policy while new work moves elsewhere. Raytheon's 2020 merger and subsequent RTX rebrand are exactly the kind of events that reset coverage assumptions. The deeper mechanics of this are covered in our piece on temporal shifts in DBA coverage.
The practical consequence is that the injury date controls everything. A Raytheon worker injured in fiscal year 2015 may have a different carrier than a worker injured on the same program in fiscal year 2019. Pinning the exact date of injury, and the exact program active on that date, is non-negotiable before you name a responsible party.
This is also where third-party administrators muddy the water. The entity that answers the phone, adjusts the claim, and sends correspondence is often a TPA, not the carrier or the self-insured employer. Treating a TPA name as the carrier is a classic error that sends attorneys chasing the wrong party in a dispute.
How do you run a clean Raytheon carrier investigation?
A reliable Raytheon trace follows a disciplined sequence. Skipping steps is what produces wrong answers that look confident.
- Fix the facts. Lock down the exact injury date, the program name, and the duty location from the LS-203 and the claimant interview.
- Resolve the entity. Translate the badge name into the actual legal employer using alias resolution and SAM.gov entity matching.
- Find the contract. Use federal spending records to identify the prime contract active on the injury date for that program and location.
- Check self-insurance. Confirm whether the responsible Raytheon entity was a DOL-authorized self-insured employer for that period before assuming a commercial carrier exists.
- Match coverage to period. Tie the contract and entity to coverage-period evidence and DOL claim records to surface the carrier responsible on the injury date.
- Separate the TPA. Confirm whether any named handler is the carrier itself or a third-party administrator acting on its behalf.
Doing this by hand means juggling spending databases, entity registries, DOL claim summaries, the self-insurance list, and decades of corporate reorganization. Each source uses a different name for the same company. Each covers a different slice of time. The work is genuinely hard, which is the entire reason it has value.
ClaimTrove collapses that workflow into a single investigation. Across more than one million records from 18-plus federal data sources, the engine resolves the Raytheon entity behind the badge, pulls the contracts active on your injury date, flags self-insurance where it applies, and surfaces the carrier evidence tied to the right period. You bring the injury date and the program; the engine brings the trail.
Stop guessing which Raytheon entity carried the policy. Run the worker's name, program, and injury date through ClaimTrove and trace the responsible party from the federal record itself. Start your investigation today.