A paralegal opens a new DBA intake. The client worked as a range instructor at a combat training center in the Middle East, teaching host-nation soldiers on an instrumented live-fire range. The employer on the injury paperwork reads "Cubic Defense Applications." That should be a clean start. It is not.
Type "Cubic" into any federal database and the results split apart. You get Cubic Corporation, Cubic Defense Applications, Cubic Transportation Systems, and several other legal entities. You also get a wave of unrelated firms that simply share the letters, from office-furniture sellers to a solar company. None of that tells you who insured the injured worker.
Cubic is a training-and-simulation prime, not a logistics giant like KBR or Fluor. That changes the shape of the DBA problem. Its overseas footprint is smaller and more specialized, spread across ranges, simulation centers, and advisory missions rather than sprawling base-operations contracts. Fewer records exist, and the ones that do sit under different corporate names and different contract vehicles.
This profile walks through what Cubic does overseas, which field roles carry Defense Base Act exposure, and why the carrier answer resists a quick lookup. Carrier identity here depends on the specific entity, contract, agency, and injury date. That is exactly the kind of question that rewards a structured investigation over a single search box.
Who Is Cubic Corporation and What Does It Do Overseas?
Cubic Corporation is a San Diego-based defense and transportation technology firm founded in 1951 by Walter J. Zable. For decades it operated through distinct business lines. One handled transportation fare systems. Another handled defense electronics and secure communications. A third, long branded as Cubic Global Defense, built the training and simulation programs that put civilians on overseas ranges.
The training arm is the piece that generates DBA exposure. Cubic builds live, virtual, and constructive training systems. That includes instrumented ground combat training centers, air combat training pods, laser-based force-on-force gear, and simulation software used to rehearse missions before they run for real.
Our federal entity data reflects this focus directly. Cubic Defense Applications is registered under a professional and management development training industry code and does business under the name Cubic Ground Training. That single registration detail tells you the company is in the business of teaching, and teaching overseas is what pulls its people into Defense Base Act territory.
Ownership shifted recently. In 2021, Cubic was taken private by the investment firms Veritas Capital and Evergreen Coast Capital. A private-equity acquisition can reorganize subsidiaries and renegotiate insurance programs, which matters when you are trying to match a carrier to an injury date that straddles the transaction.
Which Cubic Field Roles Carry Defense Base Act Exposure?
The Defense Base Act reaches employees working overseas on US government contracts or US-funded work. Training and simulation deployments create a specific cluster of at-risk roles. These are not warehouse or convoy jobs. They are technical and instructional positions that happen to sit inside a foreign military base or range.
Watch for range instructors and observer-controllers who run force-on-force exercises. Watch for field service representatives who install and maintain training instrumentation. Watch for simulation technicians, systems integrators, and software engineers embedded at a combat training center. Watch for advisors who coach host-nation forces under a security cooperation program.
Every one of these roles can trigger coverage the same way a logistics worker's does. The FAR 52.228-3 workers' compensation clause flows Defense Base Act obligations into the contract, and the statute at 42 U.S.C. 1651 extends the Longshore Act overseas. If the contract is US-funded and performed abroad, the field engineer on the range is covered just like anyone else on the base.
The zone-of-special-danger doctrine matters here too. Trainers living on or near a foreign base are often covered for injuries that happen off the clock, because remote overseas assignment itself creates the risk. A simulation technician hurt at base housing may still have a compensable claim. That expands the pool of Cubic-connected injuries an attorney should screen for coverage.
Why Does the Cubic Name Fragment Across Federal Records?
The biggest practical obstacle in a Cubic file is the name itself. Our federal entity registry, drawn from more than 865,000 records, returns multiple distinct legal entities carrying the Cubic name. Each has its own CAGE code and its own state of incorporation. Cubic Corporation registers out of Delaware. Cubic Defense Applications registers out of California. Others cover transportation, digital solutions, secure communications, and learning platforms.
That fragmentation is not cosmetic. The entity that signed a training contract is the entity whose insurance program controls the claim. If a claim names "Cubic Corporation" but the work ran under Cubic Defense Applications, you can chase the wrong records for weeks. Resolving which legal entity actually employed the worker is step one, and it is where resolving employer name variations across federal records saves the most time.
The noise problem compounds it. A raw search for the string "Cubic" also surfaces unrelated companies, from cubicle installers to a solar manufacturer to a materials firm. A human reader can filter those out. An automated match cannot always, which is why a coverage search that keys on the exact registered entity and its CAGE code beats a loose name search every time.
What Does the Contract and FOIA Data Show About Cubic Overseas?
Contract data is where a Cubic investigation gets traction. Our overseas contract-award dataset, which spans 43,298 prime awards across 193 countries, records Cubic Defense Applications with places of performance including Jordan and Lebanon. Those are real overseas performance locations that put Defense Base Act coverage squarely in play.
Those award records anchor the investigation to a place and a period. Once you know the awarding agency and the performance dates, you can start reasoning about which insurance program applied. That works because federal contract data narrows the carrier field long before you ever see a policy declarations page. The contract is the bridge between an employer name and a carrier.
FOIA database results add another layer for the Afghanistan era. Presence records for that period return entries referencing the Cubic name across prime and subcontractor fields. That kind of corroboration confirms a company operated in a theater during a window, which is powerful when an employer disputes that a worker was ever deployed there. It does not name a carrier, but it locks down the where and the when.
If you are building the file, start a ClaimTrove investigation on the specific Cubic entity. It pulls the contract awards, performance countries, entity identifiers, and presence records into one timeline. That consolidated view is the foundation every carrier question sits on.
Why Can't You Just Look Up Cubic's DBA Carrier?
Here is the hard truth for a Cubic file. No single public record names Cubic's DBA carrier outright. Our mined employer-to-carrier knowledge base, built from thousands of adjudicated proceedings, does not resolve Cubic to one clean carrier answer. The company simply has not generated the volume of litigated coverage disputes that a KBR or a DynCorp has.
Carrier identity also moves with time and contract. Training programs get rebid, and a new award can bring a new insurer. Different awarding agencies default to different coverage arrangements. A Cubic contract run for the Army may sit under a different program than one run for the Air Force or the State Department. This is why DBA carriers shift over time for the same employer, and why an injury date is not a detail you can skip.
The 2021 ownership change is another moving part. When private-equity buyers acquire a defense contractor, they often restructure entities and consolidate insurance. An injury before the transaction and an injury after it can point to different programs. Tracing that requires understanding the corporate timeline. Tracing employer corporate history for a DBA claim is the discipline that keeps you from matching a worker to a carrier that no longer covered the entity.
Finally, the entity fragmentation returns to bite you at the carrier stage. To pin the right insurer, you first need the right entity, and the surest way to fix that is the federal identifier. Using the CAGE code and UEI to lock down the exact Cubic entity stops you from attributing a claim to a sister company with a completely different policy.
How Should Attorneys Approach a Cubic DBA Investigation?
Treat a Cubic claim as a three-part sequence, not a one-line lookup. First, resolve the exact legal entity that employed the worker. Use the CAGE code, the UEI, and the registered business name rather than the loose word Cubic. This alone eliminates the false matches and the wrong-subsidiary trap.
Second, anchor the claim to a contract, an awarding agency, and a performance period. The contract award tells you where the work happened and who funded it. That is what makes the coverage argument under FAR 52.228-3 and 42 U.S.C. 1651, and it is what scopes the carrier question to a specific window.
Third, run the carrier analysis against that window rather than against the company in the abstract. Because Cubic lacks a single mined carrier answer, the strongest path is to assemble every signal at once and let the evidence weight itself by proximity to the injury date. Run this employer through ClaimTrove to resolve the entity, aliases, and subsidiaries, then surface the carrier candidates by contract period in one report instead of a week of manual cross-referencing.