
Technical Specifications
Live Tracking
Most time stopped at Port of Prince Rupert — 11 d across 60 stays.
Derived from the AIS track — runs of near-zero speed (anchored, moored or drifting) snapped to the nearest port. Builds up as we observe the vessel.
Intelligence
AIS-derived from our live feed.
Compliance
On 08 March 2025, the passenger ferry "NORTHERN ADVENTURE" reported an issue with one of its propellers while docked at the Bear Cove Ferry Terminal in Port Hardy, BC. The ferry cancelled its scheduled sailing to assess the problem and subsequently carried out repairs.
On 31 May 2024, the ferry "NORTHERN ADVENTURE" reported having sustained a total failure of its main engine fuel supply system in Wright Sound, BC. The crew effected repairs adrift and the vessel resumed its voyage.
On 15 September 2023, the passenger vessel "NORTHERN ADVENTURE", with 136 people on board, reported having sustained a fire in a vehicle on the car deck while proceeding in Hecate Strait, BC. The fire was extinguished and the vessel resumed its voyage.
On 14 July 2023, the ferry "NORTHERN ADVENTURE" reported a total failure of its starboard main engine upon departure from Skidegate, BC. The vessel proceeded to Prince Rupert, BC using its port engine and ordered a tug for berthing at its destination.
On 05 July 2023, the ferry "NORTHERN ADVENTURE" reported the total failure of its starboard engine lubricating oil pump while secured in Prince Rupert, BC. Temporary repairs were effected by the crew.
On 27 April 2022, the passenger/vehicle vessel "NORTHERN ADVENTURE" reported the breakdown of its port main engine due to cooling water system issues whilst in transit to Skidegate, Haida Gwaii, BC. The vessel continued the passage using its starboard main engine.
On 12 April 2022, the passenger vessel "NORTHERN ADVENTURE" reported having sustained a machinery failure on its port engine in Gordon Channel, BC. The crew carried out repairs and the vessel resumed its voyage.
On 02 April 2021, the passenger/vehicle ferry "NORTHERN ADVENTURE" reported a breach in its hull in way of the bilge holding tank sounding pipe striking plate while at Skidegate, Haida Gwaii, BC. The vessel travelled, without passengers, to Prince Rupert, BC for a further inspection and to perform repairs. The hole was temporarily repaired by shore technicians and the vessel was allowed to operate, pending the completion of permanent repairs within 3 months.
Recorded marine occurrences naming this vessel.
Operational Status
Stopped, anchored or moored on its latest broadcast — parked, not necessarily withdrawn.
Read from the single most-recent AIS broadcast we hold for this hull — we keep no position history, so this is a point-in-time posture, not a dwell inference. Derived in-house from our own AIS feed; weight it by the broadcast age above.
Arrivals, time in port and the load/discharge inferred from the draught change — detected from AIS track history. An open call means the vessel is still in port (no departure observed yet).
Method: each call is a run of fixes inside a port’s geofence confirmed by a stop (or an AIS gap); load/discharge is the sign of the draught delta over the call. Indicative — arrivals before our AIS history began read from the first observation.
Time-in-port summed by port from the AIS-detected port-call history — the ports this vessel has spent the most time at, longest first.
Based on 47 completed calls observed since — open calls (no departure yet) are excluded. The distribution sharpens as AIS history accrues.
Composite Risk
Multiple adverse factors, or a hard ship-specific signal, lift this hull above the fleet norm.
A coverage-weighted blend of the 2 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. This headline is flagged low-confidence (a thin or structural-only read) and should not be treated as a verdict. 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.
Fleet Management

Visual Archive
Explore More