SABINE PILOT
Pilot vessel · United States · AIS Class A
In short
SABINE PILOT (Pilot vessel, United States flag) was last seen on AIS on , not moving, near Sabine (Gulf of Mexico). Its crew-entered AIS destination is SABPLT (voyage report via AISstream.io global terrestrial AIS, received Nov 17, 2026, 23:35 UTC).
Current voyage: from Galveston (departed Nov 14, 2026, 10:31 UTC) to SABPLT
- Vessel type
- Pilot vessel
- Flag
- United States
- Year built
- —
- Gross tonnage
- —
- Size (length × beam)
- 19 m × 5 m
- Registered owner
- —
Last reported position: 29.7207° N, 93.865° W · Gulf of Mexico · See on the map
Watch this ship
Get an email when SABINE PILOT arrives or leaves port, changes destination, name, flag or owner, or is sanctioned, detained or named in an official release.
What you would have been told
Nothing in the last 24 hours: no arrival or departure at a port. You are told the moment that changes.
Detected from AIS, as of Nov 18, 2026, 00:18 UTC.
Free forever. No card. Your first follow also starts a free 14-day Plus trial: alerts for SABINE PILOT reach you the moment they happen, arrival-time changes included. When it ends you stay on Free, with a daily email, unless you keep Plus (US$7 a month). Compare plans
Get alerts on your phone: Voydar for iPhone
Last reported position
received- Position
- 29.7207° N, 93.865° W
- Area
- Gulf of Mexico
- Status
- Under way using engineWhat do AIS statuses mean?
- Speed
- 0 kn
- Course
- 353°
- Heading
- 234°
- Compass: course over ground 353°, heading 234°
- Arrow: course. Hull: heading. As broadcast on AIS.
Locator map: Natural Earth (public domain)
Last 30 days: 8 port calls (Galveston, Beaumont, and Atreco).
Port calls are detected by Voydar from AIS (at least 30 minutes slow inside a harbour area); see Port calls below.
Pro shows SABINE PILOT's track before the last 30 days. Voydar has recorded its port calls since October 3, 2026.Free forever. No card. Follow a ship and Plus is free for 14 days.
Try the live demo, no sign-upIdentity & particulars
Length overall 19 mone tick every 2 m
Beam 5 mPlan outline, to scale
- Name
- SABINE PILOT
- IMO numberWhat is an IMO number?
- 8851273
- MMSIWhat is an MMSI?
- 366896250
- Call signWhat is a call sign?
- WAK7647
- Flag
- United States
- Vessel type
- Pilot vessel
- Gross tonnageGross tonnage vs deadweight
- —
- Length overall
- 19 m
- Beam
- 5 m
- Year built
- —
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.
- Managing owner (USCG)
- CANAL BARGE LLC(Former)(not linked to a company record)Source: US Coast Guard — Merchant Vessels of the United States (documented vessels) · until 2026 · reported · high confidence · retrieved Oct 6, 2026Coast Guard documentation record (2026-09 file) matched to this ship by IMO number and call sign. The managing owner is the company the Coast Guard has on record for the ship's certificate of documentation.
- Ship radio licensee (FCC)
- SABINE PILOT SERVICE INC(not linked to a company record)Source: FCC Universal Licensing System — ship station licences · since 2025 · reported · high confidence · retrieved Nov 17, 2026Licence matched to this ship by MMSI and call sign. The licensee holds the radio licence; it is not necessarily the owner.Canal Barge LLC(not linked to a company record)Source: FCC Universal Licensing System — ship station licences · since 2020 · reported · high confidence · retrieved Nov 17, 2026Licence matched to this ship by MMSI and call sign. The licensee holds the radio licence; it is not necessarily the owner.
Checking ownership or sanctions for your business? Teams screen fleets by IMO, keep watch with alerts and keep a dated record. Voydar for business →
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 GalvestonAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at GalvestonAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left BeaumontAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at BeaumontAIS-detected | Voydar port-call detector (AIS geofence) | |
| Left AtrecoAIS-detected | Voydar port-call detector (AIS geofence) | |
| Arrived at AtrecoAIS-detected | Voydar port-call detector (AIS geofence) |
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.
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 |
|---|---|---|---|
| Galveston USGLS | Nov 13, 2026, 10:22 UTC | Nov 14, 2026, 10:31 UTC | 24 h 9 min |
| Beaumont USBPT | Nov 6, 2026, 16:15 UTC | Nov 7, 2026, 18:27 UTC | 26 h 12 min |
| Atreco USATR | Nov 5, 2026, 19:41 UTC | Nov 6, 2026, 15:12 UTC | 19 h 31 min |
| Beaumont USBPT | Oct 30, 2026, 23:44 UTC | Nov 1, 2026, 04:05 UTC | 28 h 21 min |
| Atreco USATR | Oct 30, 2026, 06:35 UTC | Oct 30, 2026, 22:43 UTC | 16 h 8 min |
| Galveston USGLS | Oct 29, 2026, 09:43 UTC | Oct 29, 2026, 20:42 UTC | 10 h 58 min |
| Galveston USGLS | Oct 23, 2026, 06:02 UTC | Oct 26, 2026, 18:44 UTC | 3 d 12 h |
| Beaumont USBPT | Oct 21, 2026, 08:37 UTC | Oct 22, 2026, 11:45 UTC | 27 h 8 min |
| Port Allen USPLL | Oct 14, 2026, 14:52 UTC | Oct 19, 2026, 23:02 UTC | 5 d 8 h |
| Beaumont USBPT | Oct 6, 2026, 15:16 UTC | Oct 8, 2026, 00:45 UTC | 33 h 30 min |
| Atreco USATR | Oct 6, 2026, 12:23 UTC | Oct 6, 2026, 14:26 UTC | 2 h 2 min |
| Houston USHOU | Oct 3, 2026, 09:21 UTC | Oct 4, 2026, 06:31 UTC | 21 h 10 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.
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 |
|---|---|---|
| Nov 17, 2026, 00:00 UTC | IMO used twice IMO 8851273 was broadcast by two ships (MMSI 366896250 and 367456860) 115 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | Medium (70%) |
| Nov 16, 2026, 00:00 UTC | IMO used twice IMO 8851273 was broadcast by two ships (MMSI 366896250 and 367456860) 115 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | Medium (70%) |
| Nov 15, 2026, 00:00 UTC | IMO used twice IMO 8851273 was broadcast by two ships (MMSI 366896250 and 367456860) 114 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | Medium (70%) |
| Nov 14, 2026, 00:00 UTC | IMO used twice IMO 8851273 was broadcast by two ships (MMSI 366896250 and 367456860) 114 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | Medium (70%) |
| Nov 13, 2026, 00:00 UTC | IMO used twice IMO 8851273 was broadcast by two ships (MMSI 366896250 and 367456860) 103 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | Medium (70%) |
| Nov 12, 2026, 00:00 UTC | IMO used twice IMO 8851273 was broadcast by two ships (MMSI 366896250 and 367456860) 100 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | Medium (70%) |
| Nov 11, 2026, 00:00 UTC | IMO used twice IMO 8851273 was broadcast by two ships (MMSI 366896250 and 367456860) 120 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | Medium (70%) |
| Nov 10, 2026, 00:00 UTC | IMO used twice IMO 8851273 was broadcast by two ships (MMSI 366896250 and 367456860) 114 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | Medium (70%) |
| Nov 9, 2026, 00:00 UTC | IMO used twice IMO 8851273 was broadcast by two ships (MMSI 366896250 and 367456860) 112 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | Medium (70%) |
| Nov 8, 2026, 00:00 UTC | IMO used twice IMO 8851273 was broadcast by two ships (MMSI 366896250 and 367456860) 114 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | Medium (70%) |
| Nov 5, 2026, 00:00 UTC | IMO used twice IMO 8851273 was broadcast by two ships (MMSI 366896250 and 367456860) 53 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | Medium (70%) |
| Nov 4, 2026, 00:00 UTC | IMO used twice IMO 8851273 was broadcast by two ships (MMSI 366896250 and 367456860) 103 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | Medium (70%) |
| Nov 3, 2026, 00:00 UTC | IMO used twice IMO 8851273 was broadcast by two ships (MMSI 366896250 and 367456860) 102 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | Medium (70%) |
| Nov 1, 2026, 00:00 UTC | IMO used twice IMO 8851273 was broadcast by two ships (MMSI 366896250 and 367456860) 81 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | Medium (70%) |
| Oct 29, 2026, 00:00 UTC | IMO used twice IMO 8851273 was broadcast by two ships (MMSI 366896250 and 367456860) 53 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | Medium (70%) |
| Oct 28, 2026, 00:00 UTC | IMO used twice IMO 8851273 was broadcast by two ships (MMSI 366896250 and 367456860) 105 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | Medium (70%) |
| Oct 26, 2026, 00:00 UTC | IMO used twice IMO 8851273 was broadcast by two ships (MMSI 366896250 and 367456860) 105 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | Medium (70%) |
| Oct 24, 2026, 00:00 UTC | IMO used twice IMO 8851273 was broadcast by two ships (MMSI 366896250 and 367456860) 104 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | Medium (70%) |
| Oct 23, 2026, 00:00 UTC | IMO used twice IMO 8851273 was broadcast by two ships (MMSI 366896250 and 367456860) 91 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | Medium (70%) |
| Oct 22, 2026, 00:00 UTC | IMO used twice IMO 8851273 was broadcast by two ships (MMSI 366896250 and 367456860) 55 km apart at the same time. One of them may be using the wrong IMO number. Method seadar.behaviour.imo_conflict v1 | Medium (70%) |
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
- What kind of ship is SABINE PILOT?
- SABINE PILOT is a pilot vessel sailing under the flag of United States. The vessel is 19 m long with a beam of 5 m.
- What sanctions and inspection records does Voydar hold for SABINE PILOT?
- Voydar has no matched sanctions record displayed for SABINE PILOT from the OFAC SDN list, the UK Sanctions List, the Canadian autonomous sanctions list, the EU list of designated vessels, the New Zealand Russia Sanctions Register and the French national asset-freeze register. Coverage may be incomplete; this is not sanctions clearance. No matched inspection records are displayed for SABINE PILOT. Missing records do not establish whether the ship has been detained.
Full Vessel Report
A dated PDF with the complete track since June 2026, every port call, ownership and flag changes, inspections, a sanctions and dark-activity screening snapshot, emissions, companies and every source.
Sample: a real report for EVER GIVEN (IMO 9811000), built from public data and marked SAMPLE on every page.
Every fact on this page stays free.
Know this ship?
Help other readers. Member posts are shown as member content, never as sourced data.
- Date, place and an optional note
- Members who know her can answer
- Suggest a correctionChecked against sources before anything changes
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/8851273Cite this page
SABINE PILOT. Voydar (voydar.com). https://www.voydar.com/vessel/8851273-sabine-pilot. Retrieved November 18, 2026.
Each fact above names its own source and date. Cite that primary source too when you rely on a fact.
Using this data in code?
Every account gets a personal API allowance: 2,500 credits a month free, 25,000 with Pro. Pro includes use in your own product. Growth and Scale add volume, and each includes one Pro membership.