How does the Novorossiysk to Turkish-Mediterranean origin-laundering pattern defeat bill-of-lading screening?

It defeats bill-of-lading screening because nothing illegal happens at the point your screening looks. In an OilFlow Intelligence first-party investigation, we auto-tagged a dark fleet cluster at a Turkish anchorage where Novorossiysk loadings are re-routed via Turkish-Mediterranean ports and subsequently offered downstream on bills of lading claiming neutral origin. The cluster cross-references the OFAC Russian Harmful Foreign Activities sanctions programme and the G7 price cap regime, and the practical consequence for an MLRO is this: a control set built on load port and BL origin will clear this cargo on every pass, because by the time the document reaches you the load port on the paper is Turkish and the origin field says something other than Russia.

This is a documentation route, not a smuggling route. The crude does not change. The paperwork does.

What the AIS cluster actually showed

Our observation is narrow and we will keep it narrow. We identified a Russia to Türkiye dark fleet inbound pattern in which Novorossiysk loadings are re-routed through Turkish-Mediterranean ports, with bills of lading presented downstream claiming neutral origin. The tag was raised automatically at the AIS cluster anchor stage, at a Turkish anchorage, and it is graded confirmed. Source: projectrussiaturkeydarkfleet.

What we are not publishing: vessel names, IMO numbers, cargo volumes, counterparty identities beyond the cluster designation, or any estimate of exposure. We do not hold those as first-party facts, so they do not appear here. The only named entity in this teardown is the Novorossiysk-Turkish-Med Dark Fleet Cluster itself, plus the public regulatory frameworks it touches.

The mechanism, step by step

The pattern has five stages. At each one, the gap between what a counterparty sees and what actually happened widens.

Stage 1. Load at Novorossiysk. A cargo lifts at a Russian Black Sea port. Under the G7 and EU price cap architecture, Western service providers may lawfully touch that cargo if it moves at or below the cap, and the compliance evidence for that is an attestation supplied up the chain. Nothing here is hidden. The counterparty who eventually receives the offer, however, never sees this stage at all, because it will not be described in the document they are handed.

Stage 2. Transit with AIS discontinuity. The voyage from the Black Sea to the Turkish Mediterranean coast is short and unremarkable. What is remarkable is a gap in position reporting that is inconsistent with the geography and the traffic density of the route. AIS silence is not itself proof of wrongdoing, and we treat it as an indicator rather than a finding. It matters because it removes the continuous track that would otherwise tie the Turkish port call to a Black Sea origin.

Stage 3. The Turkish-Mediterranean port or anchorage call. This is the pivot. Türkiye is not a price cap participant and does not apply EU import restrictions, so the arrival is lawful under local law. The tell is behavioural. A genuine commercial discharge has a dwell profile, berth occupancy, shore tank movement, and an onward domestic or refinery logic. A relay call is short, anchorage-weighted, and the barrels leave in substantially the form they arrived. Our cluster anchor sits at exactly this point in the sequence.

Stage 4. Re-documentation. A new bill of lading is issued describing a lift from a Turkish-Mediterranean port. The date is correct. The port is correct. The vessel details are correct. The origin representation is the fiction. Every verifiable field on the document survives verification, which is precisely why the document is effective.

Stage 5. The onward offer. The cargo is presented to a buyer, a financier, or a trade insurer as neutral-origin material, frequently through an intermediated chain that opens with an ICPO, then an LOI, then a request for a DLC MT700 or a transferable instrument. The buyer's compliance team screens the seller, the vessel, and the load port shown on the BL. All three clear.

The deception lives in the paperwork layer

Compliance controls in crude and products are built around two assumptions: that the physical chain and the documentary chain describe the same event, and that origin is a fact recorded at the point of loading. This pattern breaks the first assumption and exploits the second.

The cap regime is attestation-based by design. Service providers rely on representations passed to them rather than on independent verification of price and origin at each hop. That model is workable when the chain is short and the parties are known. It degrades badly once a relay call inserts a lawful, verifiable, and entirely misleading intermediate event into the record. The attestation is no longer false, it is simply about the wrong voyage.

EU import restrictions on Russian-origin seaborne crude treat origin as determinative. That makes the origin field on a bill of lading the single highest-value forgery target in the entire trade cycle, and it explains why this pattern targets documentation rather than physical concealment. Physical concealment is expensive and detectable. Rewriting an origin field is neither.

Where the mandate chain hides it: layer cake documentation

