What is LOGCAP and who are its prime contractors?

LOGCAP is the Army's Logistics Civil Augmentation Program, a standing contract vehicle for contingency logistics support. Across its four generations since 1988, the program has cycled through several primes. LOGCAP III was held by KBR as a single prime. LOGCAP IV split work among KBR, DynCorp, and Fluor under a multiple-award structure.

Why does the LOGCAP generation matter for DBA claims?

Each LOGCAP generation had a different prime contractor structure, and each prime had its own DBA insurance carrier relationships. The injury date determines which generation was active. The generation determines which prime was responsible. The prime determines which carrier was on-risk during the policy period covering the injury.

How do LOGCAP contract transitions create coverage gaps?

LOGCAP transitions were not clean handoffs. Task orders from one generation often continued running after the next generation was awarded. During transition periods, two different primes could be operating on the same base simultaneously, meaning two different carriers could be on-risk for injuries occurring at the same location.

Does DBA coverage follow the prime contractor or the subcontractor?

DBA coverage follows the employment relationship. The direct employer's carrier is primarily responsible. Some LOGCAP primes carried umbrella policies extending to certain subcontractor tiers, while others required subcontractors to carry independent coverage. The specific arrangement varied by task order, by prime, and by generation.

Can I identify a LOGCAP carrier from the USAspending prime award record alone?

No. An award record identifies the prime but does not disclose the DBA carrier. Carrier identification requires combining the prime contract data with policy period data for that prime. A prime may have had different carriers in different years even while the same task order continued running.

What records help narrow down the responsible LOGCAP prime for a specific injury?

Duty station, injury date, functional scope of the work, and direct employer name all help narrow the candidate prime. LOGCAP IV used geographic zones to assign primes, so location is especially valuable. Task order modifications preserve the original prime relationship even when work continued for years under extensions.

How do subcontractor tiers complicate LOGCAP carrier identification?

LOGCAP primes subcontracted heavily for dining, laundry, transportation, and specialized trades. A worker may have been employed two or three tiers below the prime. Subaward reporting coverage is patchy, so many smaller subcontractors never appear in federal reporting and must be identified through FOIA records or OWCP filings.

Does ClaimTrove provide carrier-specific answers for LOGCAP claims?

Yes. ClaimTrove's investigation engine cross-references prime awards, task order history, subcontractor relationships, FOIA records, and carrier policy periods to produce a ranked list of likely carriers for a specific employer and injury date within the LOGCAP contract family.

What if my client worked on a LOGCAP task order but nobody knows which generation it fell under?

The injury date is usually enough to place the claim within a generation. LOGCAP III and LOGCAP IV have well-established performance periods. Transition-period claims require checking both generations because task orders from the prior generation often continued running during the next generation's ramp-up.

How long does it take to reconstruct LOGCAP carrier coverage manually?

Manual reconstruction across USAspending, FOIA releases, OWCP coverage records, and carrier policy archives typically takes days per claim. The data is scattered across multiple federal systems with inconsistent naming. Automated reconstruction through ClaimTrove's investigation engine produces a ranked carrier list in seconds.

LOGCAP DBA Insurance: How Army Logistics Contract Transitions Create Carrier Coverage Gaps

A paralegal pulls a claim file for a former logistics worker injured at Joint Base Balad in December 2008. The client worked dining facility operations under what everyone on base called the "LOGCAP contract." The injury report names the employer. The DD Form 214 lists the duty station. The medical records document the treatment. The one thing nobody can find is the DBA insurance carrier.

This scenario repeats across thousands of LOGCAP-related claims. The Army's Logistics Civil Augmentation Program has generated more overseas contractor employment than any other federal program. It has also generated more carrier identification confusion than any other federal program. The reason is structural. LOGCAP is not one contract. It is a rolling series of umbrella contracts, each with its own prime, task order architecture, and insurance arrangement.

The LOGCAP DBA insurance Army logistics support contract carrier coverage problem is fundamentally a timeline problem. A claimant's injury date determines which LOGCAP generation was active. The generation determines the prime. The prime determines the carrier relationship. Miss one link in that chain and the claim lands on the wrong carrier's desk, or no carrier's desk at all.

This article walks through how LOGCAP's four generations distributed work among KBR, DynCorp, and Fluor, and why those transitions created coverage gaps that still complicate claims today. It does not tell you which carrier covered which prime in which year. That is what ClaimTrove's investigation engine is for.

What Is LOGCAP and Why Does It Matter for DBA Claims?

