Pacific Falcon
Bulk carrier · Japan · built 2000 · AIS Class A
In short
Pacific Falcon (Bulk carrier, Japan flag) was last seen on AIS on , at anchor, near Yokosuka (North Pacific Ocean). Its crew-entered AIS destination is JP YOK XX NGI, with an ETA of Oct 2, 2026, 08:00 UTC; its reported draught is 7.5 m (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 18:57 UTC).
Current voyage: from Chiba (departed Sep 26, 2026, 05:51 UTC) to JP YOK XX NGI
- Vessel type
- Bulk carrier
- Flag
- Japan
- Year built
- 2000
- Gross tonnage
- 7,918
- Size (length × beam)
- 126 m × 21 m
- Registered owner
- —
Watch this ship
Get an email when Pacific Falcon 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 Pacific Falcon.
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
- 35.3509° N, 139.7311° E
- Area
- North Pacific Ocean
- StatusWhat do AIS statuses mean?
- At anchor
- Speed
- 0.3 kn
- Course
- 351°
- Heading
- 101°
Last 30 days: 2 port calls (Chiba and Aomi).
Port calls are detected by Seadar 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
- Pacific Falcon
- IMO numberWhat is an IMO number?
- 9209570
- MMSIWhat is an MMSI?
- 431401846
- Call signWhat is a call sign?
- JM6622
- Flag
- Japan
- Vessel type
- Bulk carrier
- AIS ship type
- Cargo
- Gross tonnageGross tonnage vs deadweight
- 7,918
- Deadweight (DWT)
- Source: Wikidata, record Q117083037. Added to Seadar on September 23, 2026. Licence: CC0 1.0.11,310 t
- Length overall
- 126 m
- Beam
- 21 m
- Year built
- 2000
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.
No owner, operator or manager is recorded for this vessel yet.
Timeline
Dated events for this ship from every source Seadar holds, newest first. Each line names its source; derived items say how they were derived.
| Date | Event | Source |
|---|---|---|
| Left ChibaAIS-detected | Seadar port-call detector (AIS geofence) | |
| Arrived at ChibaAIS-detected | Seadar port-call detector (AIS geofence) | |
| Left AomiAIS-detected | Seadar port-call detector (AIS geofence) | |
| Arrived at AomiAIS-detected | Seadar 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 Seadar 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 |
|---|---|---|---|
| Chiba JPCHB | Sep 25, 2026, 09:31 UTC | Sep 26, 2026, 05:51 UTC | 20 h 21 min |
| Aomi JPOMA | Sep 25, 2026, 00:07 UTC | Sep 25, 2026, 08:42 UTC | 8 h 35 min |
Detected by Seadar 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 Seadar-derived
Patterns Seadar 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 26, 2026, 04:58 UTC | Draught change Reported draught went from 6.5 m to 5.5 m while in port at Chiba. Seadar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
| Sep 25, 2026, 06:22 UTC | Draught change Reported draught went from 7.5 m to 6.5 m while in port at Aomi. Seadar infers the ship probably discharged cargo. Method seadar.behaviour.draught_change v1 | Medium (65%) |
Source: AISstream.io global terrestrial AIS. AIS data: AISstream.io. Licence: none published.
Derived from AIS positions of feeds whose terms allow display on Seadar. 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 Pacific Falcon now?
- Pacific Falcon (Bulk carrier, Japan flag) was last seen on AIS on Oct 1, 2026, 18:36 UTC, at anchor, near Yokosuka (North Pacific Ocean). The crew-entered destination was JP YOK XX NGI (voyage report via AISstream.io global terrestrial AIS, received Oct 1, 2026, 18:57 UTC). This report does not confirm the ship’s current route.
- What kind of ship is Pacific Falcon?
- Pacific Falcon is a bulk carrier sailing under the flag of Japan, built in 2000. The vessel is 126 m long with a beam of 21 m and has a gross tonnage of 7,918.
- What sanctions and inspection records does Seadar hold for Pacific Falcon?
- Seadar has no matched sanctions record displayed for Pacific Falcon 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 Pacific Falcon. 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/9209570Using 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.