BARGE Appeared

Track · one row per mention

mentions

2

span

7,541 d

in force

28 d

along track

998 nm

first → last

998 nm

Events these messages belong to

• Spills · 2 messages2009-04-18 → 2009-05-28Mystery slick; w. cameron block 548, gom

Messages · 2, oldest first

1. 1
   Spills·NOAAORR-66071988-08-24 00:00Z → cancelled 1988-09-07 00:00Z
   Barge 565; chesapeake bay, virginia and maryland
   North Atlantic Ocean

   Barge 565; Chesapeake Bay, Virginia and Maryland.
   Chesapeake Bay, Virginia and Maryland.
   1. On August 24, 1988, the Barge 565 suffered a tank fracture while en route to Richmond, Virginia with its cargo of used fuel oil. A passing ship radioed the tow tug that the barge appeared to be sagging in the middle. Personnel on the tug reportedly smelled oil and believed that the barge was leaking. The barge was still underway at two knots when the U.S. Coast Guard Marine Safety Office (MSO), Hampton Roads, was notified around 0800. USCG district 5.
   2. COMMODITY: USED FUEL OIL. MAXIMUM POTENTIAL RELEASE: 168000 GALLONS.
   3. POSITION 37.016N 076.201W. NOAA INCIDENTNEWS 6607: https://incidentnews.noaa.gov/incident/6607

2. 2
   Spills·NOAAORR-80072009-04-18 00:00Z → cancelled 2009-05-02 00:00Z
   Kirby 29703 incident; gulf of mexico, offshore
   Gulf of Mexico

   Kirby 29703 Incident; Gulf of Mexico, Offshore.
   Gulf of Mexico, Offshore.
   1. On Friday morning, 17 April 2009, USCG Marine Safety Unit Port Arthur reported that a barge was observed damaged and adrift in the Gulf of Mexico. The observer reported that the barge appeared to have bene sheared in half and discharging an unknown material. Later it was determined that the barge, Kirby 29703 was in two pieces, and the bow section alone had been initially observed. The stern portion of the barge was initially attached to the tug, later released, and then sunk on its own. NOAA was requested to provide trajectory support to the USCG.
   2. THREAT: OTHER.
   3. POSITION 28.209N 092.952W. NOAA INCIDENTNEWS 8007: https://incidentnews.noaa.gov/incident/8007