ALASKAN NAVIGATOR is a 2005 tank ship. The Coast Guard has recorded 28 inspections since 2016, most recently in February 2026, along with 5 deficiencies and 7 casualty investigations between 2006 and 2021.
Records from 2006 to 2026. Most recent: inspection, 21 February 2026.
Coast Guard record current through 23 August 2026, retrieved 5 September 2026 from PSIX. Every field on this page was recorded by the Coast Guard. Records for the Tank Ship class in Maury's sources begin in 2016.
Every line above is a count of records the US Coast Guard wrote, or a date it recorded.
A blank resolution means none was recorded in this data; it does not establish that a
deficiency is outstanding. Years with a record are calendar years in which a record
exists, not years in service. What Maury does
not do.
DocumentationValid · issued 10 March 2026 · expires 31 March 2027
Service, as the file records itTank Ship
Hull formpowered (Maury's inference from propulsion, hull shape, material and length, rule hf-1; not a recorded fact)
Tonnage as PSIX records it110693 - Convention (Subpart B), Gross Ton 56439 - Convention (Subpart B), Net Ton 193049 - Dead Weight, Ton 220966 - Displacement, Ton
Every line above is a field of the National Vessel Documentation Center's file as served by NOAA Fisheries, dated 10 August 2026, matched to this hull on its Official Number. Registered and ITC measurements are two systems and are never combined. One snapshot is held so far; documentation history begins with the next.
Vessel history report
Every record for this hull, in one document — $299
Every recorded inspection, 2016 to
2026 for this class, in one chronology · every deficiency, with system, dates
and resolution · operational controls imposed and removed · every name this
hull has been recorded under · the vessels it was inspected alongside, and when
· how its record compares with hulls of similar age and size, as a fact about the
population and never a judgement about this vessel.
This report is in development and is not for sale yet. There is
no date, and nothing is charged. Leave an email and we will tell you when it exists, once.
Used only to tell you when the report exists.
Not shared, not sold, and not added to a mailing list.
The Coast Guard recorded this vessel and the following in the same
inspection activity — normally a tug and the barges in its tow. A recreational or
unclassed hull in the same activity is held and not published, so it does not appear
here: these lists are a floor, not a complete manifest.
05 - Radio Communications › N/A - No Subsystem › MF/HF Radio installation
Issued 14 December 2019Resolved
Every ship shall be provided with radio installation capable of complying with the functional requirements prescribed by the regulation 4 throughout its intended voyage. The GMDSS MF/HF radio experiences a 3-5 min alarm while restoring AC power and during this time it is not operational.
Action required: 16 - Rectify deficiencies w/in 14 days
Due 28 December 2019
Resolved 27 December 2019
Resolution: Received tech report and uploaded. Cleared CG-835.
Fire Fighting › Fixed CO2 Fire Extinguishing System › Servicing
Issued 31 October 2017Resolved
Prove proper operation of all fixed fire extinguishing system time delays. Solas(09)11-2/14.1
Condition: Improper/Lack of Maintenance
Action required: 705 - Other - as specified
Due 3 November 2017
Resolved 3 November 2017
Resolution: Witnessed servicing of fixed CO2 system.
Communications › Radio Communications › EPIRB
Issued 31 October 2017Resolved
Replace stbd bridge wing EPIRB hydrostatic release unit. Solas(09)IV/7.1.6.4
Condition: Improper Installation
Action required: 705 - Other - as specified
Due 3 November 2017
Resolved 3 November 2017
Resolution: EPIRB was replaced with proper EPIRB type hydrostatic release unit.
Fire Fighting › Fixed CO2 Fire Extinguishing System › Servicing
Issued 31 October 2017Resolved
Conduct blowout of fixed fire fighting system piping. Remove any foreign matter to blow clear. Solas(09)11-2/14.2.2.1
Condition: Improper/Lack of Maintenance
Action required: 705 - Other - as specified
Due 3 December 2017
Resolved 17 November 2017
Navigation › Voyage Data Recorder › Voyage Data Recorder (VDR)
Issued 22 June 2017Resolved
VDR not receiving video feed from RADARs. A ship 3,000 gross tonnage and upwards shall be fitted with a voyage data recorder (VDR). Repair VDR and verify proper operation via tech report to cognizant OCMI. 74SOLAS14 V/20.1.4
Action required: 705 - Other - as specified
Due 10 July 2017
Resolved 7 July 2017
Resolution: VDR repaired. Verified via tech report. All sat.
18 January 2006Routine · role: Involved in a Marine Casualty · activity 2571715
28 November 2006Routine · role: Involved in a Marine Casualty · activity 2863466
21 May 2008Routine · role: Involved in a Marine Casualty · serious marine incident, as classified · activity 3271671
25 January 2012Routine · role: Involved in a Marine Casualty · serious marine incident, as classified · activity 4232903
22 June 2013Routine · role: Involved in a Marine Casualty · activity 4630485
22 December 2016Routine · role: Involved in a Marine Casualty · activity 6061442
16 November 2021Routine · role: Involved in a Marine Casualty · 1 injured · activity 7355765
Each line is an incident investigation the Coast Guard recorded with this hull among the vessels involved, with the date and the classification the Coast Guard gave it. Involvement is not fault. The investigation narrative is not published. Source: IIR, through 2026.
Ownership record
The Coast Guard's documentation record for this hull -- the Abstract of Title,
with its owners and liens as filed -- is not in PSIX. Ask, and Maury buys it from the National
Vessel Documentation Center, files it here with its date, and every reader of this page gets it.