John D. Leitch
Bulk carrier · Canada · built 1967 · AIS Class A
In short
John D. Leitch (Bulk carrier, Canada flag) was last seen on AIS on , under way at 11.6 kn, in the Great Lakes. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. Its crew-entered AIS destination is BURNS HARBOR; its reported draught is 6.6 m (voyage report via AISstream.io global terrestrial AIS, received Sep 29, 2026, 21:00 UTC).
Current voyage: from Port Colborne (departed Sep 28, 2026, 10:16 UTC) to BURNS HARBOR
- Vessel type
- Bulk carrier
- Flag
- Canada
- Year built
- 1967
- Gross tonnage
- 22,080
- Size (length × beam)
- 223 m × 24 m
- Registered owner
- —
Watch this ship
Get an email when John D. Leitch arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
We email you a link and a code. That creates a free account, no password or card, and follows John D. Leitch.
Free account, no card: follow up to 5 ships and ports. Plus follows 50, Pro 500.
By continuing you accept the Terms and the Privacy policy.

Last reported position
received- Position
- 44.8259° N, 86.451° W
- Area
- Great Lakes
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 11.6 kn
- Course
- 196°
- Heading
- 196°
Last 30 days: 7 port calls (Port Colborne, Saint-Catharines, Port Weller, and Sault Sainte Marie).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
A year of history in the Terminal (Plus) · the full archive since June 1, 2026 (Pro)
Try the live demo, no sign-upIdentity & particulars
- Name
- John D. Leitch
- IMO numberWhat is an IMO number?
- 6714586
- MMSIWhat is an MMSI?
- 316001701
- Call signWhat is a call sign?
- VGWM
- Flag
- Canada
- Vessel type
- Detailed type from WikidataBulk carrier
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- Source: Transport Canada — Canadian Register of Large Vessels (open data), record 326395. Added to Voydar on September 23, 2026. Licence: Open Government Licence – Canada 2.0.22,080
- Length overall
- 222.5 m
- Beam
- 24 m
- Year built
- 1967
A tag next to a value names the register that supplied it (hover or tap it for the record and date). Values without a tag come from the ship's own AIS broadcasts or from Wikidata. Position and identity are derived live from AIS.
Ownership & management
Each line shows where the fact comes from. Links backed by an identifier point to the company page.
- Operator
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
- Builder
- Source: Wikidata · reported · confidence 0.8 · retrieved Sep 22, 2026
Timeline
Dated events for this ship from every source Voydar holds, newest first. Each line names its source; derived items say how they were derived.
| Date | Event | Source |
|---|---|---|
| Left Port ColborneAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Port ColborneAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Saint-CatharinesAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Saint-CatharinesAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left Port WellerAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at Port WellerAIS-detected | Voydar port-call detector (AIS geofence) | |
| Reported arrival at ROUGE RIVER, MI (INCLUDED IN PORT OF DETROIT)Authority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from ROUGE RIVER, MI (INCLUDED IN PORT OF DETROIT)Authority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from SANDUSKY HARBOR, OHAuthority-reported | USACE foreign traffic vessel entrances & clearances |
Owner, operator and manager changes found by comparing yearly EU MRV reports are dated to the reporting year ("during 2025"), not to a day. Port calls here are the most recent only; the full lists are further down.
Incidents & investigations Authority-reported
Accident and incident reports by national investigation boards, and casualty warnings, that concern this ship. Each links to the original.
- Occurred Oct 3, 2012ACC · Cargo, Dry BulkNTSB marine investigations (CAROL)Lorain, OH, USA
John D Leitch / 350 Challenger, Lorain, OH, USA (NTSB DCA13NM002)Report published May 28, 2013
The National Transportation Safety Board determines that the probable cause of the allision was the failure of the master of the John D. Leitch to properly account for bank effect while maneuvering in the confined waters of the Black River.
Source: NTSB marine investigations (CAROL). Courtesy: National Transportation Safety Board. Licence: US Government work (17 U.S.C. §105), public domain.
Port calls
Two kinds of evidence, kept apart: calls Voydar detected from the ship's AIS positions, and arrivals and departures published by port authorities and customs records.
Detected from AIS AIS-detected
| Port | Arrived | Departed | Time in port |
|---|---|---|---|
| Port Colborne CAPCO | Sep 28, 2026, 09:11 UTC | Sep 28, 2026, 10:16 UTC | 1 h 5 min |
| Saint-Catharines CASCA | Sep 28, 2026, 02:03 UTC | Sep 28, 2026, 07:10 UTC | 5 h 7 min |
| Port Weller CAPWE | Sep 28, 2026, 00:55 UTC | Sep 28, 2026, 02:03 UTC | 1 h 8 min |
| Saint-Catharines CASCA | Sep 26, 2026, 15:40 UTC | Sep 26, 2026, 22:37 UTC | 6 h 56 min |
| Port Colborne CAPCO | Sep 26, 2026, 06:08 UTC | Sep 26, 2026, 10:23 UTC | 4 h 15 min |
| Sault Sainte Marie USSSM | Sep 24, 2026, 04:05 UTC | Sep 24, 2026, 05:22 UTC | 1 h 18 min |
| Saint-Catharines CASCA | Sep 17, 2026, 23:17 UTC | Sep 18, 2026, 00:29 UTC | 1 h 12 min |
Detected by Voydar when the ship's AIS positions stayed slow inside a harbour area. Calls shorter than 30 minutes are not shown. Depends on AIS reception; detection started on June 8, 2026.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| ROUGE RIVER, MI (INCLUDED IN PORT OF DETROIT) | Arrival | Dec 31, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ROUGE RIVER, MI (INCLUDED IN PORT OF DETROIT) | Departure | Dec 31, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| SANDUSKY HARBOR, OH | Departure | Dec 27, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| SANDUSKY HARBOR, OH | Arrival | Dec 25, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| TOLEDO HARBOR, OH | Departure | Dec 20, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| TOLEDO HARBOR, OH | Arrival | Dec 20, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Lorain USLOR | Departure | Oct 27, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Lorain USLOR | Arrival | Oct 26, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| INDIANA HARBOR, IN | Departure | Oct 12, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| BURNS WATERWAY HARBOR, IN | Arrival | Oct 10, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ESCANABA, MI | Arrival | Sep 27, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| ESCANABA, MI | Departure | Sep 27, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: May 21, 2002.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
Behaviour at sea Voydar-derived
Patterns Voydar derived from this ship's AIS broadcasts. They are inferences, not reports: each one shows how it was computed and how confident we are, and none of them says why a ship behaved this way.
| When | What we observed | Confidence |
|---|---|---|
| Sep 27, 2026, 21:41 UTC | Draught change Reported draught went from 8 m to 6.6 m after leaving Saint-Catharines. Voydar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
| Sep 25, 2026, 03:01 UTC | Draught change Reported draught went from 6.1 m to 8 m after leaving Sault Sainte Marie. Voydar infers the ship probably loaded cargo. Method seadar.behaviour.draught_change v1 | Medium (55%) |
Source: AISstream.io global terrestrial AIS. AIS data: AISstream.io. Licence: none published.
Derived from AIS positions of feeds whose terms allow display on Voydar. Coverage is terrestrial: gaps are reported only where our receivers kept hearing other ships. Detections below medium confidence are not shown.
Frequently asked questions
- Where is John D. Leitch now?
- John D. Leitch (Bulk carrier, Canada flag) was last seen on AIS on Oct 1, 2026, 01:31 UTC, under way at 11.6 kn, in the Great Lakes. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was BURNS HARBOR (voyage report via AISstream.io global terrestrial AIS, received Sep 29, 2026, 21:00 UTC). This report does not confirm the ship’s current route.
- What kind of ship is John D. Leitch?
- John D. Leitch is a bulk carrier sailing under the flag of Canada, built in 1967 by Port Weller Dry Docks. The vessel is 222.5 m long with a beam of 24 m and has a gross tonnage of 22,080.
- What sanctions and inspection records does Voydar hold for John D. Leitch?
- Voydar has no matched sanctions record displayed for John D. Leitch from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels and the New Zealand Russia Sanctions Register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for John D. Leitch. Missing records do not establish whether the ship has been detained.
Use this data
This page is also available as JSON, free, with the source and licence of every section. Sections whose sources do not permit redistribution are listed as withheld.
GET /api/v1/vessels/6714586Using this data in code?
Every account gets a personal API allowance: 2,500 credits a month free, 25,000 with Pro. Pro adds internal business use; API plans add building the data into your own products.