A paralegal opens a new file. The client spent months on a flightline in the eastern Jordanian desert, working fuel systems at a place the contract calls MSAB. He was hurt on the job. Now the firm needs the DBA insurance carrier, and the injury report lists only the employer and the base.
That base is Muwaffaq Salti Air Base, near the town of Azraq. It sits in the basalt desert east of Amman, far from the tourist map. For DBA attorneys, it is one of the harder assignments in the region. The name barely appears in public claims data, yet contractors have worked there for years.
This is the base-level view of a problem we usually see at the country level. Jordan is a busy regional hub, and we cover the wider picture in a separate breakdown. What follows here is narrower. It asks what the public federal record actually shows about work and injuries at Muwaffaq Salti specifically, and where that record goes quiet.
The short answer: the contract data names the base and its primes clearly, the claims data does not. That gap is exactly where carrier identification gets hard, and where a real investigation starts.
What does the contract data show about Muwaffaq Salti Air Base?
ClaimTrove's contract award records include 178 US federal awards with a place of performance in Jordan. Of those, 40 carry the labor standards flag that signals the Defense Base Act likely applies. That flag is the first structural clue that injured workers on the contract fall under DBA jurisdiction.
Narrow the search to the base itself and the picture sharpens. Eight awards in the data name Muwaffaq Salti, MSAB, or Azraq directly in the contract description. Every one of them was issued by the Department of Defense. They span award start dates from 2017 through 2023.
The named recipients read like a roster of established overseas primes. Vectrus, Amentum, URS Federal Services International, Parsons-Versar Joint Venture, Baker Jacobs Joint Venture, and Acuity-Janus Global all hold awards tied to the base. Base-operations primes accumulate DBA exposure steadily over time. Our profile on how Vectrus and V2X carry thousands of claims behind a carrier that moves shows the pattern at scale.
The work described is exactly what generates DBA claims. The awards cover installation support services, dining facility operations, engineering and design assistance, unexploded ordnance clearance, fuel and lubricant storage design, and flightline support planning. Award values run from roughly $407,000 for an architect-engineer task to more than $18 million for dining facility services.
Three of those eight awards belong to joint ventures. That matters for coverage tracing. A joint venture files under its own name, insures under its own policy, and can dissolve when the project ends. The employer on the injury report may be an entity that no longer exists.
Why does the US operate at Azraq, and who works there?
Muwaffaq Salti Air Base hosts US Air Force units alongside the Royal Jordanian Air Force. The site has supported fighter and remotely piloted aircraft operations tied to the counter-ISIS mission across Syria and Iraq. It is an operational base, not a peacetime garrison, and that shapes the contractor footprint.
US reliance on Jordanian basing grew through the second half of the 2010s, as friction with Turkey over its S-400 missile purchase and its objections to US support for Kurdish forces raised doubts about the long-term reliability of Incirlik Air Base. Congress funded a major expansion of Muwaffaq Salti around 2018 and 2019, explicitly framed as a hedge against losing Incirlik access. Azraq offered a stable alternative inside a partner nation. That shift brought more construction, more logistics, and more support contracts, which is visible in the 2017 to 2023 clustering of the base-named awards.
The workforce at a base like this is layered. Prime contractors run installation support and dining services. Subcontractors handle specialized trades. Engineering firms rotate in for design and assessment. Ordnance teams clear ranges before construction. Each layer can sit under a different employer and a different DBA policy.
That layering is the reason a base name alone rarely answers the carrier question. A worker injured on the flightline might be employed by a prime, a sub, or a joint venture partner. The place of performance is the same for all of them. The insurance is not.
How many DBA claims come out of Jordan?
Here the public record runs into a hard limitation. The Department of Labor publishes DBA case summaries by nation, not by base. There is no Muwaffaq Salti line in the DOL data. There is a Jordan line, and it covers every contractor injury across the entire country.
The cumulative Jordan figure from 2001 through 2024 is 563 total DBA cases. Of those, 40 are death claims. That is the countrywide number, and it includes work at the embassy, at training sites, at other installations, and at Muwaffaq Salti combined. No public field isolates the base from the rest.
The annual trend tracks the operational tempo. Jordan recorded 50 cases in FY2009, then ran in the teens and twenties through the early 2010s. Claims spiked to 48 in FY2016, including 7 death claims, the highest single-year death count in the series. The most recent year, FY2024, shows 59 total cases, the largest annual figure in the dataset.
Those numbers cannot be pinned to Azraq specifically, and any honest analysis says so. What they establish is that Jordan is an active DBA jurisdiction with rising recent volume. For the wider frame, our overview of how US contractor coverage works across Jordan as a regional hub sets the country-level context this base sits inside.
The legal record is thinner still. A full-text search across the administrative law decisions in ClaimTrove turns up 72 documents containing the word Jordan, but most of that count is noise. Jordan is a common surname for claimants, physicians, and attorneys appearing in these files, and a small set of unrelated precedents, including Jordan v. Bethlehem Steel Corp. and Jordan v. SSA Terminals, get cited repeatedly across dozens of otherwise unconnected cases. Narrowed to decisions that actually discuss contractor work in the country of Jordan, fewer than ten remain, and none of them name Muwaffaq Salti or Azraq. A base can generate real claims and still leave almost no fingerprint in the published case law.
Why can't you find the carrier from the base name alone?
The contract data tells you who held the prime awards. It does not tell you which insurance carrier wrote the DBA policy for the injured worker's actual employer. Those are different questions, and the second one is the one that pays claims.
Start with the subcontract layer. A prime named in the award may not employ the person who was hurt. Installation support and dining services rely heavily on subcontracted labor. The DBA policy that responds is the sub's policy, unless the sub was uninsured and the prime becomes statutorily liable.
Then add time. A contract that runs several years can change carriers between renewals, and the carrier on the day of injury is the one that matters. We explain the mechanics in a dedicated piece on why DBA carriers shift over the life of a contract. Guessing the wrong policy year sends the claim to the wrong insurer.
The award records themselves are only a starting point, and reading them well is a skill. Our guide to reading USAspending award records for DBA investigations walks through the fields that actually move an investigation forward. The place of performance and the labor standards flag are useful. The recipient name is a lead, not an answer.
None of the public sources publish the employer-to-carrier link for a base like this. Confirming the carrier means resolving the employer's true legal name, checking coverage filings, and reconciling subcontract chains against the injury date. That is the work ClaimTrove was built to compress. Run a location investigation on Jordan inside ClaimTrove to surface the primes, subs, and carrier evidence tied to a specific award and date.
How do you actually trace a Muwaffaq Salti DBA claim?
The workflow is the same discipline you would use at any active overseas base, with extra attention to entity resolution. Regional hubs share this trait, and the approach that works at Camp Arifjan in Kuwait transfers cleanly to Azraq.
First, fix the injury date. The date controls which policy year and which carrier are in play. Everything downstream depends on it.
Second, resolve the employer's real name. The injury report may say a joint venture or a shortened trade name. Match it to the legal entity that actually held the contract or the subcontract at that base.
Third, separate prime from sub. Confirm whether your client worked directly for a named prime or for a subcontractor several tiers down. The answer decides which policy responds first.
Fourth, pull the coverage evidence. Federal award data, corporate registrations, and coverage filing records together point toward the carrier that wrote the DBA policy in force on the injury date.
Fifth, cross-check the legal record. Even with no base-specific decisions, prior rulings involving the same employer or carrier can reveal how they litigate DBA claims. That context shapes strategy before you file.
The base name will not do this work for you. Muwaffaq Salti is a place, not a policy. The carrier lives in the employer chain, the contract vehicle, and the timeline. Start a ClaimTrove investigation to pull the underlying employer, carrier, and decision data for any contractor injured at Azraq or anywhere else in Jordan.
This tool provides information from public DOL records. It is not legal advice. Always verify with primary sources.