Alliance Fairfax
Car carrier · United States · built 2005 · AIS Class A
In short
Alliance Fairfax (Car carrier, United States flag) was last seen on AIS on , under way at 15.8 kn, in the Mediterranean Sea. 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 EG SUZ (As Suways (Suez)); its reported draught is 9.6 m (voyage report via AISstream.io global terrestrial AIS, received Sep 26, 2026, 00:11 UTC). ISM manager: Maersk Line, Limited-USA (source: EU MRV (THETIS-MRV) emissions, reporting year 2025).
- Vessel type
- Car carrier
- Flag
- United States
- Year built
- 2005
- Gross tonnage
- 59,705
- Size (length × beam)
- 199 m × 32 m
- ISM manager
- Maersk Line, Limited-USA
Watch this ship
Alliance Fairfax has not been received for a while. Follow it and we will email you as soon as it is heard again, then when it reaches or leaves port.
Free forever. No card. A free account follows up to 5 ships and ports.

Last reported position
received- Position
- 36.8547° N, 1.4031° E
- Area
- Mediterranean Sea
- StatusWhat do AIS statuses mean?
- Under way using engine
- Speed
- 15.8 kn
- Course
- 76°
- Heading
- 77°
Voydar detected no port call in the last 30 days.
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)Free forever. No card. New accounts include 14 days of Pro.
Try the live demo, no sign-upIdentity & particulars
- Name
- Alliance Fairfax
- IMO numberWhat is an IMO number?
- 9303546
- MMSIWhat is an MMSI?
- 366771000
- Call signWhat is a call sign?
- WLMQ
- Flag
- United States
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 59,705
- Length overall
- 199 m
- Beam
- 32 m
- Year built
- 2005
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.
- ISM manager
- Source: EU MRV (THETIS-MRV) emissions · reporting year 2025 · reported · confidence 0.9 · retrieved Oct 5, 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 |
|---|---|---|
| Reported departure from WilmingtonAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported arrival at JACKSONVILLE HARBOR, FLAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Reported departure from JACKSONVILLE HARBOR, FLAuthority-reported | USACE foreign traffic vessel entrances & clearances | |
| Former name: Hoegh Kyoto | Wikidata | |
| Former name: Maersk Willow | Wikidata |
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.
Former and other names
Names attested for this ship other than its current name.
| Name | Evidence | Date | Source |
|---|---|---|---|
| Hoegh Kyoto | Former name | Jan 1, 2008 | Wikidata |
| Maersk Willow | Former name | Jan 1, 2005 | Wikidata |
A sanctions list's date is the earliest date the list shows the name, not when the ship took it. A name on a list is shown as a former name only where AIS shows the ship using another name after that date; otherwise it is listed as a name the list uses. AIS name changes are dated when Voydar saw them.
Source: Wikidata. Licence: CC0 1.0.
Emissions & fuel consumption
Independently verified annual figures reported under the EU MRV regulation — public environmental data the incumbents don't surface.
| Year | CO₂ emitted | Fuel burned | Time at sea | CO₂ / n mile |
|---|---|---|---|---|
| 2018 | 4,388 t | 1,407 t | 41 days | 317 kg |
| 2019 | 2,171 t | 697 t | 22 days | 302 kg |
| 2025 | 0 t | 0 t | 0 days | — |
Technical efficiency: EEXI (14.64 gCO₂/t·nm). Source: European Commission / EMSA THETIS-MRV (EU Regulation 2015/757). Covers voyages to, from and within the EU/EEA.
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.
Reported by authorities Authority-reported
| Port | Record | Date (UTC) | Berth | Source |
|---|---|---|---|---|
| Wilmington USILG | Departure | Nov 22, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| JACKSONVILLE HARBOR, FL | Arrival | Nov 18, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| JACKSONVILLE HARBOR, FL | Departure | Nov 18, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Beaumont USBPT | Arrival | Nov 14, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Beaumont USBPT | Departure | Nov 14, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Freeport USFPO | Departure | Nov 12, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Freeport USFPO | Arrival | Nov 12, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| JACKSONVILLE HARBOR, FL | Arrival | Aug 10, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| JACKSONVILLE HARBOR, FL | Departure | Aug 10, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Charleston USCHS | Arrival | Aug 9, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Charleston USCHS | Departure | Aug 9, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
| Baltimore USBAL | Arrival | Aug 7, 2016(date only) | — | USACE foreign traffic vessel entrances & clearances |
Records published by the authority named on each row. Earliest record for this ship: April 14, 2006.
Source: US Army Corps of Engineers, Waterborne Commerce Statistics Center (US CBP entrance/clearance records). Licence: US Government work — public domain.
Frequently asked questions
- Where is Alliance Fairfax now?
- Alliance Fairfax (Car carrier, United States flag) was last seen on AIS on Sep 26, 2026, 08:08 UTC, under way at 15.8 kn, in the Mediterranean Sea. Voydar has no more recent AIS position for this ship. Its current location cannot be established from this report. The crew-entered destination was EG SUZ (voyage report via AISstream.io global terrestrial AIS, received Sep 26, 2026, 00:11 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Alliance Fairfax?
- Alliance Fairfax is a car carrier sailing under the flag of United States, built in 2005 by Hanwha Ocean. The vessel is 199 m long with a beam of 32 m and has a gross tonnage of 59,705.
- Who is recorded as the owner or manager of Alliance Fairfax?
- Maersk Line, Limited-USA is recorded as ISM manager for Alliance Fairfax (source: EU MRV (THETIS-MRV) emissions; reporting year 2025). This source record does not independently confirm today’s ownership or management.
- What sanctions and inspection records does Voydar hold for Alliance Fairfax?
- Voydar has no matched sanctions record displayed for Alliance Fairfax 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 Alliance Fairfax. 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/9303546Using 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.