On September 3, 2025, OFAC announced a $1,610,775 settlement with Fracht FWO Inc., a Houston-based freight forwarder, over a single 2022 shipment of automobile parts from Mexico to Argentina. The contract for that shipment listed a Venezuelan aircraft tail number and routed through a Venezuelan carrier. 

Fracht's own staff saw the address, along with the tail number and the carrier's known ties to Venezuela's state airline, and the transaction proceeded anyway. Noticing a geographic signal was treated as the end of the screening process rather than the start of one, and therein lies the failure. 

A Flagged Address Wasn't Enough to Stop This Shipment

According to OFAC's enforcement release, Fracht's Mexico affiliate was asked to arrange urgent air transport for a customer's cargo in May 2022. Under time pressure, Fracht contracted with Empresa de Transporte Aéreocargo del Sur S.A., known as EMTRASUR, without conducting the sanctions screening or legal review of its own compliance procedures required. EMTRASUR is the cargo arm of Consorcio Venezolano de Industrias Aeronáuticas y Servicios Aéreos, or CONVIASA, Venezuela's state-owned airline, which had been designated by OFAC since 2019 and named to the SDN list outright in February 2020. 

The aircraft used for the flight had itself been separately blocked for its prior ties to Iran's Mahan Air, and the flight crew were Iranian nationals, implicating a second sanctions program on top of the first.

The Venezuelan tail number was written into the contract, the routing included a stop in Venezuela, and internal communications later reviewed by OFAC showed that Fracht personnel, including senior staff, were aware of the connection to CONVIASA before the transaction closed. 

OFAC classified the conduct as egregious, in part because the violation had already been identified by another government agency before Fracht submitted its own disclosure, and set the penalty at $1,610,775 against a statutory maximum of $2,147,700. A designated entitiy's name was in hand and never screened against a list.

The lesson is that an address, even a correctly flagged one, is not itself a control, but a prompt to run the actual controls: who is the counterparty, are any of the named parties state-linked or politically exposed, and does the specific vessel or aircraft carry its own sanctions history.

Why Address Is a Supporting Signal, Not a Primary Control

Address-based screening fails for reasons that have nothing to do with inadequate execution. A destination or shipper address is a piece of metadata attached to a specific booking, and metadata is cheap to reuse, reassign, or route around.

Addresses get reused by unrelated tenants. A commercial building in a port city can house dozens of trading companies over a few years, and a sanctioned party that vacates a premises does not remove that address from a screening system's memory of what "clean" looks like, nor does a new, legitimate occupant automatically inherit suspicion. Screening the address tells you what used to be true, not what is true now.

Sanctioned parties operate from unlisted premises. Sanctions designations name individuals, vessels, and entities. They do not typically publish a comprehensive real-time list of every building a designated party has ever operated from, and a sophisticated counterparty structures its paperwork specifically so that the address on file is unremarkable.

Transshipment through a clean address hides the actual counterparty. Cargo that transits through a legitimate port or logistics hub before reaching its real destination can carry paperwork that never lists the true endpoint at all. The address that appears on the booking is accurate and clean. It is also not the address that matters.

Fracht's case shows a fourth failure mode that is arguably more common than any of these: the address was correct, visible, and even a known red flag, and it still did not function as a control because nothing downstream of noticing it required party-level or ownership-level resolution before the shipment moved.

{{snippets-guide}}

What to Screen Instead, in Priority Order

Consignee and notify party names, at booking and on every list update

This is the baseline check that address based screening is often mistaken for. Every named party on a bill of lading, the shipper, consignee, and notify party, should be screened against denied party and sanctions lists as actual entities, not as an artifact of the jurisdiction or address they happen to be located in. This is where Fracht's process should have started: EMTRASUR was named directly in the charter contract, and CONVIASA was named in Fracht's own internal correspondence.

The less obvious half of this requirement is timing. A name cleared at onboarding is cleared against the list as it stood that day, and OFAC updates the SDN list multiple times per month. OFAC's December 2024 settlement with SkyGeek Logistics, a New York-based aviation products supplier, turned on exactly this gap: two UAE-based counterparties were designated mid-relationship, and SkyGeek's screening software was not configured to pick up designations published the same day, so orders placed on thed ate of a designation screened clean. A refund to the same party months later was processed without any-rescreening at all. OFAC noted that the sanctions nexus was identificable from information already in SkyGeek;s own customer records. Screening at booking without continuous re-screening against list updates procudes a record of having checked, not a control.

Politically exposed persons and state-linked counterparties

A large share of sanctions exposure in trade and logistics runs through state-owned enterprises, and state ownership shows up in a counterparty's leadership before it shows up in a list entry. Under FATF and EU definitions, senior management and board members of state-owned enterprises are politically exposed persons, so screening a counterparty's named directors and officers against PEP data surfaces state affiliation even where the entity itself returns a clean name match.

That is the shape of the EMTRASUR booking: a national airline's cargo arm, its leadership drawn from Venezuelan state aviation. A PEP hit does not by itself prohibit a transaction. It routes the booking into enhanced due diligence, where the CONVIASA relationship and the aircraft's designation history both surface. Paired with adverse media screening, the picture arrives faster still, since both the aircraft's Mahan Air history and EMTRASUR's own reporting profile were public well before Fracht's disclosure.

Corporate ownership is the related question. Where a counterparty is 50 percent or more owned in aggregate by one or more blocked persons, OFAC treats it as blocked whether or not it is named on the SDN list. Ownership resolution is a distinct capability from list screening and is available as an add-on from some providers;  OFAC's 50 Percent Rule covers how the rule works and when it applies.

Vessel and aircraft identifiers

