09.11.2012 Views

2012 Ocean Ranger Guidebook Revision 3-7-12 - Alaska ...

2012 Ocean Ranger Guidebook Revision 3-7-12 - Alaska ...

2012 Ocean Ranger Guidebook Revision 3-7-12 - Alaska ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>20<strong>12</strong></strong> <strong>Ocean</strong> <strong>Ranger</strong> <strong>Guidebook</strong> 3-7-<strong>12</strong><br />

Authority: AS 46.03.020 AS 46.14.030 Sec. 30, ch. 74, SLA 1993AS 46.14.010<br />

Job Aid Item: 4.1.b<br />

Text: Incinerator operation and procedures (observed if in operation) are IAW 18 AAC 50.050 and<br />

50.070<br />

Background: Cruise ships use incinerators to burn paper and other materials to reduce offloads to shore.<br />

Please note: incinerator use in port is not restricted by <strong>Alaska</strong>n law or regulations, as long as opacity<br />

limits are met. Many ships voluntarily limit incinerator use in port, but this is not a requirement.<br />

What to check for: Incinerators need to be operated below 20% opacity. Although <strong>Ocean</strong> <strong>Ranger</strong>s are<br />

not trained in Method 9, it is possible to observe for thick smoke, soot dropping from plume, that<br />

opacity meters are not in alarm, or that items are burned that create toxic smoke. Some of the items<br />

incinerated can cause higher opacity if not handled well, these include oily rags, oil filters, rubber<br />

materials, etc. Oily sludge or spent fuels have also been seen to increase opacity if not properly<br />

monitored.<br />

Some incinerators have emissions controls, these controls can affect the opacity performance, if they<br />

are installed check how they are used.<br />

Is the incinerator co-fired?<br />

Figure 5- Incinerator Display Console<br />

Citations: 18 AAC 50.050. Incinerator emission standards.<br />

154

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!