A flight attendant working an Omni Air International charter from Baltimore to Kuwait gets injured during a hard landing at Ali Al Salem Air Base. She is a U.S. citizen, employed by a Tulsa-based airline, hurt on a runway in the Middle East. Which workers' compensation system covers her? Not Oklahoma state comp. Not the carrier's domestic aviation policy. If that flight moved under a federal contract, her injury falls under the Defense Base Act, and the claim runs against a DBA insurance carrier that most people have never heard of.
This is the part of air-charter work that surprises attorneys new to the space. Omni Air International is a passenger and cargo charter operator that has flown military rotations, contractor deployments, and government cargo for decades. The pilots, flight attendants, loadmasters, and ground support staff on those missions are exactly the kind of overseas workers the DBA was written to cover. When one of them files a claim, the first question is always the same: who is the carrier?
Answering that for an aviation contractor is not a simple lookup. Air-charter companies carry layered insurance, fly under multiple contract vehicles, and sometimes operate through related corporate entities. The DBA carrier sits inside that stack, and finding it means separating aviation liability coverage from workers' compensation coverage, then tracing the right policy to the right contract and the right time period.
Why Do Air-Charter Contractors Carry DBA Exposure?
The Defense Base Act extends federal workers' compensation to employees working overseas under contracts with U.S. government agencies. The statute, 42 U.S.C. 1651, reaches employees of contractors and subcontractors on public works and national defense contracts performed outside the continental United States.
Air-charter and aviation-support contractors fit that definition cleanly. When an airline flies a Department of Defense rotation or a State Department movement, the flight crew are employees performing work under a federal contract on foreign soil the moment the aircraft touches down overseas. The DBA does not require the worker to be in a combat role. A flight attendant, a mechanic servicing an aircraft at an overseas airfield, or a loadmaster handling cargo at Bagram all carry the same statutory exposure.
Aviation work creates exposure that ground-based contractors do not face. Crews rotate through dozens of countries on a single contract. A pilot might overnight in Germany, Qatar, and Djibouti in one week. Each landing in a foreign jurisdiction can establish DBA situs. The transient nature of the work makes it harder to pin down where an injury occurred and which contract governed that specific mission.
The federal contracting structure for airlift compounds this. Charter operators often fly under teaming arrangements, brokered through aviation logistics primes rather than contracting directly with the government. ClaimTrove's contract data covers 43,298 prime contract awards and 4,315 subcontract awards, and aviation-support work frequently appears in the subcontract layer. That means the airline doing the actual flying may not be the named prime on the contract, which changes who carries the DBA policy and who sits in the liability chain.
This same complexity shows up across the defense-contractor universe. The way ITAR registration creates a carrier paper trail for security firms has a parallel in aviation, where FAA operating certificates and DOD commercial airlift agreements leave their own documentary footprint that helps confirm which entity was flying and insured.
How Is DBA Coverage Structured for an Aviation Contractor?
An air-charter operator carries several distinct insurance policies, and only one of them is the DBA workers' compensation policy. Confusing the layers is the most common mistake in these claims.
Aviation hull and liability insurance covers the aircraft and third-party damage. Aviation war risk coverage protects against losses in hostile environments. These are property and liability lines, not workers' compensation. They do not pay an injured crew member's medical bills or indemnity benefits. The DBA policy is separate, and it is the one that responds to an employee injury.
The DBA policy itself is typically written by a specialized underwriter. A small group of carriers dominate overseas workers' compensation. ClaimTrove's records identify 637 DOL-authorized DBA carriers, but the active overseas market concentrates heavily among a handful of names that write the bulk of high-volume contractor coverage. For aviation contractors, the underwriter may differ from the carrier on the same company's domestic policies, because overseas exposure is priced and placed differently.
Third-party administrators add another layer of confusion. A claim file might show ESIS, Gallagher Bassett, or Broadspire as the contact handling the claim. None of those is the actual insurance carrier. They administer claims on behalf of the underwriter behind the policy. Mistaking the TPA for the carrier sends attorneys chasing the wrong entity, and the distinction is easy to miss because the TPA's name is what appears on most correspondence.
Timing matters as much as structure. Carriers do not stay constant. Our data shows that most contractors shift DBA carriers every three to five years as policies are rebid and brokers move books of business. A crew member injured in 2014 and another injured in 2019 on the same airline may have claims against entirely different carriers. Identifying coverage requires matching the injury date to the policy period in force at that time, not just naming the company's current carrier.
What Makes Carrier Identification Hard for Omni Air International Specifically?
Aviation contractors present every carrier-tracing challenge at once: alias variation, contract-layer ambiguity, and temporal carrier shifts. Omni Air International is a strong example of why a name and a date are not enough to answer the carrier question.
Start with corporate identity. Airlines operate through holding companies, operating certificates, and related entities that may appear on contracts and claim filings under different names. A DBA case might be captioned under a parent company, an operating subsidiary, or a contracting entity that does not obviously read as the airline. This is the same problem that makes AECOM's 19 name variations the hardest carrier trace in construction, applied to the aviation sector. ClaimTrove maintains 214 employer alias mappings precisely because the name on the claim is rarely the name you searched.
Next is the contract layer. Military and government airlift moves through several channels, including DOD commercial airlift agreements and aviation logistics primes. The airline flying the mission may be a subcontractor to a larger logistics integrator, which means the DBA carrier could be the airline's own policy or could be governed by the prime's arrangement, depending on the contract terms. Resolving this requires reading the subcontract chain, not assuming the operator carried its own coverage.
Then there is the agency mandate question. Certain federal agencies have, during specific windows, required all their overseas contractors to use a single designated DBA carrier. If an air-charter mission flew under one of those mandated programs during the mandate period, the carrier is determined by the agency, not the airline. If it flew before or after that window, the carrier reverts to the open market. Getting this right means knowing which agency awarded the contract and whether a mandate was active on the injury date. The same temporal-shift problem that defines the Blackwater-to-Academi-to-Constellis carrier trail applies here in the form of changing agency mandates and rebid cycles.
Finally, the FOIA evidence layer. ClaimTrove cross-references federal coverage filing records and contractor-tracking databases that can confirm whether a specific entity held DBA coverage at a specific date and which carrier filed it. For an aviation contractor flying into Afghanistan, this matters: the carrier landscape for Afghanistan contractors was shaped by agency mandates and a concentrated underwriter market that looked very different in 2010 than in 2018.
How Should You Investigate an Omni Air International DBA Claim?
Work the problem in the order the evidence supports, strongest first. Do not start by guessing the carrier from the company name.
Begin with the contract. Identify the contract or task order the flight moved under, the awarding agency, and the date of the mission. This tells you whether an agency carrier mandate applied and whether the airline was a prime or a subcontractor. The contract number is the anchor for everything that follows.
Resolve the corporate entity next. Confirm which legal entity employed the injured worker and which entity was named on the contract. For an airline, these may differ. Run the name and its known variations rather than a single spelling, because DBA filings and coverage records use whatever name the filer entered.
Then separate the insurance lines. When you obtain claim correspondence, distinguish the DBA workers' compensation carrier from the aviation liability insurer and from any TPA. The entity sending you letters is often the administrator, not the underwriter. Confirm the actual carrier before you direct demands or pursue penalties.
Finally, match the date to the policy period. Once you have candidate carriers, weight them by how close their coverage period sits to the injury date. A carrier that covered the airline in the right year outranks one that covered it a decade earlier. This temporal weighting is exactly the kind of analysis attorneys building a defensible carrier identification for a federal technology contractor rely on, and it applies equally to aviation.
One more aviation-specific caution: crew injuries are not always on duty in the obvious sense. A layover injury, an off-duty incident at an overseas hotel, or a transit injury can raise hard coverage questions. Whether those fall under the DBA depends on the zone-of-special-danger doctrine and the facts, a question explored in our analysis of how recreational and off-duty injuries are treated under the DBA.
What Records Confirm an Air-Charter Contractor's DBA Coverage?
Several federal data sources, read together, can establish whether and how an aviation contractor was covered. No single source answers the question alone.
Federal contract award data confirms which agency hired the airline, under what contract number, and whether the work was overseas. The presence of a labor-standards flag on a contract signals that the DBA likely applies. This data also reveals whether the airline was the prime or sat in the subcontract layer beneath a logistics integrator.
DOL coverage filing records, obtained through FOIA, provide the most direct evidence available: a filed insurance record showing an employer, a carrier, and a policy date. For an aviation contractor, this can confirm coverage existed and name the underwriter who filed it. ClaimTrove's coverage records span filings from 1944 through 2022, which is enough history to cover most of a long-operating airline's contract life.
Adjudicated decisions add another confirmation layer. When a DBA claim against an aviation contractor reaches an administrative law judge or the Benefits Review Board, the case caption names the employer and the carrier. ClaimTrove holds 5,022 OALJ decisions, and the party headers in those decisions are a reliable source of confirmed employer-carrier pairs.
The reason ClaimTrove exists is that no attorney has time to pull all of these sources, normalize the carrier names, resolve the aliases, and weight the results by date for every claim. The investigation engine runs that workflow across more than 18 federal data sources at once and returns a ranked carrier answer with the evidence behind it.
We do not publish which specific carrier covered Omni Air International, or the exact policy periods, because that answer depends on the injury date, the contract, and the corporate entity involved, and getting it wrong has real consequences for a claim. Run the employer through ClaimTrove to resolve its aliases and subsidiaries, identify the governing contract and agency, and surface the carrier-by-period that matches your specific claim date.