FV Captain Justin

Track · one row per mention

mentions

2

span

0 d

in force

28 d

along track

0 nm

first → last

0 nm

Events these messages belong to

• Spills · 4 messages1998-12-15 → 1999-01-06Tampa bay, florida

Messages · 2, oldest first

1. 1
   Spills·NOAAORR-73651998-12-23 00:00Z → cancelled 1999-01-06 00:00Z
   Tampa bay, fl
   FV Captain Justin; Tampa Bay, Fl · Gulf of Mexico

   FV CAPTAIN JUSTIN; Tampa Bay, FL.
   Tampa Bay, FL.
   1. On December 23, 1998 a ship went aground in the Southwest channel, on the south side of Edgmont Key. The accident occurred at about between 0730 EST. By the end of the ebb tide at about 11:00 EST, a diesel slick extending out about 3 miles to the west-southwest was reported. The vessel contained a total of 6,000 gallons of diesel fuel. USCG district 7.
   2. COMMODITY: DIESEL. MAXIMUM POTENTIAL RELEASE: 6000 GALLONS.
   3. POSITION 27.575N 082.754W. NOAA INCIDENTNEWS 7365: https://incidentnews.noaa.gov/incident/7365

2. 2
   Spills·NOAAORR-73641998-12-23 00:00Z → cancelled 1999-01-06 00:00Z
   Tampa bay, florida
   F/V Captain Justin; Tampa Bay, Florida · Gulf of Mexico

   F/V Captain Justin; Tampa Bay, Florida.
   Tampa Bay, Florida.
   1. The F/V Captain Justin sank 1000 yards east of Egmont Key in Tampa Bay on the morning of December 23, 1998. Onboard were 6000 gallons of diesel fuel. Shortly after the vessel sank, a 3-mile sheen extending from the vessel's location seaward was reported On December 24 the vessel was submerged in 20 feet of water near Egmont Key. A preliminary salvage plan was submitted to the Unified Command. According to this plan, the Captain Justin was to be refloated on December 25. The Unified Command worked with the vessel's owner and salvor to complete formal salvage plans before salvage operations began. MSO investigators continued to investigate the cause of the incident. USCG district 7. Keyword: salvage.
   2. COMMODITY: DIESEL. MAXIMUM POTENTIAL RELEASE: 6000 GALLONS.
   3. POSITION 27.575N 082.754W. NOAA INCIDENTNEWS 7364: https://incidentnews.noaa.gov/incident/7364