A cashier at a Burger King on Ramstein Air Base slips on a wet tile floor and fractures her hip. A warehouse loader at the AAFES distribution center in Grafenwoehr crushes his hand unloading a pallet. A maintenance contractor servicing movie projectors at the exchange on Camp Humphreys falls from a ladder. All three workers have something in common, and most attorneys get it wrong on the first call.
None of them work for the Department of Defense. None of them work for a traditional federal prime contractor like KBR or Fluor. They work at AAFES, the Army and Air Force Exchange Service, a self-supporting non-appropriated fund instrumentality, and they are almost certainly entitled to Defense Base Act coverage.
AAFES operates the PX and BX network, fast food franchises, gas stations, movie theaters, and recreation facilities on Army and Air Force installations around the world. It employs roughly 35,000 workers globally, a significant portion of them on overseas bases. When those workers are injured abroad, the DBA applies. But the path from injury to carrier identification is unusual, and the documentary trail looks nothing like a standard LOGCAP claim.
This article explains what NAFI status means for DBA eligibility, which AAFES workers qualify, why alias resolution is essential, and what records exist to reconstruct carrier coverage across fiscal years. The investigation is different from a typical contractor claim, and attorneys who treat it like one lose time and leverage.
What Is a Non-Appropriated Fund Instrumentality and Why Does It Matter for DBA?
AAFES is a NAFI. That term carries specific legal weight. A non-appropriated fund instrumentality is a federal entity authorized by Congress but funded entirely through its own revenues rather than through tax dollars appropriated by the legislature. AAFES funds itself through retail sales, concession fees, and vending operations, then returns profits to morale, welfare, and recreation programs on base.
Because AAFES does not receive appropriated funds, it sits in a strange legal position. It is not a federal agency in the conventional sense. It is not a federal contractor either, since no prime contract ties it to a parent department. Courts have described NAFIs as arms of the United States for certain purposes and independent entities for others. For DBA eligibility, what matters is the statutory language at 42 U.S.C. Section 1651.
The DBA extends coverage to employees working under public works contracts on military bases outside the continental United States, and to any work performed on a United States defense base abroad by a contractor of the United States. NAFI operations at overseas exchanges have been held to fall within this reach through a combination of direct statutory inclusion and longstanding Department of Labor practice. The foundational framework is covered in our overview of what the Defense Base Act covers and who qualifies.
The practical result is that AAFES maintains DBA insurance for its contractor workforce overseas, and injured workers can file LS-203 notices and LS-201 claims the same way they would against any other DBA-covered employer. The difference shows up in how you trace the carrier.
Which AAFES Workers Qualify for DBA Coverage?
AAFES employs two broad categories of workers overseas. The first is direct NAF employees, who work for AAFES itself in store operations, food service, warehouse logistics, and administrative roles. The second is contractor and subcontractor personnel who perform services for AAFES under separate agreements, including janitorial services, facility maintenance, IT support, and specialty trades.
Both categories can qualify for DBA coverage when the work is performed on an overseas military installation. Direct NAF employees are covered through AAFES's own policy. Contractor personnel are covered through the contractor's DBA policy, which may or may not be the same carrier. This is where attorneys stumble. Assuming a single AAFES carrier covers every worker on the premises is a quick way to miss the real insurer.
The analysis mirrors the broader question of who is responsible when a subcontractor's employee is injured. The immediate employer carries the primary DBA obligation. If that employer fails to secure coverage, liability can flow up the chain to the next level of the contracting relationship. For an injured janitor at an AAFES store in Okinawa, the first question is not who AAFES uses for its own NAF employees. It is which company issued the janitor's paycheck and what DBA policy that company carried at the time of injury.
Common AAFES contractor injuries include repetitive strain from cashiering and stocking, slip and fall incidents in food service, lifting injuries at distribution centers, burns and lacerations in fast food kitchens, and traffic accidents during delivery routes between on-base locations. These are everyday retail injuries occurring in a military overseas context, and they carry the same DBA entitlements as the more dramatic combat-support injuries that dominate case law.
Why Is Alias Resolution Critical for AAFES Claims?
AAFES appears in federal records under several names. Army and Air Force Exchange Service, AAFES, Exchange, The Exchange, and historical references to the Army Exchange Service from before the 1983 reorganization. ClaimTrove's employer alias database includes 237 mapped aliases, and AAFES is among the entities that require careful normalization before any carrier search returns useful results.
Running a search for just AAFES misses records filed under Army and Air Force Exchange Service. Running a search for Exchange returns noise from unrelated employers with that word in their name. The problem compounds when concessionaires file under their franchise brand rather than the AAFES parent. A Taco Bell on Kadena Air Base may appear in DOL records under the franchisee's corporate name, not under AAFES or Taco Bell Corporation.
This is the same structural problem we address in our discussion of employer name changes and why alias resolution matters. Without a clean employer identity, no carrier search is reliable. With it, the historical record becomes legible.
Concessionaire relationships add a second layer. Many branded food outlets inside exchanges operate under concession agreements with AAFES rather than being owned by AAFES. The concessionaire is the direct employer. The concessionaire carries the DBA policy. AAFES may or may not be named in the claim depending on the theory of liability. Identifying the correct entity first is prerequisite to identifying the correct carrier.
How Do You Trace the DBA Carrier for an AAFES Claim?
AAFES carrier coverage does not come from a mandatory agency contract. Unlike USAID, which has used Allied World continuously since 2010 under AAPD mandates, or State Department, which funneled DBA through CIGNA and then CNA during specific windows, AAFES contracts DBA coverage on the open market. The mandatory agency contract framework does not apply here.
That means carrier identity shifts over time based on procurement cycles, market conditions, and AAFES's own risk management decisions. What was true in FY2014 is not necessarily true in FY2019. An attorney working an AAFES claim for a 2021 injury cannot rely on assumptions pulled from an older case file.
The investigation uses the same core sources as any DBA carrier search. FOIA database results. Coverage card data is particularly useful for AAFES because it ties carrier identity to specific employer names and effective dates, which is exactly what you need when AAFES appears under multiple aliases. The full methodology is described in our walkthrough on how to identify the correct DBA insurance carrier for your claim.
For concessionaire cases, the trail runs through the concessionaire's own records, not AAFES's. USAspending entries, SAM.gov registrations, and state insurance filings for the concessionaire corporation will often surface the carrier faster than any search tied to the AAFES parent name.
What Records Exist for AAFES DBA Investigations?
AAFES and its contractor network appear across several of the federal datasets ClaimTrove indexes. OWCP coverage cards include AAFES filings and concessionaire filings at overseas locations. Case summary data captures claim histories with enough specificity to identify carrier patterns over multi-year windows. OALJ and Benefits Review Board decisions include AAFES-related matters, though the volume is smaller than for large LOGCAP contractors.
One detail that surprises attorneys: AAFES does not appear prominently in USAspending or FPDS, because its procurements are NAFI procurements rather than appropriated contract actions. A carrier search that starts at USAspending will come up empty. The coverage card data and DOL claim histories are the more productive starting points.
FOIA contractor databases and SAM.gov are also less useful for pure AAFES questions, though both can surface concessionaires and subcontractors operating inside the exchange footprint. For concessionaire cases, SAM.gov entity registrations often provide the corporate parent and address needed to pivot into broader carrier research.
Once the employer is correctly identified and the injury date is fixed, the DBA claims process proceeds normally. Notice of injury to employer, LS-201 and LS-202 filings to OWCP, coordination with the carrier on compensation and medical, and preparation for informal conference or formal hearing as the case requires.
Find the Carrier That Covered Your AAFES Claim
AAFES claims reward careful entity work and penalize shortcuts. The NAFI status, the alias tangles, the concessionaire layers, and the absence of a mandatory carrier contract all push the investigation toward primary source documents rather than general assumptions. The good news is that the records exist. The harder news is that stitching them together by hand takes hours per claim.
ClaimTrove's employer database includes AAFES alias mappings, concessionaire relationships, and historical carrier signals drawn from coverage card filings, DOL case summaries, and OALJ decisions. For any given fiscal year and overseas location, the system surfaces the most probable carriers with a confidence score and the underlying evidence. Run your AAFES investigation through ClaimTrove to skip the alias guesswork and get directly to carrier options supported by primary sources.