LIBERTY is a 2007 towing vessel. The Coast Guard has recorded 40 inspections since 2008, most recently in July 2026, along with 6 deficiencies and 19 casualty investigations between 2009 and 2025.
Records from 2008 to 2026. Most recent: inspection, 2 July 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 Towing Vessel class in Maury's sources begin in 1980.
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.
Registered dimensions (L × B × D)87.4 ft × 32.0 ft × 13.9 ft
Registered tonnagegross 148 / net 31
ITC dimensions (L × B × D)87.4 ft × 32.0 ft × 13.9 ft
ITC tonnagegross 235 / net 70
BuilderWASHBURN & DOUGHTY ASSOC INC · EAST BOOTHBAY, ME, UNITED STATES · built 2007
Hull materialSteel
PropulsionDiesel Reduction
Hull shapeUNSPECIFIED
Hull configurationUNSPECIFIED
Hailing portTAMPA, FL
Trade endorsementsCoastwise, unrestricted
DocumentationValid · issued 6 May 2026 · expires 30 June 2027
Service, as the file records itTowing Vessel
Hull formpowered (Maury's inference from propulsion, hull shape, material and length, rule hf-1; not a recorded fact)
Tonnage as PSIX records it235 - Convention (Subpart B), Gross Ton 148 - Regulatory (Subpart C or D), Gross Ton 70 - Convention (Subpart B), Net Ton 31 - Regulatory (Subpart C or D), Net 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, 1980 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.
13 - Propulsion and Auxiliary Machinery › N/A - No Subsystem › Propulsion main engine
Issued 2 July 2026Resolved
Propulsion machinery must be maintained to ensure proper operation.
Vessel experienced a temporary loss of propulsion on the port main engine while operating in Port Manatee.
Make proper notification to vessel's TPO.
Provide diagnosis of shutdown cause and prove proper operation and/or repairs of port main engine to the satisfaction of OCMI.
46 CFR 143.205
Action required: 60 - Rectify deficiencies prior to movement
Due 2 July 2026
Resolved 2 July 2026
Resolution: Replaced both lube oil pressure sensors on the engine.
15 - Safety Management Systems (ISM) › N/A - No Subsystem › Maintenance of the ship and equipment
Issued 24 May 2023Resolved
A safety management system (SMS) which is fully compliant with the International Safety Management (ISM) Code requirements, implemented in 33 CFR part 96, will be deemed in compliance with TSMS-related requirements in this subchapter. The company should ensure that all personnel involved in the company’s safety management system have an adequate understanding of relevant rules, regulations codes and guidelines. In meeting these requirements, the company should ensure that:
.2 any non-conformity is reported, with its possible cause, if known;
.3 appropriate corrective action is taken;
Machinery Space Emergency Watertight hatch was leaking, due to waisted knife edge. Vessels crew placed plastic container under hatch to catch rain water. The vessels crew never reported the def, IAW vessels SMS. Note: Vessel utilizes checklists for crew changes between the engineering and deck department. All items had been checked as being satisfactory from both departments on 5/22/2023 and 5/23/2023. Also, vessels crew completed monthly PMS on the watertight hatch on 4/28/2023, with no deficiencies recorded. Vessel is required to conduct internal audit of the SMS, focusing on PMS, and properly completing checklist within 90 days.
46 CFR 138-225(a)
ISM Code 6.4/10.2
Action required: 705 - Other - as specified
Due 24 August 2023
Resolved 25 May 2023
Resolution: Welded a new scuttle ring- all sat.
03 - Water/Weathertight Conditions › N/A - No Subsystem › Machinery space openings
Issued 24 May 2023Resolved
All hatchways in position 1 and 2 shall be fitted with hatch covers of steel or other equivalent material. Such hatch covers shall be weather tight and fitted with gaskets and clamping devices. The arrangements shall ensure that the tightness can be maintained in any sea conditions. MI conducted a visual inspection of the machinery space emergency escape hatch and discovered waisted/holed knife edges. Witnessed failed water hose test to watertight hatch, resulting in water intrusion into machinery space.
ICLL (88) 16.1
Action required: 17 - Rectify deficiencies prior to departure
Due 24 May 2023
Resolved 25 May 2023
Resolution: knife edge of 1 inch x 24 inches inch in diameter for the emergency escape hatch was cropped to fair metal and sound material and replaced as original.
13 - Propulsion and Auxiliary Machinery › N/A - No Subsystem › Auxiliary engine
Issued 6 November 2018Resolved
Verify that the vessel complies with applicable requirements in part 143 of this subchapter, examine the condition of, and where appropriate, witness the operation of all generators. Provide MI with tech report detailing root cause of No 1. generator malfunction, repair as necessary and demonstrate proper operation and reliability to the satisfaction of the attending marine inspector.
Action required: 705 - Other - as specified
Due 13 November 2018
Resolved 8 November 2018
Resolution: New ECU was installed and tested in presence of class and MI.
13 - Propulsion and Auxiliary Machinery › N/A - No Subsystem › Auxiliary engine
Issued 12 September 2018Resolved
Verify that the vessel complies with applicable requirements in part 143 of this subchapter, examine the condition of, and where appropriate, witness the operation of all generators. Provide MI with tech report detailing root cause of stbd generator malfunction, repair as necessary and demonstrate proper operation and reliability to the satisfaction of the attending marine inspector. iaw 46CFR137.220(f)(4)
Condition: Improper/Lack of Maintenance
Action required: 705 - Other - as specified
Due 19 September 2018
Resolved 18 September 2018
Resolution: Authorized service technician, John Deere, found the root cause of the failure of the No. 1 Generator to be a faulty oil pressure sensor. The faulty sensor was replaced and checked. Engine was operationally tested and alarm performance test conducted in
10 - Safety of Navigation › N/A - No Subsystem › Automatic Identification System (AIS)
Issued 15 August 2018Resolved
Vsl is broadcasting: No static draft information.
Condition: Invalid
Action required: 705 - Other - as specified
Due 15 September 2018
Resolved 2 October 2018
21 August 2009Routine · role: Involved in a Marine Casualty · serious marine incident, as classified · 1 injured · activity 3573022
9 November 2011Routine · role: Involved in a Marine Casualty · serious marine incident, as classified · 1 injured · activity 4186455
17 July 2017Routine · role: Moored/Anchored in Vicinity of Primary Subject · activity 6213132
12 November 2017Routine · role: Involved in a Marine Casualty · activity 6317863
15 June 2018Routine · role: Involved in a Marine Casualty · activity 6445274
13 July 2018Routine · role: Involved in a Marine Casualty · activity 6483686
2 September 2018Routine · role: Transiting Vicinity of Primary Subject · activity 6533005
12 September 2018Routine · role: Involved in a Marine Casualty · activity 6547496
17 May 2019Routine · role: Involved in a Marine Casualty · activity 6704771
17 April 2020Routine · role: Involved in a Marine Casualty · activity 6942707
20 November 2020Routine · role: Involved in a Marine Casualty · activity 7099334
28 December 2020Routine · role: Involved in a Marine Casualty · activity 7117441
25 May 2022Routine · role: Involved in a Marine Investigation (non-casualty) · activity 7499423
18 June 2022Routine · role: Involved in a Marine Investigation (non-casualty) · activity 7485030
20 November 2022Routine · role: Involved in a Marine Casualty · activity 7601521
29 April 2023Routine · role: Involved in a Marine Casualty · activity 7696877
29 June 2023Routine · role: Involved in a Marine Casualty · activity 7726320
15 March 2024Routine · role: Involved in a Marine Investigation (non-casualty) · activity 7881695
27 January 2025Routine · role: Involved in a Marine Casualty · activity 8106460
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.