What is the connection between KBR and Halliburton for DBA claims?

KBR operated as a wholly owned subsidiary of Halliburton until April 5, 2007, when it became an independent public company. DBA claims from before that date may be filed under either Halliburton or KBR. Federal contract records, DOL filings, and OALJ decisions from the pre-separation period use both names interchangeably.

Was KBR covered by a mandatory DBA carrier during LOGCAP?

Yes, for part of the LOGCAP period. USACE mandated CNA as the DBA carrier for all its contractors from December 2005 through September 2013. KBR's LOGCAP contracts were awarded through USACE, so CNA was the carrier during that window. Outside that period, KBR selected its own carrier on the open market.

What name variants should I search when investigating a KBR DBA claim?

Search KBR, KBR Inc., KBR Technical Services Inc., Kellogg Brown and Root Services Inc., Kellogg Brown and Root LLC, Brown and Root Industrial Services, and Halliburton (for pre-April 2007 claims). Each variant appears in different federal databases and DOL records.

Why do KBR DBA claims involve so many third-country nationals?

KBR recruited tens of thousands of workers from South Asia and Southeast Asia for base operations under LOGCAP. These third-country nationals performed food service, maintenance, laundry, and construction work on military installations in Iraq and Afghanistan. Their DBA claims sometimes list local recruitment agencies rather than KBR as the employer.

How do burn pit claims affect KBR DBA carrier identification?

Burn pit exposure at bases like Balad Air Base occurred primarily between 2003 and 2010. Workers may not file DBA claims until years or decades later when symptoms develop. The long latency period means the carrier on risk at the time of exposure may have changed, been acquired, or restructured, requiring careful temporal matching.

What is LOGCAP and why does it matter for DBA claims?

LOGCAP (Logistics Civil Augmentation Program) is the U.S. Army's primary contract for outsourcing base operations in combat zones. LOGCAP III was sole-sourced to KBR from 2001. LOGCAP IV split work among multiple contractors from 2008. The contract vehicle determines which agency awarded the work and whether a mandatory carrier applied.

Can ClaimTrove identify the correct carrier for a KBR claim automatically?

Yes. ClaimTrove resolves all KBR name variants automatically, checks mandatory agency carrier periods based on the injury date, and searches 18 federal data sources in parallel. The engine ranks carrier matches by temporal proximity and source reliability, providing a sourced carrier identification in seconds.

Did KBR's DBA carrier change between LOGCAP III and LOGCAP IV?

Carrier arrangements could differ between contract periods. LOGCAP III and LOGCAP IV had different contract structures, awarding timelines, and scope. The mandatory USACE-CNA period overlapped both contracts. Outside that mandatory window, the carrier depended on KBR's commercial insurance arrangements at the time of injury.

KBR and DBA Claims: Tracing Carrier History for the Largest Defense Contractor

Why Is KBR the Most Complex DBA Carrier Identification Challenge?

A paralegal receives a DBA claim from a truck driver injured at a forward operating base in Iraq in 2007. The claimant says they worked for "KBR." That single name triggers one of the most tangled carrier identification puzzles in Defense Base Act practice.

KBR is not just another defense contractor. During the peak years of operations in Iraq and Afghanistan, KBR employed tens of thousands of workers across dozens of countries under the LOGCAP (Logistics Civil Augmentation Program) contract. ClaimTrove data drawn from DOL case summary records shows KBR consistently ranking among the highest-volume DBA employers across every fiscal year from 2004 through 2020.

The carrier identification challenge goes deeper than volume. KBR's corporate history involves a separation from Halliburton, multiple subsidiary names, and carrier relationships that shifted across fiscal years. An injury in 2006 may involve a different carrier than an injury in 2010, even though the claimant's employer was "KBR" in both cases. Attorneys who treat KBR as a simple, single-entity lookup will miss the correct carrier more often than they find it.

How Did KBR Become the Largest DBA Employer?

KBR's dominance in DBA claims traces directly to LOGCAP, the U.S. Army's primary vehicle for outsourcing base operations, supply chain management, and construction in combat zones. LOGCAP III, awarded in December 2001, gave KBR (then a Halliburton subsidiary) sole-source authority to provide logistics support across Iraq, Afghanistan, and other operational theaters.

At peak operations between 2004 and 2008, KBR employed an estimated 50,000 to 60,000 workers in Iraq alone. This workforce included U.S. citizens, third-country nationals from the Philippines, India, and Nepal, and local national employees. Every one of these workers fell under DBA coverage requirements.

The sheer scale of KBR's LOGCAP operations generated a proportional volume of DBA claims. Workplace injuries on military bases, vehicle accidents on convoy routes, exposure to burn pit emissions, and indirect fire incidents all produced claims. ClaimTrove tracks 4,983 DOL case summary records across all employers and fiscal years. KBR and its name variants appear repeatedly in the top tier of employer-sorted records.

LOGCAP IV, awarded in 2008, split the work among multiple contractors including KBR, Fluor, and DynCorp. This reduced KBR's individual claim volume but introduced new complexity. Workers who started under LOGCAP III with KBR sometimes transitioned to different employers under LOGCAP IV, creating coverage continuity questions for injuries with long latency periods.

What Name Variants Does KBR Operate Under?

Searching for "KBR" alone will miss significant portions of the company's DBA footprint. ClaimTrove's alias resolution system tracks multiple name variants that all map to the same corporate entity.

