<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:media="http://search.yahoo.com/mrss/"
	>

<channel>
	<title>Navigating the Regulatory Seas</title>
	<atom:link href="http://regulatoryseas.wordpress.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://regulatoryseas.wordpress.com</link>
	<description>Maritime Rules and Regulation News</description>
	<pubDate>Fri, 09 May 2008 16:19:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
	<language>en</language>
			<item>
		<title>The Importance of Maintaining Vessel Watertight Integrity</title>
		<link>http://regulatoryseas.wordpress.com/2008/05/09/the-importance-of-maintaining-vessel-watertight-integrity/</link>
		<comments>http://regulatoryseas.wordpress.com/2008/05/09/the-importance-of-maintaining-vessel-watertight-integrity/#comments</comments>
		<pubDate>Fri, 09 May 2008 16:12:54 +0000</pubDate>
		<dc:creator>raceassist</dc:creator>
		
		<category><![CDATA[Marine Safety]]></category>

		<category><![CDATA[United States Coast Guard]]></category>

		<guid isPermaLink="false">http://regulatoryseas.wordpress.com/?p=46</guid>
		<description><![CDATA[The latest from the Coast Guard&#8230;
USCG Marine Safety Alert 1-08
Assistant Commandant for Marine Safety, Security and Stewardship
May 9, 2008
Washington, DC  
Maintaining Vessel Watertight Integrity
This Safety Alert addresses two issues: watertight integrity and high level
bilge alarms. 
Recently a marine casualty involving a fishing vessel in the Bering Sea
resulted in multiple fatalities and complete loss of [...]]]></description>
			<content:encoded><![CDATA[<div class='snap_preview'><br /><p>The latest from the Coast Guard&#8230;</p>
<p>USCG Marine Safety Alert 1-08<br />
Assistant Commandant for Marine Safety, Security and Stewardship<br />
May 9, 2008</p>
<p>Washington, DC  </p>
<p>Maintaining Vessel Watertight Integrity</p>
<p>This Safety Alert addresses two issues: watertight integrity and high level<br />
bilge alarms. </p>
<p>Recently a marine casualty involving a fishing vessel in the Bering Sea<br />
resulted in multiple fatalities and complete loss of the vessel.  A Marine<br />
Board of Investigation is currently examining the various circumstances<br />
surrounding the casualty.  Although the investigation is not complete,<br />
testimony indicates the flooding of the vessel may have been exacerbated<br />
due to open or leaking watertight doors and other compartmental deficiencies<br />
which impacted the vessel&#8217;s overall watertight integrity.<br />
<span id="more-46"></span><br />
As a result of this and other similar casualties, the U. S. Coast Guard<br />
strongly recommends vessel owners and operators:</p>
<p>WATERTIGHT INTEGRITY</p>
<p>Ensure all watertight decks and bulkheads are inspected periodically to<br />
verify that there are no unprotected openings or improper penetrations that<br />
will allow progressive flooding and that closure devices (e.g. watertight<br />
doors, duct closures, etc.) are in place and in working order. </p>
<p>Ensure all crewmembers are familiar with the locations of the watertight<br />
doors (WTDs) and weather tight closures throughout their vessels. Knowing<br />
the locations of such WTDs and weather tight closures should be part of the<br />
crewmember vessel familiarization process.   </p>
<p>Ensure WTDs and hatches are closed while at sea and as otherwise specified<br />
in the stability guidance provided to the master or individual in charge.<br />
The importance of keeping WTDs and hatches closed should be emphasized on a<br />
regular basis (e.g. at safety meetings).  WTDs and hatches should be opened<br />
only briefly to allow passage and labeled appropriately to remind<br />
crewmembers to close them.  If they must remain open to permit work, WTDs<br />
and hatches should be attended at all times so that they can immediately be<br />
closed.  Any WTDs permitted to be open while the vessel is underway should<br />
be secured during drills to ensure they work properly.</p>
<p>Implement a WTD inspection program to ensure each WTD is regularly<br />
inspected and properly maintained.  As part of the inspection of each WTD, the<br />
following should be examined: straightness of the knife edge; the door<br />
assembly for twisting or warp-age; evidence of loose, missing seized or<br />
damaged components; permanent set in gasket material, cracks in the gasket;<br />
gaps at gasket joints; paint, rust, or other foreign material on gaskets,<br />
knife-edges and working parts; binding and difficult operations; and loose<br />
or excessively tight dogs. Rotating spindles of the dog, handles and<br />
hinges, and other points of friction should be lubricated to prevent seizing and<br />
allow proper closure. If fitted, the spindle packing should also be<br />
examined. </p>
<p>Ensure watertight hatches, dogged manholes, bolted manhole covers, and<br />
access plates are given similar examinations, focusing on the sealing<br />
surfaces and the method by which the hatch is secured.  Gasket materials<br />
should be replaced whenever they are found insufficient.  Regardless of the<br />
type of hatch or access, every component that secures the device, such as<br />
dogs, wing nuts, or bolts should be inspected, lubricated and free, and<br />
repaired or replaced as necessary to ensure they operate properly.  As with<br />
watertight doors, hatches and accesses should be labeled to indicate they<br />
remain closed while underway.  Most importantly, all securing devices must<br />
be used when the hatch or access is closed.  Improper closure of a hatch<br />
will not prevent flooding.</p>
<p>Ensure compartments and external hull structures fitted with ventilation<br />
ducts that have hinged covers with gaskets, hinges, sealing surfaces and<br />
securing mechanisms are regularly inspected and properly maintained (see<br />
above for guidance).  </p>
<p>Ensure electrical cables and conduits, piping runs, remote valve actuators,<br />
and other components that penetrate watertight bulkheads, decks, and<br />
compartments are inspected frequently and properly maintained.  Each may<br />
have a unique sealing method involving glands with packing assemblies,<br />
penetration seals, or other methods.  Frequent inspection and proper<br />
maintenance of these various fittings and assemblies will assist in<br />
minimizing the possibility of progressive flooding.</p>
<p>BILGE AND HIGH WATER ALARMS</p>
<p>Ensure water accumulation is minimized and all spaces are kept dry unless<br />
permitted by the stability instructions provided to the master or<br />
individual in charge.  </p>
<p>Ensure bilge high level alarms are arranged to provide the earliest<br />
warnings of abnormal accumulation.  The high level bilge alarms should be set as low<br />
as possible to the deck or bilge well and positioned along the centermost<br />
area of the compartment or in a location at which the fluids will gravitate<br />
to first.  In areas where bilge water routinely accumulates, the bilge high<br />
level alarms should be placed just above the point where under normal<br />
working conditions the accumulation would be pumped to a holding tank,<br />
overboard, or through an oily water separation system if required.  Alarms<br />
may be fitted with short time delays to prevent nuisance alarms caused by<br />
the rolling and pitching of the vessel.  </p>
<p>Ensure all crewmembers understand the importance of minimizing water in the<br />
bilges.</p>
<p>Provide the funding, labor, spare parts, and vessel availability necessary<br />
to ensure leakages stemming from machinery, equipment and other components<br />
are kept to a minimum at all times in accordance with good marine practice.</p>
<p>This safety alert is provided for informational purposes only and does not<br />
relieve any domestic or international safety, operational or material<br />
requirement.  Developed and distributed by the Office of Investigations and<br />
Analysis, United States Coast Guard Headquarters, Washington, DC. </p>
<p>*******</p>
<p>Office of Investigations and Analysis -<br />
<a href="http://www.marineinvestigations.us">http://www.marineinvestigations.us</a><br />
To subscribe - Kenneth.W.Olsen@uscg.mil</p>
<img alt="" border="0" src="http://feeds.wordpress.com/1.0/categories/regulatoryseas.wordpress.com/46/" /> <img alt="" border="0" src="http://feeds.wordpress.com/1.0/tags/regulatoryseas.wordpress.com/46/" /> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/regulatoryseas.wordpress.com/46/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/regulatoryseas.wordpress.com/46/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/regulatoryseas.wordpress.com/46/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/regulatoryseas.wordpress.com/46/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/regulatoryseas.wordpress.com/46/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/regulatoryseas.wordpress.com/46/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/regulatoryseas.wordpress.com/46/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/regulatoryseas.wordpress.com/46/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/regulatoryseas.wordpress.com/46/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/regulatoryseas.wordpress.com/46/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=regulatoryseas.wordpress.com&blog=2609173&post=46&subd=regulatoryseas&ref=&feed=1" /></div>]]></content:encoded>
			<wfw:commentRss>http://regulatoryseas.wordpress.com/2008/05/09/the-importance-of-maintaining-vessel-watertight-integrity/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Long Range Identification and Tracking and you.</title>
		<link>http://regulatoryseas.wordpress.com/2008/05/07/long-range-identification-and-tracking-and-you/</link>
		<comments>http://regulatoryseas.wordpress.com/2008/05/07/long-range-identification-and-tracking-and-you/#comments</comments>
		<pubDate>Wed, 07 May 2008 14:28:44 +0000</pubDate>
		<dc:creator>raceassist</dc:creator>
		
		<category><![CDATA[Federal Regulations]]></category>

		<category><![CDATA[Holland and Knight]]></category>

		<category><![CDATA[United States Coast Guard]]></category>

		<guid isPermaLink="false">http://regulatoryseas.wordpress.com/?p=45</guid>
		<description><![CDATA[Here is the latest from the Holland and Knight  newsletter regarding Long Range Identification and Tracking (LRIT) for all you passenger vessels out there. 
The US Coast Guard promulgated its final rule requiring certain ships to report identifying and position data electronically, utilizing the Long Range Identification and Tracking (LRIT) system.  The rule [...]]]></description>
			<content:encoded><![CDATA[<div class='snap_preview'><br /><p>Here is the latest from the <a href="http://www.hklaw.com">Holland and Knight </a> newsletter regarding Long Range Identification and Tracking (LRIT) for all you passenger vessels out there. </p>
<p>The US Coast Guard promulgated its final rule requiring certain ships to report identifying and position data electronically, utilizing the Long Range Identification and Tracking (LRIT) system.  The rule requires transmission of the LRIT data, effective December 31, 2008 for the following ships, while engaged on an international voyage: (1) passenger ships, including high speed passenger craft; (2) cargo ships, including high speed craft, of 300 gross tonnage or more; and (3) mobile offshore drilling units (MODUs) while underway and not engaged in drilling operations.  </p>
<p>For the rest of the document, click <a href="http://a257.g.akamaitech.net/7/257/2422/01jan20081800/edocket.access.gpo.gov/2008/pdf/E8-9182.pdf">73 Fed. Reg. 23310</a> </p>
<img alt="" border="0" src="http://feeds.wordpress.com/1.0/categories/regulatoryseas.wordpress.com/45/" /> <img alt="" border="0" src="http://feeds.wordpress.com/1.0/tags/regulatoryseas.wordpress.com/45/" /> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/regulatoryseas.wordpress.com/45/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/regulatoryseas.wordpress.com/45/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/regulatoryseas.wordpress.com/45/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/regulatoryseas.wordpress.com/45/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/regulatoryseas.wordpress.com/45/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/regulatoryseas.wordpress.com/45/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/regulatoryseas.wordpress.com/45/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/regulatoryseas.wordpress.com/45/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/regulatoryseas.wordpress.com/45/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/regulatoryseas.wordpress.com/45/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=regulatoryseas.wordpress.com&blog=2609173&post=45&subd=regulatoryseas&ref=&feed=1" /></div>]]></content:encoded>
			<wfw:commentRss>http://regulatoryseas.wordpress.com/2008/05/07/long-range-identification-and-tracking-and-you/feed/</wfw:commentRss>
		</item>
		<item>
		<title>New dates for TWIC announced</title>
		<link>http://regulatoryseas.wordpress.com/2008/05/06/new-dates-for-twic-announced/</link>
		<comments>http://regulatoryseas.wordpress.com/2008/05/06/new-dates-for-twic-announced/#comments</comments>
		<pubDate>Tue, 06 May 2008 13:56:00 +0000</pubDate>
		<dc:creator>raceassist</dc:creator>
		
		<category><![CDATA[Merchant Mariners Credential]]></category>

		<category><![CDATA[TWIC]]></category>

		<category><![CDATA[Uncategorized]]></category>

		<category><![CDATA[United States Coast Guard]]></category>

		<guid isPermaLink="false">http://regulatoryseas.wordpress.com/?p=44</guid>
		<description><![CDATA[In case you missed the latest in Homeland Security news yesterday, here are the new compliance dates for obtaining your TWIC:
- October 15, 2008 &#8211; ALL 33 CFR Part 105 compliant facilities in Sector Southeastern New England must comply with TWIC.
- April 15, 2009 &#8211; ALL Merchant Mariners and 33 CFR Part 104 compliant vessels [...]]]></description>
			<content:encoded><![CDATA[<div class='snap_preview'><br /><p>In case you missed the latest in Homeland Security news yesterday, here are the new compliance dates for obtaining your TWIC:</p>
<p>- <strong>October 15, 2008 </strong>&#8211; ALL 33 CFR Part 105 compliant facilities in Sector Southeastern New England must comply with TWIC.</p>
<p>- <strong>April 15, 2009 </strong>&#8211; ALL Merchant Mariners and 33 CFR Part 104 compliant vessels must comply with TWIC. </p>
<p>- <strong>June 2008 </strong>&#8211; Sector Southeastern New England will sponsor Port Safety and Security Forum&#8217;s in Rhode Island and Massachusetts to answer additional questions regarding TWIC compliance.  </p>
<p>The Department of Homeland Security Press Release on TWIC compliance dates is provided below for your information.  If you have questions, please call LT Merridith Morrison at (401) 435-2361 or Merridith.R.Morrison@uscg.mil.  </p>
<p><a href='http://regulatoryseas.files.wordpress.com/2008/05/dhs-realigns-twic-compliance-date.pdf'>Department of Homeland Security Press Release</a></p>
<img alt="" border="0" src="http://feeds.wordpress.com/1.0/categories/regulatoryseas.wordpress.com/44/" /> <img alt="" border="0" src="http://feeds.wordpress.com/1.0/tags/regulatoryseas.wordpress.com/44/" /> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/regulatoryseas.wordpress.com/44/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/regulatoryseas.wordpress.com/44/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/regulatoryseas.wordpress.com/44/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/regulatoryseas.wordpress.com/44/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/regulatoryseas.wordpress.com/44/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/regulatoryseas.wordpress.com/44/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/regulatoryseas.wordpress.com/44/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/regulatoryseas.wordpress.com/44/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/regulatoryseas.wordpress.com/44/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/regulatoryseas.wordpress.com/44/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=regulatoryseas.wordpress.com&blog=2609173&post=44&subd=regulatoryseas&ref=&feed=1" /></div>]]></content:encoded>
			<wfw:commentRss>http://regulatoryseas.wordpress.com/2008/05/06/new-dates-for-twic-announced/feed/</wfw:commentRss>
		</item>
		<item>
		<title>New Deadline for TWIC-April 15, 2009</title>
		<link>http://regulatoryseas.wordpress.com/2008/05/05/new-deadline-for-twic-april-15-2009/</link>
		<comments>http://regulatoryseas.wordpress.com/2008/05/05/new-deadline-for-twic-april-15-2009/#comments</comments>
		<pubDate>Mon, 05 May 2008 20:23:55 +0000</pubDate>
		<dc:creator>raceassist</dc:creator>
		
		<category><![CDATA[Department of Homeland Security]]></category>

		<category><![CDATA[Maritime Administration]]></category>

		<category><![CDATA[TWIC]]></category>

		<category><![CDATA[United States Coast Guard]]></category>

		<guid isPermaLink="false">http://regulatoryseas.wordpress.com/?p=39</guid>
		<description><![CDATA[From the U.S. Department of Homeland Security&#8230;.
DHS REALIGNS TWIC COMPLIANCE DATE 
WASHINGTON – The U.S Department of Homeland Security (DHS) today announced that the final compliance date for the Transportation Worker Identification Credential (TWIC) program will be April 15, 2009, which reflects a realignment of the Sept. 25, 2008 compliance date set in the final [...]]]></description>
			<content:encoded><![CDATA[<div class='snap_preview'><br /><p>From the U.S. Department of Homeland Security&#8230;.</p>
<p><strong>DHS REALIGNS TWIC COMPLIANCE DATE </strong></p>
<p>WASHINGTON – The U.S Department of Homeland Security (DHS) today announced that the final compliance date for the Transportation Worker Identification Credential (TWIC) program will be April 15, 2009, which reflects a realignment of the Sept. 25, 2008 compliance date set in the final rule.  The seven month extension is a direct result of collaboration with port officials and industry, and realigns the enrollment period with the original intent of the TWIC final rule.  </p>
<p> <span id="more-39"></span></p>
<p>TWIC was established in the Maritime Transportation Security Act and the SAFE Port Act to serve as an identification program for all Coast Guard credentialed mariners and personnel requiring unescorted access to secure areas within a port.  The program is on track to complete enrollment for a substantial number of jurisdictions by the end of 2008, and several ports will be required to comply with TWIC regulations this year.  </p>
<p>Owners and operators of facilities located within Captain of the Port Zones Boston, Northern New England, and Southeastern New England will need to comply by October 15, 2008.  These three ports were selected based on favorable conditions that facilitate near-term implementation.  These ports are ideal for initial compliance based upon geographic proximity, the size of their TWIC enrollment population, and respective enrollment efforts to date.  Additional ports will be announced in the coming weeks, and the Coast Guard will provide at least 90 days notice prior to enforcement.  </p>
<p>The TWIC program is progressing steadily and has opened more than 100 fixed enrollment centers and dozens of mobile sites nationwide.  More than 250,000 workers have enrolled to date and thousands more are processed each week.  Enrollment began at the Port of Wilmington, Del. in October 2007. </p>
<p>Workers can pre-enroll online at <a href="http://www.tsa.gov/twic">www.tsa.gov/twic</a>.  Pre-enrollment can accelerate credentialing by allowing workers to provide biographic information and schedule a time to complete the application process in person.  This eliminates delays at enrollment centers and reduces total enrollment time for each worker.</p>
<p>Although the compliance date has been extended seven months, workers are encouraged to enroll as soon as possible.  Additional information can be found on the U.S. Coast Guard&#8217;s Homeport site, <a href="http://homeport.uscg.mil">http://homeport.uscg.mil</a>, and on the Transportation Security Administration’s web site at <a href="http://www.tsa.gov/twic">www.tsa.gov/twic</a>. </p>
<p> ### </p>
<p><em>Please note: We are experiencing a delay in credential notification due to various reasons. For enrollees with fingerprint capturing problems, LM has implemented a series of patches to remedy the problem. The final patch is due out on June 6. </em></p>
<p><em>If you enrolled in November – January and have not received notification, please check your status at <a href="http://twicinformation.tsa.dhs.gov/twicinfo/">twicinformation.tsa.dhs.gov </a>or contact the Help Desk at 866-DHS-TWIC. The call center is experiencing a high volume of calls and there might be a long wait for assistance.</em></p>
<p>If you are interested in a mobile station at your location or area, please go to <a href="http://twicinformation.tsa.dhs.gov/twicinfo/">twicinformation.tsa.dhs.gov</a> at FAQs for more information.</p>
<img alt="" border="0" src="http://feeds.wordpress.com/1.0/categories/regulatoryseas.wordpress.com/39/" /> <img alt="" border="0" src="http://feeds.wordpress.com/1.0/tags/regulatoryseas.wordpress.com/39/" /> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/regulatoryseas.wordpress.com/39/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/regulatoryseas.wordpress.com/39/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/regulatoryseas.wordpress.com/39/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/regulatoryseas.wordpress.com/39/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/regulatoryseas.wordpress.com/39/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/regulatoryseas.wordpress.com/39/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/regulatoryseas.wordpress.com/39/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/regulatoryseas.wordpress.com/39/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/regulatoryseas.wordpress.com/39/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/regulatoryseas.wordpress.com/39/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=regulatoryseas.wordpress.com&blog=2609173&post=39&subd=regulatoryseas&ref=&feed=1" /></div>]]></content:encoded>
			<wfw:commentRss>http://regulatoryseas.wordpress.com/2008/05/05/new-deadline-for-twic-april-15-2009/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Replacement EPIRB deadline announced</title>
		<link>http://regulatoryseas.wordpress.com/2008/04/21/replacement-epirb-deadline-announced/</link>
		<comments>http://regulatoryseas.wordpress.com/2008/04/21/replacement-epirb-deadline-announced/#comments</comments>
		<pubDate>Mon, 21 Apr 2008 13:43:34 +0000</pubDate>
		<dc:creator>raceassist</dc:creator>
		
		<category><![CDATA[Holland and Knight]]></category>

		<category><![CDATA[Marine Safety]]></category>

		<category><![CDATA[United States Coast Guard]]></category>

		<guid isPermaLink="false">http://regulatoryseas.wordpress.com/?p=38</guid>
		<description><![CDATA[From the Holland and Knight Newsletter:  USCG – reminder to replace older EPIRBs 
The US Coast Guard issued a press release reminding mariners that older model Emergency Position Indicating Radio Beacons (EPIRBs) that broadcast on 121.5 MHz or 243 MHz will not be monitored by satellite as of February 1, 2009.  Effective that [...]]]></description>
			<content:encoded><![CDATA[<div class='snap_preview'><br /><p>From the <a href="http://www.hklaw.com">Holland and Knight Newsletter</a>:  USCG – reminder to replace older EPIRBs </p>
<p>The US Coast Guard issued a press release reminding mariners that older model Emergency Position Indicating Radio Beacons (EPIRBs) that broadcast on 121.5 MHz or 243 MHz will not be monitored by satellite as of <strong>February 1, 2009</strong>.  Effective that date, the satellites will only monitor for radio beacons broadcasting on 406 MHz.  Some of the newer EPIRBs are equipped with embedded GPS, which will automatically signal the location of the distress. </p>
<p>The official <a href="http://www.uscglosangeles.com/go/doc/830/198867/">press release </a>after the jump. </p>
<img alt="" border="0" src="http://feeds.wordpress.com/1.0/categories/regulatoryseas.wordpress.com/38/" /> <img alt="" border="0" src="http://feeds.wordpress.com/1.0/tags/regulatoryseas.wordpress.com/38/" /> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gocomments/regulatoryseas.wordpress.com/38/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/comments/regulatoryseas.wordpress.com/38/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godelicious/regulatoryseas.wordpress.com/38/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/delicious/regulatoryseas.wordpress.com/38/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/gostumble/regulatoryseas.wordpress.com/38/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/stumble/regulatoryseas.wordpress.com/38/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/godigg/regulatoryseas.wordpress.com/38/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/digg/regulatoryseas.wordpress.com/38/" /></a> <a rel="nofollow" href="http://feeds.wordpress.com/1.0/goreddit/regulatoryseas.wordpress.com/38/"><img alt="" border="0" src="http://feeds.wordpress.com/1.0/reddit/regulatoryseas.wordpress.com/38/" /></a> <img alt="" border="0" src="http://stats.wordpress.com/b.gif?host=regulatoryseas.wordpress.com&blog=2609173&post=38&subd=regulatoryseas&ref=&feed=1" /></div>]]></content:encoded>
			<wfw:commentRss>http://regulatoryseas.wordpress.com/2008/04/21/replacement-epirb-deadline-announced/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>