Fracht FWO OFAC Settlement: Lessons for Forwarders

Most forwarders screen the customer on a booking. The Fracht FWO settlement is about the rest of it: the broker, the carrier, the carrier's owner and the aircraft, all handled under a deadline. OFAC's release on it is unusually detailed about how a forwarder's own process broke down, which makes it worth reading line by line.

What happened

According to OFAC, in May 2022 a manufacturer asked Fracht's Mexico affiliate to move car parts from Mexico to Argentina on an urgent basis, and Fracht took over the search for an aircraft. Through a broker in Mexico, Fracht signed a charter contract on May 28, 2022 that named the carrier as Empresa de Transporte Aéreocargo del Sur S.A. (EMTRASUR), a wholly owned subsidiary of the Venezuelan state airline CONVIASA, which OFAC had identified on the SDN List on February 7, 2020. The aircraft, registered YV-3531, was the same airframe OFAC had listed in 2012 as blocked property of Iran's Mahan Air under its earlier registration EP-MND, and, unknown to Fracht at the time, it flew with an Iranian crew. OFAC found that Fracht compensated EMTRASUR in two transactions worth $995,000 and that the apparent violations were egregious and not voluntarily self-disclosed. Fracht agreed to pay $1,610,775 to settle its potential civil liability for apparent violations of the Venezuela, Iran, terrorism and proliferation sanctions programs.

Where the control failed

The striking thing about this case is that Fracht had the right policy on paper. OFAC found that the vice president who signed the charter did so "without undertaking sanctions screening or internal legal review, contrary to Fracht's compliance policies and procedures." The control existed. Nothing in the process stopped a senior employee from signing without it.

So the root problem was governance, and the screening gap followed from it. A screening step that depends on the person under commercial pressure choosing to run it will be skipped exactly when it matters most. The practical lesson here is that screening has to sit somewhere a deal cannot get past without it: contract signature, vendor setup, or the first payment. The release says Fracht later made legal review and sanctions due diligence mandatory before any customer, airfreight or ocean freight contract is executed, and routed all new vendors through compliance approval. Read the other way round, the remediation describes the hard stops that were not in place in May 2022.

The second failure was scope. Forwarders tend to think of screening as a customer onboarding task. In this case the customer was a manufacturer, and nothing in the release suggests the customer was a problem. The exposure came from the supply side: the broker, the carrier, the carrier's parent and the aircraft. OFAC's own compliance notes for this case list shippers, carriers, vendors, owners, operators, brokers, affiliates and agents as counterparties a forwarder deals with. If your screening only covers the party that pays you, most of that list is invisible.

The third failure is the one most specific to freight: the aircraft itself was on the SDN List, but not under the registration on the contract. According to the release, Mahan Air transferred the aircraft to CONVIASA in or around October 2021, and EMTRASUR re-registered it from EP-MND to YV-3531. OFAC found the transfer did not unblock it. The SDN entry still carried the old tail number and the manufacturer serial number, 23413, which does not change when a plane is re-registered. Since the release says the aircraft stayed listed under its former tail number, a search for "YV-3531" would not have matched that entry. The serial number was the stable identifier, and you only have it if you ask for it.

Ownership is the last piece. The SDN entry cited in the release is CONVIASA's. EMTRASUR is described as its wholly owned subsidiary and as a blocked entity. OFAC's compliance notes for this case state that property can be blocked because of who owns it, whether or not it appears on the SDN List. A carrier can therefore be off-limits even when its own trading name produces no hit, which is the same logic behind the 50 Percent Rule. Working out who owns a charter carrier requires additional due diligence beyond list screening.

Red flags that were visible at the time

None of this required inside knowledge. According to the release, the contract itself named EMTRASUR and gave its address in Venezuela. The broker sent the flight details to the vice president who signed: a tail number starting with "YV", which the release notes indicates a Venezuelan aircraft, an inbound flight from Venezuela, and a layover in Venezuela before Argentina. The broker had recently been recommended to that vice president by a mutual contact, so there was no track record. And the whole job was being run against a deadline, which OFAC notes senior executives were worried about.

A reasonable reviewer would have asked four questions before signing: who is the operating carrier and who owns it, what is the aircraft's registration and serial number, why does a Mexico to Argentina flight stop in Venezuela, and what do we know about this broker. Three of the four lead straight to Venezuela, and the first one leads to CONVIASA.

There was also a second chance. On June 4, 2022, when the aircraft arrived two days late and EMTRASUR asked for a $110,000 late fee, Fracht's CEO asked in a group chat which aircraft they were using. A vice president answered that it was EMTRASUR, a subsidiary of CONVIASA. OFAC states the CEO did not know either company was blocked or that screening had been skipped, and the group decided to keep the plane and pay the fee, which Fracht paid on June 7. A new payment request from a new party in the middle of a shipment is a natural moment to re-screen. Here, the name of a blocked airline had just been typed into the chat.