The Halliburton connection is the most significant. Before April 2007, KBR operated as a wholly owned subsidiary of Halliburton Company. Contracts awarded before the separation list "Halliburton" or "Halliburton KBR" as the contractor. DOL filings from this period may reference either name. An injury in 2005 could show up under "Halliburton" in one database and "KBR" in another.

KBR completed its separation from Halliburton on April 5, 2007, becoming an independent publicly traded company. After that date, contracts and filings should reference KBR, Inc. or KBR Technical Services. But legacy records and informal references continued using both names for years afterward.

Additional name variants in federal records include KBR Technical Services Inc., Kellogg Brown and Root Services Inc., Kellogg Brown and Root LLC, and Brown and Root Industrial Services. Each of these names may appear in contract awards, OSHA inspection records, SAM.gov registrations, or OALJ decisions. ClaimTrove's employer alias database maps 214 total alias relationships across all employers, and KBR's variants account for a notable share of that total.

The practical impact for attorneys is clear. A carrier search that only uses "KBR" will miss filings under "Kellogg Brown and Root," contracts under "Halliburton," and case summaries under "KBR Technical Services." Each missed variant is a potential missed carrier match.

How Did KBR's DBA Carrier Change Over Time?

KBR's carrier history is not static. Like most large defense contractors with sustained DBA exposure, KBR's insurance carrier relationships shifted across fiscal years as policies renewed, premiums changed, and the DBA insurance market evolved.

ClaimTrove data reveals that carrier transitions for high-volume employers like KBR typically occur on 3-to-5-year cycles. Each policy renewal is an opportunity for the employer to switch carriers, for carriers to decline renewal, or for market conditions to force a change. The date of your client's injury determines which carrier was on risk.

For LOGCAP-era claims, the awarding agency adds another layer. KBR's LOGCAP contracts were awarded by the U.S. Army through USACE (U.S. Army Corps of Engineers). Between December 2005 and September 2013, USACE mandated CNA as the DBA carrier for all its contractors. This means KBR workers on USACE-awarded contracts during that window were covered by CNA, regardless of what carrier KBR might have selected independently.

Before and after the USACE mandatory period, KBR's carrier was determined by its own commercial insurance arrangements. The carrier during these open-market periods requires checking employer-specific records: OWCP coverage card filings, BRB decisions naming parties, and industry performance reports that link primes to carriers by fiscal year.

ClaimTrove's investigation engine handles this temporal complexity automatically. When you enter "KBR" with an injury date, the system first checks whether a mandatory agency carrier applies, then searches 18 federal data sources across all known name variants, and ranks carrier matches by temporal proximity to the injury date.

What Makes LOGCAP Claims Particularly Difficult?

LOGCAP claims present unique challenges beyond standard carrier identification. The contract structure itself creates layers of complexity.

LOGCAP is a cost-reimbursement contract. KBR did not select subcontractors in the traditional sense. Instead, it managed a vast supply chain of vendors, service providers, and labor suppliers under the LOGCAP umbrella. A worker might be employed by a KBR subcontractor whose name never appears in standard contract databases because the sub operated under KBR's LOGCAP task orders rather than holding an independent federal contract.

Third-country national (TCN) workers add another dimension. KBR recruited heavily from South Asia and Southeast Asia for base operations roles. These workers often entered the claims system with employer names that reflected local recruitment agencies or labor brokers rather than KBR itself. Matching these employer names back to KBR's LOGCAP contract requires tracing the subcontract chain.

Burn pit exposure claims represent a growing category with unique carrier identification challenges. A worker exposed to burn pit emissions at Balad Air Base in 2006 may not file a DBA claim until 2020 or later, when respiratory symptoms develop. The 14-year gap between exposure and filing means the carrier on risk at the time of exposure may no longer exist as the same entity, may have been acquired, or may dispute coverage for occupational disease claims with long latency periods.

ClaimTrove's database of 5,022 OALJ decisions contains multiple cases involving KBR and its subsidiaries. These decisions provide valuable precedent for handling carrier disputes, coverage questions, and issues specific to LOGCAP employment arrangements. The vector search capability allows attorneys to find semantically relevant decisions even when the exact legal issue has not been previously categorized.

How Should You Approach a KBR DBA Investigation?

Start with the injury date, not the employer name. The date determines whether a mandatory agency carrier applies. For injuries between December 2005 and September 2013 on USACE-awarded contracts, CNA is the carrier. That check takes seconds and resolves a large percentage of LOGCAP-era claims immediately.

If the injury falls outside a mandatory carrier period, expand your search to all KBR name variants. Do not stop at "KBR." Search Halliburton, Kellogg Brown and Root, KBR Technical Services, and Brown and Root. Cross-reference each variant against coverage card filings, BRB party records, and industry performance reports for the relevant fiscal year.

Pay attention to the contract vehicle. LOGCAP III (sole-source to KBR) and LOGCAP IV (multiple awardees) have different carrier identification implications. A worker on LOGCAP IV may have been employed by a different prime contractor than KBR, even if they previously worked under KBR on LOGCAP III.

For TCN claims, identify the labor supply chain. The claimant's direct employer may be a recruitment agency, but DBA liability flows to the entity holding the contract that required the work. Trace the subcontract chain back to KBR and the LOGCAP prime contract to establish the coverage obligation.

ClaimTrove automates this entire workflow. Enter the employer name and injury date. The engine resolves aliases, checks mandatory carriers, searches 18 data sources in parallel, and ranks the most likely carrier with source citations. For KBR investigations that used to take hours of manual research, you get a sourced answer in under 10 seconds.