VELOS EMERALD

Tank Ship · Built 2000s · USCG Heartland District (CGD-H)

VELOS EMERALD is a 2008 tank ship. The Coast Guard has recorded 4 inspections since 2018, most recently in November 2025, along with 4 deficiencies.

Records from 2018 to 2025. Most recent: inspection, 4 November 2025.

Built: 2008
Last inspected: 4 November 2025
Documentation: Not in the documentation file of 10 August 2026
Inspections: 4
Deficiencies: 4 recorded · 0 without a recorded resolution
Controls: None recorded without a removal date

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.

Inspection record

Last inspected 4 November 2025

Recorded inspections4

…physical examinations3

…administrative events1

Deficiencies 4 recorded · 0 without a recorded resolution

Operational controls None recorded without a removal date

Years with a record 2 calendar years (2018–2025)

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.

Identity

—

9402213

V7A4663

996888

Flag

MARSHALL ISLANDS

Maury page id

psix-996888

Documentation record

Tonnage as PSIX records it59259 - Convention (Subpart B), Gross Ton
35459 - Convention (Subpart B), Net Ton
115042 - Dead Weight, Metric Ton
131630 - Displacement, Metric Ton

This hull's Official Number is not in the NVDC file dated 10 August 2026 as served by NOAA Fisheries, so no documentation record is shown. Absence from that file is a fact about the file, not about the hull.

Vessel history report

A report is not offered for this hull. Its record holds only 1 of the seven kinds of material a report is built from: inspections, deficiencies, operational controls, tow-unit appearances, casualty records, dimensions and documentation. That is a statement about the record, not about the vessel. What a sparse-record report looks like.

Inspection history · 4

4 November 2025 Deficiency Check

Physical examination · Marine Safety Unit Texas City · USCG Heartland District (CGD-H) · Activity 8264022

6 October 2025 Administrative Inspection

Administrative · Sector New Orleans · USCG Heartland District (CGD-H) · Activity 8247031

16 September 2025 PSC B · COC-TVE Renew

Physical examination · Sector New Orleans · USCG Heartland District (CGD-H) · Activity 8229394

3 October 2018 Ballast Water Examination · ISPS II Exam · COC-TVE Renew

Physical examination · Resident Inspection Office St. Croix · USCG Southeast District (CGD-SE) · Activity 6548423

Deficiency record · 4

11 - Life Saving Appliances › N/A - No Subsystem › Lifeboats

Issued 16 September 2025 Resolved

Before the ship leaves port and at all times during the voyage, all life-saving appliances shall be in working order and ready for immediate use. PSCO observed starboard side lifboat was not capable of starting. 74SOLAS(cons.) III/20.2 17ac

Condition: Improper/Lack of Maintenance
Action required: 17 - Rectify deficiencies prior to departure
Resolved 16 September 2025
Resolution: Received class report attesting to operation of life boat engine.

11 - Life Saving Appliances › N/A - No Subsystem › Maintenance and inspections

Issued 16 September 2025 Resolved

The following tests and inspections shall be carried out weekly and report of the inspection shall be entered in the logbook: all engines in lifeboats and rescue boats shall be run for a total period of not less than 3 minutes. It was reported to the PSCO that engines were not started on the last weekly check. 74SOLAS(cons.)III/20.6 40ac

Action required: 40 - Rectify deficiencies prior to next US port after sailing foreign
Resolved 6 October 2025
Resolution: Received internal audit stating training on lifeboats inspections and recording was completed.

15 - Safety Management Systems (ISM) › N/A - No Subsystem › Shipboard operations

Issued 16 September 2025 Resolved

The company and the ship shall comply with the requirements of the International Safety Management Code. The Company should establish procedures, plans and instructions, including checklists as appropriate for key shipboard operations concerning the safety of the personnel, ship and protection of the environment. When reviewing records it was observed that the company provided from for documenting LSA weekly inspections (MTN02813) has not been used since August 2025. Additionally, it was recorded in ORB pt II that a simulation test was conducted on 16AUG2025 for the ODME; it was later observed that no test was actually completed IAW company procedures. Request that an internal audit be conducted within 90 days. 74SOLAS(cons.)IX/3.1 ISM Code 7 abc

Action required: 705 - Other - as specified
Due 15 December 2025
Resolved 6 October 2025
Resolution: Received internal audit report accepted by flag and class.

06 - Cargo Operations Including Equipment › N/A - No Subsystem › Cargo transfer - Tankers

Issued 16 September 2025 Resolved

Each cargo tank of a tankship must be equipped with an intrinsically safe high-level alarm and a tank overfill alarm. The tank overfill alarm must activate a visible and audible alarm so that it can be seen and heard on the vessel where cargo transfer is controlled. PSCO observed overfill alarm on COT(6 port) is inoperable. Prior to loading COT 6 port, vessel must submit risk assessment satisfactory to COTP. 46CFR39.2007(d)(3) 40ac

Condition: Improper/Lack of Maintenance
Action required: 40 - Rectify deficiencies prior to next US port after sailing foreign
Resolved 17 October 2025
Resolution: The spare sensor for No.6 C.O.T.(P) overfill alarm was received, installed, tested, and found to be fully functioning.

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.