How OFAC weighed it

OFAC treated this as egregious and not voluntarily self-disclosed. Fracht did make a disclosure on its own initiative after learning about the Iranian crew, but the release says OFAC and other U.S. government agencies already knew about the charter and the aircraft's detention in Argentina. OFAC's Enforcement Guidelines do not treat a disclosure as voluntary when the government already has the information. Combined with the egregious finding, that set the base penalty at the statutory maximum, $2,147,700. The settlement of $1,610,775 is exactly 75 percent of that base.

The aggravating factors explain the egregious call. OFAC found the violations were not willful but showed reckless disregard, mainly through the conduct of two vice presidents who bypassed the compliance process despite significant red flags. It found that managers, including senior officials, knew the contract was with EMTRASUR and that payments were going to it. It counted roughly $935,000 in direct benefit to EMTRASUR (the $825,000 of the charter price that reached it plus the $110,000 late fee). And it weighed Fracht's size and sophistication as a global forwarder.

On the other side, OFAC credited the absence of any Finding of Violation or Penalty Notice in the prior five years, substantial cooperation, and remediation: terminating the employee who signed the contract, adding sanctions language to air cargo contract templates, hiring compliance staff (nine full-time employees at the time of the release), spending more than $1.0 million a year on compliance, and adding audits, quarterly reporting and recurring training.

Two things stand out for a compliance team. First, OFAC focused on what managers knew and did, not on whether a screening tool existed. The reckless-disregard finding rests on people skipping a process and ignoring red flags. Second, timing decided the disclosure question. Once another agency had found the problem, Fracht's own disclosure could not earn voluntary self-disclosure credit. Under the Guidelines, an egregious case that is voluntarily self-disclosed starts from one-half of the statutory maximum instead of the full amount.

Mapped to OFAC's Framework for OFAC Compliance Commitments, this case sits mostly in two components. Management commitment: senior managers learned the carrier's parent in a chat and approved a further payment. Internal controls: the policy existed but nothing enforced it at the point of contract or payment. The CEO not recognizing CONVIASA as blocked also points to a training gap at the senior level, though the release does not frame it that way.

What a small forwarder should check this week

List every party on your last five urgent or charter bookings, not just the customer: shipper, consignee, notify party, broker, operating carrier, aircraft or vessel operator, and whoever actually receives your payment. Check that each one was screened before you signed.
Ask for the identifiers that do not change. For aircraft, get the registration and the manufacturer serial number. For vessels, get the IMO number. Search OFAC's published SDN data for those numbers directly, since names and registrations change.
Write down your stop signs. At minimum: a carrier address, registration prefix or routing stop in a sanctioned jurisdiction (the release itself flags "YV" for Venezuela and "EP" for Iran), a carrier that belongs to a state airline, and a broker with no history with you.
Tie screening to payment. Accounts payable should not pay a new carrier or broker unless there is a screening record dated before the contract. This is the cheapest hard stop a small team can add.
Decide who can approve under time pressure, and what they cannot waive. An urgent-shipment rule should say compliance can be reached the same day and that nobody, including owners and senior managers, can skip screening to save the booking.
Re-screen when something new appears mid-shipment. A new invoice, a late fee, a substitute aircraft or a new agent is a new counterparty.
Keep the record. Save what was screened, when, the result, and who approved the booking. It is also how you show that the check came before the contract, not after.

Where software helps and where it doesn't

Screening software is good at the repetitive part. Sanctix checks names such as a carrier, broker or payee against the OFAC, EU, UN and UK lists, and on plans that include monitoring it re-checks saved entities when those lists update. It also keeps an audit trail of what was screened, when and with what result, which is the evidence a team needs when it has to show that screening happened before a contract was signed. If you run Odoo, the same checks can run there through the REST API. CONVIASA, the parent named in the June 4 chat, has had its own SDN entry since February 2020, so checking it by name is the kind of check list screening is built for.

Name screening alone would not have caught the re-registered aircraft. Sanctix accepts one ID number per screen and matches it exactly against the identifiers the lists publish. A globally unique identifier, such as a crypto wallet address, an IMO number or a long aircraft manufacturer serial number, finds the listed record whatever name is entered. Short numbers do not: an all-digit number needs at least seven digits to find a record on its own, so a five-digit serial number like this aircraft's 23413 counts only when the name also matches the listed record, and a tail number, which can be reassigned, is held for review rather than blocked. For an aircraft like this one, the check still needs a direct search of the published SDN data or a person who knows to look. Software also cannot tell you who owns a charter carrier that is not itself listed, why a route stops in Venezuela, or whether a vice president skipped the step entirely. Those need due diligence, a clear escalation rule, and someone with the authority to say no.

If you want screening on every party in a booking to be a routine step rather than something people remember under pressure, you can sign up free and screen your own carriers and brokers, or compare plans.