The Logistics Civil Augmentation Program began in 1985 as an Army initiative to pre-position commercial logistics capacity for contingency operations. Rather than scrambling to source fuel, food, laundry, transportation, and base operations support during a deployment, the Army developed standing contracts with vendors who could surge on demand.

LOGCAP became the single largest source of contingency contractor employment in US history. At its peak during the Iraq and Afghanistan wars, LOGCAP task orders employed more than 50,000 workers simultaneously. Third-country nationals, US expatriates, and host-country nationals all fell under its umbrella. Almost every one of them required DBA coverage.

For DBA claimants, LOGCAP matters because it concentrates enormous injury exposure into a single contract vehicle whose prime contractor changed multiple times. A claim filed in 2026 for an injury sustained in 2008 requires the researcher to reconstruct which LOGCAP generation was active, which task order governed the work site, and which prime held that task order. The Department of Defense's sprawling contract environment amplifies this difficulty, as explained in why DOD's 38,582 overseas contracts make DBA carrier identification so difficult.

How Did LOGCAP Cycle Through KBR, DynCorp, and Fluor?

LOGCAP has operated through four generations. LOGCAP I ran from 1988 to 1997 under a single prime. LOGCAP II covered 1997 to 2001 with a different prime. LOGCAP III, awarded in 2001, became the most visible generation of the program because it governed the bulk of Iraq and Afghanistan logistics support from 2003 through roughly 2010. LOGCAP IV, awarded in 2008 with a phased transition, introduced a multiple-award structure that split work among three primes for the first time.

KBR held LOGCAP III as a single prime. The company executed hundreds of task orders across Iraq, Afghanistan, Kuwait, Qatar, and Djibouti. LOGCAP III employment peaked well above 50,000 workers. The single-prime structure meant that carrier identification for this period collapses to one question: which carrier covered KBR employees on a given task order in a given year? The answer is not static. KBR's carrier relationships shifted multiple times, as documented in the KBR insurance story across 15 years of carrier changes.

LOGCAP IV changed the structure entirely. The Army awarded three primes under the same umbrella. DynCorp, Fluor, and KBR each received performance task orders based on geographic zones. A 2012 injury at Bagram Airfield traces to Fluor. A 2012 injury at Camp Arifjan traces to DynCorp. A 2012 injury in Kuwait traces to KBR. Same year. Same overall contract family. Three different primes and three different carrier arrangements. Tracing DynCorp's role requires specific attention to its later acquisition history, detailed in DynCorp's DBA coverage history and what the data reveals.

Why Do LOGCAP Transitions Create Coverage Gap Periods?

Contract transitions are not clean handoffs. A generation does not end on Friday with the new generation starting on Monday. LOGCAP transitions involved task order ramp-down periods, continuation of existing task orders under the old prime while new task orders were awarded under the new structure, and extended performance periods for work already in progress.

The LOGCAP III to LOGCAP IV transition illustrates this. LOGCAP IV was awarded in April 2008. Task order transitions extended through 2011. Some LOGCAP III task orders continued running under KBR well after LOGCAP IV primes had begun work in the same theaters. An injury in late 2009 in Afghanistan could fall under a LOGCAP III KBR task order or a LOGCAP IV task order held by a different prime, depending on the specific location and function.

Each transition period produces carrier identification ambiguity. The prime's name on the task order determines DBA coverage. Task order numbers are not always present in claimant records. Duty station and employer name alone are insufficient when two different primes were operating on the same base simultaneously during a transition. The broader pattern across rebid cycles is examined in what happens to DBA coverage when contracts get rebid.

Compounding the problem, carrier policy periods do not always align with contract periods. A prime may have had one carrier in 2008 and a different carrier in 2010 even though the underlying LOGCAP task order continued uninterrupted. The carrier that was on-risk when the injury occurred is the carrier that owes coverage. Not the carrier that was on-risk when the claim was filed. Not the carrier that is on-risk today.

How Do Subcontractor Layers Complicate LOGCAP Carrier Identification?

LOGCAP primes did not perform all work directly. They subcontracted heavily. Dining facility operations, laundry services, transportation support, and specialized trades frequently ran through lower-tier subcontractors. A worker injured in a LOGCAP kitchen may have been employed by a third-tier subcontractor two or three levels below the prime. For a deeper look, see how ANHAM FCZO's Iraq food service subcontractor chain creates carrier identification challenges.

DBA coverage follows the employment relationship, but prime contractors often carried umbrella DBA policies that extended to certain subcontractor tiers. Others required subcontractors to carry independent DBA coverage. The specific arrangement varied by task order, by prime, and by generation. A 2009 injury at a LOGCAP III dining facility in Iraq may produce a claim against KBR's carrier, the direct subcontractor's carrier, or both depending on how the coverage flowed down.