By the time an offer reaches a Western buyer, the mandate chain has usually grown two or three layers past the party that arranged the relay. Each layer receives the neutral-origin BL from the layer above and passes it down in good faith, or in something that can plausibly be presented as good faith. This is a layer cake in the classic sense: the function of each additional tier is not commercial, it is evidentiary distance.

FATF Recommendation 10 requires customer due diligence extending to beneficial ownership and to understanding the nature and purpose of the relationship. Applied properly to a mandate chain, that means asking who arranged the Turkish port call and on whose account the cargo sat during the relay. Applied as a box-tick against the immediate counterparty only, it produces a clean file and no visibility at all. The intermediaries are frequently not sanctioned entities, do not appear on the OFAC SDN List, and would not be caught by list-based screening in any configuration.

The same document mechanics are not specific to crude. Any offer arriving with a Turkish-Mediterranean BL and a neutral origin representation deserves the same treatment, whether the description reads crude, fuel oil, or EN590.

Why load-port and BL-origin screening passes this cargo every time

Set out plainly:

• List screening returns nothing, because the presenting entities are typically not designated.
• Load-port screening returns a Turkish-Mediterranean port, which is not restricted.
• BL-origin screening returns a neutral origin, which is the representation under test and therefore useless as a control.
• Attestation review returns a document that is internally consistent with the voyage it describes.
• Vessel screening may return an ageing tanker with opaque ownership and thin P and I cover, which is an indicator, not a determination.

The only control that engages the actual deception is behavioural: AIS discontinuity on a Black Sea to Turkish-Mediterranean leg, followed by a short-dwell relay call whose profile is inconsistent with a genuine commercial discharge, followed by an onward offer on a Turkish-Mediterranean BL. That sequence is the signal. Screen the sequence, not the document.

If you want to see how we tag clusters of this type at the AIS anchor stage, request a walkthrough of the OilFlow Intelligence cluster feed or subscribe to the research desk newsletter.

Market context, and what today's data does not support

Today's run is partial. Four of five feeds returned. Real source values available at time of writing: Brent 88.52 (+1.45), WTI 82.40 (+1.15), Dubai 86.52, the FX table, and USD per metric tonne freight flat rates.

Unavailable: product prints, crack spreads, Worldscale assessments, BDTI and BCTI. We are not going to infer them. Any netback or margin figure attached to this pattern today would be a construction rather than an observation, and constructions do not belong in a file that may end up in front of a regulator. Where economics are discussed internally, use flat rates on a USD per metric tonne basis and mark everything else unavailable.

What compliance teams should do

Re-sequence the control. Origin should be tested as a claim requiring corroboration, not accepted as a field on a document.

1. Add a voyage-continuity check to trade onboarding. For any cargo offered on a Turkish-Mediterranean bill of lading, reconstruct the full track for the preceding leg. Flag AIS gaps that are inconsistent with route geography and record the reconstruction in the file.
2. Profile the port call, not just the port. Dwell time, berth versus anchorage, and the presence or absence of shore tank movement distinguish a discharge from a relay. Build a dwell threshold appropriate to the terminal and escalate short-dwell calls to the MLRO.
3. Map the mandate chain to beneficial ownership before pricing. Under FATF Recommendation 10, an ICPO or LOI from an intermediary is not a counterparty file. Identify who controlled the cargo during the Turkish call.
4. Treat clean list screening as neutral, not exculpatory. The absence of an OFAC SDN hit tells you nothing about origin in this typology. Document that distinction in your rationale so a later reviewer can see what was and was not tested.
5. Preserve the negative evidence. Where a feed is unavailable, say so in the file. A gap that is recorded is defensible. A gap that is filled with an estimate is not.

The three questions to put to a counterparty offering neutral-origin, Med-relayed barrels

1. Where did this cargo load before the Turkish-Mediterranean port shown on the bill of lading, and can you produce the prior BL and the continuous AIS track for that leg?
2. What commercial purpose did the Turkish port call serve, and can you evidence discharge into shore tank, including tank receipts and quantity reconciliation, rather than a ship-to-ship or anchorage transfer?
3. Who held title during the Turkish call, and does the price cap attestation you are providing cover the Black Sea leg or only the leg described on the bill of lading you have handed us?

An honest chain can answer all three from existing records. A relay chain will answer the first with a refusal, the second with a narrative, and the third with an attestation that quietly describes the wrong voyage. That asymmetry is the control.