MAURY USCG vessel records
← All vessels

CHALLENGER

CHALLENGER is a 1969 commercial fishing vessel. The Coast Guard has recorded 3 inspections since 2018, most recently in March 2019, along with 1 casualty investigation in 2019.

Records from 2018 to 2019. Most recent: inspection, 16 March 2019.

Built
1969
Last inspected
16 March 2019
Documentation
Valid · documentation file of 10 August 2026
Controls
None recorded without a removal date

This record may be incomplete: the most recent inspection recorded for this vessel was 7 years ago. Maury shows what the Coast Guard recorded, not whether the vessel has been inspected since, is still in service, or what condition it is in. 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 Fishing Vessel class in Maury's sources begin in 2016.

Inspection record

Last inspected 16 March 2019
…with no type recorded2
Operational controls None recorded without a removal date
Years with a record 2 calendar years (2018–2019)
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

WAR4531
100379
Flag
UNITED STATES
Maury page id
psix-100379

Documentation record

Registered dimensions (L × B × D)58.0 ft × 17.0 ft × 8.0 ft
Registered tonnagegross 52 / net 42
ITC dimensions (L × B × D)Not recorded
ITC tonnageNot recorded
BuilderMARINE VIEW BOAT BUILDING · TACOMA, WA, UNITED STATES · built 1969
Hull materialWood
PropulsionDiesel Direct
Hull shapeShip
Hull configurationMonohull
Hailing portJUNEAU, AK
Trade endorsementsFishery
DocumentationValid · issued 26 May 2026 · expires 30 April 2027
Service, as the file records itCommercial Fishing Vessel
Hull formpowered (Maury's inference from propulsion, hull shape, material and length, rule hf-1; not a recorded fact)
Tonnage as PSIX records it42 - Simplified, Net Ton
52 - Simplified, Gross 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

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 · 3

16 March 2019 Type not recorded
No type recorded · Sector Puget Sound · USCG Northwest District (CGD-NW) · Activity 6702595
19 October 2018 Type not recorded
No type recorded · Sector Puget Sound · USCG Northwest District (CGD-NW) · Activity 6572709
7 March 2018 Administrative Inspection
Administrative · Navigation Center · Activity 6367514

Deficiency record · 0

No deficiencies recorded against this vessel. This means none were written in the records covered — it is not a statement about the vessel's condition. What a recorded resolution is.

Casualty record · 1

16 March 2019Routine · role: Involved in a Marine Casualty · serious marine incident, as classified · activity 6702595
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.