Fluor's LOGCAP IV operations illustrate the additional complexity introduced by construction-heavy task orders. Fluor executed significant base operations and construction scope under LOGCAP IV, bringing its own subcontractor ecosystem and insurance practices. The company's broader subsidiary structure adds another layer of analysis, as detailed in Fluor Corporation DBA insurance and why its subsidiary maze makes carrier tracing so hard.

ClaimTrove's data shows that LOGCAP-related claims frequently require tracing four or more contract relationships before landing on the responsible carrier. Prime contract. Task order. Subcontract tier. Policy period. Each layer introduces a potential mismatch. A single wrong assumption at any layer sends the claim to the wrong carrier.

What Does the USAspending Data Show About LOGCAP Award Volume?

ClaimTrove's federal contracting database contains 43,298 prime contract awards. LOGCAP-labeled awards and task orders represent a significant subset of the overseas work within that total. Aggregate analysis of the award data reveals several patterns that matter for LOGCAP DBA insurance Army logistics support contract carrier coverage research.

First, LOGCAP task orders cluster around specific geographic zones. Iraq and Afghanistan dominate the volume, but Kuwait, Qatar, Djibouti, and Jordan all appear frequently. A claimant's duty station often narrows the likely prime more effectively than the injury date alone.

Second, task order modifications are extensive. A single base task order may have dozens of modifications extending the period of performance, adjusting scope, or changing funding ceilings. Each modification preserves the original prime relationship, which means the prime named on the original task order is usually the prime responsible for DBA coverage even if the work continued for years.

Third, subaward data is incomplete. Our database holds 4,315 subcontract awards, but FSRS reporting coverage for LOGCAP subcontractors is patchy. Many smaller subcontractors that employed injured workers never appear in prime reporting. This is why FOIA records, OWCP filings, and OALJ decisions frequently provide the only documentary path to identify the actual employer behind a LOGCAP injury.

Fourth, carrier identification at the LOGCAP level requires combining contract data with policy period data. An award record tells you who the prime was. It does not tell you which carrier was on-risk during the injury period. ClaimTrove's investigation engine combines both, resolving the prime through USAspending and contract records, then scoring carriers based on policy history within the relevant timeframe.

How Can Attorneys Reconstruct LOGCAP Carrier Coverage for a Specific Injury Date?

The investigative sequence for a LOGCAP claim follows a specific order. Skipping steps or running them out of order produces wrong or incomplete answers.

Establish the injury date with precision, not approximation. LOGCAP generation boundaries can shift the prime assignment by entire contract families.
Establish the duty station and geographic zone. LOGCAP IV's multiple-prime structure assigned primes by region, so location narrows the candidate pool.
Identify the direct employer. If it is a subcontractor, note that fact. The direct employer's carrier may differ from the prime's carrier.
Determine which LOGCAP generation was active. Use the injury date against the published generation timeline, and check for transition-period ambiguity.
Identify the prime responsible for the relevant task order. This is where geographic zone and functional scope narrow the answer.
Match the prime to its carrier for the relevant policy period. This is the step that requires carrier policy history, not just contract award data.
Validate against OWCP filings, OALJ decisions, and any existing claim documentation that names a carrier.

Most attorneys cannot execute steps four through six without tooling. The data is scattered across USAspending, FOIA releases, OWCP coverage records, and carrier policy archives. Manual reconstruction takes days. Automated reconstruction through ClaimTrove's investigation engine takes seconds.

What Does the LOGCAP Transition Mean for Your Client's Claim?

If your client's injury falls within any LOGCAP generation, the prime contractor on the injury date governs the DBA coverage analysis. The generation alone does not answer the carrier question. The task order, the prime, the subcontractor layer, and the policy period together answer the carrier question.

LOGCAP III claims generally trace to a single prime with shifting carrier relationships over time. LOGCAP IV claims require geographic and functional analysis to identify which of three primes held the task order. Transition-period claims require checking both generations because task orders from the prior generation often continued running during the ramp-up of the next.

LOGCAP DBA insurance Army logistics support contract carrier coverage analysis cannot be resolved from contract awards alone. The investigation requires carrier policy period data matched against the specific prime, task order, and injury date. ClaimTrove's investigation engine is built to resolve exactly this kind of multi-layer contracting puzzle. Run a LOGCAP employer investigation in ClaimTrove to identify the prime and carrier for your client's specific injury period before the statute of limitations closes the window.