Registration and tail numbers, and their maritime equivalent, IMO numbers, are a distinct data point from either the operator's name or the shipment's address, because a vessel or aircraft's own designation history travels with the specific asset regardless of who is currently operating it or what address appears on the paperwork. OFAC's October 2024 maritime guidance walks through exactly this scenario: a vessel's identity, not its owner's name or its port of call, is often the fastest way to catch a previously sanctioned asset that has changed hands or been renamed. In Fracht's case, the aircraft's tail number alone, checked against OFAC's records, would have identified it as property already blocked for its Mahan Air connection, independent of any question about EMTRASUR or CONVIASA.

Denied party and entity lists

Beyond OFAC's SDN list, a full screening posture covers the Bureau of Industry and Security's Entity and Denied Persons Lists, the EU and UK consolidated lists, and any relevant sectoral or non-SDN designations. Different regulators maintain different lists for different reasons, and a shipment can clear OFAC screening while still exposing a company to BIS export control liability.

Freight forwarder and broker intermediaries

The party arranging the shipment on your behalf is itself a screenable entity, not a trusted pass-through. Fracht contracted through a Mexico-based logistics broker under time pressure without vetting that broker's own history or the specifics of what it was proposing. An intermediary that arranges a bad transaction carries the same exposure as the shipper or consignee who requested it.

The Worked Example: A Shipment That Passes an Address Check and Fails a Party Check

An address-only check saw a Venezuelan tail number and Venezuelan routing, and functionally treated that as the entire screening event, a flag noted, not escalated. A consignee and carrier name check would have surfaced EMTRASUR by name at the contracting stage, before the charter agreement was signed, and a screen of the CONVIASA name already circulating internally would have returned an SDN match outright. A PEP check on the counterparty's named officers would have flagged the carrier as state-linked and forced the booking into enhanced review rather than urgent execution. An adverse media check would have returned the aircraft's Mahan Air history and EMTRASUR's own reporting profile from public sources. An identifier check on the specific aircraft's tail number would have independently confirmed the plane itself was blocked property tied to Mahan Air, a second, entirely separate reason to stop the shipment. A denied party and entity list check would have reinforced the same conclusion across multiple sanctions programs at once, since the transaction implicated Venezuela, Iran, proliferation, and terrorism authorities simultaneously. And an intermediary check on the affiliate that arranged the charter in the first place would have added a further layer of scrutiny on how the transaction was sourced.

Any one of these checks, run as an actual control rather than a downstream afterthought to a geographic signal that had already been noticed, would have stopped the shipment. None of them ran with enough authority to override the commercial pressure to move urgent cargo.

{{snippets-case}}

Building the Priority Order Into a Screening Workflow

The practical question for a logistics compliance team is not whether these checks matter, it is which ones can run automatically at booking and which require a human to stop the shipment and escalate. Name-based screening against consignee, notify party, and intermediary fields is the most straightforward to automate at the point of booking, since it requires no more than the data already captured on a bill of lading or charter agreement, and the same screening should re-run automatically against every list update rather than only at the point of transaction. PEP screening on counterparty officers is likewise automatable at onboarding and re-runnable on a schedule, since PEP status changes with appointments rather than with individual bookings; its output is a review trigger rather than a block, so the workflow requirement is that a PEP hit on a state-linked counterparty carries the authority to hold a shipment pending review. Vessel and aircraft identifier checks are well suited to automation, since registration and tail numbers are stable data points that can be checked against blocked property records without ambiguity. Denied party list screening across multiple regulatory regimes is a coverage question more than a workflow question, and the practical requirement is simply ensuring the screening tool checks all the relevant lists, not only the most familiar one.

The sequencing matters because it determines what happens when time pressure hits, which is exactly the condition under which Fracht's failure occurred. A workflow where geography is the first thing anyone looks at, and party identity is the last thing anyone acts on, will keep producing exactly this outcome.

Screening Priority Checklist: What Each Check Catches That Address Alone Misses

• Consignee, notify party, and carrier names: Catches the actual legal parties to the transaction, independent of address. Automation potential is high, as this is automatable at booking against sanctions and denied party lists.
• PEP status of counterparty officers and directors: Catches state-owned and state-linked counterparties whose corporate name still returns a clean list match, including in the window before designation. Automation potential is high at onboarding and on a schedule, but treat hits as mandatory enhanced review rather than automatic rejection.
• Vessel and aircraft identifiers: Catches specific blocked assets that have changed operators, names, or routing. Automation potential is high, as this is automatable against blocked property and registration records.
• Denied party and entity lists (OFAC, BIS, EU, UK): Catches exposure under regulatory regimes beyond a single sanctions list. Automation potential is high, but this is a coverage question, so ensure screening spans all relevant lists.
• Freight forwarder and broker intermediaries: Catches risk introduced by the party arranging the shipment, not just the shipper or consignee. Automation potential is medium, so screen intermediaries at onboarding, not only per transaction.

Our Sanctions Screening for Freight Forwarders: A Practical Onboarding Guide covers how to build these checks into a booking workflow without adding delay to time-sensitive shipments. Our Vendor Selection Guide walks through how to evaluate whether a screening provider actually covers ownership resolution and vessel identifiers, not just name matching against a single list. You can even build your own checklist with an interactive calculator.

sanctions.io is a highly reliable and cost-effective solution for real-time screening. AI-powered and with an enterprise-grade API with 99.99% uptime are reasons why 300+ customers globally trust us with their compliance efforts and sanctions screening needs.

To learn more about how our sanctions, PEP, and criminal watchlist screening service can support your organization's compliance program: Book a free Discovery Call.

We also encourage you to take advantage of our free 7-day trial to get started with your sanctions and AML screening (no credit card is required).

‍