
One vessel, every compliance signal in one place: sanctions exposure path, composite risk, dark-fleet behaviour, flag history and safety record.
This hull carries sanctions exposure. Review the propagation path and evidence below before transacting.
This vessel is directly sanctioned.
Screened against official OFAC, EU, UN and UK designations (In-house derivation over the OpenSanctions publishable subset, GLEIF LEI (CC0) and our own vessel/owner master. No new external source fetched.). An automated exposure signal for review, not a legal determination.
Composite Risk
Strong, corroborated adverse evidence — a detention, sanctions exposure or an AIS-gap / behavioural signal.
Sanctions exposure screens the hull and its ownership chain against official OFAC, EU, UN and UK designations, then propagates a sanctioned owner or parent down to the vessels it controls. The composite risk read blends age, flag register, port-state detentions, dark-fleet behaviour and sanctions exposure, weighted by how much evidence is present. Every signal shows its own evidence. This is decision support for a compliance review, not a legal determination.
Screen the whole fleet on the risk boardA coverage-weighted blend of the 4 components we could read for this hull — the weights renormalise over only the components present, so a thin read is never inflated and a hull is never credited a “safe 0” for a signal it has no row for. Higher means riskier. Derived in-house from government-open port-State-control, flag, sanctions and our own vessel data; weight it by the coverage above.
Transparency
Behavioural flags raised against this vessel — each shown with the raw evidence behind it. Derived in-house from data we are entitled to publish; informational, not a determination of wrongdoing.
Stopped transmitting relative to the live feed front
Method: vessel is on a sanctions list but has never appeared on our live AIS feed. Source: ais_positions (absence) + sanctioned_vessels.
Signals are a current-state view: a flag clears once the vessel stops tripping its detector. These are screening indicators, not a substitute for your own due diligence.
Compliance
On 06 November 2019, the general cargo vessel0 "LEA AUERBACH", under conduct of a pilot, reported machinery failure while transiting Laredo Channel, BC. The vessel anchored and the crew carried out repairs.
On 17 December 2015, the general cargo vessel "BBC MAPLE LEA" ran aground 3 nautical miles NW of Châteauguay, QC. The vessel was refloated with 2 tugs the following day and proceeded to the dock in Sainte-Catherine, QC to undergo an underwater survey. The vessel sustained damage to its bow thruster, releasing an unknown quantity of hydraulic oil in the water.
On 21 February 2013, the C.C.G.S. "LOUIS S. ST. LAURENT" made contact with the M/V "MAPLE LEA" while escorting in ice. There were no injuries or pollution reported.
Recorded marine occurrences naming this vessel.