<?xml version="1.0" encoding="UTF-8"?>
<FEDREG xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="FRMergedXML.xsd">
    <VOL>68</VOL>
    <NO>234</NO>
    <DATE>Friday, December 5, 2003</DATE>
    <UNITNAME>Contents</UNITNAME>
    <CNTNTS>
        <AGCY>
            <EAR>Agriculture</EAR>
            <PRTPAGE P="iii"/>
            <HD>Agriculture Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Animal and Plant Health Inspection Service</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Commodity Credit Corporation</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Forest Service</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Animal</EAR>
            <HD>Animal and Plant Health Inspection Service</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Overtime services relating to imports and exports:</SJ>
                <SJDENT>
                    <SJDOC>Commuted traveltime allowances, </SJDOC>
                    <PGS>67937-67938</PGS>
                    <FRDOCBP T="05DER1.sgm" D="2">03-30230</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency information collection activities; proposals, submissions, and approvals, </DOC>
                    <PGS>68015-68020</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30231</FRDOCBP>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30232</FRDOCBP>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30233</FRDOCBP>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30234</FRDOCBP>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30235</FRDOCBP>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30236</FRDOCBP>
                </DOCENT>
                <SJ>Environmental statements; availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Double-crested cormorant management, </SJDOC>
                    <PGS>68020</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30229</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Vaccination of wild, free-ranging bison in Greater Yellowstone Area, ID, MT, and WY, </SJDOC>
                    <PGS>68020-68021</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30237</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Blind</EAR>
            <HD>Blind or Severely Disabled, Committee for Purchase From  People Who Are</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Committee for Purchase From People Who Are Blind or Severely Disabled</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Broadcasting</EAR>
            <HD>Broadcasting Board of Governors</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Meetings; Sunshine Act, </DOC>
                    <PGS>68025</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30339</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Census</EAR>
            <HD>Census Bureau</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency information collection activities; proposals, submissions, and approvals, </DOC>
                    <PGS>68026-68027</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30240</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Centers</EAR>
            <HD>Centers for Disease Control and Prevention</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency information collection activities; proposals, submissions, and approvals, </DOC>
                    <PGS>68086-68087</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30257</FRDOCBP>
                </DOCENT>
                <SJ>Meetings:</SJ>
                <SUBSJ>National Center on Birth Defects and Development Disabilities—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Impact of maternal thyroid disease on developing fetus; implications for diagnosis, treatment, and screening; workshop, </SUBSJDOC>
                    <PGS>68087</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30216</FRDOCBP>
                </SSJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Centers</EAR>
            <HD>Centers for Medicare &amp; Medicaid Services</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Medicare:</SJ>
                <SJDENT>
                    <SJDOC>Ambulance services; coverage and payment; 2004 inflation update, </SJDOC>
                    <PGS>67960-67963</PGS>
                    <FRDOCBP T="05DER1.sgm" D="4">03-30152</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Photocopying reimbursement methodology, </SJDOC>
                    <PGS>67955-67960</PGS>
                    <FRDOCBP T="05DER1.sgm" D="6">03-30096</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency information collection activities; proposals, submissions, and approvals, </DOC>
                    <PGS>68087-68088</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30200</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Coast Guard</EAR>
            <HD>Coast Guard</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Ports and waterways safety:</SJ>
                <SJDENT>
                    <SJDOC>Coronado Bay Bridge, San Diego, CA; security zone, </SJDOC>
                    <PGS>67946-67948</PGS>
                    <FRDOCBP T="05DER1.sgm" D="3">03-30277</FRDOCBP>
                </SJDENT>
                <SJ>Regattas and marine parades:</SJ>
                <SJDENT>
                    <SJDOC>2003 Holiday Boat Parade, </SJDOC>
                    <PGS>67944-67946</PGS>
                    <FRDOCBP T="05DER1.sgm" D="3">03-30278</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Commerce</EAR>
            <HD>Commerce Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Census Bureau</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Economic Analysis Bureau</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Industry and Security Bureau</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> International Trade Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> National Oceanic and Atmospheric Administration</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency information collection activities; proposals, submissions, and approvals, </DOC>
                    <PGS>68025-68026</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30238</FRDOCBP>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30285</FRDOCBP>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30286</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Committee for Purchase</EAR>
            <HD>Committee for Purchase From People Who Are Blind or Severely Disabled</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Procurement list; additions and deletions, </DOC>
                    <PGS>68023-68025</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30288</FRDOCBP>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30289</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Commodity</EAR>
            <HD>Commodity Credit Corporation</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Loan and purchase programs:</SJ>
                <SUBSJ>Farm Security and Rural Investment Act; direct and counter-cyclical program</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Correction, </SUBSJDOC>
                    <PGS>67938-67939</PGS>
                    <FRDOCBP T="05DER1.sgm" D="2">03-30198</FRDOCBP>
                </SSJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Corporation</EAR>
            <HD>Corporation for National and Community Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency information collection activities; proposals, submissions, and approvals, </DOC>
                    <PGS>68036-68037</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30228</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Customs</EAR>
            <HD>Customs and Border Protection Bureau</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Electronic cargo information; advance presentation requirement, </DOC>
                      
                    <PGS>68139-68177</PGS>
                      
                    <FRDOCBP T="05DER2.sgm" D="39">03-29798</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Economic</EAR>
            <HD>Economic Analysis Bureau</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>International services surveys:</SJ>
                <SUBSJ>Foreign direct investments in U.S.—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>BE-15; foreign direct investment in U.S.; annual survey, </SUBSJDOC>
                    <PGS>67939-67941</PGS>
                    <FRDOCBP T="05DER1.sgm" D="3">03-29996</FRDOCBP>
                </SSJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Employment</EAR>
            <HD>Employment and Training Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Reports and guidance documents; availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Workforce security programs; training and employment letter interpreting Federal law, </SJDOC>
                    <PGS>68122-68123</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30249</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Employment</EAR>
            <HD>Employment Standards Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Minimum wages for Federal and federally-assisted construction; general wage determination decisions, </DOC>
                    <PGS>68123-68124</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-29998</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Energy</EAR>
            <HD>Energy Department</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Climate change:</SJ>
                <SJDENT>
                    <SJDOC>Voluntary Greenhouse Gas Reporting Program; general guidelines; comment request and public workshop, </SJDOC>
                    <PGS>68203-68231</PGS>
                    <FRDOCBP T="05DEP3.sgm" D="29">03-29983</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>EPA</EAR>
            <HD>Environmental Protection Agency</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Air pollutants, hazardous; national emission standards:</SJ>
                <SUBSJ>Chemical recovery combustion sources at kraft, soda, sulfite, and stand-alone semichemical pulp mills</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Correction, </SUBSJDOC>
                    <PGS>67953-67955</PGS>
                    <FRDOCBP T="05DER1.sgm" D="3">03-30265</FRDOCBP>
                </SSJDENT>
                <PRTPAGE P="iv"/>
                <SJ>Air quality implementation plans; approval and promulgation; various States:</SJ>
                <SJDENT>
                    <SJDOC>Delaware, </SJDOC>
                    <PGS>67948-67953</PGS>
                    <FRDOCBP T="05DER1.sgm" D="6">03-30041</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Air quality implementation plans; approval and promulgation; various States:</SJ>
                <SJDENT>
                    <SJDOC>Delaware, </SJDOC>
                    <PGS>67993-67995</PGS>
                    <FRDOCBP T="05DEP1.sgm" D="3">03-30042</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Environmental statements; availability, etc.:</SJ>
                <SUBSJ>Agency statements—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Comment availability, </SUBSJDOC>
                    <PGS>68037-68038</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30274</FRDOCBP>
                </SSJDENT>
                <SSJDENT>
                    <SUBSJDOC>Weekly receipts, </SUBSJDOC>
                    <PGS>68037</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30273</FRDOCBP>
                </SSJDENT>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>National Environmental Education Advisory Council, </SJDOC>
                    <PGS>68038</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30268</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Neurobehavioral toxicity screening data; benchmark dose analysis; peer-review workshop, </SJDOC>
                    <PGS>68038-68039</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30269</FRDOCBP>
                </SJDENT>
                <SJ>Pesticide registration, cancellation, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Atofina Chemicals, Inc., et al., </SJDOC>
                    <PGS>68039-68042</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="4">03-30165</FRDOCBP>
                </SJDENT>
                <SJ>Pesticide, food, and feed additive petitions:</SJ>
                <SJDENT>
                    <SJDOC>Pyridalyl, </SJDOC>
                    <PGS>68044-68049</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="6">03-30164</FRDOCBP>
                </SJDENT>
                <SJ>Pesticide programs:</SJ>
                <SUBSJ>Risk assessments—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Creosote, </SUBSJDOC>
                    <PGS>68042-68044</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="3">03-30270</FRDOCBP>
                </SSJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Export</EAR>
            <HD>Export-Import Bank</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency information collection activities; proposals, submissions, and approvals, </DOC>
                    <PGS>68049-68082</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="34">03-30199</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>FAA</EAR>
            <HD>Federal Aviation Administration</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Airworthiness directives:</SJ>
                <SJDENT>
                    <SJDOC>Airbus, </SJDOC>
                    <PGS>67984-67986</PGS>
                    <FRDOCBP T="05DEP1.sgm" D="3">03-30223</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>BAE Systems (Operations) Ltd., </SJDOC>
                    <PGS>67986-67988</PGS>
                    <FRDOCBP T="05DEP1.sgm" D="3">03-30222</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Boeing, </SJDOC>
                    <PGS>67973-67977</PGS>
                    <FRDOCBP T="05DEP1.sgm" D="3">03-30219</FRDOCBP>
                    <FRDOCBP T="05DEP1.sgm" D="3">03-30220</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Bombardier, </SJDOC>
                    <PGS>67971-67973</PGS>
                    <FRDOCBP T="05DEP1.sgm" D="3">03-30221</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Dornier, </SJDOC>
                    <PGS>67980-67981</PGS>
                    <FRDOCBP T="05DEP1.sgm" D="2">03-30225</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Fokker, </SJDOC>
                    <PGS>67981-67984</PGS>
                    <FRDOCBP T="05DEP1.sgm" D="4">03-30224</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>McDonnell Douglas, </SJDOC>
                    <PGS>67978-67979</PGS>
                    <FRDOCBP T="05DEP1.sgm" D="2">03-30218</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Pilatus Aircraft Ltd., </SJDOC>
                    <PGS>67988-67991</PGS>
                    <FRDOCBP T="05DEP1.sgm" D="4">03-30256</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>FBI</EAR>
            <HD>Federal Bureau of Investigation</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Communications Assistance for Law Enforcement Act:</SJ>
                <SJDENT>
                    <SJDOC>Communications interceptions; final notice of capacity; remand response, </SJDOC>
                    <PGS>68112-68121</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="10">03-30258</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>FCC</EAR>
            <HD>Federal Communications Commission</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Radio stations; table of assignments:</SJ>
                <SJDENT>
                    <SJDOC>Florida, </SJDOC>
                    <PGS>67964</PGS>
                    <FRDOCBP T="05DER1.sgm" D="1">03-30195</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Texas, </SJDOC>
                    <PGS>67964</PGS>
                    <FRDOCBP T="05DER1.sgm" D="1">03-30194</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>FDIC</EAR>
            <HD>Federal Deposit Insurance Corporation</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Meetings; Sunshine Act, </DOC>
                    <PGS>68082</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">E3-00460</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Emergency</EAR>
            <HD>Federal Emergency Management Agency</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency information collection activities; proposals, submissions, and approvals, </DOC>
                    <PGS>68093-68094</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30290</FRDOCBP>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30291</FRDOCBP>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30292</FRDOCBP>
                </DOCENT>
                <SJ>Disaster and emergency areas:</SJ>
                <SJDENT>
                    <SJDOC>Puerto Rico, </SJDOC>
                    <PGS>68094-68095</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30297</FRDOCBP>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30298</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Washington, </SJDOC>
                    <PGS>68095</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30293</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>West Virginia, </SJDOC>
                    <PGS>68095-68096</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30294</FRDOCBP>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30295</FRDOCBP>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30296</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Reserve</EAR>
            <HD>Federal Reserve System</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency information collection activities; proposals, submissions, and approvals, </DOC>
                    <PGS>68082-68085</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30212</FRDOCBP>
                    <FRDOCBP T="05DEN1.sgm" D="3">03-30213</FRDOCBP>
                </DOCENT>
                <SJ>Banks and bank holding companies:</SJ>
                <SJDENT>
                    <SJDOC>Formations, acquisitions, and mergers, </SJDOC>
                    <PGS>68085</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30215</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Permissible nonbanking activities, </SJDOC>
                    <PGS>68085-68086</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30214</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Federal Retirement</EAR>
            <HD>Federal Retirement Thrift Investment Board</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Meetings; Sunshine Act, </DOC>
                    <PGS>68093</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30406</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Fish</EAR>
            <HD>Fish and Wildlife Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Endangered and threatened species:</SJ>
                <SUBSJ>Recovery plans—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Chittenango ovate amber snail, </SUBSJDOC>
                    <PGS>68102-68103</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30254</FRDOCBP>
                </SSJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Forest</EAR>
            <HD>Forest Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Environmental statements; notice of intent:</SJ>
                <SJDENT>
                    <SJDOC>Boise National Forest, ID, </SJDOC>
                    <PGS>68021-68023</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="3">03-30066</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Geological</EAR>
            <HD>Geological Survey</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency information collection activities; proposals, submissions, and approvals, </DOC>
                    <PGS>68103</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30196</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Health</EAR>
            <HD>Health and Human Services Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Centers for Disease Control and Prevention</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Centers for Medicare &amp; Medicaid Services</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> National Institutes of Health</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Substance Abuse and Mental Health Services Administration</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Homeland</EAR>
            <HD>Homeland Security Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Coast Guard</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Customs and Border Protection Bureau</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Federal Emergency Management Agency</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Transportation Security Administration</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Housing</EAR>
            <HD>Housing and Urban Development Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Grants and cooperative agreements; availability, etc.:</SJ>
                <SUBSJ>Facilities to assist homeless—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Excess and surplus Federal property, </SUBSJDOC>
                    <PGS>68097-68102</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="6">03-29872</FRDOCBP>
                </SSJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Indian</EAR>
            <HD>Indian Affairs Bureau</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Transportation Equity Act for 21st Century, implementation:</SJ>
                <SJDENT>
                    <SJDOC>Indian Reservation Roads Funds; 2004 FY funds distribution, </SJDOC>
                    <PGS>67941-67943</PGS>
                    <FRDOCBP T="05DER1.sgm" D="3">03-30208</FRDOCBP>
                </SJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Indian entities recognized as eligible to receive services from BIA; list, </DOC>
                    <PGS>68179-68184</PGS>
                    <FRDOCBP T="05DEN2.sgm" D="6">03-30244</FRDOCBP>
                </DOCENT>
                <SJ>Irrigation projects; operation and maintenance charges:</SJ>
                <SJDENT>
                    <SJDOC>Rate adjustments, </SJDOC>
                    <PGS>68103-68107</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="5">03-30253</FRDOCBP>
                </SJDENT>
                <SJ>Liquor and tobacco sale or distribution ordinance:</SJ>
                <SJDENT>
                    <SJDOC>Lytton Rancheria of California, </SJDOC>
                    <PGS>68107-68108</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30243</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Industry</EAR>
            <HD>Industry and Security Bureau</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency information collection activities; proposals, submissions, and approvals, </DOC>
                    <PGS>68027-68028</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30239</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Interior</EAR>
            <HD>Interior Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Fish and Wildlife Service</P>
            </SEE>
            <SEE>
                <PRTPAGE P="v"/>
                <HD SOURCE="HED">See</HD>
                <P> Geological Survey</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Indian Affairs Bureau</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Land Management Bureau</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> National Park Service</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>International</EAR>
            <HD>International Trade Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Antidumping:</SJ>
                <SUBSJ>Freshwater crawfish tail meat from—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>China, </SUBSJDOC>
                    <PGS>68028-68030</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="3">03-30263</FRDOCBP>
                </SSJDENT>
                <SUBSJ>Persulfates from—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>China, </SUBSJDOC>
                    <PGS>68030-68032</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30259</FRDOCBP>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30260</FRDOCBP>
                </SSJDENT>
                <SUBSJ>Processed hazelnuts from—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Turkey, </SUBSJDOC>
                    <PGS>68032-68034</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="3">03-30261</FRDOCBP>
                </SSJDENT>
                <SJ>Countervailing duties:</SJ>
                <SUBSJ>Pasta from—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Italy, </SUBSJDOC>
                    <PGS>68034-68035</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30262</FRDOCBP>
                </SSJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>International</EAR>
            <HD>International Trade Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Meetings; Sunshine Act, </DOC>
                    <PGS>68112</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30350</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Justice</EAR>
            <HD>Justice Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Federal Bureau of Investigation</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Labor</EAR>
            <HD>Labor Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Employment and Training Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Employment Standards Administration</P>
            </SEE>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency information collection activities; proposals, submissions, and approvals, </DOC>
                    <PGS>68121</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30248</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Land</EAR>
            <HD>Land Management Bureau</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Environmental statements; availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Glamis Marigold Mining Co./Marigold Mine Millennium Expansion Project, NV, </SJDOC>
                    <PGS>68108-68109</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30193</FRDOCBP>
                </SJDENT>
                <SJ>Meetings:</SJ>
                <SUBSJ>Resource Advisory Councils—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Western Montana, </SUBSJDOC>
                    <PGS>68109</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30255</FRDOCBP>
                </SSJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>NASA</EAR>
            <HD>National Aeronautics and Space Administration</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Acquisition regulations:</SJ>
                <SJDENT>
                    <SJDOC>Contractor access to confidential information, </SJDOC>
                    <PGS>67995-67998</PGS>
                    <FRDOCBP T="05DEP1.sgm" D="4">03-29930</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Crime</EAR>
            <HD>National Crime Prevention and Privacy Compact Council</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <DOCENT>
                    <DOC>Fingerprint submission requirements, </DOC>
                    <PGS>67991-67993</PGS>
                    <FRDOCBP T="05DEP1.sgm" D="3">03-29567</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Highway</EAR>
            <HD>National Highway Traffic Safety Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Motor vehicle safety standards:</SJ>
                <SUBSJ>Nonconforming vehicles—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Importation eligibility; determinations, </SUBSJDOC>
                    <PGS>68130</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30279</FRDOCBP>
                </SSJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>NIH</EAR>
            <HD>National Institutes of Health</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Grants and cooperative agreements; availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Novel mechanical and biological treatments in interventional cardiovascular medicine using x-ray fluoroscopy and/or real time magnetic resonance imaging, </SJDOC>
                    <PGS>68088</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30206</FRDOCBP>
                </SJDENT>
                <DOCENT>
                    <DOC>Inventions, Government-owned; availability for licensing, </DOC>
                    <PGS>68088-68090</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="3">03-30207</FRDOCBP>
                </DOCENT>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>National Institute of Child Health and Human Development, </SJDOC>
                    <PGS>68090-68091</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30205</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>National Institute of Diabetes and Digestive and Kidney Diseases, </SJDOC>
                    <PGS>68090</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30202</FRDOCBP>
                    <PGS>68090</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30203</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>National Institute of Mental Health, </SJDOC>
                    <PGS>68090</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30204</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Scientific Review Center, </SJDOC>
                    <PGS>68091</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30201</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>NOAA</EAR>
            <HD>National Oceanic and Atmospheric Administration</HD>
            <CAT>
                <HD>RULES</HD>
                <SJ>Fishery conservation and management:</SJ>
                <SUBSJ>Alaska; fisheries of Exclusive Economic Zone—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Gulf of Alaska groundfish, </SUBSJDOC>
                    <PGS>67964-67970</PGS>
                    <FRDOCBP T="05DER1.sgm" D="7">03-30282</FRDOCBP>
                </SSJDENT>
            </CAT>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Fishery conservation and management:</SJ>
                <SUBSJ>Alaska; fisheries of Exclusive Economic Zone—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Gulf of Alaska groundfish, </SUBSJDOC>
                    <PGS>68002-68014</PGS>
                    <FRDOCBP T="05DEP1.sgm" D="13">03-30283</FRDOCBP>
                </SSJDENT>
                <SUBSJ>West Coast States and Western Pacific fisheries—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Pacific Coast groundfish, </SUBSJDOC>
                    <PGS>67998-68002</PGS>
                    <FRDOCBP T="05DEP1.sgm" D="5">03-30284</FRDOCBP>
                </SSJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Reports and guidance documents; availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Laboratory consolidation plan; comment request, </SJDOC>
                    <PGS>68035-68036</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-29888</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Park</EAR>
            <HD>National Park Service</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency information collection activities; proposals, submissions, and approvals, </DOC>
                    <PGS>68109-68112</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-29987</FRDOCBP>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-29988</FRDOCBP>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-29989</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>National Science</EAR>
            <HD>National Science Foundation</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Antarctic Conservation Act of 1978; permit applications, etc., </DOC>
                    <PGS>68124</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30197</FRDOCBP>
                </DOCENT>
                <DOCENT>
                    <DOC>Meetings; Sunshine Act, </DOC>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30328</FRDOCBP>
                    <PGS>68124-68125</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30329</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Nuclear</EAR>
            <HD>Nuclear Regulatory Commission</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Environmental statements; notice of intent:</SJ>
                <SJDENT>
                    <SJDOC>Southern Nuclear Operating Co., </SJDOC>
                    <PGS>68125-68126</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30247</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>SEC</EAR>
            <HD>Securities and Exchange Commission</HD>
            <CAT>
                <HD>PROPOSED RULES</HD>
                <SJ>Practice and procedure:</SJ>
                <SUBSJ>Sarbanes-Oxley Act of 2002; implementation—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Rules of practice and related provisions; amendments, </SUBSJDOC>
                    <PGS>68185-68201</PGS>
                    <FRDOCBP T="05DEP2.sgm" D="17">03-29932</FRDOCBP>
                </SSJDENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Meetings; Sunshine Act, </DOC>
                    <PGS>68126</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30325</FRDOCBP>
                </DOCENT>
                <SJ>Self-regulatory organizations; proposed rule changes:</SJ>
                <SJDENT>
                    <SJDOC>Boston Stock Exchange, Inc., </SJDOC>
                    <PGS>68127-68128</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30252</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>Chicago Board Options Exchange, Inc., </SJDOC>
                    <PGS>68128-68129</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30250</FRDOCBP>
                </SJDENT>
                <SJDENT>
                    <SJDOC>National Association of Securities Dealers, Inc., </SJDOC>
                    <PGS>68129</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30251</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>SBA</EAR>
            <HD>Small Business Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SUBSJ>Regulatory Fairness Boards—</SUBSJ>
                <SSJDENT>
                    <SUBSJDOC>Region IX; Public Roundtable, </SUBSJDOC>
                    <PGS>68129</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30209</FRDOCBP>
                </SSJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>State</EAR>
            <HD>State Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency information collection activities; proposals, submissions, and approvals, </DOC>
                    <PGS>68129-68130</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30275</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Substance</EAR>
            <HD>Substance Abuse and Mental Health Services Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Federal agency urine drug testing; certified laboratories meeting minimum standards, list, </DOC>
                    <PGS>68091-68092</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30217</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Surface</EAR>
            <PRTPAGE P="vi"/>
            <HD>Surface Transportation Board</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Railroad operation, acquisition, construction, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Duluth, Missabe &amp; Iron Range Railway Co. et al., </SJDOC>
                    <PGS>68130-68137</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="8">03-30090</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Transportation</EAR>
            <HD>Transportation Department</HD>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Federal Aviation Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> National Highway Traffic Safety Administration</P>
            </SEE>
            <SEE>
                <HD SOURCE="HED">See</HD>
                <P> Surface Transportation Board</P>
            </SEE>
        </AGCY>
        <AGCY>
            <EAR>Transportation</EAR>
            <HD>Transportation Security Administration</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Reports and guidance documents; availability, etc.:</SJ>
                <SJDENT>
                    <SJDOC>Maritime security; maritime vulnerability self-assessment tool, </SJDOC>
                    <PGS>68096-68097</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30281</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Treasury</EAR>
            <HD>Treasury Department</HD>
            <CAT>
                <HD>RULES</HD>
                <DOCENT>
                    <DOC>Privacy Act; implementation, </DOC>
                    <PGS>67943-67944</PGS>
                    <FRDOCBP T="05DER1.sgm" D="2">03-30241</FRDOCBP>
                </DOCENT>
            </CAT>
            <CAT>
                <HD>NOTICES</HD>
                <DOCENT>
                    <DOC>Agency information collection activities; proposals, submissions, and approvals, </DOC>
                    <PGS>68137-68138</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="2">03-30242</FRDOCBP>
                </DOCENT>
            </CAT>
        </AGCY>
        <AGCY>
            <EAR>Veterans</EAR>
            <HD>Veterans Affairs Department</HD>
            <CAT>
                <HD>NOTICES</HD>
                <SJ>Meetings:</SJ>
                <SJDENT>
                    <SJDOC>Capital Asset Realignment for Enhanced Services Commission, </SJDOC>
                    <PGS>68138</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30227</FRDOCBP>
                </SJDENT>
                <SJ>Real property; enhanced-use leases:</SJ>
                <SJDENT>
                    <SJDOC>Dayton, OH: Veterans Affairs Department Medical Center, </SJDOC>
                    <PGS>68138</PGS>
                    <FRDOCBP T="05DEN1.sgm" D="1">03-30226</FRDOCBP>
                </SJDENT>
            </CAT>
        </AGCY>
        <PTS>
            <HD SOURCE="HED">Separate Parts In This Issue</HD>
            <HD>Part II</HD>
            <DOCENT>
                <DOC>Homeland Security Department, Customs and Border Protection Bureau, </DOC>
                  
                <PGS>68139-68177</PGS>
                  
                <FRDOCBP T="05DER2.sgm" D="39">03-29798</FRDOCBP>
            </DOCENT>
            <HD>Part III</HD>
            <DOCENT>
                <DOC>Interior Department, Indian Affairs Bureau, </DOC>
                <PGS>68179-68184</PGS>
                <FRDOCBP T="05DEN2.sgm" D="6">03-30244</FRDOCBP>
            </DOCENT>
            <HD>Part IV</HD>
            <DOCENT>
                <DOC>Securities and Exchange Commission, </DOC>
                <PGS>68185-68201</PGS>
                <FRDOCBP T="05DEP2.sgm" D="17">03-29932</FRDOCBP>
            </DOCENT>
            <HD>Part V</HD>
            <DOCENT>
                <DOC>Energy Department, </DOC>
                <PGS>68203-68231</PGS>
                <FRDOCBP T="05DEP3.sgm" D="29">03-29983</FRDOCBP>
            </DOCENT>
        </PTS>
        <AIDS>
            <HD SOURCE="HED">Reader Aids</HD>
            <P>Consult the Reader Aids section at the end of this issue for phone numbers, online resources, finding aids, reminders, and notice of recently enacted public laws.</P>
            <P>To subscribe to the Federal Register Table of Contents LISTSERV electronic mailing list, go to http://listserv.access.gpo.gov and select Online mailing list archives, FEDREGTOC-L, Join or leave the list (or change settings); then follow the instructions.</P>
        </AIDS>
    </CNTNTS>
    <VOL>68</VOL>
    <NO>234</NO>
    <DATE>Friday, December 5, 2003</DATE>
    <UNITNAME>Rules and Regulations</UNITNAME>
    <RULES>
        <RULE>
            <PREAMB>
                <PRTPAGE P="67937"/>
                <AGENCY TYPE="F">DEPARTMENT OF AGRICULTURE </AGENCY>
                <SUBAGY>Animal and Plant Health Inspection Service </SUBAGY>
                <CFR>7 CFR Part 354 </CFR>
                <DEPDOC>[Docket No. 03-098-1] </DEPDOC>
                <SUBJECT>Commuted Traveltime Periods: Overtime Services Relating to Imports and Exports </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Animal and Plant Health Inspection Service, USDA. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>We are amending the regulations concerning overtime services provided by employees of Plant Protection and Quarantine by adding commuted traveltime allowances for travel between Hilo, HI, and five new locations in Hawaii. Commuted traveltime allowances are the periods of time required for Plant Protection and Quarantine employees to travel from their dispatch points and return there from the places where they perform Sunday, holiday, or other overtime duty. The Government charges a fee for certain overtime services provided by Plant Protection and Quarantine employees and, under certain circumstances, the fee may include the cost of commuted traveltime. This action is necessary to inform the public of commuted traveltime for these locations. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>December 5, 2003. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mr. Michael Caporaletti, Program Analyst, PPQ, APHIS, 4700 River Road Unit 120, Riverdale, MD 20737-1238; (301) 734-5781. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background </HD>
                <P>The regulations in 7 CFR, chapter III, and 9 CFR, chapter I, subchapter D, require inspection, laboratory testing, certification, or quarantine of certain plants, plant products, animals, animal products, or other commodities intended for importation into, or exportation from, the United States. </P>
                <P>When these services must be provided by an employee of Plant Protection and Quarantine (PPQ) on a Sunday or holiday, or at any other time outside the PPQ employee's regular duty hours, the Government charges a fee for the services in accordance with 7 CFR part 354. Under circumstances described in § 354.1(a)(2), this fee may include the cost of commuted traveltime. Section 354.2 contains administrative instructions prescribing commuted traveltime allowances, which reflect, as nearly as practicable, the periods of time required for PPQ employees to travel from their dispatch points and return there from the places where they perform Sunday, holiday, or other overtime duty. </P>
                <P>We are amending § 354.2 of the regulations by adding commuted traveltime allowances for travel between Hilo, HI, and five new locations in Hawaii. The amendments are set forth in the rule portion of this document. This action is necessary to inform the public of the commuted traveltime between the dispatch and service locations. </P>
                <HD SOURCE="HD1">Effective Date </HD>
                <P>The commuted traveltime allowances appropriate for employees performing services at ports of entry, and the features of the reimbursement plan for recovering the cost of furnishing port of entry services, depend upon facts within the knowledge of the Department of Agriculture. It does not appear that public participation in this rulemaking proceeding would make additional relevant information available to the Department. </P>
                <P>
                    Accordingly, pursuant to the administrative procedure provisions in 5 U.S.C. 553, we find upon good cause that prior notice and other public procedure with respect to this rule are impracticable and unnecessary; we also find good cause for making this rule effective less than 30 days after publication of this document in the 
                    <E T="04">Federal Register</E>
                    . 
                </P>
                <HD SOURCE="HD1">Executive Order 12866 and Regulatory Flexibility Act </HD>
                <P>This final rule has been reviewed under Executive Order 12866. For this action, the Office of Management and Budget has waived its review under Executive Order 12866. </P>
                <P>The number of requests for overtime services of a PPQ employee at the locations affected by this rule represents an insignificant portion of the total number of requests for these services in the United States. </P>
                <P>Under these circumstances, the Administrator of the Animal and Plant Health Inspection Service has determined that this action will not have a significant economic impact on a substantial number of small entities. </P>
                <HD SOURCE="HD1">Executive Order 12988 </HD>
                <P>This final rule has been reviewed under Executive Order 12988, Civil Justice Reform. This rule is intended to have preemptive effect with respect to any State or local laws, regulations, or policies that conflict with its provisions or that would otherwise impede its full implementation. This rule is not intended to have retroactive effect. There are no administrative procedures that must be exhausted prior to any judicial challenge to the provisions of this rule or the application of its provisions. </P>
                <HD SOURCE="HD1">Paperwork Reduction Act </HD>
                <P>
                    This rule contains no new information collection or recordkeeping requirements under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ). 
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 7 CFR Part 354 </HD>
                    <P>Exports, Government employees, Imports, Plant diseases and pests, Quarantine, Reporting and recordkeeping requirements, Travel and transportation expenses.</P>
                </LSTSUB>
                <REGTEXT TITLE="7" PART="354">
                    <AMDPAR>Accordingly, we are amending 7 CFR part 354 as follows:</AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 354—OVERTIME SERVICES RELATING TO IMPORTS AND EXPORTS; AND USER FEES </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 354 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>7 U.S.C. 8301-8317; 21 U.S.C. 136 and 136a; 49 U.S.C. 80503; 7 CFR 2.22, 2.80, and 371.3. </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="354">
                    <AMDPAR>2. Section 354.2 is amended by adding in the table, in alphabetical order, under Hawaii, the following entries to read as follows: </AMDPAR>
                    <SECTION>
                        <PRTPAGE P="67938"/>
                        <SECTNO>§ 354.2 </SECTNO>
                        <SUBJECT>Administrative instructions prescribing commuted traveltime. </SUBJECT>
                        <STARS/>
                        <GPOTABLE COLS="4" OPTS="L1,i1" CDEF="xls100,xl100,10C,10C">
                            <TTITLE>Commuted Traveltime Allowances </TTITLE>
                            <TDESC>[In hours] </TDESC>
                            <BOXHD>
                                <CHED H="1">Location covered </CHED>
                                <CHED H="1">Served from— </CHED>
                                <CHED H="1">Metropolitan area </CHED>
                                <CHED H="2">Within </CHED>
                                <CHED H="2">Outside </CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         * </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="11">Hawaii: </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         * </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Hakalau </ENT>
                                <ENT>Hilo </ENT>
                                <ENT> </ENT>
                                <ENT>2 </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         * </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Kurtistown </ENT>
                                <ENT>Hilo </ENT>
                                <ENT> </ENT>
                                <ENT>2 </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         * </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Mt. View </ENT>
                                <ENT>Hilo </ENT>
                                <ENT> </ENT>
                                <ENT>2 </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         * </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Pepeekeo </ENT>
                                <ENT>Hilo </ENT>
                                <ENT> </ENT>
                                <ENT>2 </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         * </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="03">Umauma </ENT>
                                <ENT>Hilo </ENT>
                                <ENT> </ENT>
                                <ENT>2 </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="28">*         *         *         *         *         *         * </ENT>
                            </ROW>
                        </GPOTABLE>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Done in Washington, DC, this 2nd day of December 2003. </DATED>
                    <NAME>Kevin Shea, </NAME>
                    <TITLE>Acting Administrator, Animal and Plant Health Inspection Service. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30230 Filed 12-4-03; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3410-34-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE </AGENCY>
                <SUBAGY>Commodity Credit Corporation </SUBAGY>
                <CFR>7 CFR parts 1412 and 1421 </CFR>
                <RIN>RIN 0560-AG71 and 0560-AG72 </RIN>
                <SUBJECT>Direct and Counter Cyclical Program; Marketing Assistance Loans and Loan Deficiency Payments for Peanuts, Pulse Crops, Wheat, Feed Grains, Soybeans and Other Oilseeds; Correction </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCIES:</HD>
                    <P>Commodity Credit Corporation, USDA. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule (correcting amendments). </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document also corrects the regulations published by the Commodity Credit Corporation (CCC) entitled “Direct and Counter Cyclical Program” and “Marketing Assistance Loans and Loan Deficiency Payments.” Corrections are necessary for provisions that conflict with statute or other program requirements and are intended to ensure that Agency regulations are properly written and implemented. These changes will apply retroactively to actions taken under the subject regulations since their effective date. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The revisions to part 1412 are effective as of October 16, 2002; the revisions to part 1421 are effective as of October 8, 2002. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Sharon Biastock at 720-6336, or Kimberly Graham, at 202-720-9154. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Discussion of Corrections </HD>
                <P>
                    (1) 
                    <E T="03">Interstate transfer of peanut acreage.</E>
                     This document also corrects 7 CFR part 1412, published in the 
                    <E T="04">Federal Register</E>
                     on October 21, 2002, 67 FR 64751, by authority of the Farm Security and Rural Investment Act of 2002 (“2002 Act”). Part 1412 is entitled “Direct and Counter-Cyclical Program and Peanut Quota Buyout Program,” and provides for direct and counter-cyclical payments for the crop years 2002 through 2007 for a number of crops to provide income support to producers of eligible commodities. The error is in the introductory language in section 1412.703(b) of part 1412, which states, “Notwithstanding paragraph (a) of this section, the average acreage determined under § 1412.701 for a farm may be assigned to a farm in a contiguous county only if either of the following apply:” This correction substitutes the word “state” for “county” in that sentence, as the provisions are directed to special allowance for interstate transfers for peanuts as reflected elsewhere and in the authorizing statute. 
                </P>
                <P>
                    (2) 
                    <E T="03">Penalties for erroneous certification.</E>
                     This document corrects the regulations for CCC Marketing Assistance Loans and Loan Deficiency Payments for Peanuts, Pulse Crops, Wheat, Feed Grains, Soybeans and Other Oilseeds at 7 CFR Part 1421. The current provisions of Part 1421 were published in the 
                    <E T="04">Federal Register</E>
                     on Friday, October 11, 2002 (67 FR 63511). Marketing assistance loans and loan deficiency payments are authorized by title I of the 2002 Act. 
                </P>
                <P>This document corrects sections 1421.109 of 7 CFR part 1421 relating to a producer's violation of a loan agreement, and the resulting administrative remedies. Specifically, § 1421.109(e) is corrected so that the amount due for a violation of this provision is based only on the quantity of the commodity “removed or disposed of” and not the “quantity incorrectly certified or the loan quantity removed or disposed.” As to the reference to “quantity incorrectly certified” there can never be less than a full loan repayment as is clear from the circumstances and other provisions in the regulations. Accordingly, this section is corrected by removing that reference. Also, a clarifying comma is added after the word “interest” in § 1421.109(e)(1)(i). </P>
                <P>Section 1421.109 is also corrected in paragraph (g) so that, “The county committee may waive the liquidated damages if it determines that the violation was inadvertent, accidental, or unintentional.” instead of “* * * and unintentional.” The word “or” was used here instead of “and” to comport fully with the original and continuing intent of this provision. </P>
                <P>
                    These changes are to clarify and correct regulations, and delaying their publication to request public comment is contrary to the public interest. Further, section 1601 of the 2002 Act exempts these changes from notice and comment rulemaking. So that they may apply equally with existing regulations, 
                    <PRTPAGE P="67939"/>
                    these changes are effective as of the original filing of the rules implementing the 2002 Act. 
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects </HD>
                    <CFR>7 CFR Part 1412 </CFR>
                    <P>Direct and counter-cyclical payments, Grains, Peanuts, Oilseeds, Reporting and record keeping requirements.</P>
                    <CFR>7 CFR Part 1421 </CFR>
                    <P>Agricultural commodities, Feed grains, Grains, Loan programs—agriculture, Oilseeds, Price support programs. </P>
                </LSTSUB>
                <REGTEXT TITLE="7" PART="1412">
                    <AMDPAR>Accordingly, 7 CFR chapter XIV is corrected as follows:</AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 1412—DIRECT AND COUNTER-CYCLICAL PROGRAM AND PEANUT QUOTA BUYOUT PROGRAM </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 1412 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>7 U.S.C. 7911-7918, 7951-7956; 15 U.S.C. 714b and 714c.   </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1412">
                    <SUBPART>
                        <HD SOURCE="HED">Subpart G—Establishment and Assignment of Peanut Base Acres and Yields for a Farm </HD>
                    </SUBPART>
                    <AMDPAR>2. Revise § 1412.703(b) to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1412.703 </SECTNO>
                        <SUBJECT>Assignment of average peanut yields and average peanut acreages to farms. </SUBJECT>
                        <STARS/>
                        <P>(b) Notwithstanding paragraph (a) of this section, the average acreage determined under § 1412.701 for a farm may be assigned to a farm in a contiguous state only if either of the following apply: </P>
                        <P>(1) The historic peanut producer making the assignment produced peanuts in that State during at least one of the 1998 through 2001 crop years; or </P>
                        <P>(2) As of March 31, 2003, the historic peanut producer is a producer on a farm in that State. </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1421">
                    <PART>
                        <HD SOURCE="HED">PART 1421—GRAINS AND SIMILARLY HANDLED COMMODITIES—MARKETING ASSISTANCE LOANS AND LOAN DEFICIENCY PAYMENTS FOR THE 2002 THROUGH 2007 CROP YEARS </HD>
                    </PART>
                    <AMDPAR>3. The authority citation for part 1421 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>
                            7 U.S.C. 7231-7237 and 7931 
                            <E T="03">et seq.</E>
                            ; 15 U.S.C. 714b, 714c. 
                        </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="7" PART="1421">
                    <SUBPART>
                        <HD SOURCE="HED">Subpart B—Marketing Assistance Loans </HD>
                    </SUBPART>
                    <AMDPAR>4. In § 1421.109, paragraphs (e)(1) and (g) are corrected to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 1421.109 </SECTNO>
                        <SUBJECT>Personal liability of the producer. </SUBJECT>
                        <STARS/>
                        <P>(e) For violations and the liquidated damages under paragraph (d)(1) of this section, the county committee shall: </P>
                        <P>(1) Require repayment of the marketing assistance loan quantity removed or disposed of at the lesser of: </P>
                        <P>(i) The applicable loan principal, and charges, plus interest, or: </P>
                        <P>(ii) The announced alternative repayment rate in effect on date the violation occurred, plus 15 percent of the loan rate, or as otherwise determined by the Deputy Administrator, and </P>
                        <STARS/>
                        <P>(g) The county committee may waive imposing liquidated damages if it determines that the violation was inadvertent, accidental, or unintentional. </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Signed in Washington, DC, on November 26, 2003. </DATED>
                    <NAME>James R. Little, </NAME>
                    <TITLE>Executive Vice President, Commodity Credit Corporation. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30198 Filed 12-4-03; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3410-05-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF COMMERCE </AGENCY>
                <SUBAGY>Bureau of Economic Analysis </SUBAGY>
                <CFR>15 CFR Part 806 </CFR>
                <DEPDOC>[Docket No. 030818205-3281-02] </DEPDOC>
                <RIN>RIN 0691-AA48 </RIN>
                <SUBJECT>Direct Investment Surveys: BE-15, Annual Survey of Foreign Direct Investment in the United States </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Economic Analysis, Commerce. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This final rule amends regulations that set forth reporting requirements for the BE-15, Annual Survey of Foreign Direct Investment in the United States. The annual survey is comprised of four forms—the BE-15(LF) long form, the BE-15(SF) short form, the BE-15(EZ) form, which is a new form, and the BE-15 Supplement C-Claim for Exemption From Filing a BE-15(LF), BE-15(SF), or BE-15(EZ). The annual survey is a sample survey that collects data on the financial structure and operations of nonbank U.S. affiliates of foreign companies needed to update similar data for the universe of U.S. affiliates collected once every 5 years in the BE-12 benchmark survey. The data are used to derive annual estimates of the operations of U.S. affiliates of foreign companies, including their balance sheets; income statements; property, plant, and equipment; external financing; employment and employee compensation; merchandise trade; sales of goods and services; taxes; and research and development activity. The data are needed to measure the size and economic significance of foreign direct investment in the United States, to measure changes in such investment, and to assess its impact on the U.S. economy. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This final rule will be effective January 5, 2004. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Obie G. Whichard, Chief, International Investment Division (BE-50), Bureau of Economic Analysis, U.S. Department of Commerce, Washington, DC 20230; phone (202) 606-9890. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    On August 29, 2003, the Bureau of Economic Analysis (BEA) published in the 
                    <E T="04">Federal Register</E>
                     (68 FR 51942) a notice of proposed rulemaking setting forth revised reporting requirements for the BE-15, Annual Survey of Foreign Direct Investment in the United States. No comments on the proposed rule were received. Thus, the provisions in the proposed rule are adopted without change. 
                </P>
                <HD SOURCE="HD1">Description of Revisions </HD>
                <P>The BE-15, Annual Survey of Foreign Direct Investment in the United States, is mandatory and is conducted annually by the Bureau of Economic Analysis (BEA), U.S. Department of Commerce, under the International Investment and Trade in Services Survey Act (22 U.S.C. 3101-3108)—hereinafter, “the Act.” BEA will send the survey to potential respondents in March of each year; responses will be due by May 31. </P>
                <P>
                    BEA will introduce a sampling procedure to help reduce respondent burden for some U.S. businesses. The procedure utilizes the new BE-15(EZ) form; this form provides a few basic indicators for non-sample firms that can be used as a basis for estimating data that they otherwise would have to report on the lengthier BE-15(LF) and BE-15(SF) forms. To bring the annual survey into conformity with the Benchmark Survey of Foreign Direct Investment in the United States-2002, the following changes are being made to the Code of Federal Regulations: (1) Direct that only nonbank majority-owned U.S. affiliates of foreign companies report on the BE-15(LF) long form (minority-owned affiliates will report on the BE-15(SF) short form, or 
                    <PRTPAGE P="67940"/>
                    the BE-15(EZ) form, regardless of size); (2) raise the exemption level on the BE-15(LF) long form from $100 million to $125 million (reporting on a given form is required if the affiliate's assets, sales, or net income (or loss) exceed the exemption level); and (3) exempt nonbank subsidiaries or units of U.S. bank or bank holding company affiliates from reporting. 
                </P>
                <P>In addition, the following changes are being made to the forms: (1) Add questions to the BE-15 (LF) long form to collect detail on premiums earned and claims paid for U.S. affiliates operating in the insurance industry, and to collect detail on finished goods purchased for resale for U.S. affiliates operating in the wholesale and retail trade industries; (2) in conjunction with increasing the exemption level for reporting on the BE-15(LF) long form, add four items to the short form that will serve to improve estimates of gross product for majority-owned U.S. affiliates—certain realized and unrealized gains and losses, U.S. income taxes, interest received, and interest paid; (3) in conjunction with requiring all minority-owned U.S. affiliates to file on the short form, revise the State Schedule to collect additional detail, by State, for minority-owned U.S. affiliates with activities in more than five States; and (4) to reduce overall respondent burden, drop several questions that BEA feels are no longer of significant analytical interest to the data users. </P>
                <HD SOURCE="HD1">Survey Background </HD>
                <P>The Bureau of Economic Analysis (BEA), U.S. Department of Commerce, will conduct the survey under the International Investment and Trade in Services Survey Act (22 U.S.C. 3101-3108), hereinafter, “the Act.” Section 4(a) of the Act provides that with respect to foreign direct investment in the United States, the President shall, to the extent he deems necessary and feasible, conduct a regular data collection program to secure current information on international capital flows and other information related to international investment and trade in services, including (but not limited to) such information as may be necessary for computing and analyzing the United States balance of payments, the employment and taxes of United States parents and affiliates, and the international investment and trade in services position of the United States. </P>
                <P>In Section 3 of Executive Order 11961, the President delegated authority granted under the Act as concerns direct investment to the Secretary of Commerce, who has redelegated it to BEA. </P>
                <P>The annual survey is a sample survey that collects data on the financial structure and operations of nonbank U.S. affiliates of foreign companies needed to update similar data for the universe of U.S. affiliates collected once every 5 years in the BE-12 benchmark survey. The data are used to derive annual estimates of the operations of U.S. affiliates of foreign companies, including their balance sheets; income statements; property, plant, and equipment; external financing; employment and employee compensation; merchandise trade; sales of goods and services; taxes; and research and development activity. The data are needed to measure the size and economic significance of foreign direct investment in the United States, to measure changes in such investment, and to assess its impact on the U.S. economy. Such data are generally found in enterprise-level accounting records of respondent companies. The data are disaggregated by industry of U.S. affiliate, by country and industry of foreign parent or ultimate beneficial owner, and, for selected items, by State. </P>
                <HD SOURCE="HD1">Executive Order 13132 </HD>
                <P>This final rule does not contain policies with Federalism implications, as that term is defined in E.O. 13132. </P>
                <HD SOURCE="HD1">Executive Order 12866 </HD>
                <P>This final rule has been determined to be not significant for purposes of E.O. 12866. </P>
                <HD SOURCE="HD1">Paperwork Reduction Act </HD>
                <P>Notwithstanding any other provisions of law, no person is required to respond to, nor shall any person be subject to a penalty for failure to comply with, a collection of information subject to the requirements of the Paperwork Reduction Act (PRA) unless that collection displays a currently valid Office of Management and Budget (OMB) Control Number. This final rule covers a collection of information subject to the provisions of the PRA. The OMB has approved this collection and assigned to it OMB Control Number 0608-0034. The collection will display this control number. </P>
                <P>The survey is expected to result in the filing of reports from approximately 4,950 U.S. affiliates. The respondent burden for this collection of information is expected to vary from 20 minutes for the smallest and least complex company reporting on the BE-15 Supplement C form to 550 hours for the largest and most complex company reporting on the BE-15(LF) long form, with an average burden of 21.8 hours per response (down from 32 hours for the previous annual survey), including time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Total respondent burden for the previous (2001) annual survey was estimated at 128,000 hours. Total respondent burden for this survey is estimated to be 107,900 hours (4,950 responses times 21.8 hours average burden). The decrease of 20,100 hours in the estimated total respondent burden is largely attributable to the changes to the reporting requirements. </P>
                <HD SOURCE="HD1">Regulatory Flexibility Act </HD>
                <P>The Chief Counsel for Regulation, Department of Commerce, has certified to the Chief Counsel for Advocacy, Small Business Administration, under the provisions of the Regulatory Flexibility Act (5 U.S.C. 605(b)), that the proposed rule would not have a significant economic impact on a substantial number of small entities as that term is defined in the Regulatory Flexibility Act. The factual basis for the certification was published with the proposed rule. No comments were received regarding the economic impact of the rule. As a result, no final regulatory flexibility analysis was prepared. </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 15 CFR Part 806 </HD>
                    <P>International transactions, Economic statistics, Foreign investment in the United States, Penalties, Reporting and record keeping requirements.</P>
                </LSTSUB>
                <SIG>
                    <DATED>Dated: November 24, 2003. </DATED>
                    <NAME>J. Steven Landefeld, </NAME>
                    <TITLE>Director, Bureau of Economic Analysis. </TITLE>
                </SIG>
                <REGTEXT TITLE="15" PART="806">
                    <AMDPAR>For reasons set forth in the preamble, BEA amends 15 CFR part 806 as follows: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 806—DIRECT INVESTMENT SURVEYS </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for 15 CFR Part 806 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>5 U.S.C. 301; 22 U.S.C. 3101-3108; and E.O. 11961 (3 CFR, 1977 Comp., p. 86), as amended by E.O. 12013 (3 CFR, 1977 Comp., p. 147), E.O. 12318 (3 CFR, 1981 Comp., p. 173), and E.O. 12518 (3 CFR, 1985 Comp., p. 348).   </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="15" PART="806">
                    <AMDPAR>2. Section 806.15(i) is revised to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 806.15 </SECTNO>
                        <SUBJECT>Foreign direct investment in the United States. </SUBJECT>
                        <STARS/>
                        <P>
                            (i) 
                            <E T="03">Annual report form.</E>
                             BE-15-Annual Survey of Foreign Direct Investment in the United States: One report is required for each consolidated 
                            <PRTPAGE P="67941"/>
                            U.S. affiliate, except a U.S. banking affiliate or U.S. bank holding company affiliate (including all of the subsidiaries and units of the bank holding company), exceeding an exemption level of $30 million. A long form, BE-15(LF), must be filed by each nonbank majority-owned U.S. affiliate (a “majority-owned” U.S. affiliate is one in which the combined direct and indirect ownership interests of all foreign parents of the U.S. affiliate exceed 50 percent) for which at least one of the three items-total assets, sales or gross operating revenues excluding sales taxes, or net income after provision for U.S. income taxes-exceeds $125 million (positive or negative), unless the nonbank majority-owned U.S. affiliate is selected to file a BE-15(EZ) form. A short form, BE-15(SF), must be filed by each nonbank majority-owned U.S. affiliate for which at least one of the three items-total assets, sales or gross operating revenues excluding sales taxes, or net income after provision for U.S. income taxes-exceeds $30 million but no one item exceeds $125 million (positive or negative), and by each nonbank minority-owned U.S. affiliate (a “minority-owned” U.S. affiliate is one in which the combined direct and indirect ownership interest of all foreign parents of the U.S. affiliate is 50 percent or less) for which at least one of the three items-total assets, sales or gross operating revenues excluding sales taxes, or net income after provision for U.S. income taxes-exceeds $30 million (positive or negative), unless the nonbank U.S. affiliate is selected to file a BE-15(EZ) form. A BE-15(EZ) form must be filed by each nonbank U.S. affiliate that is selected to file this form in lieu of filing the BE-15(LF) or BE-15(SF). A BE-15 Supplement C (Exemption Claim) must be filed by each nonbank U.S. affiliate to claim exemption from filing a BE-15(LF), BE-15(SF), or BE-15(EZ). Following an initial filing, the BE-15 Supplement C is not required annually from those nonbank U.S. affiliates that meet the stated exemption criteria from year to year. 
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-29996 Filed 12-4-03; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3510-06-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE INTERIOR </AGENCY>
                <SUBAGY>Bureau of Indian Affairs </SUBAGY>
                <CFR>25 CFR Part 170 </CFR>
                <RIN>RIN 1076-AE50 </RIN>
                <SUBJECT>Partial Distribution of Fiscal Year 2004 Indian Reservation Roads Funds </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Indian Affairs, Interior. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>We are issuing a rule requiring that we immediately distribute $25 million of fiscal year 2004 Indian Reservation Roads (IRR) funds to projects on or near Indian reservations using the relative need formula. This partial distribution reflects the funds the Federal Highway Administration has allocated to the Department of the Interior and is based on funding appropriated by a continuing resolution and the Surface Transportation Extension Act of 2003 in effect until February 29, 2004. We are using the Federal Highway Administration (FHWA) Price Trends report for the relative need formula distribution process, with appropriate modifications to address non-reporting States. This distribution will allow an immediate allocation of funds based on an existing formula, final allocations will be dependent on a final authorization of highway trust funds and a fiscal year 2004 appropriations. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>December 10, 2003. Section 170.4b expires September 30, 2004. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>LeRoy Gishi, Chief, Division of Transportation, Tribal Services, Bureau of Indian Affairs, 1849 C Street, NW., MS-4058-MIB, Washington, DC 20240. Mr. Gishi may also be reached at (202) 208-4359 (phone) or (202) 208-4696 (fax). </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <HD SOURCE="HD1">Background </HD>
                <HD SOURCE="HD2">Where Can I Find General Background Information on the Indian Reservation Roads (IRR) Program, the Relative Need Formula, the Federal Highway Administration (FHWA) Price Trends Report, and the Transportation Equity Act for the 21st Century (TEA-21) Negotiated Rulemaking Process? </HD>
                <P>
                    The background information on the IRR program, the relative need formula, the FHWA Price Trends Report, and the TEA-21 Negotiated Rulemaking process is detailed in the 
                    <E T="04">Federal Register</E>
                     notice dated February 15, 2000 (65 FR 7431). 
                </P>
                <HD SOURCE="HD2">Why Are You Publishing This Rule? </HD>
                <P>We are publishing this rule to distribute $25 million of fiscal year 2004 IRR Program funds. This rule sets no precedent for the final rule to be published as required by Section 1115 of TEA-21. </P>
                <HD SOURCE="HD2">Where Can I Find Information on the Distribution of Fiscal Year 2003 IRR Program Funds? </HD>
                <P>
                    You can find this information in the 
                    <E T="04">Federal Register</E>
                     notice dated June 5, 2003 (68 FR 33625). 
                </P>
                <HD SOURCE="HD2">How Will the Secretary Distribute $25 Million of Fiscal Year 2004 IRR Program Funds? </HD>
                <P>Upon publication of this rule, the Secretary will distribute only $25 million of fiscal year 2004 IRR program funds based on the current relative need formula used in fiscal years 2000, 2001, 2002 and in the first distribution in fiscal year 2003. We are using the latest indices from the FHWA Price Trends Report with appropriate modifications for non-reporting States in the relative need formula distribution process. </P>
                <HD SOURCE="HD1">Regulatory Planning and Review (Executive Order 12866) </HD>
                <P>
                    Under the criteria in Executive Order 12866, this rule is not a significant regulatory action because it will not have an annual effect of more than $100 million on the economy. The total amount currently available for distribution of fiscal year 2004 IRR program funds is approximately $145 million and we are distributing only $25 million under this rule. Congress has authorized these funds and FHWA has already allocated them to BIA. The cost to the government of distributing the IRR program funds, especially under the relative need formula with which the tribal governments and tribal organizations and the BIA are already familiar, is negligible. The distribution of fiscal year 2004 IRR program funds does not require tribal governments and tribal organizations to expend any of their own funds. This rule is consistent with the policies and practices that currently guide our distribution of IRR program funds. This rule continues to adopt the relative need formula that we have used since 1993, adjusting the FHWA Price Trends Report indices for states that do not have current data reports. This rule will not create a serious inconsistency or otherwise interfere with an action taken or planned by another Federal agency. The FHWA has transferred the IRR program funds to us and fully expects the BIA to distribute the funds according to a funding formula approved by the 
                    <PRTPAGE P="67942"/>
                    Secretary. This rule does not alter the budgetary effects on any tribes from any previous or any future distribution of IRR program funds and does not alter entitlement, grants, user fees, or loan programs or the rights or obligations of their recipients. This rule does not raise novel legal or policy issues. It is based on the relative need formula in use since 1993. We are changing determination of relative need only by appropriately modifying the FHWA Price Trend Report indices for states that did not report data for the FHWA Price Trends Report, just as we did for the partial distributions for fiscal years 2000, 2001, 2002 and 2003 IRR Program funds. Approximately 350 road and bridge construction projects are at various phases that depend on this fiscal year's IRR program funds. Leaving these ongoing projects unfunded will create undue hardship on tribes and tribal members. Lack of funding would also pose safety threats by leaving partially constructed road and bridge projects to jeopardize the health and safety of the traveling public. Thus, the benefits of this rule far outweigh the costs. This rule is consistent with the policies and practices that currently guide our distribution of IRR Program funds. 
                </P>
                <HD SOURCE="HD1">Regulatory Flexibility Act </HD>
                <P>
                    A Regulatory Flexibility analysis under the Regulatory Flexibility Act (5 U.S.C. 601 
                    <E T="03">et seq.</E>
                    ) is not required for this rule because it applies only to tribal governments, not State and local governments. 
                </P>
                <HD SOURCE="HD1">Small Business Regulatory Enforcement Fairness Act (SBREFA) </HD>
                <P>This rule is not a major rule under 5 U.S.C. 804(2), the Small Business Regulatory Enforcement Fairness Act, because it does not have an annual effect on the economy of $100 million or more. We are distributing only $25 million under this rule. Congress has authorized these funds and FHWA has already allocated them to BIA. The cost to the government of distributing the IRR Program funds, especially under the relative need formula with which tribal governments, tribal organizations, and the BIA are already familiar, is negligible. The distribution of the IRR Program funds does not require tribal governments and tribal organizations to expend any of their own funds. This rule will not cause a major increase in costs or prices for consumers, individual industries, Federal, State, or local government agencies, or geographic regions. Actions under this rule will distribute Federal funds to projects for transportation planning, road and bridge construction, and road improvements. This rule does not have significant adverse effects on competition, employment, investment, productivity, innovation, or the ability of U.S.-based enterprises to compete with foreign based enterprises. In fact, actions under this rule will provide a beneficial effect on employment through funding for construction jobs. </P>
                <HD SOURCE="HD1">Unfunded Mandates Reform Act </HD>
                <P>
                    Under the Unfunded Mandates Reform Act (2 U.S.C. 1531 
                    <E T="03">et seq.</E>
                    ), this rule will not significantly or uniquely affect small governments, or the private sector. A Small Government Agency Plan is not required. This rule will not produce a federal mandate that may result in an expenditure by State, local, or tribal governments of $100 million or greater in any year. The effect of this rule is to immediately provide $25 million of fiscal year 2004 IRR Program funds for ongoing IRR activities and construction projects. 
                </P>
                <HD SOURCE="HD1">Takings Implications (Executive Order 12630) </HD>
                <P>With respect to Executive Order 12630, the rule does not have significant takings implications since it involves no transfer of title to any property. A takings implication assessment is not required. </P>
                <HD SOURCE="HD1">Federalism (Executive Order 13132) </HD>
                <P>With respect to Executive Order 13132, the rule does not have significant Federalism implications to warrant the preparation of a Federalism Assessment. This rule should not affect the relationship between state governments and the Federal government because this rule concerns administration of a fund dedicated to IRR projects on or near Indian reservations that has no effect on Federal funding of state roads. Therefore, the rule has no Federalism effects within the meaning of Executive Order 13132. </P>
                <HD SOURCE="HD1">Civil Justice Reform (Executive Order 12988) </HD>
                <P>This rule does not unduly burden the judicial system and meets the requirements of sections 3(a) and 3(b)(2) of Executive Order 12988. This rule contains no drafting errors or ambiguity and is clearly written to minimize litigation, provide clear standards, simplify procedures, and reduce burden. This rule does not preempt any statute. Under The Transportation Equity Act for the 21st Century negotiated rulemaking, we have published a proposed rule and funding formula which is currently being finalized. A final funding formula for fiscal year 2004 will be published in 2004. The rule is not retroactive with respect to any funding from any previous fiscal year (or prospective to funding from any future fiscal year), but applies only to $25 million of fiscal year 2004 IRR Program funding. </P>
                <HD SOURCE="HD1">Paperwork Reduction Act </HD>
                <P>
                    The Paperwork Reduction Act does not apply because this rule does not impose record keeping or information collection requirements or the collection of information from offerors, contractors, or members of the public that require the approval of the Office of Management and Budget under 44 U.S.C. 501 
                    <E T="03">et seq.</E>
                     We already have all of the necessary information to implement this rule. 
                </P>
                <HD SOURCE="HD1">National Environmental Policy Act </HD>
                <P>
                    This rule is categorically excluded from the preparation of an environmental assessment or an environmental impact statement under the National Environmental Policy Act of 1969, 42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    , because its environmental effects are too broad, speculative, or conjectural to lend themselves to meaningful analysis and the road projects funded as a result of this rule will be subject later to the National Environmental Policy Act process, either collectively or case-by-case. Further, no extraordinary circumstances exist to require preparation of an environmental assessment or environmental impact statement. 
                </P>
                <HD SOURCE="HD1">Consultation and Coordination With Indian Tribal Governments (Executive Order 13175) </HD>
                <P>
                    Pursuant to Executive Order 13175 of November 6, 2000, “Consultation and Coordination with Indian Tribal Governments,” we have consulted with tribal representatives throughout the negotiated rulemaking process. We have evaluated any potential effects on federally recognized Indian tribes and have determined that there are no potential adverse effects and have determined that this rule preserves the integrity and consistency of the relative need formula process we have used since 1993 to distribute IRR Program funds. We are making a change from previous years (which we also made for fiscal years 2000, 2001, 2002 and 2003 IRR Program funds (see 
                    <E T="04">Federal Register</E>
                     notices at 65 FR 37697, 66 FR 17073, 67 FR 44355 and 68 FR 33625 ) to modify the FHWA Price Trends Report indices for non-reporting states which do not have current price trends data reports. The yearly FHWA Report is used as part of the process to determine the cost-to-
                    <PRTPAGE P="67943"/>
                    improve portion of the relative need formula. Consultation with tribal governments and tribal organizations is ongoing as part of the TEA-21 negotiated rulemaking process. 
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 25 CFR Part 170 </HD>
                    <P>Highways and Roads, Indians-lands.</P>
                </LSTSUB>
                <REGTEXT TITLE="25" PART="170">
                    <AMDPAR>In order to distribute part of fiscal year 2004 IRR Program funds immediately we are amending part 170 in chapter I of title 25 of the Code of Federal Regulations as follows. </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 170—ROADS OF THE BUREAU OF INDIAN AFFAIRS </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 170 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>36 Stat. 861; 78 Stat. 241, 253, 257; 45 Stat. 750 (25 U.S.C. 47; 42 U.S.C. 2000e(b), 2000e-2(i); 23 U.S.C. 101(a), 202, 204), unless otherwise noted.   </P>
                    </AUTH>
                </REGTEXT>
                  
                <REGTEXT TITLE="25" PART="170">
                    <AMDPAR>2. Revise § 170.4b to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 170.4b </SECTNO>
                        <SUBJECT>What formula will BIA use to distribute $25 million of fiscal year 2004 Indian Reservation Roads Program funds? </SUBJECT>
                        <P>On December 10, 2003, we will distribute $25 million of fiscal year 2004 IRR Program funds authorized under the Surface Transportation Extension Act of 2003, Pub. L. 108-88. We will distribute the funds to Indian Reservation Roads projects on or near Indian reservations using the relative need formula established and approved in January 1993. The formula has been modified to account for non-reporting States by inserting the latest data reported for those states for use in the relative need formula process.   </P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: November 25, 2003. </DATED>
                    <NAME>Aurene Martin, </NAME>
                    <TITLE>Principal Deputy Assistant Secretary—Indian Affairs. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30208 Filed 12-4-03; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4310-LY-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBAGY>Office of the Secretary</SUBAGY>
                <CFR>31 CFR Parts 1 and 323</CFR>
                <SUBJECT>Privacy Act of 1974; Implementation</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of the Public Debt, Treasury.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the requirements of the Privacy Act of 1974, as amended, the Department of the Treasury exempts a Bureau of the Public Debt system of records entitled “Treasury/BPD.009—U.S. Treasury Securities Fraud Information System” from certain provisions of the Privacy Act.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>December 5, 2003.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For information about Public Debt's anti-money laundering and fraud suppression program, contact the Fraud Inquiry Line at 304-480-8555. The phone line is administered by the Office of the Chief Counsel, Bureau of the Public Debt. For information about this document, contact the Office of the Chief Counsel, Bureau of the Public Debt, at 304-480-8692 or by e-mail at 
                        <E T="03">chcounsel@bpd.treas.gov</E>
                        . Copies of this rule can be downloaded from the public Web site at 
                        <E T="03">http://www.publicdebt.treas.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Department of the Treasury published a system notice for “Treasury/BPD.009-U.S. Treasury Securities Fraud Information System” in its entirety at 68 FR 34486-34489 (June 9, 2003). We did not receive any comments on the notice. The system of records became effective July 21, 2003.</P>
                <P>We issued a proposed rule exempting the system of records from certain provisions of the Privacy Act of 1974, as amended, at 68 FR 36955-36957 (June 20, 2003). Under 5 U.S.C. 552a(k)(2), the head of an agency may promulgate rules to exempt any system of records within the agency from certain provisions of the Privacy Act of 1974, as amended, if the system is investigatory material compiled for law enforcement purposes. The system of records contains investigatory material compiled for law enforcement purposes.</P>
                <P>The provisions of the Privacy Act from which exemption is claimed pursuant to 5 U.S.C. 552a(k)(2) are: 5 U.S.C. 552a(c)(3) (Accounting of certain disclosures available to the individual), (d)(1)-(4) (Access to records), (e)(1) (Maintenance of information to accomplish purposes authorized by statute or executive order only), (e)(4)(G) (Publication of procedures for notification), (e)(4)(H) (Publication of procedures for access and contest), (e)(4)(I) (Publication of sources of records), and (f) (Rules for notification, access and contest) to the extent that information in the system is subject to exemption pursuant to 5 U.S.C. 552a(k)(2) as material compiled for law enforcement purposes.</P>
                <P>In an unrelated change, the proposed rule clarified the privacy interests afforded to close survivors of a deceased securities holder. Public Debt protected the privacy interests of securities holders by regulation long before the passage of the Privacy Act of 1974. We proposed to amend part 323 to comport with exemption 6 of the Freedom of Information Act which permits us to withhold all information about individuals in “personnel and medical files and similar files” when the disclosure of such information “would constitute a clearly unwarranted invasion of personal privacy.” Although the right to privacy of a deceased securities holder extinguishes upon death, the exemption will protect the deceased person's family-related privacy interests in certain cases.</P>
                <P>The proposed rule requested that public comments be sent to the Disclosure Officer, Administrative Resource Center, Bureau of the Public Debt, no later than July 21, 2003. We did not receive comments on the proposed rule. Accordingly, the Department of the Treasury is hereby giving notice that the system of records entitled “Treasury/BPD.009-U.S. Treasury Securities Fraud Information System.”, is exempt from certain provisions of the Privacy Act.</P>
                <P>As required by Executive Order 12866, it has been determined that this final rule is not a “significant regulatory action,” and therefore, does not require a Regulatory Impact Analysis.</P>
                <P>The regulation will not have a substantial direct effect on the States, on the relationship between the Federal Government and the States, or on the distribution of power and responsibilities among the various levels of government. Therefore, it is determined that this final rule does not have federalism implications under Executive Order 13132.</P>
                <P>Pursuant to the requirements of the Regulatory Flexibility Act, 5 U.S.C. 601-612, the Department of the Treasury and Public Debt certify that these regulations will not significantly affect a substantial number of small entities. The final rule imposes no duties or obligations on small entities.</P>
                <P>In accordance with the provisions of the Paperwork Reduction Act of 1995, the Department of the Treasury and Public Debt have determined that this final rule would not impose new record keeping, application, reporting, or other types of information collection requirements.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects</HD>
                    <CFR>31 CFR Part 1</CFR>
                    <P>Privacy.</P>
                    <CFR>31 CFR Part 323</CFR>
                    <P>Freedom of Information Act, Privacy.</P>
                </LSTSUB>
                <REGTEXT TITLE="31" PART="1">
                    <AMDPAR>Accordingly, for the reasons stated in the preamble, 31 CFR part 1, is amended as follows:</AMDPAR>
                    <AMDPAR>1. The authority citation for part 1 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <PRTPAGE P="67944"/>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>5 U.S.C. 301 and 31 U.S.C. 321. Subpart A also issued under 5 U.S.C. 552, as amended. Subpart C also issued under 5 U.S.C. 552a.</P>
                    </AUTH>
                    <PART>
                        <HD SOURCE="HED">PART 1—[AMENDED]</HD>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart C—Privacy Act</HD>
                        </SUBPART>
                    </PART>
                </REGTEXT>
                <REGTEXT TITLE="31" PART="1">
                    <AMDPAR>2. In Subpart C, §1.36, paragraph (g)(1)(x) is amended by adding the following new table below the heading BUREAU OF THE PUBLIC DEBT:</AMDPAR>
                    <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="xs50,r50">
                        <TTITLE>  </TTITLE>
                        <BOXHD>
                            <CHED H="1">Number </CHED>
                            <CHED H="1">System name </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">BPD.009</ENT>
                            <ENT>U.S. Treasury Securities Fraud Information System. </ENT>
                        </ROW>
                    </GPOTABLE>
                </REGTEXT>
                <REGTEXT TITLE="31" PART="323">
                    <PART>
                        <HD SOURCE="HED">PART 323—[AMENDED]</HD>
                    </PART>
                    <AMDPAR>3. The authority citation for part 323 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>80 Stat. 379; sec. 3., 60 Stat. 238, as amended; 5 U.S.C. 301, 552.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="31" PART="323">
                    <AMDPAR>4. Revise § 323.2(b) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 323.2 </SECTNO>
                        <SUBJECT>Rules Governing Availability of Information.</SUBJECT>
                        <STARS/>
                        <P>
                            (b) 
                            <E T="03">Limitations on the availability of records relating to securities</E>
                            . Records relating to the purchase, ownership of, and transactions in Treasury securities or other securities handled by the Bureau of the Public Debt for government agencies or wholly or partially Government-owned corporations will ordinarily be disclosed only to the owners of such securities, their executors, administrators or other legal representatives or to their survivors or to investigative and certain other agencies of the Federal and State governments, to trustees in bankruptcy, receivers of insolvents' estates or where a proper order has been entered requesting disclosure of information to Federal and State courts. These records are confidential because they relate to private financial affairs of the owners under this Part. In addition, the information falls within the category of “personnel and medical files and similar files the disclosure of which would constitute a clearly unwarranted invasion of personal privacy” under the Freedom of Information Act (FOIA), 5 U.S.C. 552(b)(6). FOIA Exemption (b)(6) protects the privacy of living persons who own securities as well as the close survivors of deceased owners. Privacy interests, in the sense of the right to control, use, or disclose information about oneself, cease at death. However, the exemption protects the deceased person's family-related privacy interests that survive death where disclosure would cause embarrassment, pain, grief, or disrupt the peace of mind, of the surviving family. The Bureau of the Public Debt will determine, under FOIA exemption (b)(6), whether disclosure of the records is in the public interest by balancing the surviving family members' privacy interest against the public's right to know the information.
                        </P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: November 18, 2003.</DATED>
                    <NAME>Teresa Mullett Ressel,</NAME>
                    <TITLE>Assistant Secretary for Management and Chief Financial Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30241 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4810-39-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Coast Guard</SUBAGY>
                <CFR>33 CFR Part 100</CFR>
                <DEPDOC>[CGD07-03-151]</DEPDOC>
                <RIN>RIN 1625-AA08</RIN>
                <SUBJECT>Special Local Regulations; 2003 Holiday Boat Parade of the Palm Beaches, Riviera Beach, FL</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Temporary final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Temporary special local regulations are being established for the 2003 Holiday Boat Parade in Riviera Beach, Florida. The event will be held on December 6, 2003, on the waters of the Intracoastal Waterway staging in the Lake Worth turning basin southeast of Peanut Island, and proceeding north from Lake Worth South Section Marker 1 and to Jonathan's Landing Marina, Lake Worth Creek Marker 19. These regulations exclude non-participant vessels from the regulated area, which includes the staging area and the parade route, and are needed to provide for the safety of life on navigable waters during the event.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>These regulations are effective from 6 p.m. until 9 p.m. on December 6, 2003.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Documents indicated in this preamble as being available in the docket are part of [CGD07-03-151] and are available for inspection or copying at Coast Guard Group Miami, 100 MacArthur Causeway, Miami Beach, Florida, 33139 between 8 a.m. and 4 p.m., Monday through Friday, except Federal holidays.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>BMC Vaughn, Coast Guard Group Miami, Florida at (305) 535-4317.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P> </P>
                <HD SOURCE="HD1">Good Cause</HD>
                <P>We did not publish a notice of proposed rulemaking (NPRM) for this regulation. Under 5 U.S.C. 553(b)(B), the Coast Guard finds that good cause exists for not publishing an NPRM. Publishing an NPRM would be unnecessary and contrary to public safety interests. These regulations are needed to minimize danger to the public resulting from numerous spectator and participant craft in close proximity to each other around the staging area and parade route. The event will be held on Saturday December 6, 2003. There is not sufficient time to allow for a notice and comment period, prior to the event. For the safety concerns noted, it is in the public interest to have these regulations in effect during the event. In addition, advance notifications will be made via marine information broadcasts.</P>
                <P>
                    For the same reasons, the Coast Guard finds that good cause exists for making this rule effective less than 30 days after publication in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <HD SOURCE="HD1">Background and Purpose</HD>
                <P>The 2003 Holiday Boat Parade of the Palm Beaches is a nighttime parade of approximately 60 pleasure boats decorated with holiday lights. These boats range in length from 15 feet to 50 feet. It is anticipated that approximately 200 spectator craft will view the parade. The parade will form in a staging area located within the Lake Worth turning basin on the southeast side of Peanut Island and encompassing all waters within the turning basin west of a line connecting Marker 12 on the north side of the turning basin and Marker 13 on the south side of the turning basin. The parade will then commence and proceed north from Lake Worth South Section Marker 1 on the Intracoastal Waterway (ICW) to Jonathan's Landing Marina at Lake Worth Creek Marker 19, where the parade will disperse. The regulated area includes the staging area and the parade route.</P>
                <HD SOURCE="HD1">Discussion of Rule</HD>
                <P>The special local regulations for this event prohibit non-participant vessels from entering the regulated area, which includes the staging area and the parade route.</P>
                <P>The staging area encompasses all waters within the Lake Worth turning basin on the southeast side of Peanut Island west of a line connecting Lake Worth Inlet Marker 12 on the north side of the turning basin and Marker 13 on the south side of the turning basin. No anchoring is permitted in the staging area.</P>
                <P>
                    The parade route encompasses the Intracoastal Waterway from Lake Worth 
                    <PRTPAGE P="67945"/>
                    South Section Marker 1 to Lake Worth Creek Marker 19. During transit of the parade, these regulations prohibit non-participating vessels from approaching within 500 feet ahead of the lead parade vessel, 500 feet astern of the last participating vessel, or within 50 feet on either side of the outboard parade vessels in the regulated area, unless authorized by the Coast Guard patrol commander.
                </P>
                <HD SOURCE="HD1">Regulatory Evaluation</HD>
                <P>This proposal is not a “significant regulatory action” under section 3(f) of Executive Order 12866, Regulatory Planning and Review, and does not require an assessment of potential costs and benefits under section 6(a)(3) of that Order. The Office of Management and Budget has not reviewed it under that Order. It is not “significant” under the regulatory policies and procedures of the Department of Homeland Security (DHS). This regulation will have a minimal impact on non-participant and non-spectator vessels due to the normally low volume of vessel traffic on the ICW during this time this rule is effective. Moreover, this rule is effective for only 3 hours, it regulates only the waters immediately surrounding the parade vessels, and moves with the parade vessels and should therefore have a minimal impact on non-participant and non-spectator vessels.</P>
                <HD SOURCE="HD1">Small Entities</HD>
                <P>Under the Regulatory Flexibility Act (5 U.S.C. 601-612), we have considered whether this rule would have a significant economic impact on a substantial number of small entities. The term “small entities” comprises small businesses, not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000.</P>
                <P>The Coast Guard certifies under 5 U.S.C. 605(b) that this rule will not have a significant economic impact on a substantial number of small entities. This rule may affect the following entities, some of which may be small entities: The owners or operators of vessels intending to transit or anchor in a portion of the regulated area from 6 p.m. to 9 p.m. on December 6, 2003. This rule will not have a significant economic impact on a substantial number of small entities for the following reasons. This rule is for a highly publicized event and will be in effect for only three hours late in the day when vessel traffic is minimal. Any traffic that needs to pass through the regulated area will be allowed to pass with the permission of the Coast Guard patrol commander once the parade participants have moved further along the parade route.</P>
                <HD SOURCE="HD1">Assistance for Small Entities</HD>
                <P>
                    Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121), we offer to assist small entities in understanding the rule so that they can better evaluate its effects on them and participate in the rulemaking process. Small businesses may contact the person listed under 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     for assistance in understanding and participating in this rulemaking. Small businesses may send comments on the actions of Federal employees who enforce, or otherwise determine compliance with, Federal regulations to the Small Business and Agriculture Regulatory Enforcement Ombudsman and the Regional Small Business Regulatory Fairness Boards. The Ombudsman evaluates these actions annually and rates each agency's responsiveness to small business. If you wish to comment on actions by employees of the Coast Guard, call 1-888-REG-FAIR (1-888-734-3247).
                </P>
                <HD SOURCE="HD1">Collection of Information</HD>
                <P>This rule calls for no new collection of information requirements under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520).</P>
                <HD SOURCE="HD1">Federalism</HD>
                <P>A rule has implications for federalism under Executive Order 13132, Federalism, if it has a substantial direct effect on State or local governments and would either preempt State law or impose a substantial direct cost of compliance on them. We have analyzed this rule under that Order and have determined that it does not have implications for federalism.</P>
                <HD SOURCE="HD1">Unfunded Mandates Reform Act</HD>
                <P>The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) requires Federal agencies to assess the effects of their discretionary regulatory actions. In particular, the Act addresses actions that may result in the expenditure by a State, local, or tribal government, in the aggregate, or by the private sector of $100,000,000 or more in any one year. Though this rule will not result in such an expenditure, we do discuss the effects of this rule elsewhere in the preamble.</P>
                <HD SOURCE="HD1">Taking of Private Property</HD>
                <P>This rule will not effect a taking of private property or otherwise have taking implications under Executive Order 12630, Governmental Actions and Interference with Constitutionally Protected Property Rights.</P>
                <HD SOURCE="HD1">Civil Justice Reform</HD>
                <P>This rule meets applicable standards in sections 3(a) and 3(b)(2) of Executive Order 12988, Civil Justice Reform, to minimize litigation, eliminate ambiguity, and reduce burden.</P>
                <HD SOURCE="HD1">Protection of Children</HD>
                <P>We have analyzed this rule under Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks. This rule is not an economically significant rule and does not create an environmental risk to health or safety that may disproportionately affect children.</P>
                <HD SOURCE="HD1">Indian Tribal Governments</HD>
                <P>This rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it does not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes.</P>
                <HD SOURCE="HD1">Energy Effects</HD>
                <P>We have analyzed this rule under Executive Order 13211, Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use. We have determined that it is not a “significant energy action” under that Order, because it is not a “significant regulatory action” under Executive Order 12866 and is not likely to have a significant adverse effect on the supply, distribution, or use of energy. The Administrator of the Office of Information and Regulatory Affairs has not designated it as a significant energy action. Therefore, it does not require a Statement of Energy Effects under Executive Order 13211.</P>
                <HD SOURCE="HD1">Environment</HD>
                <P>
                    We have analyzed this rule under Commandant Instruction M16475.1D, which guides the Coast Guard in complying with the National Environmental Policy Act of 1969 (NEPA) (42 U.S.C. 4321-4370f), and have concluded that there are no factors in this case that would limit the use of a categorical exclusion under section 2.B.2 of the Instruction. Therefore, this rule is categorically excluded, under figure 2-1, paragraph 34(h), of the Instruction, from further environmental documentation. Under figure 2-1, 
                    <PRTPAGE P="67946"/>
                    paragraph (34)(h), of the Instruction, an “Environmental Analysis Check List” and a “Categorical Exclusion Determination” are not required for this rule.
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 33 CFR Part 100</HD>
                    <P>Marine safety, Navigation (water), Reporting and recordkeeping requirements, Waterways.</P>
                </LSTSUB>
                <AMDPAR>For the reasons set out in the preamble, the Coast Guard amends 33 CFR part 100 as follows:</AMDPAR>
                <PART>
                    <HD SOURCE="HED">PART 100—[MARINE EVENTS]</HD>
                </PART>
                <AMDPAR>1. The authority citation for Part 100 continues to read as follows:</AMDPAR>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>33 U.S.C. 1233; Department of Homeland Security Delegation No. 0170.1.</P>
                </AUTH>
                <REGTEXT TITLE="33" PART="100">
                    <AMDPAR>2. Add § 100.35T-07-151 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 100.35T-07-151 2003 </SECTNO>
                        <SUBJECT>Holiday Boat Parade of the Palm Beaches, Riviera Beach, FL</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Regulated areas.</E>
                             (1) The regulated staging area encompasses all waters within the Lake Worth Inlet, Port of Palm Beach, turning basin, west of a line connecting Marker 12 on the north side of the turning basin and Marker 13 on the south side of the turning basin.
                        </P>
                        <P>(2) The regulated parade area encompasses all waters of the Intracoastal Waterway from Lake Worth South Section Marker 1 behind Peanut Island north to Lake Worth Creek Marker 19 at Jonathan's Landing Marina.</P>
                        <P>
                            (b) 
                            <E T="03">Coast Guard patrol commander.</E>
                             The Coast Guard patrol commander is a commissioned, warrant, or petty officer of the Coast Guard who has been designated by Commander, Coast Guard Group Miami, Florida.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Special local regulations. (1) Staging areas.</E>
                             Entry or anchoring in the staging area by non-participating vessels is prohibited, unless authorized by the Coast Guard patrol commander.
                        </P>
                        <P>
                            (2) 
                            <E T="03">Parade route.</E>
                             During the transit of parade vessels, non-participating vessels are prohibited from approaching within 500 feet ahead of the lead parade vessel, 500 feet astern of the last participating vessel in the parade, or within 50 feet either side of the outboard parade vessels, unless authorized by the Coast Guard patrol commander.
                        </P>
                        <P>
                            (d) 
                            <E T="03">Effective period:</E>
                             This section is effective from 6 p.m. until 9 p.m. on December 6, 2003.
                        </P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: November 25, 2003.</DATED>
                    <NAME>Harvey E. Johnson, Jr.,</NAME>
                    <TITLE>Rear Admiral, U.S. Coast Guard, Commander, Seventh Coast Guard District.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30278 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-15-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY </AGENCY>
                <SUBAGY>Coast Guard </SUBAGY>
                <CFR>33 CFR Part 165 </CFR>
                <DEPDOC>[COTP San Diego 03-032] </DEPDOC>
                <RIN>RIN 1625-AA00 </RIN>
                <SUBJECT>Security Zone: Coronado Bay Bridge, San Diego, CA </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Coast Guard, DHS. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Temporary final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Coast Guard is establishing temporary security zones encompassing navigable waters 25 yards around all piers, abutments, fenders and pilings of the Coronado Bay Bridge. These temporary security zones are needed for national security reasons to protect the public and ports from potential subversive actions. Persons and vessels are prohibited from entering into, transiting through, loitering, or anchoring within these security zones unless authorized by the Captain of the Port, or his designated representative. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>This rule is effective from November 7, 2003, until May 1, 2004. </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Documents indicated in this preamble as being available in the docket, are part of docket [COTP San Diego 03-032] and are available for inspection or copying at Marine Safety Office San Diego, 2716 North Harbor Drive, San Diego, CA 92101-1064 between 8 a.m. and 4 p.m., Monday through Friday, except Federal holidays. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Petty Officer Austin Murai, USCG, c/o U.S. Coast Guard Captain of the Port, telephone (619) 683-6495 </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Regulatory Information </HD>
                <P>
                    We did not publish a notice of proposed rulemaking (NPRM) for this regulation. Under 5 U.S.C. 553(b)(B) the Coast Guard finds that good cause exists for not publishing an NPRM. Also, for the same reasons, under 5 U.S.C. 553(d)(3), the Coast Guard finds that good cause exists for making this rule effective less than 30 days after publication in the 
                    <E T="04">Federal Register</E>
                    . The threat of maritime attacks is real as evidenced by the October 2002 attack of a tank vessel off the coast of Yemen and the continuing threat to U.S. assets as described in the President's finding in Executive Order 13273 of August 21, 2002 (67 FR 56215, September 3, 2002) that the security of the U.S. is endangered by the September, 11, 2001 attacks and that such disturbances continue to endanger the international relations of the United States. See also Continuation of the National Emergency with Respect to Certain Terrorist Attacks, (67 FR 58317, September 13, 2002); Continuation of the National Emergency With Respect To Persons Who Commit, Threaten To Commit, Or Support Terrorism, (67 FR 59447, September 20, 2002). 
                </P>
                <P>As a result, a heightened level of security has been established around the Coronado Bridge. Maintaining the structural integrity of the Coronado Bridge, which spans San Diego Bay, is very important to the local economy and military units within the San Diego Area. The measures contemplated by this rule are intended to prevent future terrorist attacks against individuals on or near the Coronado Bridge. Any delay in the effective date of this TFR is impractical and contrary to the public interest. </P>
                <HD SOURCE="HD1">Background and Purpose </HD>
                <P>Since the September 11, 2001 terrorist attacks on the World Trade Center in New York, the Pentagon in Arlington, Virginia and Flight 93, the Federal Bureau of Investigation (FBI) has issued several warnings concerning the potential for additional terrorist attacks within the United States. In addition, the ongoing hostilities in Afghanistan and the war with Iraq have made it prudent to U.S. ports to be on higher state of alert because the Al-Qaeda organization and other similar organizations have declared an ongoing intention to conduct armed attacks on U.S. interests worldwide. In its effort to thwart terrorist activity, the Coast Guard has increased safety and security measures on U.S. ports and waterways. As part of the Diplomatic Security and Antiterrorism Act of 1986 (Pub. L. 99-399), Congress amended section 7 of the Ports and Waterways Safety Act (PWSA), 33 U.S.C. 1226, to allow the Coast Guard to take actions, including the establishment of security and safety zones, to prevent or respond to acts of terrorism against individuals, vessels, or public or commercial structures.</P>
                <P>
                    In this particular rulemaking, to address the aforementioned security concerns, and to take steps to prevent the catastrophic impact that a terrorist attack against the Coronado Bridge would have on the public interest, the Coast Guard is establishing security zones around the Coronado Bridge. These security zones help the Coast Guard to prevent vessels or persons from engaging in terrorist actions against these bridges. Due to these heightened security concerns, and the catastrophic impact a terrorist attack on this bridge would have on the public, 
                    <PRTPAGE P="67947"/>
                    the transportation system and surrounding areas and communities, security zones are prudent for these structures. 
                </P>
                <HD SOURCE="HD1">Discussion of Rule </HD>
                <P>In this temporary rule, the Coast Guard is establishing fixed security zones encompassing, from the surface to the sea floor, navigable waters 25 yards around all piers, abutments, fenders and pilings of the Coronado Bridge, San Diego Bay, California. Entry into these security zones is prohibited unless doing so is necessary for safe navigation or to conduct official business such as scheduled maintenance or retrofit operations. Vessels and people may be allowed to enter an established security zone on a case-by-case basis with authorization from the Captain of the Port. </P>
                <P>Vessels or persons violating this section will be subject to the penalties set forth in 33 U.S.C. 1232. Pursuant to 33 U.S.C. 1232, any violation of the security zone described herein is punishable by civil penalties, criminal penalties (including imprisonment up to 6 years), and in rem liability against the offending vessel. Any person who violates this section using a dangerous weapon or who engages in conduct that causes bodily injury or fear of imminent bodily injury to any officer authorized to enforce this regulation, also faces imprisonment up to 12 years. </P>
                <P>Coast Guard personnel will enforce this regulation and the Captain of the Port may be assisted by other Federal, State, or local agencies in the patrol and enforcement of the regulation. This regulation is proposed under the authority of 33 U.S.C. 1226 in addition to the authority contained in 33 U.S.C. 1231. </P>
                <HD SOURCE="HD1">Regulatory Evaluation </HD>
                <P>This rule is not a “significant regulatory action” under section 3(f) of Executive Order 12866, Regulatory Planning and Review, and does not require an assessment of potential costs and benefits under section 6(a)(3) of that Order. The Office of Management and Budget has not reviewed it under that Order. It is not “significant” under the regulatory policies and procedures of the Department of Homeland Security (DHS). </P>
                <P>Although this regulation restricts access to portions of the navigable waterways around the bridge, the effect of this regulation will not be significant because: (i) The zones will encompass only a small portion of the waterway; (ii) Vessels will be able to pass safely around the zones; and (iii) Vessels may be allowed to enter these zones on a case-by-case basis with permission of the Captain of the Port, or his designated representative. </P>
                <P>The sizes of the zones are the minimum necessary to provide adequate protection for the bridges, vessels operating in the vicinity, adjoining areas and the public. The entities most likely to be affected are commercial vessels transiting the main ship channel en route the southern San Diego Bay and Chula Vista ports and pleasure craft engaged in recreational activities and sightseeing. </P>
                <HD SOURCE="HD1">Small Entities </HD>
                <P>Under the Regulatory Flexibility Act (5 U.S.C. 601-612), we have considered whether this rule would have a significant economic impact on a substantial number of small entities. The term “small entities” comprises small businesses, not-for-profit organizations that are independently owned and operated and are not dominant in their fields, and governmental jurisdictions with populations of less than 50,000. </P>
                <P>The Coast Guard certifies under 5 U.S.C. 605(b) that this rule will not have a significant economic impact on a substantial number of small entities. This rule will affect the following entities, some of which may be small entities: the owners or operators of commercial vessels transiting the main ship channel en route the southern San Diego Bay and Chula Vista ports and pleasure craft engaged in recreational activities and sightseeing. The security zones will not have a significant economic impact on a substantial number of small entities for several reasons: small vessel traffic can pass safely around the security zones and vessels engaged in recreational activities, sightseeing and commercial fishing have ample space outside of the security zones to engage in these activities. Small entities and the maritime public will be advised of these security zones via public notice to mariners. </P>
                <HD SOURCE="HD1">Assistance for Small Entities </HD>
                <P>Under section 213(a) of the Small Business Regulatory Enforcement Fairness Act of 1996 (Pub. L. 104-121), we offered to assist small entities in understanding the rule so that they could better evaluate its effects on them and participate in the rulemaking process. If the rule will affect your small business, organization, or government jurisdiction and you have questions concerning its provisions or options for compliance, please contact Lieutenant Commander Rick Sorrell, USCG, c/o U.S. Coast Guard Captain of the Port, telephone (619) 683-6495 for assistance in understanding this rule. </P>
                <P>Small businesses may send comments on the actions of Federal employees who enforce, or otherwise determine compliance with, Federal regulations to the Small Business and Agriculture Regulatory Enforcement Ombudsman and the Regional Small Business Regulatory Fairness Boards. The Ombudsman evaluates these actions annually and rates each agency's responsiveness to small business. If you wish to comment on actions by employees of the Coast Guard, call 1-888-REG-FAIR (1-888-734-3247). </P>
                <HD SOURCE="HD1">Collection of Information </HD>
                <P>This rule calls for no new collection of information under the Paperwork Reduction Act of 1995 (44 U.S.C. 3501-3520). </P>
                <HD SOURCE="HD1">Federalism </HD>
                <P>A rule has implications for federalism under Executive Order 13132, Federalism, if it has a substantial direct effect on State or local governments and would either preempt State law or impose a substantial direct cost of complianc e on them. We have analyzed this rule under that Order and have determined that it does not have implications for federalism. </P>
                <HD SOURCE="HD1">Unfunded Mandates Reform Act </HD>
                <P>The Unfunded Mandates Reform Act of 1995 (2 U.S.C. 1531-1538) requires Federal agencies to assess the effects of their discretionary regulatory actions. In particular, the Act addresses actions that may result in the expenditure by a State, local, or tribal government, in the aggregate, or by the private sector of $100,000,000 or more in any one year. Though this rule will not result in such expenditure, we do discuss the effects of this rule elsewhere in this preamble. </P>
                <HD SOURCE="HD1">Taking of Private Property </HD>
                <P>This rule will not effect a taking of private property or otherwise have taking implications under Executive Order 12630, Governmental Actions and Interference with Constitutionally Protected Property Rights. </P>
                <HD SOURCE="HD1">Civil Justice Reform </HD>
                <P>This rule meets applicable standards in sections 3(a) and 3(b)(2) of Executive Order 12988, Civil Justice Reform, to minimize litigation, eliminate ambiguity, and reduce burden. </P>
                <HD SOURCE="HD1">Protection of Children </HD>
                <P>
                    We have analyzed this rule under Executive Order 13045, Protection of Children from Environmental Health Risks and Safety Risks. This rule is not 
                    <PRTPAGE P="67948"/>
                    an economically significant rule and does not create an environmental risk to health or risk to safety that may disproportionately affect children. 
                </P>
                <HD SOURCE="HD1">Indian Tribal Governments </HD>
                <P>This rule does not have tribal implications under Executive Order 13175, Consultation and Coordination with Indian Tribal Governments, because it does not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes. </P>
                <HD SOURCE="HD1">Energy Effects </HD>
                <P>We have analyzed this rule under Executive Order 13211, Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use. We have determined that it is not a “significant energy action” under that order because it is not a “significant regulatory action” under Executive Order 12866 and is not likely to have a significant adverse effect on the supply, distribution, or use of energy. The administrator of the Office of Information and Regulatory Affairs has not designated it as a significant energy action. Therefore, it does not require a Statement of Energy Effects under Executive Order 13211. </P>
                <HD SOURCE="HD1">Environment</HD>
                <P>We have analyzed this rule under Commandant Instruction M16475.lD, which guides the Coast Guard in complying with the National Environmental Policy Act of 1969 (NEPA)(42 U.S.C. 4321-4370f), and have concluded that there are no factors in this case that would limit the use of a categorical exclusion under section 2.B.2 of the Instruction. Therefore, this rule is categorically excluded, under figure 2-1, paragraph (34)(g), of the Instruction, from further environmental documentation because we are establishing a security zone.</P>
                <P>
                    A final “Environmental Analysis Check List” and a final “Categorical Exclusion Determination” will be available in the docket where indicated under 
                    <E T="02">ADDRESSES.</E>
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 33 CFR Part 165</HD>
                    <P>Harbors, Marine safety, Navigation (water), Reporting and recordkeeping requirements, Security measures, Waterways.</P>
                </LSTSUB>
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>For the reasons discussed in the preamble, the Coast Guard amends 33 CFR Part 165 as follows:</AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 165—REGULATED NAVIGATION AREAS AND LIMITED ACCESS AREAS</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 165 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>33 U.S.C. 1226, 1231; 46 U.S.C. Chapter 701; 50 U.S.C. 191, 195; 33 CFR 1.05-1(g), 6.04-1, 6.04-6, and 160.5; Pub. L. 107-295, 116 Stat. 2064; Department of Homeland Security Delegation No. 0170.1.</P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="33" PART="165">
                    <AMDPAR>2. Add new § 165.T11-030 to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 165.T11-030 </SECTNO>
                        <SUBJECT>Security Zone: Coronado Bay Bridge, San Diego, CA.</SUBJECT>
                        <P>
                            (a) 
                            <E T="03">Location.</E>
                             All navigable waters, extending from the surface to the sea floor, 25 yards around all piers, abutments, fenders and pilings of the Coronado Bay Bridge spanning San Diego Bay. This security zone will not restrict the main navigational channel and vessels will not be restricted from transiting through the channel.
                        </P>
                        <P>
                            (b) 
                            <E T="03">Effective period.</E>
                             This section is effective from November 7, 2003, until May 1, 2004. If the Coast Guard terminates enforcement of this security zone prior to the scheduled termination time, the Captain of the Port will cease enforcement of this safety zone and will announce that fact via Broadcast Notice to Mariners.
                        </P>
                        <P>
                            (c) 
                            <E T="03">Regulations.</E>
                             In accordance with the general regulations in § 165.33 of this part, entry into, transit through, loitering, or anchoring within this security zone by all persons and vessels is prohibited, unless authorized by the Captain of the Port, or his designated representative. Mariners are advised that the security zones will not restrict the main navigational channel and transit through the channel is not prohibited. Mariners requesting permission to transit through the security zone may request authorization to do so from Captain of the Port or his designated representative. The Coast Guard can be contacted on San Diego Bay via VHF-FM channel 16.
                        </P>
                        <P>
                            (d) 
                            <E T="03">Authority.</E>
                             In addition to 33 U.S.C. 1231, the authority for this section includes 33 U.S.C. 1226.
                        </P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <DATED>Dated: November 4, 2003.</DATED>
                    <NAME>Stephen P. Metruck,</NAME>
                    <TITLE>Commander, U.S. Coast Guard, Captain of the Port, San Diego.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30277 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-15-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY </AGENCY>
                <CFR>40 CFR Part 52 </CFR>
                <DEPDOC>[DE072-1042a; FRL-7593-5] </DEPDOC>
                <SUBJECT>Approval and Promulgation of Air Quality Implementation Plans; Delaware; MOBILE6-Based Motor Vehicle Emission Budgets for the Delaware Portion of the Philadelphia-Wilmington-Trenton 1-Hour Ozone Nonattainment Area </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Direct final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>EPA is taking direct final action to approve a revision to the Delaware State Implementation Plan (SIP). Specifically, EPA is approving amendments to the 2005 highway (on road) motor vehicle emission inventory for the Delaware portion of the Philadelphia-Wilmington-Trenton area's (the Philadelphia area) 1-hour ozone attainment plan as a revision to the Delaware SIP. This revision also serves to amend the 2005 motor vehicle emission budgets (MVEBs) used for determining transportation conformity under the Clean Air Act. The revised MVEBs were developed using MOBILE6, the most recent version of EPA's mobile source emission factor model. Revision of the MVEBs was a requirement of EPA's prior approval of Delaware's 1-hour ozone attainment demonstration plan for the Philadelphia severe ozone nonattainment area. The intended effect of this direct final approval action is to approve a SIP revision that will assist Delaware in attaining and demonstrating conformity with the 1-hour ozone standard. This action is being taken by EPA in accordance with the requirements of the Clean Air Act. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        This rule is effective on February 3, 2004 without further notice, unless EPA receives adverse written comment by January 5, 2004. If EPA receives such comments, it will publish a timely withdrawal of the direct final rule in the 
                        <E T="04">Federal Register</E>
                         and inform the public that the rule will not take effect. 
                    </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments may be submitted either by mail or electronically. Written comments should be mailed to Robert Kramer, Chief, Energy, Radiation and Indoor Environment Branch, Mailcode 3AP23, U.S. Environmental Protection Agency, Region III, 1650 Arch Street, Philadelphia, Pennsylvania 19103. Electronic comments should be sent either to 
                        <E T="03">kramer.robert@epa.gov</E>
                         or to 
                        <PRTPAGE P="67949"/>
                        <E T="03">http://www.regulations.gov,</E>
                         which is an alternative method for submitting electronic comments to EPA. To submit comments, please follow the detailed instructions described in Part III of the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section. Copies of the documents relevant to this action are available for public inspection during normal business hours at the Air Protection Division, U.S. Environmental Protection Agency, Region III, 1650 Arch Street, Philadelphia, Pennsylvania 19103; and at the Delaware Department of Natural Resources and Environmental Control, 156 South State Street, Dover, Delaware 19901. 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Larry Budney, (215) 814-2184, or by e-mail at 
                        <E T="03">budney.larry@epa.gov</E>
                        . 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background </HD>
                <HD SOURCE="HD2">A. Delaware's SIP-Approved Attainment Demonstration and Mobile Budget </HD>
                <P>On October 29, 2001 ( 66 FR 54598), EPA approved Delaware's 1-hour ozone attainment demonstration plan for the Philadelphia area. As part of that final rule, EPA required that Delaware revise the plan to recalculate the 2005 attainment year motor vehicle emission budgets (MVEBs) for the Delaware portion of the Philadelphia area (Kent and New Castle Counties). The 2005 MVEBs were to be updated using MOBILE6, the most recent version of MOBILE, EPA's mobile emission factor model. On September 2, 2003, Delaware formally submitted a revision to its attainment demonstration plan for the Philadelphia area, consisting of updated MOBILE6-based MVEBs for the Delaware portion of the Philadelphia area. </P>
                <HD SOURCE="HD2">B. Background on the MOBILE Emission Factor Model and Related EPA Policy </HD>
                <P>
                    MOBILE is an EPA emission factor model for estimating pollution from on-road motor vehicles. The MOBILE model calculates emissions of volatile organic compounds (VOCs), nitrogen oxides (NO
                    <E T="52">X</E>
                    ) and carbon monoxide (CO) from passenger cars, motorcycles, buses, and light-duty and heavy-duty trucks. The model accounts for the emission impacts of factors such as changes in vehicle emission standards, changes in vehicle populations and activity, and variation in local conditions such as temperature, humidity, fuel quality, and air quality programs. The MOBILE model, first developed in 1978, has been updated several times to reflect changes to motor vehicles and fuel composition, to incorporate better understanding of vehicle emissions, and to reflect new emissions programs. The MOBILE model is used to calculate current and future inventories of motor vehicle emissions at the national and local level. These inventories are used to make decisions about air pollution policy and programs at the local, state and national level. Mobile source emission inventories based on MOBILE are used to meet the Federal Clean Air Act's requirements for SIPs and transportation conformity. EPA announced the release of the MOBILE6 version of the MOBILE model on January 29, 2002 (67 FR 4254) as a replacement for a MOBILE5 version of the model. In November of 1999, EPA issued two memoranda 
                    <SU>1</SU>
                    <FTREF/>
                     to articulate its policy regarding states that incorporated MOBILE5-based interim Tier 2 standard 
                    <SU>2</SU>
                    <FTREF/>
                     benefits into their attainment demonstration plans and those plans' associated MVEBs. EPA has implemented this policy in all ozone nonattainment areas where a state assumed Federal Tier 2 benefits in its attainment demonstration plans according to EPA's April 2000 MOBILE5 guidance, “MOBILE5 Information Sheet #8: Tier 2 Benefits Using MOBILE5.” States whose approved attainment demonstrations or maintenance plans include interim MOBILE5-based estimates of the Tier 2 standards were required to update and resubmit the MVEBs of those plans after the final release of MOBILE6. EPA's October 29, 2001 (66 FR 54598) approval of Delaware's 1-hour ozone attainment demonstration plan for the Philadelphia area was based upon interim mobile emission budgets, with projected reductions from Tier 2 motor vehicle standards estimated using the MOBILE5 model. EPA's October 29, 2001 approval of Delaware's 1-hour ozone attainment demonstration for the Philadelphia area required a MOBILE6-based motor vehicle emission budget SIP revision. 
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         Memoranda, “Guidance on Motor Vehicle Emissions Budgets in 1-Hour Ozone Attainment Demonstrations,” issued November 3, 1999, and “1-Hour Ozone Attainment Demonstrations and Tier2/Sulfur Rulemaking,” issued November 8, 1999. Copies of these memoranda can be found on EPA's Web site at 
                        <E T="03">http://www.epa.gov/otaq/transp/traqconf.htm</E>
                        .
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         The final rule on Tier 2 Motor Vehicle Emissions Standards and Gasoline Sulfur Control Requirements (“Tier 2 standards”) for passenger cars, light trucks, and larger passenger vehicles was published on February 10, 2000 (65 FR 6698).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">II. Summary of Delaware's SIP Revision and EPA's Review </HD>
                <HD SOURCE="HD2">A. MOBILE6-Based Highway Mobile Source Emission Inventories </HD>
                <P>
                    On September 2, 2003, the Delaware Department of Natural Resources and Environmental Control (DNREC) submitted an SIP revision to its approved attainment plan for the Philadelphia area. The revision consists of updated inventories of emissions calculated using the MOBILE6 emission factor model of the ozone precursors VOC and NO
                    <E T="52">X</E>
                     from highway mobile sources operating in the Delaware portion (Kent and New Castle Counties) of the Philadelphia area. These inventories were generated for summertime periods in 1990, and for 2005, the year the Philadelphia area is to attain the 1-hour ozone standard. The MOBILE6-based highway emission inventory projections for VOCs and NO
                    <E T="52">X</E>
                     for 2005 also serve as the attainment plan's MVEBs for transportation conformity planning. 
                </P>
                <P>
                    The SIP revision is intended to demonstrate that the updated MOBILE6-based projections of motor vehicle emissions continue to support the demonstration of attainment of the 1-hour ozone NAAQS for the Philadelphia area by 2005. Table 1 is presented to compare Delaware's revised MOBILE6-based motor vehicle emissions inventories with the previously approved MOBILE5-based inventories, by pollutant, expressed in units of tons per summer day (tpd). The MOBILE6-based inventories were developed using the latest available planning assumptions, including 2002 data from Delaware's Department of Transportation for vehicle registration, vehicle miles traveled (VMT) and speeds. 
                    <PRTPAGE P="67950"/>
                </P>
                <GPOTABLE COLS="7" OPTS="L2,i1" CDEF="s50,8.2,8.2,8.2,8.2,8.2,8.2">
                    <TTITLE>Table 1.—Comparison of the MOBILE5 and MOBILE6-Based Highway Mobile Emissions for the Delaware Portion of the Philadelphia-Wilmington-Trenton 1-Hour Ozone Attainment Plan </TTITLE>
                    <BOXHD>
                        <CHED H="1"/>
                        <CHED H="1">Kent County </CHED>
                        <CHED H="2">VOC </CHED>
                        <CHED H="2">
                            NO
                            <E T="52">X</E>
                        </CHED>
                        <CHED H="1">New Castle County </CHED>
                        <CHED H="2">VOC </CHED>
                        <CHED H="2">
                            NO
                            <E T="52">X</E>
                        </CHED>
                        <CHED H="1">Two-county totals </CHED>
                        <CHED H="2">VOC </CHED>
                        <CHED H="2">
                            NO
                            <E T="52">X</E>
                        </CHED>
                        <CHED H="2">VOC </CHED>
                        <CHED H="2">
                            NO
                            <E T="52">X</E>
                        </CHED>
                    </BOXHD>
                    <ROW EXPSTB="06" RUL="s">
                        <ENT I="21">
                            <E T="02">MOBILE6-Based Estimates (tpd)</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">1990 Base Year </ENT>
                        <ENT>11.84 </ENT>
                        <ENT>9.24 </ENT>
                        <ENT>42.16 </ENT>
                        <ENT>31.03 </ENT>
                        <ENT>54.00 </ENT>
                        <ENT>40.27 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">2005 Attainment Year </ENT>
                        <ENT>5.14 </ENT>
                        <ENT>8.42 </ENT>
                        <ENT>15.08 </ENT>
                        <ENT>21.28 </ENT>
                        <ENT>20.22 </ENT>
                        <ENT>29.70 </ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">Percent Reduction </ENT>
                        <ENT>56.6 </ENT>
                        <ENT>8.9 </ENT>
                        <ENT>64.2 </ENT>
                        <ENT>31.4 </ENT>
                        <ENT>62.6 </ENT>
                        <ENT>26.2 </ENT>
                    </ROW>
                    <ROW EXPSTB="06" RUL="s">
                        <ENT I="21">
                            <E T="02">MOBILE5-Based Estimates (tpd)</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="01">1990 Base Year </ENT>
                        <ENT>12.89 </ENT>
                        <ENT>10.62 </ENT>
                        <ENT>34.07 </ENT>
                        <ENT>27.04 </ENT>
                        <ENT>46.96 </ENT>
                        <ENT>37.66 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">2005 Attainment Year </ENT>
                        <ENT>4.84 </ENT>
                        <ENT>7.90 </ENT>
                        <ENT>14.76 </ENT>
                        <ENT>22.92 </ENT>
                        <ENT>19.60 </ENT>
                        <ENT>30.83 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Percent Reduction </ENT>
                        <ENT>62.5 </ENT>
                        <ENT>25.6 </ENT>
                        <ENT>56.7 </ENT>
                        <ENT>15.2 </ENT>
                        <ENT>58.3 </ENT>
                        <ENT>18.1 </ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    EPA's articulated its policy regarding the use of MOBILE6 modeling for purposes of SIP development in guidance documents entitled “Policy Guidance on the Use of MOBILE6 for SIP Development and Transportation Conformity” 
                    <SU>3</SU>
                    <FTREF/>
                     and “Clarification of Policy Guidance for MOBILE6 in Mid-course Review Areas.” 
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         Memorandum, “Policy Guidance on the Use of MOBILE6 for SIP development and Transportation Conformity,” issued January 18, 2002. A copy of this memorandum can be found on EPA's Web site at 
                        <E T="03">http://www.epa.gov/otaq/transp/traqconf.htm</E>
                        .
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         Memorandum, “Clarification of Policy Guidance for MOBILE6 SIPs in Mid-course Review Areas,” issued February 12, 2003. A copy of this memorandum can be found on EPA's Web site at 
                        <E T="03">http://www.epa.gov/otaq/transp/traqconf.htm</E>
                        .
                    </P>
                </FTNT>
                <P>
                    Delaware's September 2, 2003 SIP revision submittal includes an explanation of the differences between the MOBILE5 and MOBILE6-based inventories. The submittal also provides a comparison of the relative reduction, by percentage, between the 1990 and 2005 inventories generated using the two different versions of the model to ensure that the approved Philadelphia area 1-hour ozone attainment demonstration will continue to demonstrate attainment by 2005. The methodology for this relative reduction comparison consists of comparing the revised MOBILE6 baseline and attainment case inventories, by pollutant, with the previously approved MOBILE5 inventory totals for the Delaware portion of Philadelphia area to determine if attainment can still be predicted by the attainment date. Delaware then compared these relative reduction percentages for the MOBILE5 versus MOBILE6 inventories for 1990 and 2005. As indicated in Table 1, the State's relative reduction comparison for the two-county Delaware portion of the Philadelphia area shows that the reductions in NO
                    <E T="52">X</E>
                     and VOC emissions, on a percentage basis, are greater in the revised MOBILE 6-based inventories than in the previously approved MOBILE5-based inventories. It should be noted that because the latest available planning assumptions (
                    <E T="03">e.g.</E>
                    , 2002 data for vehicle registration, vehicle miles traveled (VMT) and speeds) were also used in the revised MOBILE6-based modeling, this relative reduction comparison is not a strict comparison of the differences resulting solely from the use of the MOBILE6 versus MOBILE5 version of the MOBILE model. 
                </P>
                <P>
                    EPA's relevant policy guidance also requires Delaware to consider whether growth and control strategy assumptions for other sources (
                    <E T="03">i.e,</E>
                     point, area, and non-road mobile sources) were still accurate at the time of the revised MOBILE6-based MVEBs were developed for submittal as a SIP revision to the Philadelphia area attainment plan. Delaware's September 2, 2003 SIP submittal indicates that the overall emissions of VOC and/or NO
                    <E T="52">X</E>
                     in the 1996 and 1999 periodic emissions inventories are below the rate-of-progress emission targets for those two milestone years, and concludes that the assumptions for growth and control strategies continue to be valid for the Delaware portion of the Philadelphia area. EPA finds that Delaware's September 2, 2003 SIP revision satisfies the conditions outlined in EPA's MOBILE6 policy guidance, and demonstrates that the new levels of motor vehicle emissions calculated using MOBILE6 continue to support achievement of the projected attainment of the 1-hour ozone standard by the attainment date of 2005 for the Delaware portion of the Philadelphia area. 
                </P>
                <HD SOURCE="HD2">B. MOBILE6-Based Motor Vehicle Emission Budgets (MVEBs) </HD>
                <P>
                    As previously stated, the on-road components of VOC and NO
                    <E T="52">X</E>
                     emissions of the 2005 attainment plan emission inventories are the 2005 MVEBs for the Philadelphia area. Those MVEBs for the Delaware portion of the Philadelphia area are summarized in Table 2. As indicated in Delaware's September 2, 2003 submittal, these budgets were developed using the latest planning assumptions, including 2002 vehicle registration, speed and vehicle miles traveled (VMT) data. Because Delaware's September 2, 2003 submittal satisfies the conditions outlined in EPA's MOBILE6 policy guidance and demonstrates that the new levels of motor vehicle emissions calculated using MOBILE6 continue to support achievement of the projected attainment of the 1-hour ozone standard, EPA is approving these MVEBs. 
                </P>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s50,12,12,12,12">
                    <TTITLE>Table 2.—MOBILE6-Based Motor Vehicle Emission Budgets (MVEBs) for the Delaware Portion of the 1-Hour Attainment Demonstration Plan for the Philadelphia-Wilmington-Trenton Area </TTITLE>
                    <BOXHD>
                        <CHED H="1">2005 Attainment year </CHED>
                        <CHED H="1">Kent County </CHED>
                        <CHED H="2">VOC </CHED>
                        <CHED H="2">
                            NO
                            <E T="52">X</E>
                        </CHED>
                        <CHED H="1">New Castle County </CHED>
                        <CHED H="2">VOC </CHED>
                        <CHED H="2">
                            NO
                            <E T="52">X</E>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Emission Budgets (tpd) </ENT>
                        <ENT>5.14 </ENT>
                        <ENT>8.42 </ENT>
                        <ENT>15.08 </ENT>
                        <ENT>21.28 </ENT>
                    </ROW>
                </GPOTABLE>
                <PRTPAGE P="67951"/>
                <HD SOURCE="HD1">III. Final Action </HD>
                <P>
                    EPA is approving Delaware's September 2, 2003 SIP revision submittal which updates the 1990 and 2005 highway mobile VOC and NO
                    <E T="52">X</E>
                     emissions inventories and the 2005 MVEBs of the Philadelphia area attainment plan to reflect the use of MOBILE6. This SIP revision fulfills the requirement of EPA's October 29, 2001 ( 66 FR 54598) approval of Delaware's 1-hour attainment demonstration plan for the Philadelphia area that the 2005 highway mobile emissions inventory and, therefore, the 2005 MVEBs of the plan be updated after the release of MOBILE6. EPA is publishing this rule without prior proposal because the Agency views this as a noncontroversial amendment and anticipates no adverse comment. However, in the “Proposed Rules” section of today's 
                    <E T="04">Federal Register</E>
                    , EPA is also publishing a separate document that will serve as the proposal to approve this SIP revision if adverse comments are filed. This rule will be effective on February 3, 2004 without further notice unless EPA receives adverse comment by January 5, 2004. If EPA receives adverse comment, EPA will publish a timely withdrawal of this action in the 
                    <E T="04">Federal Register</E>
                     informing the public that the rule will not take effect. EPA will address public comments in a subsequent final rule based on the proposed rule. EPA will not institute a second comment period on this action. Any parties interested in commenting must do so at this time. Please note that if EPA receives adverse comment on an amendment, paragraph, or section of this rule and if that provision may be severed from the remainder of the rule, EPA may adopt as final those provisions of the rule that are not the subject of an adverse comment. 
                </P>
                <P>You may submit comments either electronically or by mail. To ensure proper receipt by EPA, identify the appropriate rulemaking identification number (DE072-1042) in the subject line on the first page of your comment. Please ensure that your comments are submitted within the specified comment period. Comments received after the close of the comment period will be marked “late.” EPA is not required to consider these late comments. </P>
                <P>
                    1. 
                    <E T="03">Electronically.</E>
                     If you submit an electronic comment as prescribed below, EPA recommends that you include your name, mailing address, and an e-mail address or other contact information in the body of your comment. Also include this contact information on the outside of any disk or CD-ROM you submit, and in any cover letter accompanying the disk or CD-ROM. This ensures that you can be identified as the submitter of the comment and allows EPA to contact you in case EPA cannot read your comment due to technical difficulties or needs further information on the substance of your comment. EPA's policy is that EPA will not edit your comment, and any identifying or contact information provided in the body of a comment will be included as part of the comment that is placed in the official public docket. If EPA cannot read your comment due to technical difficulties and cannot contact you for clarification, EPA may not be able to consider your comment.
                </P>
                <P>
                    i. 
                    <E T="03">E-mail.</E>
                     Comments may be sent by electronic mail (e-mail) to: 
                    <E T="03">kramer.robert@epa.gov,</E>
                     attention DE072-1042. EPA's e-mail system is not an “anonymous access” system. If you send an e-mail comment directly without going through Regulations.gov, EPA's e-mail system automatically captures your e-mail address. E-mail addresses that are automatically captured by EPA's e-mail system are included as part of the comment that is placed in the official public docket. 
                </P>
                <P>
                    ii. 
                    <E T="03">Regulations.gov.</E>
                     Your use of Regulation.gov is an alternative method of submitting electronic comments to EPA. Go directly to 
                    <E T="03">http://www.regulations.gov,</E>
                     then select “Environmental Protection Agency” at the top of the page and use the “go” button. The list of current EPA actions available for comment will be listed. Please follow the online instructions for submitting comments. The system is an “anonymous access” system, which means EPA will not know your identity, e-mail address, or other contact information unless you provide it in the body of your comment. 
                </P>
                <P>
                    iii. 
                    <E T="03">Disk or CD-ROM.</E>
                     You may submit comments on a disk or CD-ROM that you mail to the mailing address identified in the 
                    <E T="02">ADDRESSES</E>
                     section of this document. These electronic submissions will be accepted in WordPerfect, Word or ASCII file format. Avoid the use of special characters and any form of encryption. 
                </P>
                <P>
                    2. 
                    <E T="03">By Mail.</E>
                     Written comments should be addressed to the EPA Regional office listed in the 
                    <E T="02">ADDRESSES</E>
                     section of this document. For public commenters, it is important to note that EPA's policy is that public comments, whether submitted electronically or in paper, will be made available for public viewing at the EPA Regional Office, as EPA receives them and without change, unless the comment contains copyrighted material, confidential business information (CBI), or other information whose disclosure is restricted by statute. When EPA identifies a comment containing copyrighted material, EPA will provide a reference to that material in the version of the comment that is placed in the official public rulemaking file. The entire printed comment, including the copyrighted material, will be available at the Regional Office for public inspection. 
                </P>
                <HD SOURCE="HD2">Submittal of CBI Comments </HD>
                <P>
                    Do not submit information that you consider to be CBI electronically to EPA. You may claim information that you submit to EPA as CBI by marking any part or all of that information as CBI (if you submit CBI on disk or CD-ROM, mark the outside of the disk or CD-ROM as CBI and then identify electronically within the disk or CD-ROM the specific information that is CBI). Information so marked will not be disclosed except in accordance with procedures set forth in 40 CFR Part 2. In addition to one complete version of the comment that includes any information claimed as CBI, a copy of the comment that does not contain the information claimed as CBI must be submitted for inclusion in the official public regional rulemaking file. If you submit the copy that does not contain CBI on disk or CD-ROM, mark the outside of the disk or CD-ROM clearly that it does not contain CBI. Information not marked as CBI will be included in the public file and available for public inspection without prior notice. If you have any questions about CBI or the procedures for claiming CBI, please consult the person identified in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section. 
                </P>
                <HD SOURCE="HD2">Considerations When Preparing Comments to EPA </HD>
                <P>You may find the following suggestions helpful for preparing your comments: </P>
                <P>1. Explain your views as clearly as possible. </P>
                <P>2. Describe any assumptions that you used. </P>
                <P>3. Provide any technical information and/or data you used that support your views. </P>
                <P>4. If you estimate potential burden or costs, explain how you arrived at your estimate. </P>
                <P>5. Provide specific examples to illustrate your concerns. </P>
                <P>6. Offer alternatives. </P>
                <P>7. Make sure to submit your comments by the comment period deadline identified. </P>
                <P>
                    8. To ensure proper receipt by EPA, identify the appropriate regional file/rulemaking identification number in the subject line on the first page of your 
                    <PRTPAGE P="67952"/>
                    response. It would also be helpful if you provided the name, date, and Federal Register citation related to your comments. 
                </P>
                <HD SOURCE="HD1">IV. Statutory and Executive Order Reviews </HD>
                <HD SOURCE="HD2">A. General Requirements </HD>
                <P>
                    Under Executive Order 12866 (58 FR 51735, October 4, 1993), this action is not a “significant regulatory action” and therefore is not subject to review by the Office of Management and Budget. For this reason, this action is also not subject to Executive Order 13211, “Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use” (66 FR 28355, May 22, 2001). This action merely approves state law as meeting federal requirements and imposes no additional requirements beyond those imposed by state law. Accordingly, the Administrator certifies that this rule will not have a significant economic impact on a substantial number of small entities under the Regulatory Flexibility Act (5 U.S.C. 601 
                    <E T="03">et seq.</E>
                    ). Because this rule approves pre-existing requirements under state law and does not impose any additional enforceable duty beyond that required by state law, it does not contain any unfunded mandate or significantly or uniquely affect small governments, as described in the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4). This rule also does not have tribal implications because it will not have a substantial direct effect on one or more Indian tribes, on the relationship between the Federal Government and Indian tribes, or on the distribution of power and responsibilities between the Federal Government and Indian tribes, as specified by Executive Order 13175 (65 FR 67249, November 9, 2000). This action also does not have federalism implications because it does not have substantial direct effects on the states, on the relationship between the national government and the states, or on the distribution of power and responsibilities among the various levels of government, as specified in Executive Order 13132 (64 FR 43255, August 10, 1999). This action merely approves a state rule implementing a federal standard, and does not alter the relationship or the distribution of power and responsibilities established in the Clean Air Act. This rule also is not subject to Executive Order 13045 “Protection of Children from Environmental Health Risks and Safety Risks” (62 FR 19885, April 23, 1997), because it is not economically significant. In reviewing SIP submissions, EPA's role is to approve state choices, provided that they meet the criteria of the Clean Air Act. In this context, in the absence of a prior existing requirement for the State to use voluntary consensus standards (VCS), EPA has no authority to disapprove a SIP submission for failure to use VCS. It would thus be inconsistent with applicable law for EPA, when it reviews a SIP submission, to use VCS in place of a SIP submission that otherwise satisfies the provisions of the Clean Air Act. Thus, the requirements of section 12(d) of the National Technology Transfer and Advancement Act of 1995 (15 U.S.C. 272 note) do not apply. This rule does not impose an information collection burden under the provisions of the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ).
                </P>
                <HD SOURCE="HD2">B. Submission to Congress and the Comptroller General </HD>
                <P>
                    The Congressional Review Act, 5 U.S.C. 801 
                    <E T="03">et seq.</E>
                    , as added by the Small Business Regulatory Enforcement Fairness Act of 1996, generally provides that before a rule may take effect, the agency promulgating the rule must submit a rule report, which includes a copy of the rule, to each House of the Congress and to the Comptroller General of the United States. EPA will submit a report containing this rule and other required information to the U.S. Senate, the U.S. House of Representatives, and the Comptroller General of the United States prior to publication of the rule in the 
                    <E T="04">Federal Register</E>
                    . This rule is not a “major rule” as defined by 5 U.S.C. 804(2). 
                </P>
                <HD SOURCE="HD2">C. Petitions for Judicial Review </HD>
                <P>Under section 307(b)(1) of the Clean Air Act, petitions for judicial review of this action must be filed in the United States Court of Appeals for the appropriate circuit by February 3, 2004. Filing a petition for reconsideration by the Administrator of this final rule does not affect the finality of this rule for the purposes of judicial review nor does it extend the time within which a petition for judicial review may be filed, and shall not postpone the effectiveness of such rule or action. </P>
                <P>
                    This action approving Delaware's updates to the 1990 and 2005 highway mobile VOC and NO
                    <E T="52">X</E>
                     emissions inventories and the 2005 MVEBs of its 1-hour ozone attainment demonstration plan for the Philadelphia area to reflect the use of MOBILE6 may not be challenged later in proceedings to enforce its requirements. (See section 307(b)(2).) 
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 40 CFR Part 52 </HD>
                    <P>Environmental protection, Air pollution control, Nitrogen dioxide, Ozone, Reporting and recordkeeping requirements, Volatile organic compounds.</P>
                </LSTSUB>
                <SIG>
                    <DATED>Dated: November 20, 2003. </DATED>
                    <NAME>Thomas Voltaggio, </NAME>
                    <TITLE>Acting Regional Administrator, Region III. </TITLE>
                </SIG>
                <REGTEXT TITLE="40" PART="52">
                    <AMDPAR>40 CFR part 52 is amended as follows: </AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 52—[AMENDED] </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 52 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>
                            42 U.S.C. 7401 
                            <E T="03">et seq.</E>
                        </P>
                    </AUTH>
                </REGTEXT>
                  
                <REGTEXT TITLE="40" PART="52">
                    <SUBPART>
                        <HD SOURCE="HED">Subpart I—Delaware </HD>
                    </SUBPART>
                    <AMDPAR>2. Section 52.426 is amended by: </AMDPAR>
                    <AMDPAR>a. Removing and reserving paragraph (c)(2); </AMDPAR>
                    <AMDPAR>b. Revising paragraph (d); </AMDPAR>
                    <AMDPAR>c. Adding paragraph (e). </AMDPAR>
                    <P>The revision and addition read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 52.426 </SECTNO>
                        <SUBJECT>Control strategy plans for attainment and rate-of-progress: ozone. </SUBJECT>
                        <STARS/>
                        <P>(c) * * * </P>
                        <P>(2) [Reserved] </P>
                        <STARS/>
                        <P>(d) EPA is approving the following mobile budgets, explicitly quantified as sub-budgets for each of Kent and New Castle Counties, of the Post 1996 ROP Plans and the 1-Hour Ozone Attainment Demonstration Plan: </P>
                        <GPOTABLE COLS="7" OPTS="L2,i1" CDEF="s50,8,8,8,8,8,r50">
                            <TTITLE>Transportation Conformity Emission Budgets for the Delaware Portion of the Philadelphia Area </TTITLE>
                            <BOXHD>
                                <CHED H="1">Type of control strategy SIP </CHED>
                                <CHED H="1">Year </CHED>
                                <CHED H="1">Kent County </CHED>
                                <CHED H="2">VOC </CHED>
                                <CHED H="2">
                                    NO
                                    <E T="52">X</E>
                                </CHED>
                                <CHED H="1">New Castle County </CHED>
                                <CHED H="2">VOC </CHED>
                                <CHED H="2">
                                    NO
                                    <E T="52">X</E>
                                </CHED>
                                <CHED H="1">
                                    Effective date of adequacy
                                    <LI>determination or SIP approval </LI>
                                </CHED>
                            </BOXHD>
                            <ROW>
                                <ENT I="01">Post-1996 ROP Plan </ENT>
                                <ENT>1999 </ENT>
                                <ENT>7.55 </ENT>
                                <ENT>11.17 </ENT>
                                <ENT>22.49 </ENT>
                                <ENT>29.41 </ENT>
                                <ENT>April 29, 1999, (64 FR 31217, published June 10, 1999). </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Post-1996 ROP Plan</ENT>
                                <ENT>2002 </ENT>
                                <ENT>6.30 </ENT>
                                <ENT>9.81 </ENT>
                                <ENT>18.44 </ENT>
                                <ENT>27.29 </ENT>
                                <ENT>June 23, 2000, (65 FR 36440, published June 8, 2000). </ENT>
                            </ROW>
                            <ROW>
                                <PRTPAGE P="67953"/>
                                <ENT I="01">Post-1996 ROP Plan </ENT>
                                <ENT>2005 </ENT>
                                <ENT>4.84 </ENT>
                                <ENT>7.90 </ENT>
                                <ENT>14.76 </ENT>
                                <ENT>22.92 </ENT>
                                <ENT>May 2, 2001, (66 FR 19769, published April 17, 2001). </ENT>
                            </ROW>
                            <ROW>
                                <ENT I="01">Attainment Demonstration </ENT>
                                <ENT>2005 </ENT>
                                <ENT>5.14 </ENT>
                                <ENT>8.42 </ENT>
                                <ENT>15.08 </ENT>
                                <ENT>21.28 </ENT>
                                <ENT>SIP approval on December 5, 2003; Effective on February 3, 2004. </ENT>
                            </ROW>
                        </GPOTABLE>
                        <P>(1)(2) [Reserved] </P>
                        <P>
                            (e) EPA approves Delaware's revised 2005 VOC and NO
                            <E T="52">X</E>
                             motor vehicle emission budgets for the 1-hour ozone attainment plan for the Delaware portion of the Philadelphia-Wilmington-Trenton severe ozone nonattainment area as a SIP revision. The revisions were submitted by the Delaware Department of Natural Resources and Environmental Control on September 2, 2003. Submittal of these revised MOBILE6-based motor vehicle emissions budgets was a requirement of EPA's approval of the attainment demonstration under paragraph (c) of this section. 
                        </P>
                    </SECTION>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30041 Filed 12-4-03; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <CFR>40 CFR Part 63</CFR>
                <DEPDOC>[OAR-2002-0045, FRL-7594-8]</DEPDOC>
                <RIN>RIN 2060-AK53</RIN>
                <SUBJECT>National Emission Standards for Hazardous Air Pollutants for Chemical Recovery Combustion Sources at Kraft, Soda, Sulfite, and Stand-Alone Semichemical Pulp Mills</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule; technical corrections.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>On July 18, 2003, the EPA promulgated amendments to the national emission standards for hazardous air pollutants (NESHAP) for chemical recovery combustion sources at kraft, soda, sulfite, and stand-alone semichemical pulp mills. The technical corrections in this action restore provisions which were inadvertently deleted by the July 18, 2003, amendments and restore a provision which was inadvertently omitted from the January 12, 2001, final rule.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>December 5, 2003.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Docket numbers OAR-2002-0045 and A-94-67, containing supporting information used in the development of this notice, are available for public viewing at the EPA Docket Center (Air Docket), EPA West, Room B-102, 1301 Constitution Avenue, NW., Washington, DC.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Mr. Jeff Telander, Minerals and Inorganic Chemicals Group, Emission Standards Division (C504-05), Office of Air Quality Planning and Standards, U.S. EPA, Research Triangle Park, NC 27711, telephone number (919) 541-5427, facsimile number (919) 541-5600, electronic mail address 
                        <E T="03">telander.jeff@epa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    <E T="03">Docket.</E>
                     The EPA has established an official public docket for this action including both Docket ID No. OAR-2002-0045 and Docket ID No. A-94-67. The official public docket consists of the documents specifically referenced in this action, any public comments received, and other information related to this action. All items may not be listed under both docket numbers, so interested parties should inspect both docket numbers to ensure that they have received all materials relevant to the final rule. Although a part of the official docket, the public docket does not include Confidential Business Information (CBI) or other information whose disclosure is restricted by statute. The official public docket is available for public viewing at the Air Docket in the EPA Docket Center, EPA West, Room B-102, 1301 Constitution Avenue, NW., Washington, DC 20460. The EPA Docket Center Public Reading Room is open from 8:30 a.m. to 4:30 p.m., Monday through Friday, excluding legal holidays. The telephone number for the Public Reading Room is (202) 566-1744, and the telephone number for the Air Docket is (202) 566-1742.
                </P>
                <P>
                    <E T="03">Electronic Access.</E>
                     You may access this 
                    <E T="04">Federal Register</E>
                     document electronically through the EPA Internet under the 
                    <E T="04">Federal Register</E>
                     listings at 
                    <E T="03">http://www.epa.gov/fedrgstr/</E>
                    . You may also access a copy of the final rule incorporating the provisions of this 
                    <E T="04">Federal Register</E>
                     notice through the Technology Transfer Network (TTN) at 
                    <E T="03">http://www.epa.gov/ttn/atw/pulp/pulppg.html.</E>
                </P>
                <P>
                    An electronic version of the public docket is available through EPA's electronic public docket and comment system, EPA Dockets. You may use EPA Dockets at 
                    <E T="03">http://www.epa.gov.edocket/</E>
                     to view public comments, access the index listing of the contents of the official public docket, and to access those documents in the public docket that are available electronically. Although not all docket materials may be available electronically, you may still access any of the publicly available docket materials through the docket facility identified above. Once in the system, select search, then key in the appropriate docket identification number.
                </P>
                <P>
                    <E T="03">Background:</E>
                     On February 18, 2003, we published a direct final rule (68 FR 7706) and parallel proposal (68 FR 7735) amending the NESHAP for chemical recovery combustion sources at kraft, soda, sulfite, and stand-alone semichemical pulp mills (40 CFR part 63, subpart MM). The amendments clarified and consolidated the monitoring and testing requirements and added a site-specific alternative standard for one pulp mill. The consolidation of the monitoring and testing requirements resulted in significant text shifts within and between the monitoring and testing sections of the final rule.
                </P>
                <P>On July 18, 2003 (68 FR 42603), we published amendments to the final rule that deleted portions of subpart MM added by the direct final rule (68 FR 7706), the provisions of which were the subject of adverse comment. The amendments also made two technical corrections to inadvertent errors in rule language. The EPA indicated in that notice that if we took further action, we would do so by acting on the pending proposed rule (68 FR 7735) and would not submit that proposal to another round of public comment.</P>
                <P>
                    However, the amendments inadvertently failed to restore some of the underlying rule language from the original rule. We are restoring those provisions here. The technical 
                    <PRTPAGE P="67954"/>
                    corrections in this action restore the following provisions inadvertently deleted by the July 18, 2003, amendments:
                </P>
                <P>• Reference in § 63.864(d) to the procedures in §§ 63.6(h) and 63.8 for installing, calibrating, maintaining, and operating a continuous opacity monitoring system;</P>
                <P>• Requirement in § 63.864(e)(10) to determine and record the pressure drop across the scrubber and the scrubbing liquid flow rate at least once every successive 15-minute period;</P>
                <P>• Requirement in § 63.864(e)(11) to determine and record the operating temperature of the regenerative thermal oxidizer at least once every successive 15-minute period; and, </P>
                <P>• “Eq. 1” label for the equation in § 63.865(a)(1).</P>
                <P>The technical corrections in this action also restore the particulate matter (PM) emission limit in English units in § 63.862(b)(1) for new kraft and soda recovery furnaces, which was inadvertently omitted from the January 12, 2001, final rule. This addition to the rule text does not alter the standard. It merely expresses it in English units, to go along with the metric units already in the rule.</P>
                <P>The EPA is issuing today's technical corrections in final form because we are acting on the pending proposal on which there has been notice and opportunity for public comment. In addition, we gave actual notice of this action to the commenters to that proposed rule, alerted them to the possibility of this action, and considered their comments.</P>
                <P>Section 553(d) of 5 U.S.C. allows an agency, upon a finding of good cause, to make a rule effective immediately. Because today's technical corrections restore regulatory language which was inadvertently deleted by previous amendments, do not add any requirements necessitating additional time for compliance, and otherwise do not substantively change the requirements of the final rule, we find good cause to make the technical corrections effective immediately.</P>
                <HD SOURCE="HD1">Statutory and Executive Order Review</HD>
                <P>
                    Under Executive Order 12866 (58 FR 51736, October 4, 1993), this action is not a “significant regulatory action” and is, therefore, not subject to review by the Office of Management and Budget. Because EPA has made a “good cause” finding that this action is not subject to notice and comment requirements under the Administrative Procedure Act or any other statute, it is not subject to the regulatory flexibility provisions of the Regulatory Flexibility Act (5 U.S.C. 601 
                    <E T="03">et seq.</E>
                    ), or to sections 202 and 205 of the Unfunded Mandates Reform Act of 1995 (UMRA) (Public Law 104-4). In addition, this action does not significantly or uniquely affect small governments or impose a significant intergovernmental mandate, as described in sections 203 and 204 of the UMRA. This action also does not significantly or uniquely affect the communities of tribal governments, as specified by Executive Order 13084 (63 FR 27655, May 10, 1998). This action will not have substantial direct effects on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government, as specified in Executive Order 13132 (64 FR 43255, August 10, 1999). This action also is not subject to Executive Order 13045 (62 FR 19885, April 23, 1997) because it is not economically significant.
                </P>
                <P>Section 12(d) of the National Technology Transfer and Advancement Act (NTTAA) of 1995 (Public Law 104-113; 15 U.S.C. 272 note) directs EPA to use voluntary consensus standards in its regulatory and procurement activities unless to do so would be inconsistent with applicable law or otherwise impractical. The EPA is not proposing/adopting any voluntary consensus standards in this action.</P>
                <P>
                    This action does not involve special consideration of environmental justice related issues as required by Executive Order 12898 (59 FR 7629, February 16, 1994). In issuing these technical corrections, EPA has taken the necessary steps to eliminate drafting errors and ambiguity, minimize potential litigation, and provide a clear legal standard for affected conduct, as required by section 3 of Executive Order 12988 (61 FR 4729, February 7, 1996). The EPA has complied with Executive Order 12630 (53 FR 8859, March 15, 1988) by examining the takings implications of these technical corrections in accordance with the “Attorney General's Supplemental Guidelines for the Evaluation of Risk and Avoidance of Unanticipated Takings” issued under the executive order. These technical corrections do not impose an information collection burden under the provisions of the Paperwork Reduction Act of 1995 (44 U.S.C. 3501 
                    <E T="03">et seq.</E>
                    ).
                </P>
                <P>
                    The Congressional Review Act (5 U.S.C. 801 
                    <E T="03">et seq.</E>
                    ), as added by the Small Business Regulatory Enforcement Fairness Act of 1996, generally provides that, before a rule may take effect, the agency promulgating the rule must submit a rule report, which includes a copy of the rule, to each House of the Congress and to the Comptroller General of the United States. Section 808 allows the issuing agency to make a rule effective sooner than otherwise provided by the Congressional Review Act if the agency makes a good cause finding that notice and public procedure is impracticable, unnecessary, or contrary to the public interest. This determination must be supported by a brief statement (5 U.S.C. 808(2)). As stated previously, EPA has made such a good cause finding, including the reasons therefor, and established an effective date of December 5, 2003. The EPA will submit a report containing the rule and other required information to the U.S. Senate, the U.S. House of Representatives, and the Comptroller General of the United States prior to publication of the rule in the 
                    <E T="04">Federal Register</E>
                    . This action is not a “major rule” as defined by 5 U.S.C. 804(2).
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 40 CFR Part 63</HD>
                    <P>Environmental protection, Administrative practice and procedure, Air pollution control, Hazardous substances, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <SIG>
                    <DATED>Dated: November 10, 2003.</DATED>
                    <NAME>Robert Brenner,</NAME>
                    <TITLE>Acting Assistant Administrator for Air and Radiation.</TITLE>
                </SIG>
                <REGTEXT TITLE="40" PART="63">
                    <AMDPAR>For the reasons set out in the preamble, title 40, chapter I, part 63 of the Code of Federal Regulations is amended as follows:</AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 63—[AMENDED]</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 63 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>
                            42 U.S.C. 7401 
                            <E T="03">et seq.</E>
                        </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="40" PART="63">
                    <SUBPART>
                        <HD SOURCE="HED">Subpart MM—National Emission Standards for Hazardous Air Pollutants for Chemical Recovery Combustion Sources at Kraft, Soda, Sulfite, and Stand-Alone Semichemical Pulp Mills</HD>
                    </SUBPART>
                    <AMDPAR>2. Section 63.862 is amended by revising paragraph (b)(1) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 63.862 </SECTNO>
                        <SUBJECT>Standards.</SUBJECT>
                        <STARS/>
                        <P>
                            (b) 
                            <E T="03">Standards for HAP metals: new sources.</E>
                             (1) The owner or operator of any new kraft or soda recovery furnace must ensure that the concentration of PM in the exhaust gases discharged to the atmosphere is less than or equal to 0.034 g/dscm (0.015 gr/dscf) corrected to 8 percent oxygen.
                        </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="40" PART="63">
                    <AMDPAR>
                        3. Section 63.864 is amended by: 
                        <PRTPAGE P="67955"/>
                    </AMDPAR>
                    <AMDPAR>a. Revising paragraph (d) introductory paragraph; </AMDPAR>
                    <AMDPAR>b. Revising paragraph (e)(10)introductory text; and</AMDPAR>
                    <AMDPAR>c. Revising paragraph (e)(11).</AMDPAR>
                    <P>The revisions read as follows:</P>
                    <SECTION>
                        <SECTNO>§ 63.864 </SECTNO>
                        <SUBJECT>Monitoring requirements.</SUBJECT>
                        <STARS/>
                        <P>
                            (d) 
                            <E T="03">Continuous opacity monitoring system (COMS).</E>
                             The owner or operator of each affected kraft or soda recovery furnace or lime kiln equipped with an ESP must install, calibrate, maintain, and operate a COMS according to the provisions in §§ 63.6(h) and 63.8 and paragraphs (d)(1) through (4) of this section.
                        </P>
                        <STARS/>
                        <P>(e) * * *</P>
                        <P>(10) The owner or operator of each affected kraft or soda recovery furnace, kraft or soda lime kiln, sulfite combustion unit, or kraft or soda smelt dissolving tank equipped with a wet scrubber must install, calibrate, maintain, and operate a CPMS that can be used to determine and record the pressure drop across the scrubber and the scrubbing liquid flow rate at least once every successive 15-minute period using the procedures in § 63.8(c), as well as the procedures in paragraphs (e)(10)(i) and (ii) of this section:</P>
                        <STARS/>
                        <P>(11) The owner or operator of each affected semichemical combustion unit equipped with an RTO must install, calibrate, maintain, and operate a CPMS that can be used to determine and record the operating temperature of the RTO at least once every successive 15-minute period using the procedures in § 63.8(c). The monitor must compute and record the operating temperature at the point of incineration of effluent gases that are emitted using a temperature monitor accurate to within ±1 percent of the temperature being measured.</P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="40" PART="63">
                    <AMDPAR>4. Section 63.865 is amended by revising paragraph (a)(1) to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 63.865 </SECTNO>
                        <SUBJECT>Performance test requirements and test methods.</SUBJECT>
                        <STARS/>
                        <P>(a) * * *</P>
                        <P>(1) Determine the overall PM emission limit for the chemical recovery system at the mill using Equation 1 of this section as follows:</P>
                        <MATH SPAN="3" DEEP="36">
                            <MID>ER05DE03.004</MID>
                        </MATH>
                        <FP SOURCE="FP-2">Where:</FP>
                        <FP SOURCE="FP-2">
                            EL
                            <E T="52">PM</E>
                             = overall PM emission limit for all existing process units in the chemical recovery system at the kraft or soda pulp mill, kg/Mg (lb/ton) of black liquor solids fired.
                        </FP>
                        <FP SOURCE="FP-2">
                            C
                            <E T="52">ref, RF</E>
                             = reference concentration of 0.10 g/dscm (0.044 gr/dscf) corrected to 8 percent oxygen for existing kraft or soda recovery furnaces.
                        </FP>
                        <FP SOURCE="FP-2">
                            Q
                            <E T="52">RFtot</E>
                             = sum of the average volumetric gas flow rates measured during the performance test and corrected to 8 percent oxygen for all existing recovery furnaces in the chemical recovery system at the kraft or soda pulp mill, dry standard cubic meters per minute (dscm/min) (dry standard cubic feet per minute (dscf/min)).
                        </FP>
                        <FP SOURCE="FP-2">
                            C
                            <E T="52">ref,LK</E>
                             = reference concentration of 0.15 g/dscm (0.064 gr/dscf) corrected to 10 percent oxygen for existing kraft or soda lime kilns.
                        </FP>
                        <FP SOURCE="FP-2">
                            Q
                            <E T="52">LKtot</E>
                             = sum of the average volumetric gas flow rates measured during the performance test and corrected to 10 percent oxygen for all existing lime kilns in the chemical recovery system at the kraft or soda pulp mill, dscm/min (dscf/min).
                        </FP>
                        <FP SOURCE="FP-2">F1 = conversion factor, 1.44 minutes·kilogram/day·gram (min·kg/d·g) (0.206 minutes·pound/day·grain (min·b/d·gr)).</FP>
                        <FP SOURCE="FP-2">
                            BLS
                            <E T="52">tot</E>
                             = sum of the average black liquor solids firing rates of all existing recovery furnaces in the chemical recovery system at the kraft or soda pulp mill measured during the performance test, megagrams per day (Mg/d) (tons per day (ton/d)) of black liquor solids fired.
                        </FP>
                        <FP SOURCE="FP-2">
                            ER1
                            <E T="52">ref, SDT</E>
                             = reference emission rate of 0.10 kg/Mg (0.20 lb/ton) of black liquor solids fired for existing kraft or soda smelt dissolving tanks.
                        </FP>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30265 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>Centers for Medicare &amp; Medicaid Services </SUBAGY>
                <CFR>42 CFR Parts 412, 413, 476, and 484 </CFR>
                <DEPDOC>[CMS-3055-F] </DEPDOC>
                <RIN>RIN 0938-AK68 </RIN>
                <SUBJECT>Medicare Program; Photocopying Reimbursement Methodology </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Medicare &amp; Medicaid Services (CMS), HHS. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This final rule increases the rate of reimbursement for expenses incurred by prospective payment system (PPS) hospitals for photocopying medical records requested by Quality Improvement Organizations (QIOs), formerly known as Utilization and Quality Control Peer Review Organizations (PROs). We are increasing the rate from 7 cents per page to 12 cents per page to reflect inflationary changes in the labor and supply cost components of the formula. </P>
                    <P>This final rule also provides for the periodic review and adjustment of the per-page reimbursement rate to account for inflation and changes in technology. The methodology for calculating the per-page reimbursement rate will remain unchanged. </P>
                    <P>We are also providing for the payment of the expenses of furnishing photocopies to QIOs, to other providers subject to a PPS (for example, skilled nursing facilities and home health agencies), in accordance with the rules established for reimbursing PPS hospitals for these expenses. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>These regulations are effective on January 5, 2004. </P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Les Caplan, (410) 786-7223. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background </HD>
                <P>
                    Section 1866(a)(1)(F) of the Social Security Act (the Act) requires a hospital, as a condition of Medicare participation, to enter into an agreement with a quality improvement organization (QIO), for the peer review of Medicare services provided by the hospital. (
                    <E T="04">Note:</E>
                     QIOs were formerly known as peer review organizations (PROs). We published a final rule with comment period on May 24, 2002 (67 FR 36539), changing the name to QIOs.) Our regulations at 42 CFR 476.78 provide that health care facilities that 
                    <PRTPAGE P="67956"/>
                    submit Medicare claims must cooperate in the conduct of QIO reviews, including providing the QIO with information necessary to its determinations. This often includes providing the QIO with photocopies of patients' medical records. 
                </P>
                <P>
                    We published a final rule on October 20, 1992, in the 
                    <E T="04">Federal Register</E>
                     (57 FR 47779), following notice-and-comment rulemaking, which established a formula for calculating the rate of reimbursement for these photocopy costs incurred by hospitals. Using this formula, we set the rate at 7 cents per page. The regulation requires us to determine a fixed payment amount per page by adding per-page labor costs and per-page supply costs. The regulation also provides for Medicare payment for the costs of first class postage for mailing records to QIOs. As discussed in detail in the October 20, 1992, final rule (57 FR 47779), the payment established by § 476.78 represents an additional payment to hospitals under the prospective payment system (PPS) for photocopy costs. Payment for the equipment and overhead costs associated with furnishing the QIO with required documentation is made under other Medicare payment provisions for capital-related costs and inpatient operating costs. 
                </P>
                <P>The formula for calculating the per-page reimbursement rate for photocopies is set forth at § 476.78(c), which provides: </P>
                <P>
                    <E T="03">Photocopying reimbursement methodology for prospective payment system hospitals.</E>
                     Hospitals subject to the prospective payment system are paid for the photocopying costs that are directly attributable to the hospitals' responsibility to the QIOs to provide photocopies of requested hospital records. The payment is in addition to payment already provided for these costs under other provisions of the Social Security Act and is based on a fixed amount per page as determined by CMS as follows: 
                </P>
                <P>
                    (1) 
                    <E T="03">Step one.</E>
                     CMS adds the annual salary of a photocopy machine operator and the costs of fringe benefits as determined in accordance with the principles set forth in OMB circular A-76. 
                </P>
                <P>
                    (2) 
                    <E T="03">Step two.</E>
                     CMS divides the amount determined in paragraph (c)(1) of this section by the number of pages that can be reasonably expected to be made annually by the photocopy machine operator to establish the labor cost per page. 
                </P>
                <P>(3) CMS adds to the per-page labor cost determined in paragraph (c)(2) of this section the per-page costs of supplies. </P>
                <P>
                    Using this formula we established the per-page rate of 7 cents in the October 20, 1992, final rule. The validity of this rule and its reimbursement methodology were challenged in a certified class action by Medicare—participating hospitals, in the U.S. Court of Appeals for the Ninth Circuit. 
                    <E T="03">Queen of Angels/Hollywood Presbyterian Medical Center</E>
                     v. 
                    <E T="03">Shalala,</E>
                     65 F.3d 1472, 1476 (9th Cir. 1995). The Court of Appeals upheld the validity of our photocopy reimbursement methodology and sustained the lawfulness of the 7 cents per page rate established in the rule. 
                </P>
                <P>Due to increases in labor and supply costs, we are increasing the reimbursement rate from 7 cents per page to 12 cents per page in accordance with the established court-approved methodology set forth in § 476.78(c). </P>
                <HD SOURCE="HD2">Current Photocopy Reimbursement Rate </HD>
                <P>Under the current regulation, we apply a uniform per-page rate on a nationwide basis to all PPS hospitals that have QIO agreements. We base the calculation on labor and supply costs. The calculation in the current rule, as discussed in the preamble to the October 20, 1992, rule, is based on the following: </P>
                <P>• An operator will copy approximately 364,320 pages annually. </P>
                <P>• The salary level of an operator is equivalent to a GS-5 experienced midlevel secretary ($17,686) plus 27.9 percent fringe benefits ($4,934) for a total salary of $22,620. </P>
                <P>• Paper costs are 0.5 cents per page ($25 per case of paper with 5,000 sheets in a case). </P>
                <P>• Toner and developer costs are 0.5 cents per page.</P>
                <FP>The total cost per page is 7 cents. </FP>
                <HD SOURCE="HD1">II. Provisions of the Proposed Regulations </HD>
                <P>On November 22, 2002, we published a proposed rule (67 FR 70358) in which we proposed to increase the rate of QIO-related photocopy reimbursement from 7 cents to 12 cents per page. We calculated this rate by updating the salary, fringe benefits, and supply figures used in the October 20, 1992, final rule. In accordance with the methodology at § 476.78(c), we considered the following factors in calculating the proposed rate: (1) The labor costs associated with photocopying and (2) the costs of supplies. </P>
                <HD SOURCE="HD2">A. Labor Costs </HD>
                <P>Labor costs were calculated consistent with the methodology at § 476.78(c), first, by adding the annual salary of a photocopy machine operator with the costs of fringe benefits, and second, by dividing that sum by the number of pages that can reasonably be expected to be made in a year. </P>
                <HD SOURCE="HD2">B. Annual Salary of a Photocopy Machine Operator </HD>
                <P>In the October 20, 1992, rule, we adopted the salary level for an experienced (GS-5) midlevel secretary in the Federal government as representative of that of a photocopy machine operator. Use of this figure approximated or exceeded the actual salary information for individuals performing these tasks that had been submitted by various commenters. Furthermore, we determined that use of this salary level yielded payments that were more than adequate to ensure a sufficient skill level. The annual salary of $17,686 used in the October 20, 1992, rule was derived from the U.S. Office of Personnel Management's 1992 General Schedule. </P>
                <P>In this final rule, we will continue to deem the salary of a Federal GS-5 midlevel secretary as representative of a photocopy operator's salary; however, we will update the figure to take into account increases in the payment rate of a midlevel secretary. Thus, as discussed in the proposed rule, we are using the GS-5 annual salary of $28,727 derived from the U.S. Office of Personnel Management's 2002 General Schedule to calculate the revised rate. </P>
                <HD SOURCE="HD2">C. Fringe Benefits </HD>
                <P>
                    In the October 20, 1992, final rule, we ascribed the fringe benefits of an employee to be 27.9 percent of the employee's salary, which was the standard percentage dictated by the cost principles set forth in the Office of Management and Budget (OMB) Circular A-76. While there may be other yardsticks to measure this component of costs, we find this to be a reasonable resource since the thrust of this OMB circular is to help the government compare potentially incurred costs to determine whether the costs can be more economically incurred internally or through contract with a commercial source. Therefore, we continue to use OMB Circular A-76 to calculate the annual fringe benefit cost. Accordingly, fringe benefits were calculated in the November 22, 2002, proposed rule based on 29.7 percent of the GS-5 salary as outlined in the OMB Circular A-76 Transmittal Memorandum 19—FY 2000 estimate. Thus, the annual fringe benefit cost is $8,532 ($28,727 * 29.7 percent). 
                    <PRTPAGE P="67957"/>
                </P>
                <HD SOURCE="HD2">D. Number of Pages Copied Annually </HD>
                <P>In this final rule, we are using 364,320 pages per year in the calculation of the annual labor cost. In the October 20, 1992, rule, we determined that 364,320 was the number of pages that could reasonably be expected to be copied in a year. Earlier, in the proposed rule “Changes to Peer Review Organizations Regulations”, published on March 16, 1988, at 53 FR 8654, we had proposed the use of 748,000 pages per year in the calculation of the annual labor cost. This initial figure was determined based on copying documents at a rate of six pages per minute for each hour in an 8 hour day, 5 days a week, 52 weeks per year. The estimate was based on hand feeding of documents into the photocopying machine for duplication, although we recognized that there are many photocopying tasks that may be accomplished through automatic feeds. Automatic feeds greatly increase the number of pages that can be generated by a machine on an hourly basis, and as a result, greatly decrease the cost of photocopying per page. </P>
                <P>In response to comments received on the March 16, 1988, proposed rule (53 FR 8654), we revised the 748,000 figure in the October 20, 1992, final rule to account for time spent by the photocopy machine operator in search and retrieval tasks, and time away from work on annual vacation, sick, and holiday leave. This resulted in a reduction from 748,000 to 364,320 in our estimate of the number of pages that may be reasonably expected to be made annually, and a corresponding increase in the per-page labor rate. </P>
                <P>We are unaware of any significant changes in technology since the October 20, 1992, final rule (57 FR 47779) that would lead to either a significant decrease or increase in the annual number of pages that may be copied. Nor are we aware of any changes that would significantly increase or decrease the time allocated to search and retrieval tasks. Therefore, we continue to use the 364,320 figure to calculate the per-page labor cost. </P>
                <HD SOURCE="HD2">E. Calculation of Per-Page Labor Costs </HD>
                <P>To determine the per-page labor cost, the total of salary ($28,727) and fringe benefits ($8,532) costs, which amount to $37,259, was divided by 364,320 pages, the number of copies made in a year, resulting in an annual labor cost per page of 10 cents ($37,259/364,320 pages). </P>
                <HD SOURCE="HD2">F. Supply Costs </HD>
                <P>In the proposed rule, we proposed a total supply cost of 2.3 cents per page. This is based on a per-page paper cost of 0.5 cents and a developer and toner cartridge cost of 1.8 cents per page. The paper costs were calculated based on $23 per case of paper with 5,000 sheets in a case. This equates to 0.5 cents per page ($23/5,000). </P>
                <P>In this rule, we used an objective methodology to calculate the per-page cost for toner and developer that can also be used in future updates. We calculated these costs using estimates of the costs for toner cartridges and developer drums contained in the General Services Administration (GSA) supply catalogue, and on the basis of a photocopy machine producing 364,320 pages annually. </P>
                <HD SOURCE="HD2">G. Payment Rate Per Page </HD>
                <P>Consistent with § 476.78(c)(3), the payment rate per page is the total of the per-page labor cost and the per-page supply cost, which is equivalent to 12 cents. The established calculation methodology actually results in a cost of 12.3 cents per page, however, consistent with our policy and generally accepted mathematics principles, we chose to round down to 12 cents. We believe this decision is both reasonable and supportable, based on the fact that the higher amount substantially exceeds all published OMB inflation indexes, including the Consumer Price Index (CPI)-Wage index (photocopying expense is largely comprised of labor costs). </P>
                <HD SOURCE="HD2">H. Future Updates to Rate of Photocopy Reimbursement </HD>
                <P>In addition to updating the rate of reimbursement for photocopies, we are also amending the existing regulation to permit the rate to be adjusted without undergoing notice-and-comment rulemaking each time it needs to be adjusted to reflect inflationary or technology changes. </P>
                <P>We intend to review and adjust the rate periodically in accordance with the same factors considered in establishing the rate in the October 20, 1992, final rule and the updated rate in this final rule. This review will include an examination of the labor and supply components of the formula, and we will update the rate as necessary to account for significant inflationary changes to these components. </P>
                <P>Absent some compelling reason, in future updates, we will continue to deem the salary and fringe benefits of a Federal government GS-5 midlevel secretary as representative of the salary and fringe benefits of a photocopy machine operator and use those values to calculate the reimbursement rate. Also, absent some compelling reason or major technological change that would lead to a significant increase or decrease in the number of pages that can be made annually, we will not change the number of pages used in calculating the rate. </P>
                <HD SOURCE="HD2">I. Reimbursement to Other PPS Providers of the Cost of Photocopying </HD>
                <P>We will provide for the payment of the expenses of furnishing photocopies to QIOs, to other providers subject to a PPS (for example, skilled nursing facilities (SNFs) and home health agencies (HHAs)), in accordance with the rules established at § 476.78 for reimbursing PPS hospitals for these expenses. </P>
                <P>Current regulations do not address reimbursement for providers other than hospitals for costs of photocopying medical records in cooperation with QIO review activities because in the past QIO review of providers other than hospitals was relatively insignificant. To the extent that this review activity took place, it was minimal, and the related costs were included on the provider's cost report. SNFs, HHAs, and other providers have recently converted from the cost-based reimbursement system to a PPS. Because QIO review of these providers has been minimal or nonexistent, costs related to this activity are not adequately reflected in the base PPS rate. Therefore, we believe it is appropriate to provide for a means of paying for these costs when they occur. To accomplish this change, we will replace the more narrow term “hospitals” with “providers,” in § 476.78(b)(2) and (c), to include other providers subject to a PPS. </P>
                <P>Additionally, we will revise the payment provisions for SNFs and HHAs by adding a paragraph at § 413.355 and § 484.265, that authorizes reimbursement for the costs of photocopying and mailing medical records required for QIO review, to SNFs and HHAs. </P>
                <P>We will amend § 476.78(d) to provide that, as with other disputes regarding Medicare payment to providers, disputes concerning payments for costs related to QIO review under § 476.78 and the other payment provisions of the Medicare statute and regulations must be presented in accordance with the administrative and judicial review requirements of section 1878 of the Act and subpart R of 42 CFR part 405. </P>
                <HD SOURCE="HD1">III. Analysis of and Responses to Public Comments </HD>
                <P>
                    We received three timely items of correspondence in response to the proposed rule published on November 22, 2002. A summary of the major issues 
                    <PRTPAGE P="67958"/>
                    raised in those comments and our responses follow: 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     One QIO commented that the November 22, 2002, proposed rule would increase pass-through photocopy costs well beyond the amount budgeted in their seventh round Medicare contract. This increase could cause the QIO to exceed the total cost of its contract. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     Increased photocopying costs are included in the seventh round scope of work funding level. However, these costs are a true pass-through; that is, CMS is responsible for paying providers, and CMS uses its QIO contractors as the vehicle to pay them. Although CMS does not anticipate increasing the total cost of each QIO contract immediately upon publication of this rule, any time a QIO believes it will exceed the total cost of its contract, the QIO should immediately notify CMS (see “Limitation of Cost” clause in the seventh round contract). If the excess costs are the result of increased photocopying reimbursement, CMS will exercise one of the four options CMS always uses in similar cases—we will either request that money be added to the contract, reduce work, ask the QIO to move funds between cost centers or line items, or some combination of these options. In no case will CMS expect the QIO to absorb any excess pass-through with existing contract funds without a corresponding reduction or shifting in level of effort. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     One hospital commented that the method for calculating labor costs described in section II.A of the preamble of the November 22, 2002, proposed rule only provides for the cost of a photocopy machine operator, while in actual practice a significant portion of records reproduction time should be attributed to record retrieval, review, and re-filing by a records technician. The hospital further stated its pay scale for a records technician ranges from $8.30 to $11.22 per hour. 
                </P>
                <P>
                    <E T="03">Response:</E>
                     We agree with this comment. However, in section II.D of the preamble of the November 22, 2002, proposed rule, we explained how we calculated the estimated number of pages copied annually. As discussed in detail at 57 FR 47780, this estimate was adjusted before publication of the current regulation to take into account the appropriate amount of labor time required to perform all of the steps that are performed in addition to the actual photocopying, such as logging in the request, retrieving the record, refiling the record, and mailing copies. Thus, the term “photocopy machine operator” can reasonably be interpreted to include records technicians or anyone else directly involved in the hands-on process. Further, section II.B of the preamble of the November 22, 2002, proposed rule explains that we used an updated representative annual salary of $28,727, or an hourly rate of $13.81, which exceeds this provider's salary range for a records technician. Therefore, we have not increased the per-page reimbursement rate based on this comment. 
                </P>
                <P>
                    <E T="03">Comment:</E>
                     Another commenter questioned the raw data we applied to the approved methodology for calculating the per-page cost of photocopying medical records. Although this commenter strongly supported the three primary objectives of the rule (to increase reimbursement, extend provisions of the rule to all PPS providers, and allow for periodic adjustment of rates without notice and comment rulemaking), the commenter contended the rate should be significantly higher than the proposed 12 cents per page. 
                </P>
                <P>In particular, this organization stated the proposed labor rate is insufficient to retain qualified personnel in the private sector, fringe benefit rates are too low, the number of pages copied annually is too high due to recent Health Insurance Portability and Accountability Act of 1996 (HIPAA) requirements, and the cost of supplies is too low as a result of comparing GSA bulk purchase costs to actual costs available to private sector companies. The commenter believes we used the October 20, 1992, regulation as a starting point for current calculations and that regulation was based on artificially low cost assumptions. </P>
                <P>The commenter supports extending the proposed reimbursement methodology to non-hospital PPS providers and also supported the periodic review provisions. However, the commenter asked us to amend the rate review section to require such a review at no more than 5-year intervals. </P>
                <P>
                    <E T="03">Response:</E>
                     In this rule, we used recent cost data to calculate the proposed per-page photocopy costs and did not simply build on 1992 data. However, we believe that the data used in both this rule and the 1992 rule is reasonable and accurately reflects the costs associated with this responsibility. Further, we believe the proposed representative salary and fringe benefit rates of $28,727 and 29.7 percent, respectively, are reasonable and sufficient to attract and retain qualified personnel. The fringe benefit (F/B) rate, in particular, is very close to the mean F/B rate of the numerous contractors we reviewed before publication of the November 22, 2002, proposed rule, to validate the A-76 Transmittal Memorandum. Although the 29.7 percent F/B rate is based on the 2000 OMB guidance, we have applied it to a higher base figure and see no reason to adjust it further. The $28,727 salary estimate represents a mid-level GS-5 secretary salary in 2002, which we believe is a fair and accurate comparison to the skill level necessary to process medical record photocopying requests. 
                </P>
                <P>The estimated number of pages has remained constant since the October 20, 1992, regulation was published. Although the commenter may be correct that HIPAA privacy requirements will modestly reduce the maximum number of pages an operator or technician can copy per year, it is still too soon to calculate the exact effect of that legislation. Further, we believe that increases in the speed and simplicity of reproduction hardware over the last 10 years may offset any decreases in volume resulting from HIPAA. </P>
                <P>The comment that the cost of supplies to non-governmental organizations exceeds the GSA catalogue price may be valid. However, the GSA price provides a solid benchmark that does not vary widely by vendor or product quality. Further, our proposed overall reimbursement rate per page amounts to a 7 percent annual increase over the 10 years since publication of the previous rule. This is approximately twice the inflation index rate and adequately compensates for any modest differences between the government and private-sector costs of supplies. </P>
                <P>We believe the suggestion to include a maximum 5-year interval between review periods has some merit but may be unnecessary. By eliminating the need for notice and comment rulemaking, it becomes unlikely that any future rate adjustment will take longer than 5 years and potentially could be more frequent. </P>
                <HD SOURCE="HD1">IV. Provisions of the Final Regulations </HD>
                <P>This final rule incorporates the provisions of the proposed rule with only one minor change. We have deleted the proposed revision of § 476.78(b)(4), thus leaving that section unchanged from the existing text. The proposed amendment, replacing “hospital” with “provider,” had an unintended consequence of appearing to extend the requirement to provide QIOs with discharge notices from hospitals to other inpatient providers. That is neither the purpose nor the intent of this final rule. </P>
                <HD SOURCE="HD1">V. Collection of Information Requirements </HD>
                <P>
                    Under the Paperwork Reduction Act (PRA) of 1995, agencies are required to provide 60-day notice in the 
                    <E T="04">
                        Federal 
                        <PRTPAGE P="67959"/>
                        Register
                    </E>
                     and solicit public comment before a collection of information requirement is submitted to the Office of Management and Budget (OMB) for review and approval. In order to fairly evaluate whether an information collection should be approved, section 3506(c)(2)(A) of the PRA of 1995 requires that we solicit comment on the following issues: 
                </P>
                <P>• Whether the information collection is necessary and useful to carry out the proper functions of the agency; </P>
                <P>• The accuracy of the agency's estimate of the information collection burden; </P>
                <P>• The quality, utility, and clarity of the information to be collected; and </P>
                <P>• Recommendations to minimize the information collection burden on the affected public, including automated collection techniques. </P>
                <P>Section 476.78 of this regulation contains information collection requirements. In summary, § 476.78 requires providers to submit information to the QIO during the conduct of a QIO review. Because this information is collected during the conduct of an audit, investigation, and/or an administrative action, we believe these collection requirements are not subject to the PRA as stipulated under 5 CFR 1320.4. </P>
                <HD SOURCE="HD1">VI. Regulatory Impact </HD>
                <P>We have examined the impacts of this rule as required by Executive Order 12866 (September 1993, Regulatory Planning and Review), the Regulatory Flexibility Act (RFA) (September 16, 1980, Pub. L. 96-354), section 1102(b) of the Social Security Act, the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4), and Executive Order 13132. </P>
                <P>Executive Order 12866 (as amended by Executive Order 13258, which merely reassigns responsibility of duties) directs agencies to assess all costs and benefits of available regulatory alternatives and when regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety effects, distributive impacts, and equity). A regulatory impact analysis (RIA) must be prepared for rules that constitute significant regulatory action, including rules that have an economic effect of $100 million or more annually. This final rule is not a major rule in terms of the aggregate costs involved. </P>
                <P>The 53 separate QIO contracts are awarded on a staggered 3-year basis. Current sixth scope of work contracts provide photocopy reimbursement costs of 7 cents per page. The total dollars budgeted were $8.6 million per year and the 3-year costs were $25.9 million. We estimate by the time this final regulation is published, 19 QIOs will have completed their sixth round contracts, and the other 34 will have less than 153 months (combined) out of a total of 636 months (for all 53 QIOs) remaining in the final year of their sixth round contracts. This translates to 24 percent of the final sixth round year. As such, we project this regulation will increase the costs in the last (that is, current) year of the sixth scope of work by $1.5 million above the previous budgeted level of $8.6 million, to a total of $10.1 million. However, in future years—based on the full 12 months and all 53 QIOs under contract—the increase will be nearly $6.2 million annually. </P>
                <P>Thus, we have determined that this final rule is not a major rule with economically significant effects because it will not result in increases in total expenditures of $100 million or more per year. </P>
                <P>The RFA requires agencies to analyze options for regulatory relief of small businesses. For purposes of the RFA, small entities include small businesses, nonprofit organizations, and small governmental jurisdictions. Most hospitals and most other providers and suppliers are small entities, either by nonprofit status or by having revenues of $6 million to $29 million or less annually (see 65 FR 69432). Individuals and States are not included in the definition of a small entity. </P>
                <P>We generally prepare a regulatory flexibility analysis that is consistent with the RFA unless we certify that a rule will not have a significant impact on a substantial number of small entities. We have not prepared an analysis for the RFA because we have determined, and certify, that this final rule will have no significant economic impact on small entities. The regulation will not impose any economic or operational regulatory burdens on small entities. The regulation will only assist providers in performing the tasks required under the QIO program sixth scope of work, by increasing the reimbursement for providing copies of documents to the QIOs. </P>
                <P>Section 1102(b) of the Act requires us to prepare a regulatory impact analysis if a rule may have a significant impact on the operations of a substantial number of small rural hospitals. This analysis must conform to the provisions of section 604 of the RFA. For purposes of section 1102(b) of the Act, we define a small rural hospital as a hospital that is located outside of a Metropolitan Statistical Area and has fewer than 100 beds. We have not prepared an analysis for section 1102(b) of the Act because we have determined that this final regulation will not have a significant impact on the operations of small rural hospitals for the reasons stated above in our discussion of the RFA. </P>
                <P>Section 202 of the Unfunded Mandates Reform Act of 1995 also requires that agencies prepare an assessment of anticipated costs and benefits before issuing any rule that may result in an expenditure in any 1 year by State, local, or tribal governments, in the aggregate, or by the private sector, of $110 million or more. We have determined that this final rule will not result in such an expenditure. Rather, the final rule will benefit providers by increasing the photocopy reimbursement rate. </P>
                <P>Executive Order 13132 establishes certain requirements that an agency must meet when it promulgates a rule that imposes substantial direct compliance costs on State and local governments, preempts State law, or otherwise has Federalism implications. We have reviewed this final rule under the threshold criteria of Executive Order 13132 and have determined that it will not have a substantial direct effect on the rights, roles, and responsibilities of States or local governments. </P>
                <P>In accordance with the provisions of Executive Order 12866, this regulation was reviewed by the Office of Management and Budget. </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects </HD>
                    <CFR>42 CFR Part 412 </CFR>
                    <P>Administrative practice and procedure, Health facilities, Medicare, Puerto Rico, Reporting and recordkeeping requirements. </P>
                    <CFR>42 CFR Part 413 </CFR>
                    <P>Health facilities, Kidney diseases, Medicare, Puerto Rico, Reporting and recordkeeping requirements. </P>
                    <CFR>42 CFR Part 476 </CFR>
                    <P>Grant programs-health, Health care, Health facilities, Health professions, Quality Improvement Organizations (QIO), Reporting and record keeping requirements. </P>
                    <CFR>42 CFR Part 484 </CFR>
                    <P>Health facilities, Health professions, Medicare, Reporting and recordkeeping requirements. </P>
                </LSTSUB>
                <REGTEXT TITLE="42" PART="412">
                    <AMDPAR>For the reasons set forth in the preamble, the Centers for Medicare &amp; Medicaid Services is amending 42 CFR chapter IV as follows: </AMDPAR>
                    <PART>
                        <PRTPAGE P="67960"/>
                        <HD SOURCE="HED">PART 412—PROSPECTIVE PAYMENT SYSTEMS FOR INPATIENT HOSPITAL SERVICES </HD>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart H—Payment to Hospitals Under the Prospective Payment Systems </HD>
                        </SUBPART>
                    </PART>
                    <AMDPAR>1. The authority citation for part 412 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>Secs. 1102 and 1871 of the Social Security Act (42 U.S.C. 1302 and 1395hh). </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="42" PART="412">
                    <AMDPAR>2. In § 412.115, revise paragraph (c) to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 412.115 </SECTNO>
                        <SUBJECT>Additional payments. </SUBJECT>
                        <STARS/>
                        <P>
                            (c) 
                            <E T="03">QIO photocopy and mailing costs.</E>
                             An additional payment is made to a hospital in accordance with § 476.78 of this chapter for the costs of photocopying and mailing medical records requested by a QIO. 
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="42" PART="413">
                    <PART>
                        <HD SOURCE="HED">PART 413—PRINCIPLES OF REASONABLE COST REIMBURSEMENT; PAYMENT FOR END-STAGE RENAL DISEASE SERVICES; PROSPECTIVELY DETERMINED PAYMENT RATES FOR SKILLED NURSING FACILITIES </HD>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart J—Prospective Payment for Skilled Nursing Facilities </HD>
                        </SUBPART>
                    </PART>
                    <AMDPAR>1. The authority citation for part 413 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>Secs. 1102, 1812(d), 1814(b), 1815, 1833(a), (i), and (n), 1871, 1881, 1883, and 1886 of the Social Security Act (42 U.S.C. 1302, 1395d(d), 1395f(b), 1395l(a), (i), and (n), 1395hh, 1395rr, 1395tt, and 1395ww). </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="42" PART="413">
                    <AMDPAR>2. Add a new § 413.355 to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 413.355 </SECTNO>
                        <SUBJECT>Additional payment: QIO photocopy and mailing costs. </SUBJECT>
                        <P>An additional payment is made to a skilled nursing facility in accordance with § 476.78 of this chapter for the costs of photocopying and mailing medical records requested by a QIO. </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="42" PART="476">
                    <PART>
                        <HD SOURCE="HED">PART 476—UTILIZATION AND QUALITY CONTROL REVIEW </HD>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart C—Review Responsibilities of Quality Improvement Organizations (QIOs) </HD>
                            <HD SOURCE="HD1">General Provisions </HD>
                        </SUBPART>
                    </PART>
                    <AMDPAR>1. The authority citation for part 476 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>Secs. 1102 and 1871 of the Social Security Act (42 U.S.C. 1302 and 1395hh). </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="42" PART="476">
                    <AMDPAR>2. In § 476.78, revise the introductory text to paragraph (b); revise paragraphs (b)(2), and the introductory text to paragraph (c); add new paragraph (c)(4); and revise paragraph (d) to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 476.78 </SECTNO>
                        <SUBJECT>Responsibilities of health care providers. </SUBJECT>
                        <STARS/>
                        <P>
                            (b) 
                            <E T="03">Cooperation with QIOs.</E>
                             Health care providers that submit Medicare claims must cooperate in the assumption and conduct of QIO review. Providers must— 
                        </P>
                        <STARS/>
                        <P>(2) Provide patient care data and other pertinent data to the QIO at the time the QIO is collecting review information that is required for the QIO to make its determinations. The provider must photocopy and deliver to the QIO all required information within 30 days of a request. QIOs pay providers paid under the prospective payment system for the costs of photocopying records requested by the QIO in accordance with the payment rate determined under the methodology described in paragraph (c) of this section and for first class postage for mailing the records to the QIO. When the QIO does postadmission, preprocedure review, the facility must provide the necessary information before the procedure is performed, unless it must be performed on an emergency basis. </P>
                        <STARS/>
                        <P>
                            (c) 
                            <E T="03">Photocopying reimbursement methodology for prospective payment system providers.</E>
                             Providers subject to the prospective payment system are paid for the photocopying costs that are directly attributable to the providers' responsibility to the QIOs to provide photocopies of requested provider records. The payment is in addition to payment already provided for these costs under other provisions of the Social Security Act and is based on a fixed amount per page as determined by CMS as follows: 
                        </P>
                        <STARS/>
                        <P>
                            (4) CMS will periodically review the photocopy reimbursement rate to ensure that it still accurately reflects provider costs. CMS will publish any changes to the rate in a 
                            <E T="04">Federal Register</E>
                             notice. 
                        </P>
                        <P>
                            (d) 
                            <E T="03">Appeals.</E>
                             Reimbursement for the costs of photocopying and mailing records for QIO review is an additional payment to providers under the prospective payment system, as specified in § 412.115, § 413.355, and § 484.265 of this chapter. Thus, appeals concerning these costs are subject to the review process specified in part 405, subpart R of this chapter. 
                        </P>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="42" PART="484">
                    <PART>
                        <HD SOURCE="HED">PART 484—HOME HEALTH SERVICES </HD>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart E—Prospective Payment System for Home Health Agencies </HD>
                        </SUBPART>
                    </PART>
                    <AMDPAR>1. The authority citation for part 484 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>Secs. 1102 and 1871 of the Social Security Act (42 U.S.C. 1302 and 1395(hh) unless otherwise indicated. </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="42" PART="484">
                    <AMDPAR>2. Add a new § 484.265 to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 484.265 </SECTNO>
                        <SUBJECT>Additional payment. </SUBJECT>
                        <P>
                            <E T="03">QIO photocopy and mailing costs.</E>
                             An additional payment is made to a home health agency in accordance with § 476.78 of this chapter for the costs of photocopying and mailing medical records requested by a QIO. 
                        </P>
                    </SECTION>
                </REGTEXT>
                <SIG>
                    <FP>(Catalog of Federal Domestic Assistance Program No. 93.773, Medicare—Hospital Insurance; and Program No. 93.774, Medicare—Supplementary Medical Insurance Program) </FP>
                    <DATED>Dated: May 23, 2003. </DATED>
                    <NAME>Thomas A. Scully, </NAME>
                    <TITLE>Administrator, Center for Medicare &amp; Medicaid Services. </TITLE>
                    <APPR>Approved: August 28, 2003. </APPR>
                    <NAME>Tommy G. Thompson, </NAME>
                    <TITLE>Secretary. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30096 Filed 11-28-03; 11:32 am] </FRDOC>
            <BILCOD>BILLING CODE 4120-01-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES </AGENCY>
                <SUBAGY>Centers for Medicare &amp; Medicaid Services </SUBAGY>
                <CFR>42 CFR Part 414 </CFR>
                <DEPDOC>[CMS-1232-FC] </DEPDOC>
                <RIN>RIN 0938-AM44 </RIN>
                <SUBJECT>Medicare Program; Coverage and Payment of Ambulance Services; Inflation Update for CY 2004 </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Centers for Medicare &amp; Medicaid Services (CMS), HHS. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule with comment period. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This final rule provides the sunset date for the interim bonus payment for rural ambulance mileage of 18 through 50 miles as required by the Medicare, Medicaid and State Child Health Insurance Program Benefits Improvement and Protection Act of 2000 (BIPA) and provides notice of the annual Ambulance Inflation Factor (AIF) for ambulance services for calendar year (CY) 2004. The statute requires that this inflation factor be 
                        <PRTPAGE P="67961"/>
                        applied in determining the fee schedule amounts and payment limits for ambulance services. 
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        <E T="03">Effective date:</E>
                         These revisions are effective on January 1, 2004. The ambulance inflation factor for 2004 applies to ambulance services furnished during the period January 1, 2004, through December 31, 2004. 
                    </P>
                    <P>
                        <E T="03">Comment date:</E>
                         Comments will be considered if we receive them at the appropriate address, as provided below, no later than 5 p.m. on January 29, 2004. 
                    </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Mail written comments (one original and three copies) to the following address: Centers for Medicare &amp; Medicaid Services, Department of Health and Human Services, Attention: CMS-1232-FC, P.O. Box 8013, Baltimore, MD 21244-8013.</P>
                    <P>If you prefer, you may deliver your written comments (one original and three copies) to one of the following addresses: Hubert H. Humphrey Building, Room 443-G, 200 Independence Avenue, SW., Washington, DC 20201, or  Centers for Medicare &amp; Medicaid Services, Room C5-14-03, 7500 Security Boulevard, Baltimore, MD 21244-8013.</P>
                    <P>Comments mailed to those addresses designated for courier delivery may be delayed and could be considered late. Because of staffing and resource limitations, we cannot accept comments by facsimile (FAX) transmission. Please refer to file code CMS-1232-FC on each comment. Comments received timely will be available for public inspection as they are received, generally beginning approximately 3 weeks after publication of this document, in Room C5-12-08 of the Centers for Medicare &amp; Medicaid Services, 7500 Security Boulevard, Baltimore, Maryland, Monday through Friday of each week from 8:30 a.m. to 4 p.m. Please call (410) 786-7197 to make an appointment to view comments. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Anne E. Tayloe, (410) 786-4546. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Background </HD>
                <HD SOURCE="HD2">A. Legislative and Regulatory History </HD>
                <P>Under section 1861(s)(7) of the Social Security Act (the Act), Medicare Part B (Supplementary Medical Insurance) covers and pays for ambulance services, to the extent prescribed in regulations, when the use of other methods of transportation would be contraindicated. The House Ways and Means Committee and Senate Finance Committee Reports that accompanied the 1965 legislation creating the Social Security Act suggest that the Congress intended that (1) the ambulance benefit cover transportation services only if other means of transportation are contraindicated by the beneficiary's medical condition, and (2) only ambulance service to local facilities be covered unless necessary services are not available locally, in which case, transportation to the nearest facility furnishing those services is covered (H.R. Rep. No. 213, 89th Cong., 1st Sess. 37 and S. Rep. No. 404, 89th Cong., 1st Sess., Pt I, 43 (1965)). The reports indicate that transportation may also be provided from one hospital to another, to the beneficiary's home, or to an extended care facility. </P>
                <P>Our regulations relating to ambulance services are located at 42 CFR part 410, subpart B and 42 CFR part 414, subpart H. Section 410.10(i) lists ambulance services as one of the covered medical and other health services under Medicare Part B. Ambulance services are subject to basic conditions and limitations set forth at § 410.12 and to specific conditions and limitations included at § 410.40. Part 414, subpart H describes how payment is made for ambulance services covered by Medicare. </P>
                <P>The Medicare program pays for ambulance services for Medicare beneficiaries when other means of transportation are contraindicated. Ambulance services are divided into different levels of services based on the medically necessary treatment provided during transport as well as into ground (including water) and air ambulance services. These services include the levels of service listed below. </P>
                <FP>
                    <E T="03">For ground:</E>
                </FP>
                <P>• Basic Life Support (BLS) </P>
                <P>• Advanced Life Support, Level 1 (ALS1) </P>
                <P>• Advanced Life Support, Level 2 (ALS2) </P>
                <P>• Specialty Care Transport (SCT) </P>
                <P>• Paramedic ALS Intercept (PI) </P>
                <FP>
                    <E T="03">For air:</E>
                </FP>
                <P>• Fixed Wing Air Ambulance (FW) </P>
                <P>• Rotary Wing Air Ambulance (RW) </P>
                <P>Historically, payment levels for ambulance services depended, in part, upon the entity that furnished the services. Prior to implementation of the ambulance fee schedule on April 1, 2002, providers (hospitals, including critical access hospitals, skilled nursing facilities, and home health agencies) were paid on a retrospective reasonable cost basis. Suppliers, which are entities that are independent of any provider, were paid on a reasonable charge basis. </P>
                <P>
                    On February 27, 2002, a final rule was published in the 
                    <E T="04">Federal Register</E>
                     (67 FR 9100) that established a fee schedule for the payment of ambulance services under the Medicare program, effective for services furnished on or after April 1, 2002. This rule implemented section 1834(l) of the Act. The fee schedule described in the final rule replaced the retrospective reasonable cost payment system for providers and the reasonable charge system for suppliers of ambulance services. In addition, that final rule implemented that statutory requirement that ambulance suppliers accept Medicare assignment; codified the establishment of new Health Care Common Procedure Coding System (HCPCS) codes to be reported on claims for ambulance services; established increased payment under the fee schedule for ambulance services furnished in rural areas based on the location of the beneficiary at the time the beneficiary is placed on board the ambulance; and revised the certification requirements for coverage of nonemergency ambulance services. The final rule also provided for a 5-year transition period during which program payment for Medicare covered ambulance services would be based upon a blended rate comprised of a fee schedule portion and a reasonable cost (providers) or reasonable charge (suppliers) portion. We are now in the second year of that transition over to full payment based solely on the fee schedule amount. 
                </P>
                <HD SOURCE="HD2">B. Transitional Assistance for Rural Mileage 18 through 50—Section 221 of the Medicare, Medicaid and SCHIP Benefits Improvement and Protection Act of 2000 (BIPA) </HD>
                <P>Section 221 of BIPA provided that, for services furnished during the period July 1, 2001 through, December 31, 2003, a bonus payment, not less than one-half of the bonus paid under the ambulance fee schedule for rural mileage 1 through 17 miles, would be paid for rural mileage 18 through 50. This provision was implemented by § 414.610(c) with the ambulance fee schedule. </P>
                <P>
                    The statute provided for this bonus payment only for the interim period specified. We inadvertently omitted from the regulation the time period during which this benefit is payable. Therefore, we are revising § 414.610(c) to reflect that this bonus payment applies only for services furnished during the statutory period. This revision to the regulation is a technical correction to conform the regulation to the statute. Therefore, we believe that notice and comment are unnecessary, and we are waiving proposed rulemaking. 
                    <PRTPAGE P="67962"/>
                </P>
                <HD SOURCE="HD2">C. Ambulance Inflation Factor (AIF) for CY 2004</HD>
                <P>
                    Section 1834(l)(3)(B) of the Act provides the basis for updating payment amounts for ambulance services. Our regulations at § 414.620(f) provide that the ambulance fee schedule must be updated by the AIF annually, based on the percentage increase in the consumer price index (CPI) for all urban consumers (U.S. city average) for the 12-month period ending with June of the previous year (§ 414.610(f)). The regulations also provide that notice of the AIF be published in the 
                    <E T="04">Federal Register</E>
                     without opportunity for prior notice and comment. We will follow applicable rulemaking procedures in publishing revisions to the fee schedule for ambulance services that result from any factors other than the inflation factor. In this preamble, we set forth the ambulance inflation factor applicable for services furnished in CY 2004. 
                </P>
                <HD SOURCE="HD1">II. Provisions of the Final Rule </HD>
                <HD SOURCE="HD2">A. Transitional Assistance for Rural Mileage 18 Through 50 </HD>
                <P>Section 414.610(c)(5) is amended to clarify that this benefit is no longer payable for services furnished after December 31, 2003. </P>
                <HD SOURCE="HD2">B. Ambulance Inflation Factor for 2004 </HD>
                <P>Section 1834(l)(3)(B) of the Act, specified in § 414.620(f), provides for an update in payments for CY 2004 that is equal to the percentage increase in the CPI for all urban consumers (CPI-U), for the 12-month period ending with June of the previous year (that is, June 2003). For CY 2004, that percentage is 2.1 percent. </P>
                <P>During the transition period (described in § 414.615, Transition to the ambulance fee schedule), the AIF is applied to both the fee schedule portion of the blended payment amount and to the reasonable charge/cost portion of the blended payment amount separately for each ambulance provider/supplier. Then, these two amounts are added together to determine the total payment amount for each provider/supplier. </P>
                <HD SOURCE="HD1">III. Technical Corrections </HD>
                <P>We are also making the following technical corrections to § 414.605, Definitions. </P>
                <P>
                    • In the definition of “
                    <E T="03">Advanced life support (ALS) intervention,</E>
                    ” we are clarifying that an ALS intervention must be furnished by ALS personnel. 
                </P>
                <P>
                    • A comma was inadvertently omitted in the definition of “
                    <E T="03">Advanced life support, Level 2 (ALS2).</E>
                    ” That comma is now inserted after the phrase “or by continuous infusion” and before the phrase “excluding crystalloid. * * *” 
                </P>
                <P>
                    • There was an inadvertent misuse of the term “supplier” in the definition of the term “
                    <E T="03">emergency response.</E>
                    ” The correct term is “entity.” Providers, as well as suppliers, may furnish an emergency response. We did not intend to exclude providers from receiving payment for this service. 
                </P>
                <P>
                    • In the definition of “
                    <E T="03">Rural area</E>
                    ”, we are clarifying that only New England County Metropolitan Areas (NECMAs) (and not MSAs) apply in New England. (NECMAs exist only in New England. All other areas have MSAs.) Also, the term “NECMA” was inadvertently omitted from the discussion of the Goldsmith modification. The phrase “or NECMA” is now inserted after the term “MSA” and before the phrase “that is identified as rural by the Goldsmith modification.” This clarifies that a Goldsmith modification can apply to a NECMA as well as an MSA. 
                </P>
                <P>• Section 414.610(c)(3) is revised to conform the first two sentences to reflect the fact that the process for determining payment for mileage is the same for ground and air miles. </P>
                <HD SOURCE="HD1">IV. Waiver of Proposed Rulemaking </HD>
                <P>
                    We ordinarily publish a proposed rule in the 
                    <E T="04">Federal Register</E>
                     and provide a period for public comment before we publish a final rule. We can waive this procedure, however, if we find good cause that notice and comment procedure is impracticable, unnecessary, or contrary to the public interest and we incorporate a statement of this finding and its reasons in the rule issued. We find it unnecessary to undertake notice and comment rulemaking in this instance because the statute specifies the method of computation of annual updates, and we have no discretion in this matter. Further, this rule does not change substantive policy, but merely applies the statutorily-specified update method. Therefore, under 5 U.S.C. 553(b)(B), for good cause, we waive notice and comment procedures. 
                </P>
                <P>We also find it unnecessary to undertake notice and comment rulemaking as to the technical changes because they merely provide technical corrections to the regulations and do not make any substantive changes to the regulations. Therefore, for good cause, we waive notice and comment procedures. </P>
                <HD SOURCE="HD1">V. Collection of Information Requirements </HD>
                <P>This document does not impose information collection and recordkeeping requirements. Consequently, it need not be reviewed by the Office of Management and Budget under the authority of the Paperwork Reduction Act of 1995. </P>
                <HD SOURCE="HD1">VI. Regulatory Impact Statement </HD>
                <P>We have examined the impacts of this rule as required by Executive Order 12866 (September 1993, Regulatory Planning and Review), the Regulatory Flexibility Act (RFA) (September 16, 1980, Pub. L. 96-354), section 1102(b) of the Social Security Act, the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4), and Executive Order 13132. </P>
                <P>Executive Order 12866 directs agencies to assess all costs and benefits of available regulatory alternatives and, if regulation is necessary, to select regulatory approaches that maximize net benefits (including potential economic, environmental, public health and safety effects, distributive impacts, and equity). A regulatory impact analysis (RIA) must be prepared for major rules with economically significant effects ($100 million or more in any 1 year). This final rule is not considered a major rule because it has an effect on the Medicare program of less than $100 million in any 1 year. Application of an AIF of 2.1 percent will result in an additional total program expenditure of approximately $65 million. </P>
                <P>The RFA requires agencies to analyze options for regulatory relief of small businesses. For purposes of the RFA, small entities include small businesses, nonprofit organizations, and government agencies. Most hospitals and most other providers and suppliers are small entities, either by nonprofit status or by having revenues of $6 million to $29 million in any 1 year. For purposes of the RFA, all ambulance providers/suppliers are considered to be small entities. Individuals and States are not included in the definition of a small entity. </P>
                <P>
                    HHS considers that a substantial number of entities are affected if the rule impacts more than 5 percent of the total number of small entities as it does in this rule. Although this rule impacts every ambulance provider and supplier because all ambulance payment rates are increased by the 2.1 percent ambulance inflation factor, we do not believe that this has a significant impact. We estimate the combined impact of this rule would be an approximate 2 percent increase in Medicare revenues, which, therefore, would be a somewhat less than 2 percent increase in total revenues (that is, Medicare plus non-Medicare revenues). This estimated impact does not meet the threshold established by 
                    <PRTPAGE P="67963"/>
                    HHS to be considered a significant impact. Nonetheless, we have prepared the analysis below to describe the impact of this rule. 
                </P>
                <P>In addition, section 1102(b) of the Act requires us to prepare a regulatory impact analysis if a rule may have a significant impact on the operations of a substantial number of small rural hospitals. This analysis must conform to the provisions of section 604 of the RFA. For purposes of section 1102(b) of the Act, we define a small rural hospital as a hospital that is located outside of a Metropolitan Statistical Area and has fewer than 100 beds. This rule applies to small rural hospitals that furnish at least one Medicare covered ambulance service to at least one Medicare beneficiary. </P>
                <P>Section 202 of the Unfunded Mandates Reform Act of 1995 also requires that agencies assess anticipated costs and benefits before issuing any rule that may result in expenditure in any 1 year by State, local, or tribal governments, in the aggregate, or by the private sector, of $110 million. This final rule does not result in an expenditure in any 1 year by State, local, or tribal governments of $110 million. </P>
                <P>Executive Order 13132 establishes certain requirements that an agency must meet when it publishes a proposed rule (and subsequent final rule) that imposes substantial direct requirement costs on State and local governments, preempts State law, or otherwise has Federalism implications. This rule will not have a substantial effect on State or local governments. </P>
                <P>This final rule sunsets the rural mileage bonus for rural mileage 18 through 50 as required by statute, provides an update for inflation as mandated by statute, and changes the term “supplier” to the term “entity” in the definition of an emergency service. Elimination of the bonus payment for rural mileage 18 through 50 will result in a savings to the program of $6 million in CY 2004. Therefore, this is not a major rule. </P>
                <P>We estimate that the total program expenditure for CY 2004 for ambulance services covered by the Medicare program is approximately $3 billion. Application of an AIF of 2.1 percent will result in an additional total program expenditure of approximately $65 million. </P>
                <P>Our clarification that an ALS intervention must be furnished by ALS personnel will have negligible impact because generally ALS services are required to be furnished by ALS personnel. </P>
                <P>The insertion of the comma that had been inadvertently omitted in the definition of “Advanced life support, Level 2 (ALS2)” will have no impact since it conforms the regulation to the existing implementing instructions. </P>
                <P>Changing the term “supplier” to the term “entity” in the definition of “emergency services” is not a material change because it simply conforms the regulation to actual practice as the program is currently administered. </P>
                <P>Our clarification in the definition of “Rural area” that NECMAs apply in New England and our addition of NECMA to the discussion of the Goldsmith Modification have a negligible impact because of the very few ambulance suppliers affected. Also, the statute requires that this policy be followed in updating rates by using the most recent Goldsmith modifications. </P>
                <P>Our clarification for loaded mileage has no impact because it conforms the regulation to actual practice as the program is correctly administered. </P>
                <P>In accordance with the provisions of Executive Order 12866, this regulation was reviewed by the Office of Management and Budget. </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 42 CFR Part 414 </HD>
                    <P>Administrative practice and procedure, Health facilities, Health professions, Kidney diseases, Medicare, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <P>For the reasons set forth in the preamble, the Centers for Medicare &amp; Medicaid Services is amending 42 CFR chapter IV as follows: </P>
                <REGTEXT TITLE="42" PART="414">
                    <PART>
                        <HD SOURCE="HED">PART 414—PAYMENT FOR PART B MEDICAL AND OTHER HEALTH SERVICES </HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 414 continues to read as follows: </AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>Secs. 1102, 1871, and 1881(b)(1) of the Social Security Act (42 U.S.C. 1302, 1395hh, and 1395rr(b)(1)). </P>
                    </AUTH>
                </REGTEXT>
                <REGTEXT TITLE="42" PART="414">
                    <SUBPART>
                        <HD SOURCE="HED">Subpart H—Fee Schedule for Ambulance Services </HD>
                        <SECTION>
                            <SECTNO>§ 414.605 </SECTNO>
                            <SUBJECT>[Amended] </SUBJECT>
                        </SECTION>
                    </SUBPART>
                    <AMDPAR>2. In § 414.605, the following changes are made: </AMDPAR>
                    <AMDPAR>
                        A. The definition of “
                        <E T="03">Advanced life support (ALS) intervention</E>
                        ” is revised by removing the phrase “beyond the scope of authority of an emergency medical technician-basic (EMT-Basic)” and adding in its place the phrase “required to be furnished by ALS personnel.” 
                    </AMDPAR>
                    <AMDPAR>
                        B. A comma is inserted in the definition of “
                        <E T="03">Advanced Life Support, Level 2 (ALS2)</E>
                        ” after the phrase “or by continuous infusion” and before the phrase “excluding crystalloid. * * *” 
                    </AMDPAR>
                    <AMDPAR>C. The term “supplier” in the definition of “Emergency response” is removed and the term “entity” is added in its place. </AMDPAR>
                    <AMDPAR>D. The definition of “Rural area” is revised to read as follows:</AMDPAR>
                    <SECTION>
                        <SECTNO>§ 414.605 </SECTNO>
                        <SUBJECT>Definitions. </SUBJECT>
                        <STARS/>
                        <P>Rural area means an area located outside a Metropolitan Statistical Area (MSA), or, in New England, a New England County Metropolitan Area (NECMA), or an area within an MSA or NECMA that is identified as rural by the Goldsmith modification. </P>
                        <STARS/>
                    </SECTION>
                    <AMDPAR>3. Section 414.610 is amended by revising paragraphs (c)(3) and (c)(5) to read as follows: </AMDPAR>
                    <SECTION>
                        <SECTNO>§ 414.610 </SECTNO>
                        <SUBJECT>Basis of payment. </SUBJECT>
                        <STARS/>
                        <P>(c) * * * </P>
                        <STARS/>
                        <P>(3) Loaded mileage. Payment is based on loaded miles. Payment for air mileage is based on loaded miles flown as expressed in statute miles. There are three mileage payment rates: a rate for FW services, a rate for RW services, and a rate for all levels of ground transportation. </P>
                        <STARS/>
                        <P>(5) Rural adjustment factor (RAF). For ground ambulance services where the point of pickup is in a rural area, the mileage rate is increased by 50 percent for each of the first 17 miles and, for services furnished before January 1, 2004, by 25 percent for miles 18 through 50. The standard mileage rate applies to every mile over 50 miles and, for services furnished after December 31, 2003, to every mile over 17 miles. For air ambulance services where the point of pickup is in a rural area, the total payment is increased by 50 percent; that is, the rural adjustment factor applies to the sum of the base rate and the mileage rate. </P>
                        <STARS/>
                    </SECTION>
                </REGTEXT>
                <EXTRACT>
                    <FP>(Catalog of Federal Domestic Assistance Program No. 93.774, Medicare—Supplementary Medical Insurance Program) </FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: September 2, 2003. </DATED>
                    <NAME>Thomas A. Scully, </NAME>
                    <TITLE>Administrator, Centers for Medicare &amp; Medicaid Services. </TITLE>
                    <APPR>Approved: October 27, 2003. </APPR>
                    <NAME>Tommy G. Thompson, </NAME>
                    <TITLE>Secretary. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30152 Filed 12-1-03; 12:43 pm] </FRDOC>
            <BILCOD>BILLING CODE 4120-01-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <PRTPAGE P="67964"/>
                <AGENCY TYPE="S">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                <CFR>47 CFR Part 73</CFR>
                <DEPDOC>[DA 03-3555; MB Docket No. 03-24; RM-10636]</DEPDOC>
                <SUBJECT>Radio Broadcasting Services; Apopka, Homosassa Springs, Maitland, FL </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Audio Division, at the request of Cox Radio, Inc., licensee of FM Station WPYO, Channel 237A, Apopka, Florida, deletes Apopka, Florida, Channel 237A, from the FM Table of Allotments, allots Channel 237C3 at Maitland, Florida, as the community's first local FM service, and modifies the license of FM Station WPYO to specify operation on Channel 237C3 at Maitland. Channel 237C3 can be allotted to Maitland, Florida, in compliance with the Commission's minimum distance separation requirements with a site restriction of 14.7 km (9.2 miles) east of Maitland. The coordinates for Channel 237C3 at Maitland, Florida, are 28-39-38 North Latitude and 81-13-02 West Longitude.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective January 5, 2004.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Deborah Dupont, Media Bureau, (202) 418-2180.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    This is a synopsis of the Commission's 
                    <E T="03">Report and Order,</E>
                     MB Docket No. 03-24, adopted November 12, 2003, and released November 14, 2003. The full text of this Commission decision is available for inspection and copying during normal business hours in the FCC Information Center, Portals II, 445 12th Street, SW., Room CY-A257, Washington, DC 20554. The complete text of this decision may also be purchased from the Commission's duplicating contractor, Qualex International, Portals II, 445 12th Street, SW., Room CY-B402, Washington, DC 20554, (202) 863-2893, facsimile (202) 863-2898, or via e-mail 
                    <E T="03">qualexint@aol.com.</E>
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 47 CFR Part 73</HD>
                    <P>Radio, Radio broadcasting.</P>
                </LSTSUB>
                <REGTEXT TITLE="47" PART="73">
                    <AMDPAR>Part 73 of title 47 of the Code of Federal Regulations is amended as follows:</AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 73—RADIO BROADCAST SERVICES</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 73 continues to read as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>47 U.S.C. 154, 303, 334 and 336.</P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 73.202 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                </REGTEXT>
                <REGTEXT TITLE="47" PART="73">
                    <AMDPAR>2. Section 73.202(b), the Table of FM Allotments under Florida, is amended by removing Apopka, Channel 237A, and by adding Maitland, Channel 237C3.</AMDPAR>
                </REGTEXT>
                <SIG>
                    <FP>Federal Communications Commission.</FP>
                    <NAME>John A. Karousos,</NAME>
                    <TITLE>Assistant Chief, Audio Division, Media Bureau.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30195 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL COMMUNICATIONS COMMISSION</AGENCY>
                <CFR>47 CFR Part 73</CFR>
                <DEPDOC>[DA 03-3650; MB Docket No. 02-243; RM-10533; RM-10712*]</DEPDOC>
                <SUBJECT>Radio Broadcasting Services; Marathon and Mertzon, TX </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Communications Commission.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final rule.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        In response to a 
                        <E T="03">Notice of Proposed Rule Making,</E>
                         67 FR 57779 (September 12, 2001), this 
                        <E T="03">Report and Order</E>
                         allots Channel 278C to Marathon, Texas, and provides Marathon with its first local aural transmission service. This document also allots Channel 278C2 to Mertzon, Texas and provides that community with its second local aural transmission service. The coordinates for Channel 278C at Marathon, Texas, are 30-21-56 North Latitude and 103-17-40 West Longitude. This allotment has a site restriction of 18.4 kilometers (11.5 miles) north of Marathon, Texas. The coordinates for Channel 278C2 at Mertzon, Texas, are 31-10-09 North Latitude and 100-51-41 West Longitude, with a site restriction of 10.8 kilometers (6.7 miles) southwest of Mertzon, Texas.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Effective January 8, 2004.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>R. Barthen Gorman, Media Bureau, (202) 418-2180.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    This is a synopsis of the Commission's Report and Order, MB Docket No. 02-243, adopted November 14, 2003, and released November 17, 2003. The full text of this Commission decision is available for inspection and copying during normal business hours in the FCC's Reference Information Center at Portals II, 445 12th Street, SW., Room CY-A257, Washington, DC 20554. The document may also be purchased from the Commission's duplicating contractor, Qualex International, Portals II, 445 12th Street, SW., Room CY-B402, Washington, DC 20554, telephone 202 863-2893, facsimile 202 863-2898, or via e-mail 
                    <E T="03">qualexint@aol.com.</E>
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 47 CFR Part 73</HD>
                    <P>Radio, Radio broadcasting.</P>
                </LSTSUB>
                <REGTEXT TITLE="47" PART="73">
                    <AMDPAR>Part 73 of title 47 of the Code of Federal Regulations is amended as follows:</AMDPAR>
                    <PART>
                        <HD SOURCE="HED">PART 73—RADIO BROADCAST SERVICES</HD>
                    </PART>
                    <AMDPAR>1. The authority citation for part 73 reads as follows:</AMDPAR>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>47 U.S.C. 154, 303, 334 and 336.</P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 73.202 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                    </SECTION>
                    <AMDPAR>2. Section 73.202(b), the Table of FM Allotments under Texas, is amended by adding Marathon, Channel 278C, and Channel 278C2 at Mertzon.</AMDPAR>
                </REGTEXT>
                <SIG>
                    <FP>Federal Communications Commission.</FP>
                    <NAME>John A. Karousos,</NAME>
                    <TITLE>Assistant Chief, Audio Division, Media Bureau.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30194 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6712-01-P</BILCOD>
        </RULE>
        <RULE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF COMMERCE </AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration </SUBAGY>
                <CFR>50 CFR Part 679 </CFR>
                <DEPDOC>[Docket No. 031126297-3297-01; I.D. 111703D] </DEPDOC>
                <SUBJECT>Fisheries of the Exclusive Economic Zone Off Alaska; Gulf of Alaska; Interim 2004 Harvest Specifications for Groundfish </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Interim final rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>NMFS issues interim 2004 total allowable catch (TAC) amounts for each category of groundfish, American Fisheries Act (AFA) sideboard amounts, and prohibited species catch (PSC) amounts for the groundfish fisheries of the Gulf of Alaska (GOA). The intended effect is to conserve and manage the groundfish resources in the GOA. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        The interim harvest specifications are effective from 0001 hrs, Alaska local time (A.l.t.), January 1, 2004, until the effective date of the final 2004 harvest specifications for GOA groundfish, which will be published in the 
                        <E T="04">Federal Register</E>
                        . 
                    </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Copies of the Environmental Assessment/Initial Regulatory Flexibility Analysis (EA/
                        <PRTPAGE P="67965"/>
                        IFRA) prepared for this action, the final 2002 Stock Assessment and Fishery Evaluation (SAFE) report, dated November 2002, and the final 2003 SAFE report, dated November 2003, is available from the North Pacific Fishery Management Council, 605 West 4th Avenue, Suite 306, Anchorage, AK 99501-2252, telephone (907) 271-2809 or from its homepage at 
                        <E T="03">http://www.fakr.noaa.gov/npfmc.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Thomas Pearson, (907) 481-1780 or 
                        <E T="03">tom.pearson@noaa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background </HD>
                <P>Federal regulations at 50 CFR part 679 implementing the Fishery Management Plan (FMP) for Groundfish of the GOA govern the groundfish fisheries in the GOA. The North Pacific Fishery Management Council (Council) prepared the FMP, and NMFS approved it under the authority of the Magnuson-Stevens Fishery Conservation and Management Act (Magnuson-Stevens Act). General regulations that also pertain to the U.S. fisheries appear at subpart H of 50 CFR part 600. </P>
                <P>
                    The Council met in October 2003 to review scientific information concerning groundfish stocks including the 2002 SAFE report and the EA (see 
                    <E T="02">ADDRESSES</E>
                    ) and recommended proposed 2004 specifications. The Council recommended and NMFS proposed a total acceptable biological catch (ABC) of 409,690 mt and a TAC of 227,797 mt for the 2004 fishing year. The proposed TAC amounts for each species were based on the best available biological and socioeconomic information.
                </P>
                <P>
                    Under § 679.20(c)(1)(ii), NMFS published in the 
                    <E T="04">Federal Register</E>
                     proposed harvest specifications for groundfish in the GOA for the 2004 fishing year published elsewhere in this issue. That document contains a detailed discussion of the proposed 2004 TACs, groundfish reserves, apportionments of TAC, ABC amounts, overfishing levels (OFLs), PSC amounts and apportionments, of the GOA groundfish fishery. 
                </P>
                <P>This action provides interim harvest specifications and apportionments thereof for the 2004 fishing year that will become available on January 1, 2004, and remain in effect until superseded by the final 2004 harvest specifications. Background information concerning the 2004 groundfish harvest specification process, on which this interim action is based, is provided in the above mentioned proposed specification document. </P>
                <HD SOURCE="HD1">Establishment of Interim TACs </HD>
                <P>Regulations at § 679.20(c)(2)(i) require that one-fourth of each proposed TAC and apportionment thereof (not including the reserves and the first seasonal allowance of pollock and Pacific cod) and one-fourth of the halibut PSC amounts become effective at 0001 hours, A.l.t., January 1, on an interim basis and remain in effect until superseded by the final harvest specifications. As stated in the proposed specifications publication published elsewhere in this issue, no harvest of groundfish is authorized before the effective date of this action implementing the interim specifications. </P>
                <P>Regulations at § 679.20(a)(6)(i) and (ii) allocate 100 percent of the pollock TAC to vessels catching pollock for processing by the inshore component, 90 percent of the Pacific cod TAC to vessels catching Pacific cod for processing by the inshore component and 10 percent to vessels catching Pacific cod for processing by the offshore component. </P>
                <P>The reserves for the GOA are 20 percent of the TAC amounts for pollock, Pacific cod, flatfish species, and the “other species” category (§ 679.20(b)(2)). The GOA groundfish TAC amounts have been utilized fully since 1987, and NMFS expects this trend to continue in 2004. Therefore, NMFS has proposed reapportioning all the reserves to the TAC. The interim TAC amounts contained in Table 1 reflect the reapportionment of reserves to the TAC. </P>
                <HD SOURCE="HD1">Interim 2004 GOA Groundfish Harvest Specifications and Apportionments </HD>
                <P>Table 1 provides interim TAC amounts, the first seasonal allowance of pollock in the combined Western and Central Regulatory Areas, the first seasonal allowance of Pacific cod in the Western and Central Regulatory Areas, interim TAC allocations of Pacific cod to the inshore and offshore components, and interim sablefish TAC apportionments to hook-and-line and trawl gear. These interim TAC amounts and apportionments become effective at 0001 hours, A.l.t., January 1, 2004. </P>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s50,r50,14,10">
                    <TTITLE>
                        Table 1.—Interim 2004 TAC Amounts of Groundfish for the Combined Western/Central (W/C), Western (W), Central (C), and Eastern (E) Regulatory Areas and in the West Yakutat (WYK), Southeast Outside (SEO), and Gulfwide (GW) Districts of the Gulf of Alaska (GOA) 
                        <E T="51">1,2</E>
                    </TTITLE>
                    <TDESC>[The first seasonal allowances of pollock in the Combined W/C Regulatory Areas, the first seasonal allowances of Pacific cod. Interim sablefish TAC apportionments to hook-and-line (H/L) and trawl (TRW) gear. Interim TAC amounts have been rounded to nearest metric tons] </TDESC>
                    <BOXHD>
                        <CHED H="1">Species </CHED>
                        <CHED H="1">Area </CHED>
                        <CHED H="1">Interim TAC </CHED>
                        <CHED H="1">Total </CHED>
                    </BOXHD>
                    <ROW RUL="n,n,n,s">
                        <ENT I="01">
                            Pollock 
                            <SU>3,4</SU>
                              
                        </ENT>
                        <ENT>
                            W (610)
                            <LI>C (620)</LI>
                            <LI>C (630) </LI>
                        </ENT>
                        <ENT>
                            2,894
                            <LI>6,535</LI>
                            <LI>2,274 </LI>
                        </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">Subtotal </ENT>
                        <ENT>W/C </ENT>
                        <ENT>  </ENT>
                        <ENT>11,703 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>WYK (640) </ENT>
                        <ENT>270 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,n,n,d">
                        <ENT I="22"> </ENT>
                        <ENT>SEO (650) </ENT>
                        <ENT>1,615 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total </ENT>
                        <ENT>  </ENT>
                        <ENT>  </ENT>
                        <ENT>13,588 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Pacific cod 
                            <SU>5</SU>
                              
                        </ENT>
                        <ENT>Inshore W </ENT>
                        <ENT>7,553 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>Offshore W </ENT>
                        <ENT>839 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>Inshore C </ENT>
                        <ENT>10,916 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>Offshore C </ENT>
                        <ENT>1,213 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>Inshore E </ENT>
                        <ENT>587 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,n,n,s">
                        <ENT I="22">  </ENT>
                        <ENT>Offshore E </ENT>
                        <ENT>65 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total </ENT>
                        <ENT>  </ENT>
                        <ENT>  </ENT>
                        <ENT>21,173 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Flatfish, Deep-water 
                            <SU>6</SU>
                              
                        </ENT>
                        <ENT>W </ENT>
                        <ENT>45 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>C </ENT>
                        <ENT>555 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="67966"/>
                        <ENT I="22">  </ENT>
                        <ENT>WYK </ENT>
                        <ENT>332 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,n,n,s">
                        <ENT I="22">  </ENT>
                        <ENT>SEO </ENT>
                        <ENT>288 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total </ENT>
                        <ENT>  </ENT>
                        <ENT>  </ENT>
                        <ENT>1,220 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Rex sole </ENT>
                        <ENT>W </ENT>
                        <ENT>320 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>C </ENT>
                        <ENT>1,385 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>WYK </ENT>
                        <ENT>400 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,n,n,s">
                        <ENT I="22">  </ENT>
                        <ENT>SEO </ENT>
                        <ENT>262 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total </ENT>
                        <ENT>  </ENT>
                        <ENT>  </ENT>
                        <ENT>2,367 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Flathead sole </ENT>
                        <ENT>W </ENT>
                        <ENT>500 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>C </ENT>
                        <ENT>1,250 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>WYK </ENT>
                        <ENT>659 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,n,n,s">
                        <ENT I="22">  </ENT>
                        <ENT>SEO </ENT>
                        <ENT>284 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total </ENT>
                        <ENT>  </ENT>
                        <ENT>  </ENT>
                        <ENT>2,693 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Flatfish, Shallow-water 
                            <SU>7</SU>
                              
                        </ENT>
                        <ENT>W </ENT>
                        <ENT>1,125 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>C </ENT>
                        <ENT>3,250 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>WYK </ENT>
                        <ENT>290 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,n,n,s">
                        <ENT I="22">  </ENT>
                        <ENT>SEO </ENT>
                        <ENT>740 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total </ENT>
                        <ENT>  </ENT>
                        <ENT>  </ENT>
                        <ENT>5,405 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Arrowtooth flounder </ENT>
                        <ENT>W </ENT>
                        <ENT>2,000 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>C </ENT>
                        <ENT>6,250 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>WYK </ENT>
                        <ENT>625 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,n,n,s">
                        <ENT I="22">  </ENT>
                        <ENT>SEO </ENT>
                        <ENT>625 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total </ENT>
                        <ENT>  </ENT>
                        <ENT>  </ENT>
                        <ENT>9,500 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Sablefish 
                            <SU>8,9,10</SU>
                              
                        </ENT>
                        <ENT>H/L W </ENT>
                        <ENT>N/A (394) </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>TRW W </ENT>
                        <ENT>98 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>H/L C </ENT>
                        <ENT>N/A (986) </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>TRW C </ENT>
                        <ENT>247 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>TRW WYak </ENT>
                        <ENT>56 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>H/L WYak </ENT>
                        <ENT>N/A (388) </ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,n,n,s">
                        <ENT I="22">  </ENT>
                        <ENT>H/L SEO </ENT>
                        <ENT>N/A (682) </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total </ENT>
                        <ENT>  </ENT>
                        <ENT>  </ENT>
                        <ENT>2,851 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Pacific ocean perch 
                            <SU>11</SU>
                              
                        </ENT>
                        <ENT>W </ENT>
                        <ENT>675 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>C </ENT>
                        <ENT>2,127 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>WYK </ENT>
                        <ENT>203 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,n,n,s">
                        <ENT I="22">  </ENT>
                        <ENT>SEO </ENT>
                        <ENT>410 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total </ENT>
                        <ENT>  </ENT>
                        <ENT>  </ENT>
                        <ENT>3,415 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Shortraker/rougheye 
                            <SU>12</SU>
                              
                        </ENT>
                        <ENT>W </ENT>
                        <ENT>55 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>C </ENT>
                        <ENT>210 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,n,n,s">
                        <ENT I="22">  </ENT>
                        <ENT>E </ENT>
                        <ENT>140 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total </ENT>
                        <ENT>  </ENT>
                        <ENT>  </ENT>
                        <ENT>405 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Rockfish, northern 
                            <SU>13</SU>
                              
                        </ENT>
                        <ENT>W </ENT>
                        <ENT>197 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>C </ENT>
                        <ENT>1,028 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,n,n,s">
                        <ENT I="22">  </ENT>
                        <ENT>E </ENT>
                        <ENT>N/A </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total </ENT>
                        <ENT>  </ENT>
                        <ENT>  </ENT>
                        <ENT>1,225 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Rockfish, other 
                            <SU>14,15</SU>
                              
                        </ENT>
                        <ENT>W </ENT>
                        <ENT>22 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>C </ENT>
                        <ENT>138 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>WYK </ENT>
                        <ENT>38 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,n,n,s">
                        <ENT I="22">  </ENT>
                        <ENT>SEO </ENT>
                        <ENT>50 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total </ENT>
                        <ENT>  </ENT>
                        <ENT>  </ENT>
                        <ENT>248 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Rockfish, pelagic shelf 
                            <SU>16</SU>
                              
                        </ENT>
                        <ENT>W </ENT>
                        <ENT>128 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>C </ENT>
                        <ENT>870 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>WYK </ENT>
                        <ENT>160 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,n,n,s">
                        <ENT I="22">  </ENT>
                        <ENT>SEO </ENT>
                        <ENT>215 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total </ENT>
                        <ENT>  </ENT>
                        <ENT>  </ENT>
                        <ENT>1,373 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Rockfish, demersal shelf SEO 
                            <SU>17</SU>
                              
                        </ENT>
                        <ENT>SEO </ENT>
                        <ENT>98 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="01">Thornyhead rockfish </ENT>
                        <ENT>W </ENT>
                        <ENT>90 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>C </ENT>
                        <ENT>210 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,n,n,s">
                        <PRTPAGE P="67967"/>
                        <ENT I="22">  </ENT>
                        <ENT>E </ENT>
                        <ENT>200 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total </ENT>
                        <ENT>  </ENT>
                        <ENT>  </ENT>
                        <ENT>500 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Atka mackerel </ENT>
                        <ENT>GW </ENT>
                        <ENT>150 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,n,n,d">
                        <ENT I="01">
                            Other species 
                            <SU>18</SU>
                              
                        </ENT>
                        <ENT>GW </ENT>
                        <ENT>2,712 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">GOA Total Interim TAC </ENT>
                        <ENT>  </ENT>
                        <ENT>  </ENT>
                        <ENT>68,921 </ENT>
                    </ROW>
                    <TNOTE>
                        <SU>1</SU>
                         Reserves have been reapportioned back to each species TAC and are reflected in the interim TAC amounts (
                        <E T="03">see</E>
                         § 679.20(a)(2)). 
                    </TNOTE>
                    <TNOTE>
                        <SU>2</SU>
                         
                        <E T="03">See</E>
                         § 679.2 for definitions of regulatory area and statistical area. 
                        <E T="03">See</E>
                         Figure 3b to part 679 for a description of regulatory districts.
                    </TNOTE>
                    <TNOTE>
                        <SU>3</SU>
                         The first seasonal allowance of pollock TAC in the W/C combined area is set at 25% of the annual TAC for the area which is 11,703 mt. Within the W/C area pollock is apportioned between Statistical Areas 610, 620, and 630 based on adjusted estimate of the relative distribution of pollock biomass in the area which is approximately 25% in Area 610 (2,894 mt), 56% in Area 620 (6,535 mt), and 19% in Area 630 (2,274 mt). In the Eastern Regulatory Area, pollock is not divided into less than annual allowances, and one-fourth of the TAC is available on an interim basis. 
                    </TNOTE>
                    <TNOTE>
                        <SU>4</SU>
                         The pollock TAC in all regulatory areas will be allocated 100 percent to vessels catching groundfish for processing by the inshore component after subtraction of amounts that are determined by the Regional Administrator, NMFS, to be necessary to support the bycatch needs of the offshore component in directed fisheries for other groundfish species. At this time, these bycatch amounts are unknown and will be determined during the fishing year (
                        <E T="03">see</E>
                         § 679.20(a)(6)(i)). 
                    </TNOTE>
                    <TNOTE>
                        <SU>5</SU>
                         The Pacific cod TAC in all regulatory areas is allocated 90 percent to vessels catching groundfish for processing by the inshore component and 10 percent to vessels catching groundfish for processing by the offshore component (
                        <E T="03">see</E>
                         § 679.20(a)(6)(ii)). The first seasonal apportionment of Pacific cod in the GOA is 60% of the annual TAC. 
                    </TNOTE>
                    <TNOTE>
                        <SU>6</SU>
                         “Deep-water flatfish” means Dover sole, Greenland turbot and deepsea sole. 
                    </TNOTE>
                    <TNOTE>
                        <SU>7</SU>
                         “Shallow-water flatfish” means flatfish not including “deep-water flatfish”, flathead sole, rex sole, or arrowtooth flounder. 
                    </TNOTE>
                    <TNOTE>
                        <SU>8</SU>
                         Sablefish TAC amounts for each of the regulatory areas and districts are assigned to hook-and-line and trawl gear. In the Central and Western Regulatory Areas, 80 percent of the TAC is allocated to hook-and-line gear and 20 percent to trawl gear. In the Eastern Regulatory Area, 95 percent of the TAC is assigned to hook-and-line gear. Five percent is allocated to trawl gear and may only be used as bycatch to support directed fisheries for other target species (
                        <E T="03">see</E>
                         § 679.20(a)(4)). 
                    </TNOTE>
                    <TNOTE>
                        <SU>9</SU>
                         The sablefish hook-and-line (H/L) gear fishery is managed under the Individual Fishing Quota (IFQ) program and is subject to regulations contained in subpart D of 50 CFR part 679. Annual IFQ amounts are based on the final TAC amount specified for the sablefish H/L gear fishery as contained in the final specifications for groundfish. Under § 679.7(f)(3)(ii), retention of sablefish caught with H/L gear is prohibited unless the harvest is authorized under a valid IFQ permit and IFQ card. In 2004, IFQ permits and IFQ cards will not be valid before the effective date of the 2004 final specifications. Thus, fishing for sablefish with H/L gear will not be authorized under these interim specifications. Nonetheless, interim amounts are shown in parentheses to reflect assignments of one-fourth of the proposed TAC amounts among gear categories and regulatory areas in accordance with § 679.20(c)(2)(i). See § 679.40 for guidance on the annual allocation of IFQ. 
                    </TNOTE>
                    <TNOTE>
                        <SU>10</SU>
                         Sablefish caught in the GOA with gear other than hook-and-line or trawl gear must be treated as a prohibited species and may not be retained. 
                    </TNOTE>
                    <TNOTE>
                        <SU>11</SU>
                         “Pacific ocean perch” means 
                        <E T="03">Sebastes alutus.</E>
                    </TNOTE>
                    <TNOTE>
                        <SU>12</SU>
                         “Shortraker/rougheye rockfish” means 
                        <E T="03">Sebastes borealis</E>
                         (shortraker) and 
                        <E T="03">S. aleutianus</E>
                         (rougheye). 
                    </TNOTE>
                    <TNOTE>
                        <SU>13</SU>
                         “Northern rockfish” means 
                        <E T="03">Sebastes polyspinis.</E>
                    </TNOTE>
                    <TNOTE>
                        <SU>14</SU>
                         “Other rockfish” in the Western and Central Regulatory Areas and in the West Yakutat District means slope rockfish and demersal shelf rockfish. The category “other rockfish” in the Southeast Outside District means slope rockfish. 
                    </TNOTE>
                    <TNOTE>
                        <SU>15</SU>
                         “Slope rockfish” means 
                        <E T="03">Sebastes aurora</E>
                         (aurora), 
                        <E T="03">S. melanostomus</E>
                         (blackgill), 
                        <E T="03">S. paucispinis</E>
                         (bocaccio), 
                        <E T="03">S. goodei</E>
                         (chilipepper), 
                        <E T="03">S. crameri</E>
                         (darkblotch), 
                        <E T="03">S. elongatus</E>
                         (greenstriped), 
                        <E T="03">S. variegateu</E>
                         (harlequin), 
                        <E T="03">S. wilsoni</E>
                         (pygmy), 
                        <E T="03">S. proriger</E>
                         (redstripe), 
                        <E T="03">S. zacentrus</E>
                         (sharpchin), 
                        <E T="03">S. jordani</E>
                         (shortbelly), 
                        <E T="03">S. brevispinis</E>
                         (silvergrey), 
                        <E T="03">S. diploproa</E>
                         (splitnose), 
                        <E T="03">S. saxicola</E>
                         (stripetail), 
                        <E T="03">S. miniatus</E>
                         (vermilion), 
                        <E T="03">S. babcocki</E>
                         (redbanded), and 
                        <E T="03">S. reedi</E>
                         (yellowmouth). 
                    </TNOTE>
                    <TNOTE>
                        <SU>16</SU>
                         “Pelagic shelf rockfish” includes 
                        <E T="03">Sebastes ciliatus</E>
                         (dusky), 
                        <E T="03">S. entomelas</E>
                         (widow), and 
                        <E T="03">S. flavidus</E>
                         (yellowtail). 
                    </TNOTE>
                    <TNOTE>
                        <SU>17</SU>
                         “Demersal shelf rockfish” means 
                        <E T="03">Sebastes pinniger</E>
                         (canary), 
                        <E T="03">S. nebulosus</E>
                         (china), 
                        <E T="03">S. caurinus</E>
                         (copper), 
                        <E T="03">S. maliger</E>
                         (quillback), 
                        <E T="03">S. helvomaculatus</E>
                         (rosethorn), 
                        <E T="03">S. nigrocinctus</E>
                         (tiger), and 
                        <E T="03">S. ruberrimus</E>
                         (yelloweye). 
                    </TNOTE>
                    <TNOTE>
                        <SU>18</SU>
                         “Other species” includes sculpins, sharks, skates, squid, and octopus. The TAC for “other species” equals 5 percent of the TAC amounts of target species. 
                    </TNOTE>
                </GPOTABLE>
                <HD SOURCE="HD1">Interim 2004 Halibut PSC Mortality Limits </HD>
                <P>Under § 679.21(d), annual Pacific halibut PSC mortality limits are established for trawl and hook-and-line gear and may be established for pot gear. The Council recommended and NMFS proposed to reestablish the 2003 halibut mortality limits for 2004 because no new information was available. Consistent with 2003, the Council recommended and NMFS proposed exemptions for pot gear, jig gear and the sablefish hook-and-line fishery from halibut PSC limits for 2004. The fishery specific interim PSC allowances for halibut are in effect at 0001 hours, A.l.t., January 1, 2004, and remain in effect until superseded by the final 2004 harvest specifications. The interim halibut PSC limits are: (1) 500 mt to trawl gear, (2) 72.5 mt to hook-and-line gear for fisheries other than demersal shelf rockfish, and (3) 2.5 mt to hook-and-line gear for the demersal shelf rockfish fishery in the Southeast Outside District.</P>
                <P>Regulations at § 679.21(d)(3)(iii) authorize apportionments of the trawl halibut PSC limit as bycatch allowances to a deep-water species complex, comprised of rex sole, sablefish, rockfish, deep-water flatfish, and arrowtooth flounder; and a shallow-water species complex, comprised of pollock, Pacific cod, shallow-water flatfish, flathead sole, Atka mackerel, and “other species.” The interim 2004 apportionment for the shallow-water species complex is 409 mt and for the deep-water species complex is 91 mt.</P>
                <HD SOURCE="HD1">Interim 2004 Non-Exempt AFA Catcher Vessel Groundfish Harvest and PSC Limitations</HD>
                <P>
                    The AFA regulations implemented groundfish harvesting and processing limitations, also called sideboards, on AFA catcher/processors and catcher vessels in the GOA. These limitations are considered necessary for fishermen and processors who have received an exclusive harvesting and processing 
                    <PRTPAGE P="67968"/>
                    privilege under the AFA to protect the interests of fishermen and processors who do not have such privileges. In the GOA, AFA catcher/processors are prohibited from fishing for any species of fish (§ 679.7(k)(1)(ii)) and from processing any groundfish harvested in Statistical Area 630 of the GOA (§ 679.7(k)(1)(iv)). The Council recommended and NMFS proposed that certain AFA catcher vessels in the GOA be exempt from groundfish harvest limitations. Regulations at § 679.64(b)(2)(ii) exempt AFA catcher vessels in the GOA less than 125 ft (38.1 m) length overall (LOA) whose annual Bering Sea and Aleutian Islands management area pollock landings totaled less than 5,100 mt and that made 40 or more GOA groundfish landings from 1995 through 1997.
                </P>
                <P>For non-exempt AFA catcher vessels in the GOA, harvest limitations are based on their traditional harvest levels of TAC in groundfish fisheries covered by the GOA FMP. Regulations at § 679.64(b)(3)(iii) establish the groundfish harvest limits in the GOA based on the retained catch of non-exempt AFA catcher vessels of each sideboard species from 1995 through 1997, divided by the sum of the TACs for that species over the same period. These amounts are listed in Table 2. All harvests of sideboard species made by non-exempt AFA catcher vessels, whether as targeted catch or bycatch, will be deducted from the sideboard limits in Table 2.</P>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s50,xs100,18,10,16">
                    <TTITLE>Table 2.—Interim 2004 GOA Non-Exempt American Fisheries Act Catcher Vessel (CV) Groundfish Harvest Sideboard Limitations</TTITLE>
                    <BOXHD>
                        <CHED H="1">Species</CHED>
                        <CHED H="1">
                            Apportionments and allocations by area/season/
                            <LI>processor/gear</LI>
                        </CHED>
                        <CHED H="1">Ratio of 1995 1997 non-exempt AFA CV catch to 1995-1997 TAC</CHED>
                        <CHED H="1">2004 interim TAC (mt)</CHED>
                        <CHED H="1">2004 Non-Exempt AFA catcher vessel sideboard (mt)</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Pollock </ENT>
                        <ENT>Shumagin (610) </ENT>
                        <ENT>0.6112 </ENT>
                        <ENT>2,894 </ENT>
                        <ENT>1,769</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>Chirikof (620) </ENT>
                        <ENT>0.1427 </ENT>
                        <ENT>933 </ENT>
                        <ENT>6,535</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>Kodiak (630) </ENT>
                        <ENT>0.2438 </ENT>
                        <ENT>554 </ENT>
                        <ENT>2,274</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>WYK (640) </ENT>
                        <ENT>0.3499 </ENT>
                        <ENT>270 </ENT>
                        <ENT>94</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>SEO (650) </ENT>
                        <ENT>0.3499 </ENT>
                        <ENT>1,615 </ENT>
                        <ENT>565</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pacific cod </ENT>
                        <ENT>W inshore </ENT>
                        <ENT>0.1423 </ENT>
                        <ENT>7,553 </ENT>
                        <ENT>1,075</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>W offshore </ENT>
                        <ENT>0.1026 </ENT>
                        <ENT>839 </ENT>
                        <ENT>86</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>C inshore </ENT>
                        <ENT>0.0722 </ENT>
                        <ENT>10,916 </ENT>
                        <ENT>788</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>C offshore </ENT>
                        <ENT>0.0721 </ENT>
                        <ENT>1,213 </ENT>
                        <ENT>87</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>E inshore </ENT>
                        <ENT>0.0079 </ENT>
                        <ENT>587 </ENT>
                        <ENT>5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>E offshore </ENT>
                        <ENT>0.0078 </ENT>
                        <ENT>65 </ENT>
                        <ENT>1</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Flatfish deep-water </ENT>
                        <ENT>W </ENT>
                        <ENT>0.0000 </ENT>
                        <ENT>45 </ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>C </ENT>
                        <ENT>0.0670 </ENT>
                        <ENT>555 </ENT>
                        <ENT>37</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>E </ENT>
                        <ENT>0.0171 </ENT>
                        <ENT>620 </ENT>
                        <ENT>11</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Rex sole </ENT>
                        <ENT>W </ENT>
                        <ENT>0.0010 </ENT>
                        <ENT>320 </ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>C </ENT>
                        <ENT>0.0402 </ENT>
                        <ENT>1,385 </ENT>
                        <ENT>56</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>E </ENT>
                        <ENT>0.0153 </ENT>
                        <ENT>662 </ENT>
                        <ENT>10</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Flathead sole </ENT>
                        <ENT>W </ENT>
                        <ENT>0.0036 </ENT>
                        <ENT>500 </ENT>
                        <ENT>2</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>C </ENT>
                        <ENT>0.0261 </ENT>
                        <ENT>1,250 </ENT>
                        <ENT>33</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>E </ENT>
                        <ENT>0.0048 </ENT>
                        <ENT>943 </ENT>
                        <ENT>5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Flatfish shallow-water </ENT>
                        <ENT>W </ENT>
                        <ENT>0.0156 </ENT>
                        <ENT>1,125 </ENT>
                        <ENT>18</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>C </ENT>
                        <ENT>0.0598 </ENT>
                        <ENT>3,250 </ENT>
                        <ENT>194</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>E </ENT>
                        <ENT>0.0126 </ENT>
                        <ENT>1,030 </ENT>
                        <ENT>13</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Arrowtooth flounder </ENT>
                        <ENT>W </ENT>
                        <ENT>0.0021 </ENT>
                        <ENT>2,000 </ENT>
                        <ENT>4</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>C </ENT>
                        <ENT>0.0309 </ENT>
                        <ENT>6,250 </ENT>
                        <ENT>193</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>E </ENT>
                        <ENT>0.0020 </ENT>
                        <ENT>1,250 </ENT>
                        <ENT>3</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Sablefish </ENT>
                        <ENT>W trawl gear </ENT>
                        <ENT>0.0000 </ENT>
                        <ENT>98 </ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>C trawl gear </ENT>
                        <ENT>0.0720 </ENT>
                        <ENT>247 </ENT>
                        <ENT>18</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>E trawl gear </ENT>
                        <ENT>0.0488 </ENT>
                        <ENT>56 </ENT>
                        <ENT>3</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pacific ocean perch </ENT>
                        <ENT>W </ENT>
                        <ENT>0.0623 </ENT>
                        <ENT>675 </ENT>
                        <ENT>42</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>C </ENT>
                        <ENT>0.0866 </ENT>
                        <ENT>2,127 </ENT>
                        <ENT>184</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>E </ENT>
                        <ENT>0.0466 </ENT>
                        <ENT>613 </ENT>
                        <ENT>29</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Shortraker/Rougheye </ENT>
                        <ENT>W </ENT>
                        <ENT>0.0000 </ENT>
                        <ENT>55 </ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>C </ENT>
                        <ENT>0.0237 </ENT>
                        <ENT>210 </ENT>
                        <ENT>5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>E </ENT>
                        <ENT>0.0124 </ENT>
                        <ENT>140 </ENT>
                        <ENT>2</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Other rockfish </ENT>
                        <ENT>W </ENT>
                        <ENT>0.0034 </ENT>
                        <ENT>23 </ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>C </ENT>
                        <ENT>0.2065 </ENT>
                        <ENT>138 </ENT>
                        <ENT>28</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>E </ENT>
                        <ENT>0.0000 </ENT>
                        <ENT>88 </ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Northern rockfish </ENT>
                        <ENT>W </ENT>
                        <ENT>0.0003 </ENT>
                        <ENT>197 </ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>C </ENT>
                        <ENT>0.0336 </ENT>
                        <ENT>1,028 </ENT>
                        <ENT>35</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pelagic shelf rockfish </ENT>
                        <ENT>W </ENT>
                        <ENT>0.0001 </ENT>
                        <ENT>128 </ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>C </ENT>
                        <ENT>0.0000 </ENT>
                        <ENT>870 </ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>E </ENT>
                        <ENT>0.0067 </ENT>
                        <ENT>375 </ENT>
                        <ENT>3</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Thornyhead rockfish </ENT>
                        <ENT>W </ENT>
                        <ENT>0.0308 </ENT>
                        <ENT>90 </ENT>
                        <ENT>3</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>C </ENT>
                        <ENT>0.0308 </ENT>
                        <ENT>210 </ENT>
                        <ENT>6</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>E </ENT>
                        <ENT>0.0308 </ENT>
                        <ENT>200 </ENT>
                        <ENT>6</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Demersal shelf rockfish </ENT>
                        <ENT>SEO </ENT>
                        <ENT>0.0020 </ENT>
                        <ENT>98 </ENT>
                        <ENT>0</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Atka mackerel </ENT>
                        <ENT>Gulfwide </ENT>
                        <ENT>0.0309 </ENT>
                        <ENT>150 </ENT>
                        <ENT>5</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Other species </ENT>
                        <ENT>Gulfwide </ENT>
                        <ENT>0.0090 </ENT>
                        <ENT>2,712 </ENT>
                        <ENT>24</ENT>
                    </ROW>
                </GPOTABLE>
                <PRTPAGE P="67969"/>
                <P>In accordance with regulations at § 679.64(b)(4), PSC bycatch limits for non-exempt AFA catcher vessels in the GOA are based on the ratio of aggregate retained groundfish catch by non-exempt AFA catcher vessels in each PSC target category from 1995 through 1997, relative to the retained catch of all vessels in that fishery from 1995 through 1997. These amounts are shown in Table 3.</P>
                <GPOTABLE COLS="5" OPTS="L2" CDEF="i1,s50,r50,15,15,15">
                    <TTITLE>Table 3.—Interim 2004 Non-Exempt American Fisheries Act Catcher Vessel Prohibited Species Catch (PSC) Limits for the GOA</TTITLE>
                    <BOXHD>
                        <CHED H="1">PSC species</CHED>
                        <CHED H="1">Target fishery</CHED>
                        <CHED H="1">Ratio of 1995-1997 non-exempt AFA CV retained catch to total retained catch</CHED>
                        <CHED H="1">2004 interim PSC limit (mt)</CHED>
                        <CHED H="1">2004 non-exempt AFA catcher vessel PSC limit (mt)</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Halibut (mortality in mt) </ENT>
                        <ENT>
                            shallow water targets 
                            <LI>deep water targets </LI>
                        </ENT>
                        <ENT>
                            0.340 
                            <LI>0.070 </LI>
                        </ENT>
                        <ENT>
                            409 
                            <LI>91 </LI>
                        </ENT>
                        <ENT>
                            139 
                            <LI>6</LI>
                        </ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Directed Fishing Closures </HD>
                <P>In accordance with § 679.20(d)(1)(i), if the Regional Administrator determines that any allocation or apportionment of a target species or “other species” category apportioned to a fishery or, with respect to pollock and Pacific cod, to an inshore or offshore component allocation, will be reached, the Regional Administrator may establish a directed fishing allowance for that species or species group. If the Regional Administrator establishes a directed fishing allowance, and that allowance is or will be reached before the end of the fishing year, NMFS will prohibit directed fishing for that species or species group in the specified GOA regulatory area or district (§ 679.20(d)(1)(iii)). </P>
                <P>The Regional Administrator has determined that the TAC amounts in Table 4 are necessary as incidental catch to support other anticipated groundfish fisheries for the 2004 fishing year. </P>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s100,r75,r75,10">
                    <TTITLE>Table 4.—Incidental Catch Needed to Support Other Directed Fisheries in the GOA in 2004. </TTITLE>
                    <TDESC>[Amounts are in metric tons] </TDESC>
                    <BOXHD>
                        <CHED H="1">Target </CHED>
                        <CHED H="1">Regulatory area </CHED>
                        <CHED H="1">Gear/component </CHED>
                        <CHED H="1">Amount </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Atka Mackerel </ENT>
                        <ENT>entire GOA </ENT>
                        <ENT>all </ENT>
                        <ENT>150 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Thornyhead Rockfish </ENT>
                        <ENT>entire GOA </ENT>
                        <ENT>all </ENT>
                        <ENT>500 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Shortraker Rougheye Rockfish </ENT>
                        <ENT>entire GOA </ENT>
                        <ENT>all </ENT>
                        <ENT>405 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Other Rockfish </ENT>
                        <ENT>entire GOA </ENT>
                        <ENT>all </ENT>
                        <ENT>248 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Sablefish </ENT>
                        <ENT>entire GOA </ENT>
                        <ENT>trawl </ENT>
                        <ENT>401 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pollock </ENT>
                        <ENT>entire GOA </ENT>
                        <ENT>all/offshore </ENT>
                        <ENT>0 </ENT>
                    </ROW>
                </GPOTABLE>
                <P>In accordance with § 679.20(d)(1)(i), the Regional Administrator establishes the directed fishing allowances for the above species or species groups as zero. Therefore, in accordance with § 679.20(d)(1)(iii), NMFS immediately is prohibiting directed fishing for those species, areas, gear types, and components listed in Table 4. These closures will remain in effect until superseded by the final 2004 harvest specifications. </P>
                <P>Regulations at § 679.64(b)(5) provide for management of AFA catcher vessel groundfish harvest limits and PSC bycatch limits using directed fishing closures and PSC closures according to procedures set out at §§ 679.20(d)(1)(iv), 679.21(d)(8) and 679.21(e)(3)(v). The Regional Administrator has determined that in addition to the closures listed above, many of the non-exempt AFA catcher vessel sideboard amounts listed in Table 2 are necessary as incidental catch to support other anticipated groundfish fisheries for the 2004 fishing year. In accordance with § 679.20(d)(1)(iv) the Regional Administrator establishes these amounts as directed fishing allowances. The Regional Administrator finds that many of these directed fishing allowances will be reached before the end of the year. Therefore, in accordance with § 679.20(d)(1)(iii), NMFS is prohibiting directed fishing by non-exempt AFA catcher vessels in the GOA for the species and specified areas in Table 5. These closures will remain in effect until superseded by the final 2004 harvest specifications. </P>
                <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s100,r100,xs20">
                    <TTITLE>Table 5.—2004 Non-Exempt American Fisheries Act Catcher Vessel Sideboard Directed Fishing Closures in the GOA </TTITLE>
                    <BOXHD>
                        <CHED H="1">Species </CHED>
                        <CHED H="1">Regulatory area district </CHED>
                        <CHED H="1">Gear </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Pacific cod </ENT>
                        <ENT>Eastern GOA </ENT>
                        <ENT>all </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Deep-water flatfish </ENT>
                        <ENT>Western and Eastern GOA </ENT>
                        <ENT>all </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Rex sole </ENT>
                        <ENT>Western and Eastern GOA </ENT>
                        <ENT>all </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Flathead sole </ENT>
                        <ENT>Eastern GOA </ENT>
                        <ENT>all </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Shallow-water flatfish </ENT>
                        <ENT>Eastern GOA </ENT>
                        <ENT>all </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Arrowtooth flounder </ENT>
                        <ENT>Eastern GOA </ENT>
                        <ENT>all </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pacific ocean perch </ENT>
                        <ENT>Western GOA </ENT>
                        <ENT>all </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Northern rockfish </ENT>
                        <ENT>Western GOA </ENT>
                        <ENT>all </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Pelagic shelf rockfish </ENT>
                        <ENT>entire GOA </ENT>
                        <ENT>all </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Demersal shelf rockfish </ENT>
                        <ENT>SEO District </ENT>
                        <ENT>all </ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="67970"/>
                        <ENT I="01">Other species </ENT>
                        <ENT>entire GOA </ENT>
                        <ENT>all </ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Classification </HD>
                <P>This action is authorized under 50 CFR 679.20 and is exempt from review under Executive Order 12866. </P>
                <P>Because this action is a final action by NMFS, analyses required under the Magnuson-Stevens Act must be completed and considered by the agency before promulgation of the interim harvest specifications. </P>
                <P>Regulations at 50 CFR 679.20(c)(2) require NMFS to specify harvest specifications to be effective January 1 and to remain in effect until superceded by the final specifications. Without interim specifications in effect on January 1, the groundfish fisheries would not be able to open, resulting in disruption within the fishing industry. NMFS cannot publish interim specifications until proposed specifications are completed, because the interim specifications are derived from the proposed specifications, as required by regulations at 50 CFR 679.20(c)(2). </P>
                <P>The proposed specifications are based on the preliminary recommendations of the Plan Team, which were reviewed by the Scientific and Statistical Committee, Advisory Panel, and Council in October, 2003 in projecting 2003 biomass amounts, as identified in the 2002 SAFE Report, for the proposed 2004 ABC, overfishing levels, and TAC amounts. The Plan Team recommendations incorporate the most current data available from a number of sources, including current-year industry catch levels, and current-year trawl and hydro-acoustic surveys. These data are not available in time for Council review prior to the October Council meeting, as the surveys are conducted during the summer months, and industry catch levels reflect current year activity. These up-dated data sources represent the best available scientific information. These data provide the basis for the proposed and interim specifications. </P>
                <P>The proposed specifications, as required by regulations at 50 CFR 679.20(c)(1)(i)(A), must be published as soon as practicable after consultation with the Council, which occurs at the Council's October meeting. This requirement, along with the requirement of national standard 2 of the Magnuson-Stevens Act to use the best scientific information available, prevents NMFS from publishing the proposed specifications early enough to provide sufficient time to have a public comment period for the interim specifications, which are derived from the proposed specifications, and to have the interim specifications effective on January 1. </P>
                <P>As stated above, disruption of the fishing industry, and consequent impacts to fishing communities and the public, would occur if the interim specifications were not effective January 1. Additionally, the public is provided an opportunity to comment on the proposed specifications, from which the interim specifications are derived. For these reasons, good cause exists under 5 U.S.C. 553(b)(B) to waive prior notice and opportunity for public comment on this action as such procedures would be impracticable and contrary to the public interest. </P>
                <P>Likewise, the AA finds good cause to waive the 30-day delay in effectiveness date of the interim specifications. Regulations at 50 CFR 679.20(c)(2) requires NMFS to establish interim harvest specifications to be effective on January 1 and to remain in effect until superseded by the publication of final harvest specifications by the Office of the Federal Register. NMFS interprets regulations at § 679.20(c)(2) as requiring the filing of interim specifications with the Office of the Federal Register before any harvest of groundfish is authorized. The interim specifications are based on the proposed 2004 specifications. </P>
                <P>The interim specifications rely on data used to propose the 2004 specifications, and those data are not available until the after summer surveys are conducted (see above). Without interim specifications in effect on January 1, the groundfish fisheries would not be able to open on that date, resulting in disruption of the fishing industry. These reasons constitute good cause pursuant to 5 U.S.C. 553(d)(3) to waive the 30-day delay in effectiveness date. </P>
                <P>Because these interim specifications are not required to be issued with prior notice and opportunity for public comment pursuant to 5 U.S.C. 553, or any other law, the analytical requirements of the Regulatory Flexibility Act do not apply. Consequently, no regulatory flexibility analysis has been prepared for this action. </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>
                        16 U.S.C. 773 
                        <E T="03">et seq.</E>
                        , 1801 
                        <E T="03">et seq.</E>
                        , and 3631 
                        <E T="03">et seq.</E>
                        . 
                    </P>
                </AUTH>
                <SIG>
                    <DATED>Dated: December 1, 2003. </DATED>
                    <NAME>William T. Hogarth, </NAME>
                    <TITLE>Assistant Administrator for Fisheries, National Marine Fisheries Service. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30282 Filed 12-4-03; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3510-22-P</BILCOD>
        </RULE>
    </RULES>
    <VOL>68</VOL>
    <NO>234</NO>
    <DATE>Friday, December 5, 2003</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <PRORULES>
        <PRORULE>
            <PREAMB>
                <PRTPAGE P="67971"/>
                <AGENCY TYPE="F">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. 2003-NM-139-AD]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; Bombardier Model CL-215-1A10 and CL-215-6B11 Series Airplanes</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration, DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking (NPRM).</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document proposes the supersedure of an existing airworthiness directive (AD), applicable to certain Bombardier Model CL-215-1A10 and CL-215-6B11 series airplanes, that currently requires repetitive inspections to detect cracking of main landing gear (MLG) axles that have been reworked by chromium plating, and replacement of cracked axles with serviceable axles. This action would add a dimensional check and follow-on corrective actions, mandate terminating action for certain airplanes, and add three airplanes to the applicability in the existing AD. The actions specified by the proposed AD are intended to prevent cracking of the inner bearing surface of the MLG axles, which could result in failure of an axle, subsequent separation of the wheel from the airplane, and consequent reduced controllability of the airplane during takeoff or landing. This action is intended to address the identified unsafe condition.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received by January 5, 2004.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit comments in triplicate to the Federal Aviation Administration (FAA), Transport Airplane Directorate, ANM-114, Attention: Rules Docket No. 2003-NM-139-AD, 1601 Lind Avenue, SW., Renton, Washington 98055-4056. Comments may be inspected at this location between 9 a.m. and 3 p.m., Monday through Friday, except Federal holidays. Comments may be submitted via fax to (425) 227-1232. Comments may also be sent via the Internet using the following address: 
                        <E T="03">9-anm-nprmcomment@faa.gov.</E>
                         Comments sent via fax or the Internet must contain “Docket No. 2003-NM-139-AD” in the subject line and need not be submitted in triplicate. Comments sent via the Internet as attached electronic files must be formatted in Microsoft Word 97 or 2000 or ASCII text.
                    </P>
                    <P>The service information referenced in the proposed rule may be obtained from Bombardier, Inc., Canadair, Aerospace Group, P.O. Box 6087, Station Centre-ville, Montreal, Quebec H3C 3G9, Canada. This information may be examined at the FAA, Transport Airplane Directorate, 1601 Lind Avenue, SW., Renton, Washington; or at the FAA, New York Aircraft Certification Office, 10 Fifth Street, Third Floor, Valley Stream, New York.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>David Lawson, Aerospace Engineer, Airframe and Propulsion Branch, ANE-171, FAA, New York Aircraft Certification Office, 10 Fifth Street, Third Floor, Valley Stream, New York 11581; telephone (516) 256-4227; fax (516) 568-2716.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P> </P>
                <HD SOURCE="HD1">Comments Invited</HD>
                <P>Interested persons are invited to participate in the making of the proposed rule by submitting such written data, views, or arguments as they may desire. Communications shall identify the Rules Docket number and be submitted in triplicate to the address specified above. All communications received on or before the closing date for comments, specified above, will be considered before taking action on the proposed rule. The proposals contained in this action may be changed in light of the comments received.</P>
                <P>Submit comments using the following format:</P>
                <P>• Organize comments issue-by-issue. For example, discuss a request to change the compliance time and a request to change the service bulletin reference as two separate issues.</P>
                <P>• For each issue, state what specific change to the proposed AD is being requested.</P>
                <P>
                    • Include justification (
                    <E T="03">e.g.</E>
                    , reasons or data) for each request.
                </P>
                <P>Comments are specifically invited on the overall regulatory, economic, environmental, and energy aspects of the proposed rule. All comments submitted will be available, both before and after the closing date for comments, in the Rules Docket for examination by interested persons. A report summarizing each FAA-public contact concerned with the substance of this proposal will be filed in the Rules Docket.</P>
                <P>Commenters wishing the FAA to acknowledge receipt of their comments submitted in response to this action must submit a self-addressed, stamped postcard on which the following statement is made: “Comments to Docket Number 2003-NM-139-AD.” The postcard will be date stamped and returned to the commenter.</P>
                <HD SOURCE="HD1">Availability of NPRMs</HD>
                <P>Any person may obtain a copy of this NPRM by submitting a request to the FAA, Transport Airplane Directorate, ANM-114, Attention: Rules Docket No. 2003-NM-139-AD, 1601 Lind Avenue, SW., Renton, Washington 98055-4056.</P>
                <HD SOURCE="HD1">Discussion</HD>
                <P>On October 16, 1995, the FAA issued AD 95-22-04, amendment 39-9411 (60 FR 54421, October 24, 1995), applicable to certain Canadair Model CL-215-1A10 and CL-215-6B11 series airplanes, to require inspections to detect cracking of main landing gear (MLG) axles that have been reworked by chromium plating, and replacement of cracked axles with serviceable axles. That action was prompted by reports of fatigue cracking found on several MLG wheel axes that had been chromium-plated during rework. The requirements of that AD are intended to prevent such cracking, which can result in failure of the axle, separation of the wheel from the aircraft, and consequent reduced controllability of the airplane during takeoff or landing.</P>
                <HD SOURCE="HD1">Actions Since Issuance of Previous AD</HD>
                <P>
                    Since the issuance of AD 95-22-04, Transport Canada Civil Aviation (TCCA), which is the airworthiness authority for Canada, issued Canadian airworthiness directive CF-1993-08R3, dated March 30, 2000; applicable to certain Bombardier Model CL-215-1A10 and CL-215-6B11 series airplanes. The Canadian airworthiness directive was issued to require eventual 
                    <PRTPAGE P="67972"/>
                    replacement of the MLG axles following an evaluation of the service history that showed the maximum number of allowable landings that could be accumulated on the MLG axles before replacement is necessary.
                </P>
                <HD SOURCE="HD1">Explanation of Relevant Service Information</HD>
                <P>Bombardier has issued Service Bulletin 215-A462, Revision 3, dated January 17, 2000 (Canadair Alert Service Bulletin 215-A462, dated June 2, 1993, was referenced for accomplishment of the actions specified in the existing AD). Revision 3 contains the same inspection procedures as those in the original issue of the service bulletin, but a new dimensional check is added to determine whether the MLG axle has been reworked outside the dimensions specified in the Overhaul Manual. If the axle has been reworked outside those dimensions, has unknown rework dimensions, or has an unknown service life, repetitive ultrasonic inspections (as specified in the existing AD) are recommended until the MLG axle is replaced with a serviceable axle. Revision 3 also recommends replacement of the MLG axles after accumulation of the maximum number of allowable landings on the axles. The replacement eliminates the need for the repetitive inspections. TCCA classified this service bulletin as mandatory and issued Canadian airworthiness directive CF-1993-08R3, dated March 30, 2000, to ensure the continued airworthiness of these airplanes in Canada.</P>
                <HD SOURCE="HD1">FAA's Conclusions</HD>
                <P>This airplane model is manufactured in Canada and is type certificated for operation in the United States under the provisions of § 21.29 of the Federal Aviation Regulations (14 CFR 21.29) and the applicable bilateral airworthiness agreement. Pursuant to this bilateral airworthiness agreement, TCCA has kept the FAA informed of the situation described above. We have examined the findings of TCCA, reviewed all available information, and determined that AD action is necessary for products of this type design that are certificated for operation in the United States.</P>
                <HD SOURCE="HD1">Explanation of Requirements of Proposed AD</HD>
                <P>Since an unsafe condition has been identified that is likely to exist or develop on other airplanes of the same type design registered in the United States, the proposed AD would supersede AD 95-22-04 to continue to require repetitive inspections to detect cracking of MLG axles that have been reworked by chromium plating, and replacement of cracked axles with serviceable axles. The proposed AD would add a dimensional check and follow-on corrective actions, mandate terminating action for certain airplanes, add three airplanes to the applicability in the existing AD, and remove the reporting requirement. The actions would be required to be accomplished in accordance with the service bulletin described previously, except as discussed below.</P>
                <HD SOURCE="HD1">Difference Between Service Bulletin and Proposed AD</HD>
                <P>The service bulletin referenced in this proposed AD specifies to submit certain inspection findings to the manufacturer; however, this proposed AD does not include such a requirement.</P>
                <HD SOURCE="HD1">Revised Labor Rate</HD>
                <P>After the existing AD was issued, we reviewed the figures we use to calculate the labor rate to do the required actions. To account for various inflationary costs in the airline industry, we find it appropriate to increase the labor rate used in these calculations from $60 per work hour to $65 per work hour. The economic impact information, below, has been revised to reflect this increase in the specified hourly labor rate.</P>
                <HD SOURCE="HD1">Cost Impact</HD>
                <P>There are approximately 3 airplanes of U.S. registry that would be affected by this proposed AD.</P>
                <P>The inspections that are currently required by AD 95-22-04 take about 2 work hours per airplane to accomplish, at an average labor rate of $65 per work hour. Based on these figures, the cost impact of the currently required inspections on U.S. operators is estimated to be $390, or $130 per airplane, per inspection cycle.</P>
                <P>The dimensional check and ultrasonic inspection proposed in this AD action would take about 2 work hours per airplane to accomplish, at an average labor rate of $65 per work hour. Based on these figures, the cost impact of these checks and inspections on U.S. operators is estimated to be $390, or $130 per airplane, per inspection cycle.</P>
                <P>The replacement proposed in this AD action, if done, would take about 8 work hours per airplane to accomplish, at an average labor rate of $65 per work hour. Required parts would cost approximately $13,000 per assembly (two per airplane). Based on these figures, the cost impact of the replacement proposed by this AD on U.S. operators is estimated to be $26,520 per airplane.</P>
                <P>The cost impact figures discussed above are based on assumptions that no operator has yet accomplished any of the current or proposed requirements of this AD action, and that no operator would accomplish those actions in the future if this AD were not adopted. The cost impact figures discussed in AD rulemaking actions represent only the time necessary to perform the specific actions actually required by the AD. These figures typically do not include incidental costs, such as the time required to gain access and close up, planning time, or time necessitated by other administrative actions.</P>
                <HD SOURCE="HD1">Regulatory Impact</HD>
                <P>The regulations proposed herein would not have a substantial direct effect on the States, on the relationship between the national Government and the States, or on the distribution of power and responsibilities among the various levels of government. Therefore, it is determined that this proposal would not have federalism implications under Executive Order 13132.</P>
                <P>
                    For the reasons discussed above, I certify that this proposed regulation (1) is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under the DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979); and (3) if promulgated, will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act. A copy of the draft regulatory evaluation prepared for this action is contained in the Rules Docket. A copy of it may be obtained by contacting the Rules Docket at the location provided under the caption 
                    <E T="02">ADDRESSES.</E>
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Proposed Amendment</HD>
                <P>Accordingly, pursuant to the authority delegated to me by the Administrator, the Federal Aviation Administration proposes to amend part 39 of the Federal Aviation Regulations (14 CFR part 39) as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
                    <P>1. The authority citation for part 39 continues to read as follows:</P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>49 U.S.C. 106(g), 40113, 44701.</P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 39.13 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                        <P>
                            2. Section 39.13 is amended by removing amendment 39-9411 (60 FR 
                            <PRTPAGE P="67973"/>
                            54421, October 24, 1995), and by adding a new airworthiness directive (AD), to read as follows:
                        </P>
                        <EXTRACT>
                            <FP SOURCE="FP-2">
                                <E T="04">Bombardier, Inc.</E>
                                 (Formerly Canadair): Docket 2003-NM-139-AD. Supersedes AD 95-22-04, Amendment 39-9411.
                            </FP>
                            <P>
                                <E T="03">Applicability:</E>
                                 Model CL-215-1A10 (piston) and CL-215-6B11 (turboprop) series airplanes, having serial numbers 1001 through 1125 inclusive, certificated in any category.
                            </P>
                            <P>
                                <E T="03">Compliance:</E>
                                 Required as indicated, unless accomplished previously.
                            </P>
                            <P>To prevent cracking in the inner bearing surface of the main landing gear (MLG) axles, which could result in failure of an axle, subsequent separation of the wheel from the airplane, and consequent reduced controllability of the airplane during takeoff or landing, accomplish the following:</P>
                            <HD SOURCE="HD1">Restatement of Certain Requirements of AD 95-22-04</HD>
                            <HD SOURCE="HD2">Repetitive Inspections/Corrective Action</HD>
                            <P>(a) Within 60 days after November 8, 1995 (the effective date of AD 95-22-04, amendment 39-9411), perform either an eddy current inspection or a chemical inspection of the inner bearing surface area of the left and right MLG axles to determine if they have been reworked using chromium plating, in accordance with Bombardier Service Bulletin 215-A462, dated June 2, 1993, or Revision 3, dated January 17, 2000. If the inner bearing surface of the MLG axle has not been reworked using chromium plating, no further action is required by this paragraph for that axle only.</P>
                            <P>(b) If the inner bearing surface of the MLG axle has been reworked using chromium plating, prior to further flight, perform an ultrasonic inspection to detect cracking in the axle, in accordance with Bombardier Service Bulletin 215-A462, dated June 2, 1993, or Revision 3, dated January 17, 2000.</P>
                            <P>(1) If no crack is detected during this inspection, repeat the ultrasonic inspection at intervals not to exceed 150 landings.</P>
                            <P>(2) If any crack is detected during this inspection, prior to further flight, remove the cracked axle and replace it with a serviceable axle that does not have an inner bearing surface that has been reworked using chromium plating, in accordance with the service bulletin.</P>
                            <HD SOURCE="HD1">New Requirements of This AD</HD>
                            <HD SOURCE="HD2">Dimensional Check/Follow-on Corrective Actions</HD>
                            <P>(c) Within 150 landings after the effective date of this AD: Do a dimensional check by measuring the diameter of the left and right MLG axles to determine if they have been reworked outside the dimensions specified in Canadair CL-215 Overhaul Manual PSP 298, or if the axle has unknown rework dimensions or the service life of that axle cannot be determined, in accordance with Bombardier Service Bulletin 215-A462, Revision 3, dated January 17, 2000.</P>
                            <P>(1) If any axle has been reworked outside the specified dimensions, or has unknown rework dimensions, or if the service life of that axle cannot be determined: Prior to further flight, do an ultrasonic inspection to detect cracking of the axle, in accordance with the service bulletin, and replace the axle with a serviceable axle before the accumulation of 1,050 total landings, in accordance with the service bulletin. Such replacement ends the repetitive inspections for that axle only.</P>
                            <P>(i) If no cracking is detected during the inspection required by paragraph (c)(1) of this AD, repeat the inspection at intervals not to exceed 150 landings, and replace with a serviceable axle before the accumulation of 1,050 total landings.</P>
                            <P>(ii) If any cracking is detected during the inspection required by paragraph (c)(1) of this AD, prior to further flight, replace the axle with a serviceable axle per the service bulletin.</P>
                            <P>(2) If the service life of the axle is known, and the axle has not been reworked outside the specified dimensions, no further action is required by this AD for that axle only.</P>
                            <HD SOURCE="HD2">Actions Done Per Previous Issues of Service Bulletin</HD>
                            <P>(d) Inspections and replacements done before the effective date of this AD in accordance with Canadair Alert Service Bulletin 215-A462, dated June 2, 1993; or Bombardier Service Bulletin 215-A462, Revision 1, dated August 26, 1996; or Revision 2, dated March 3, 1999; are considered acceptable for compliance with the applicable actions specified in this AD.</P>
                            <HD SOURCE="HD2">Alternative Methods of Compliance</HD>
                            <P>(e) In accordance with 14 CFR 39.19, the Manager, New York Aircraft Certification Office, FAA, is authorized to approve alternative methods of compliance for this AD.</P>
                            <NOTE>
                                <HD SOURCE="HED">Note 1:</HD>
                                <P>The subject of this AD is addressed in Canadian airworthiness directive CF-1993-08R3, dated March 30, 2000. </P>
                            </NOTE>
                              
                        </EXTRACT>
                    </SECTION>
                    <SIG>
                        <DATED>Issued in Renton, Washington, on November 28, 2003.</DATED>
                        <NAME>Kevin Mullin,</NAME>
                        <TITLE>Acting Manager, Transport Airplane Directorate, Aircraft Certification Service.</TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30221 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. 2002-NM-198-AD]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; Boeing Model 767-200, -300, and -300F Series Airplanes</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration, DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking (NPRM).</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document proposes the adoption of a new airworthiness directive (AD) that is applicable to certain Boeing Model 767-200, -300, and -300F series airplanes. This proposal would require performing, for both main landing gear (MLG), gap measurements of the upper and lower joint gaps; an ultrasonic inspection of the outer cylinder of the MLG for cracks between the downlock fitting attach lugs; and follow-on and corrective actions if necessary. This action is necessary to detect and correct cracks in the outer cylinder of the MLG, which could result in collapsed MLG and consequent reduced controllability of the airplane during takeoff and landing. This action is intended to address the identified unsafe condition.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received by January 20, 2004.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit comments in triplicate to the Federal Aviation Administration (FAA), Transport Airplane Directorate, ANM-114, Attention: Rules Docket No. 2002-NM-198-AD, 1601 Lind Avenue, SW., Renton, Washington 98055-4056. Comments may be inspected at this location between 9 a.m. and 3 p.m., Monday through Friday, except Federal holidays. Comments may be submitted via fax to (425) 227-1232. Comments may also be sent via the Internet using the following address: 
                        <E T="03">9-anm-nprmcomment@faa.gov.</E>
                         Comments sent via fax or the Internet must contain “Docket No. 2002-NM-198-AD” in the subject line and need not be submitted in triplicate. Comments sent via the Internet as attached electronic files must be formatted in Microsoft Word 97 or 2000 or ASCII text.
                    </P>
                    <P>The service information referenced in the proposed rule may be obtained from Boeing Commercial Airplane Group, P.O. Box 3707, Seattle, Washington 98124-2207. This information may be examined at the FAA, Transport Airplane Directorate, 1601 Lind Avenue, SW., Renton, Washington.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Suzanne Masterson, Aerospace Engineer, Airframe Branch, ANM-120S, FAA, Seattle Aircraft Certification Office, 1601 Lind Avenue, SW., Renton, Washington 98055-4056; telephone (425) 917-6441; fax (425) 917-6590.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Comments Invited</HD>
                <P>
                    Interested persons are invited to participate in the making of the proposed rule by submitting such written data, views, or arguments as they may desire. Communications shall identify the Rules Docket number and be submitted in triplicate to the address specified above. All communications 
                    <PRTPAGE P="67974"/>
                    received on or before the closing date for comments, specified above, will be considered before taking action on the proposed rule. The proposals contained in this action may be changed in light of the comments received.
                </P>
                <P>Submit comments using the following format:</P>
                <P>• Organize comments issue-by-issue. For example, discuss a request to change the compliance time and a request to change the service bulletin reference as two separate issues.</P>
                <P>• For each issue, state what specific change to the proposed AD is being requested.</P>
                <P>
                    • Include justification (
                    <E T="03">e.g.</E>
                    , reasons or data) for each request.
                </P>
                <P>Comments are specifically invited on the overall regulatory, economic, environmental, and energy aspects of the proposed rule. All comments submitted will be available, both before and after the closing date for comments, in the Rules Docket for examination by interested persons. A report summarizing each FAA-public contact concerned with the substance of this proposal will be filed in the Rules Docket.</P>
                <P>Commenters wishing the FAA to acknowledge receipt of their comments submitted in response to this action must submit a self-addressed, stamped postcard on which the following statement is made: “Comments to Docket Number 2002-NM-198-AD.” The postcard will be date stamped and returned to the commenter.</P>
                <HD SOURCE="HD1">Availability of NPRMs</HD>
                <P>Any person may obtain a copy of this NPRM by submitting a request to the FAA, Transport Airplane Directorate, ANM-114, Attention: Rules Docket No. 2002-NM-198-AD, 1601 Lind Avenue, SW., Renton, Washington 98055-4056.</P>
                <HD SOURCE="HD1">Discussion</HD>
                <P>The FAA has received a report indicating that a crack was found on the outer cylinder of the main landing gear (MLG) at the attach lugs for the drag strut downlock fitting on a Model 767-300 series airplane. The cause of the crack was due to heat damage from the upper bearing rubbing on the cylinder. Excessive torque on the downlock fitting attachment fasteners during production of Model 767-300 series airplanes produced local deflection of the outer cylinder, causing contact or interference with the upper bearing. This condition, if not corrected, could result in cracks in the outer cylinder of the MLG, which could result in collapsed MLG and consequent reduced controllability of the airplane during takeoff and landing.</P>
                <HD SOURCE="HD1">Similar Models</HD>
                <P>The subject area on certain Boeing Model 767-200 and -300F series airplanes is almost identical to that on the affected Boeing Model 767-300 series airplanes. Therefore, all of these models may be subject to the same unsafe condition.</P>
                <HD SOURCE="HD1">Explanation of Relevant Service Information</HD>
                <P>The FAA has reviewed and approved Boeing Service Bulletin 767-32A0196, Revision 2, dated May 15, 2003, which describes procedures, for both MLG, for performing gap measurements of the upper and lower joint gaps (includes measuring and recording upper and lower joint gaps twice); an ultrasonic inspection of the outer cylinder of the MLG for cracks between the downlock fitting attach lugs; and follow-on and corrective actions if necessary. The follow-on action includes restoring the MLG (includes installing shims as applicable, electrical bracket, and cotter pins; and marking the MLG). The corrective actions include overhauling the outer cylinder of the MLG; replacing the outer cylinder of the MLG with an interchangeable outer cylinder, and contacting the manufacturer if there is any crack in the outer cylinder that cannot be removed within the repair limits. Accomplishment of the actions specified in the service bulletin is intended to adequately address the identified unsafe condition.</P>
                <HD SOURCE="HD1">Explanation of Requirements of Proposed Rule</HD>
                <P>Since an unsafe condition has been identified that is likely to exist or develop on other products of this same type design, the proposed AD would require accomplishment of the actions specified in the service bulletin described previously, except as discussed below.</P>
                <HD SOURCE="HD1">Difference Between Proposed Rule and Service Bulletin</HD>
                <P>Operators should note that, although the service bulletin specifies that the manufacturer may be contacted for disposition of certain repair conditions, this proposal would require the repair to be accomplished per a method approved by the FAA, or per data meeting the type certification basis of the airplane approved by a Boeing Company Designated Engineering Representative who has been authorized by the FAA to make such findings.</P>
                <HD SOURCE="HD1">Cost Impact</HD>
                <P>There are approximately 833 airplanes of the affected design in the worldwide fleet. The FAA estimates that 353 airplanes of U.S. registry would be affected by this proposed AD, that it would take approximately 16 work hours per airplane to accomplish the proposed gap measurement and inspection, and that the average labor rate is $65 per work hour. Based on these figures, the cost impact of the proposed AD on U.S. operators is estimated to be $367,120, or $1,040 per airplane.</P>
                <P>The cost impact figures discussed above are based on assumptions that no operator has yet accomplished any of the proposed requirements of this AD action, and that no operator would accomplish those actions in the future if this proposed AD were not adopted. The cost impact figures discussed in AD rulemaking actions represent only the time necessary to perform the specific actions actually required by the AD. These figures typically do not include incidental costs, such as the time required to gain access and close up, planning time, or time necessitated by other administrative actions. Manufacturer warranty remedies may be available for labor costs associated with this proposed AD. As a result, the costs attributable to the proposed AD may be less than stated above.</P>
                <HD SOURCE="HD1">Regulatory Impact</HD>
                <P>The regulations proposed herein would not have a substantial direct effect on the States, on the relationship between the national Government and the States, or on the distribution of power and responsibilities among the various levels of government. Therefore, it is determined that this proposal would not have federalism implications under Executive Order 13132.</P>
                <P>
                    For the reasons discussed above, I certify that this proposed regulation (1) is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under the DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979); and (3) if promulgated, will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act. A copy of the draft regulatory evaluation prepared for this action is contained in the Rules Docket. A copy of it may be obtained by contacting the Rules Docket at the location provided under the caption 
                    <E T="02">ADDRESSES.</E>
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, Safety.</P>
                </LSTSUB>
                <PRTPAGE P="67975"/>
                <HD SOURCE="HD1">The Proposed Amendment</HD>
                <P>Accordingly, pursuant to the authority delegated to me by the Administrator, the Federal Aviation Administration proposes to amend part 39 of the Federal Aviation Regulations (14 CFR part 39) as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
                    <P>1. The authority citation for part 39 continues to read as follows:</P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>49 U.S.C. 106(g), 40113, 44701.</P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 39.13 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                        <P>2. Section 39.13 is amended by adding the following new airworthiness directive:</P>
                        <EXTRACT>
                            <FP SOURCE="FP-2">
                                <E T="04">Boeing:</E>
                                 Docket 2002-NM-198-AD.
                            </FP>
                            <P>
                                <E T="03">Applicability:</E>
                                 Model 767-200, -300, and -300F series airplanes, line numbers 1 through 883 inclusive; certificated in any category.
                            </P>
                            <P>
                                <E T="03">Compliance:</E>
                                 Required as indicated, unless accomplished previously.
                            </P>
                            <P>To detect and correct cracks in the outer cylinder of the main landing gear (MLG), which could result in collapsed MLG and consequent reduced controllability of the airplane during takeoff and landing, accomplish the following:</P>
                            <HD SOURCE="HD1">Service Bulletin References</HD>
                            <P>(a) The term “service bulletin,” as used in this AD, means the Accomplishment Instructions of Boeing Service Bulletin 767-32A0196, Revision 2, dated May 15, 2003.</P>
                            <HD SOURCE="HD1">Inspection and Corrective Actions</HD>
                            <P>(b) Within 18 months after the effective date of this AD, for both MLG, do a gap measurement of the upper and lower joint gaps (includes measuring and recording upper and lower joint gaps twice); and an ultrasonic inspection of the outer cylinder of the main landing gear for cracks between the downlock fitting attach lugs, per Part 1 of the service bulletin.</P>
                            <P>(c) If no crack is found during the inspection required by paragraph (b) of this AD, before further flight, do the restoration (includes installing shims as applicable, electrical bracket, and cotter pins; and marking the main landing gear) per the service bulletin.</P>
                            <P>(d) If any crack is found during the inspection required by paragraph (b) of this AD: Before further flight, overhaul the outer cylinder of the MLG or replace the outer cylinder of the MLG with an interchangeable outer cylinder per Part 2 of the service bulletin, except as provided by paragraph (e) of this AD.</P>
                            <P>(e) If any crack is found in the outer cylinder that cannot be removed within the repair limits specified in the service bulletin, during the overhaul specified in paragraph (d) of this AD, and the service bulletin specifies to contact Boeing for appropriate action: Before further flight, repair per a method approved by the Manager, Seattle Aircraft Certification Office (ACO), FAA; or per data meeting the type certification basis of the airplane approved by a Boeing Company Designated Engineering Representative who has been authorized by the Manager, Seattle ACO, to make such findings. For a repair method to be approved, the approval must specifically reference this AD.</P>
                            <NOTE>
                                <HD SOURCE="HED">Note 1:</HD>
                                <P>When the outer cylinder is re-installed, attach the downlock fittings onto the outer cylinder as specified in the applicable Boeing Component Maintenance Manual (CMM), document number 161T1000, Section 32-11-19, temporary revision (TR) 32-61, dated March 26, 2002 or Section 32-11-19 pages 712 through 716 dated July 01, 2002, or dated July 01, 2003; or CMM 32-11-20, TR 32-62, dated March 26, 2002, or Section 32-11-20 pages 718 through 722 dated July 01, 2002, or dated July 01, 2003. </P>
                            </NOTE>
                            <HD SOURCE="HD1">Actions Accomplished Per Previous Issue of Service Bulletin</HD>
                            <P>(f) Accomplishment of the applicable actions before the effective date of this AD per Boeing Service Bulletin 767-32A0196, dated August 1, 2002; or, Revision 1, dated September 26, 2002; are considered acceptable for compliance with the corresponding action specified in this AD.</P>
                            <HD SOURCE="HD1">Parts Installation</HD>
                            <P>(g) As of the effective date of this AD, no person may install a MLG on any airplane, unless the outer cylinder of the MLG has been inspected and follow-on and corrective actions have been accomplished per Boeing Service Bulletin 767-32A0196, Revision 2, dated May 15, 2003.</P>
                            <HD SOURCE="HD1">Alternative Methods of Compliance</HD>
                            <P>(h) In accordance with 14 CFR 39.19, the Manager, Seattle Aircraft Certification Office, FAA, is authorized to approve alternative methods of compliance for this AD.</P>
                        </EXTRACT>
                    </SECTION>
                    <SIG>
                        <DATED>Issued in Renton, Washington, on November 28, 2003.</DATED>
                        <NAME>Kevin Mullin,</NAME>
                        <TITLE>Acting Manager, Transport Airplane Directorate, Aircraft Certification Service.</TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30220 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. 2002-NM-174-AD]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; Boeing Model 737-300, -400, and -500 Series Airplanes</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration, DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking (NPRM).</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document proposes the supersedure of an existing airworthiness directive (AD), applicable to certain Boeing Model 737 series airplanes. That AD currently requires a one-time general visual inspection of the seat locks and seat tracks of the flightcrew seats to ensure that the seats lock in position and to verify that lock nuts and bolts of adequate length are installed on the rear track lock bracket, and corrective action, if necessary. This action would revise the applicability of the existing AD by adding airplanes. The actions specified by the proposed AD are intended to prevent uncommanded movement of the flightcrew seats during acceleration and take-off of the airplane, which could result in reduced controllability of the airplane. This action is intended to address the identified unsafe condition.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received by January 20, 2004.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit comments in triplicate to the Federal Aviation Administration (FAA), Transport Airplane Directorate, ANM-114, Attention: Rules Docket No. 2002-NM-174-AD, 1601 Lind Avenue, SW., Renton, Washington 98055-4056. Comments may be inspected at this location between 9 a.m. and 3 p.m., Monday through Friday, except Federal holidays. Comments may be submitted via fax to (425) 227-1232. Comments may also be sent via the Internet using the following address: 
                        <E T="03">9-anm-nprmcomment@faa.gov.</E>
                         Comments sent via fax or the Internet must contain “Docket No. 2002-NM-174-AD” in the subject line and need not be submitted in triplicate. Comments sent via the Internet as attached electronic files must be formatted in Microsoft Word 97 or 2000 or ASCII text.
                    </P>
                    <P>The service information referenced in the proposed rule may be obtained from Boeing Commercial Airplane Group, P.O. Box 3707, Seattle, Washington 98124-2207. This information may be examined at the FAA, Transport Airplane Directorate, 1601 Lind Avenue, SW., Renton, Washington.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Shannon Lennon, Aerospace Engineer, Cabin Safety and Environmental Systems Branch, ANM-150S, FAA, Seattle Aircraft Certification Office, 1601 Lind Avenue, SW., Renton, Washington; telephone (425) 917-6435; fax (425) 917-6590.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P> </P>
                <HD SOURCE="HD1">Comments Invited</HD>
                <P>
                    Interested persons are invited to participate in the making of the proposed rule by submitting such written data, views, or arguments as they may desire. Communications shall 
                    <PRTPAGE P="67976"/>
                    identify the Rules Docket number and be submitted in triplicate to the address specified above. All communications received on or before the closing date for comments, specified above, will be considered before taking action on the proposed rule. The proposals contained in this action may be changed in light of the comments received.
                </P>
                <P>Submit comments using the following format:</P>
                <P>• Organize comments issue-by-issue. For example, discuss a request to change the compliance time and a request to change the service bulletin reference as two separate issues.</P>
                <P>• For each issue, state what specific change to the proposed AD is being requested.</P>
                <P>
                    • Include justification (
                    <E T="03">e.g.</E>
                    , reasons or data) for each request.
                </P>
                <P>Comments are specifically invited on the overall regulatory, economic, environmental, and energy aspects of the proposed rule. All comments submitted will be available, both before and after the closing date for comments, in the Rules Docket for examination by interested persons. A report summarizing each FAA-public contact concerned with the substance of this proposal will be filed in the Rules Docket.</P>
                <P>Commenters wishing the FAA to acknowledge receipt of their comments submitted in response to this action must submit a self-addressed, stamped postcard on which the following statement is made: “Comments to Docket Number 2002-NM-174-AD.” The postcard will be date stamped and returned to the commenter.</P>
                <HD SOURCE="HD1">Availability of NPRMs</HD>
                <P>Any person may obtain a copy of this NPRM by submitting a request to the FAA, Transport Airplane Directorate, ANM-114, Attention: Rules Docket No. 2002-NM-174-AD, 1601 Lind Avenue, SW., Renton, Washington 98055-4056.</P>
                <HD SOURCE="HD1">Discussion</HD>
                <P>On May 18, 2000, the FAA issued AD 2000-10-21, amendment 39-11745 (65 FR 34063, May 26, 2000), applicable to certain Boeing Model 737 airplanes, to require a one-time general visual inspection of the seat locks and seat tracks of the flightcrew seats to ensure that the seats lock in position and to verify that lock nuts and bolts of adequate length are installed on the rear track lock bracket, and corrective action, if necessary. That action was prompted by reports indicating instances of the pilot seat sliding to the aft-most position during acceleration and take-off on certain Boeing Model 737 series airplanes. The requirements of that AD are intended to prevent uncommanded movement of the flightcrew seats during acceleration and take-off of the airplane, which could result in reduced controllability of the airplane.</P>
                <HD SOURCE="HD1">Actions Since Issuance of Previous Rule</HD>
                <P>Since the issuance of that AD, the airplane manufacturer has informed the FAA that additional airplanes may be equipped with IPECO flightcrew seats that are subject to the identified unsafe condition. Those seats may have been installed on airplanes out of operators' stock or from an airplane not yet modified per AD 2000-10-21, amendment 39-11745.</P>
                <HD SOURCE="HD1">Explanation of Relevant Service Information</HD>
                <P>We have reviewed and approved Boeing Alert Service Bulletin 737-25A1363, Revision 1, dated March 28, 2002, which revises the effectivity of the initial release (which was referenced as the appropriate source of service information for the actions required by AD 2000-10-21) of the service bulletin by adding additional airplanes. The procedures for a one-time general visual inspection and corrective actions if necessary specified in Revision 1 are essentially identical to those described in the initial release of the service bulletin. No more work is necessary on airplanes changed per the initial release of this service bulletin. Accomplishment of the actions specified in the alert service bulletin is intended to adequately address the identified unsafe condition.</P>
                <P>Boeing Alert Service Bulletin 737-25A1363, Revision 1, dated March 28, 2002, refers to IPECO Service Bulletin A001-25-47, dated January 13, 1992, as an additional source of service information for accomplishment of the inspection of the seat locks and seat tracks of the flightcrew seats and corrective action, if necessary.</P>
                <HD SOURCE="HD1">Explanation of Requirements of Proposed Rule</HD>
                <P>Since an unsafe condition has been identified that is likely to exist or develop on other products of this same type design, the proposed AD would supersede AD 2000-10-21 to continue to require a one-time general visual inspection of the seat locks and seat tracks of the flightcrew seats to ensure that the seats lock in position and to verify that lock nuts and bolts of adequate length are installed on the rear track lock bracket, and corrective action, if necessary. The proposed AD would also revise the applicability of the existing AD by adding airplanes. The actions would be required to be accomplished in accordance with the Boeing alert service bulletin described previously, except as discussed below.</P>
                <HD SOURCE="HD1">Difference Between Service Bulletin and Proposed AD</HD>
                <P>Operators should note that, although the Boeing alert service bulletin does not recommend a compliance time for accomplishment of the described actions, the FAA has determined that a 90-day compliance time would address the identified unsafe condition in a timely manner. In developing an appropriate compliance time for this proposed AD, we considered the degree of urgency associated with addressing the subject unsafe condition, the average utilization of the affected fleet, and the time necessary to perform the actions. In light of all of these factors, we find a 90-day compliance time for completion of the actions to be warranted, in that it represents an appropriate interval of time allowable for affected airplanes to continue to operate without compromising safety.</P>
                <HD SOURCE="HD1">Explanation of Change Made to Existing Requirements</HD>
                <P>For clarification, we have revised the definition of a “general visual inspection” in this proposed AD.</P>
                <HD SOURCE="HD1">Cost Impact</HD>
                <P>There are approximately 1,385 airplanes of the affected design in the worldwide fleet. The FAA estimates that 282 airplanes of U.S. registry would be affected by this proposed AD.</P>
                <P>For Group 1 airplanes listed in Boeing Alert Service Bulletin 737-25A1363, Revision 1: The actions that are currently required by AD 2000-10-21 take approximately 3 work hours per airplane to accomplish, at an average labor rate of $65 per work hour. Based on these figures, the cost impact of the currently required actions on U.S. operators is estimated to be $195 per airplane.</P>
                <P>For Group 2 airplanes listed in Boeing Alert Service Bulletin 737-25A1363, Revision 1: The new actions that are proposed in this AD action would take approximately 3 work hours per airplane to accomplish, at an average labor rate of $65 per work hour. Based on these figures, the cost impact of the proposed requirements of this AD on U.S. operators is estimated to be $195 per airplane.</P>
                <P>
                    The cost impact figures discussed above are based on assumptions that no operator has yet accomplished any of the current or proposed requirements of this AD action, and that no operator would accomplish those actions in the future if this AD were not adopted. The 
                    <PRTPAGE P="67977"/>
                    cost impact figures discussed in AD rulemaking actions represent only the time necessary to perform the specific actions actually required by the AD. These figures typically do not include incidental costs, such as the time required to gain access and close up, planning time, or time necessitated by other administrative actions.
                </P>
                <HD SOURCE="HD1">Regulatory Impact</HD>
                <P>The regulations proposed herein would not have a substantial direct effect on the States, on the relationship between the national Government and the States, or on the distribution of power and responsibilities among the various levels of government. Therefore, it is determined that this proposal would not have federalism implications under Executive Order 13132.</P>
                <P>
                    For the reasons discussed above, I certify that this proposed regulation (1) is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under the DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979); and (3) if promulgated, will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act. A copy of the draft regulatory evaluation prepared for this action is contained in the Rules Docket. A copy of it may be obtained by contacting the Rules Docket at the location provided under the caption 
                    <E T="02">ADDRESSES</E>
                    .
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Proposed Amendment</HD>
                <P>Accordingly, pursuant to the authority delegated to me by the Administrator, the Federal Aviation Administration proposes to amend part 39 of the Federal Aviation Regulations (14 CFR part 39) as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
                    <P>1. The authority citation for part 39 continues to read as follows:</P>
                    <AUTH>
                        <HD SOURCE="HED">
                            <E T="04">Authority:</E>
                              
                        </HD>
                        <P>49 U.S.C. 106(g), 40113, 44701.</P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 39.13 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                        <P>2. Section 39.13 is amended by removing amendment 39-11745 (65 FR 34063, May 26, 2000), and by adding a new airworthiness directive (AD), to read as follows:</P>
                        <EXTRACT>
                            <FP SOURCE="FP-2">
                                <E T="04">Boeing:</E>
                                 Docket 2002-NM-174-AD. Supersedes AD 2000-10-21, Amendment 39-11745. 
                            </FP>
                            <P>
                                <E T="03">Applicability:</E>
                                 Model 737-300, -400, and -500 series airplanes equipped with IPECO flightcrew seats, as listed in Boeing Alert Service Bulletin 737-25A1363, Revision 1, dated March 28, 2002; certificated in any category.
                            </P>
                            <P>
                                <E T="03">Compliance:</E>
                                 Required as indicated, unless accomplished previously.
                            </P>
                            <P>To prevent uncommanded movement of the flightcrew seats during acceleration and take-off of the airplane, which could result in reduced controllability of the airplane, accomplish the following:</P>
                            <HD SOURCE="HD1">One-Time Inspection</HD>
                            <P>(a) Perform a one-time general visual inspection of the seat locks and seat tracks of the flightcrew seats to ensure that the seats lock in position and to verify that lock nuts and bolts of adequate length are installed on the rear track lock bracket, at the applicable time and per the Work Instructions of the applicable service bulletin specified in Table 1 of this AD. Table 1 follows:</P>
                            <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s100,r100,r100">
                                <TTITLE>Table 1.—Compliance Time/Service Bulletin </TTITLE>
                                <BOXHD>
                                    <CHED H="1">Airplanes— </CHED>
                                    <CHED H="1">Compliance Time— </CHED>
                                    <CHED H="1">Service Bulletin— </CHED>
                                </BOXHD>
                                <ROW>
                                    <ENT I="01">For Group 1 airplanes listed in Boeing Alert Service Bulletin 737-25A1363, Revision 1, dated March 28, 2002</ENT>
                                    <ENT>Within 90 days after September 26, 2001 (the effective date AD 2000-10-21, amendment 39-11745)</ENT>
                                    <ENT>Boeing Alert Service Bulletin 737-25A1363, dated November 5, 1998. </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">For Group 2 airplanes listed in Boeing Alert Service Bulletin 737-25A1363, Revision 1, dated March 28, 2002</ENT>
                                    <ENT>Within 90 days after the effective date of this AD</ENT>
                                    <ENT>Boeing Alert Services Bulletin 737-25A1363, Revision 1, dated March 28, 2002. </ENT>
                                </ROW>
                            </GPOTABLE>
                            <NOTE>
                                <HD SOURCE="HED">
                                    <E T="04">Note 1:</E>
                                      
                                </HD>
                                <P>For the purposes of this AD, a general visual inspection is defined as: “A visual examination of an interior or exterior area, installation, or assembly to detect obvious damage, failure, or irregularity. This level of inspection is made from within touching distance unless otherwise specified. A mirror may be necessary to enhance visual access to all exposed surfaces in the inspection area. This level of inspection is made under normally available lighting conditions such as daylight, hangar lighting, flashlight, or droplight and may require removal or opening of access panels or doors. Stands, ladders, or platforms may be required to gain proximity to the area being checked.”</P>
                            </NOTE>
                            <HD SOURCE="HD1">Corrective Action</HD>
                            <P>(1) If the seat lock pin fully engages in all lock positions of the seat track, and the rear track lock bracket is correctly installed: No further action is required by this AD.</P>
                            <P>(2) If the seat lock pin does not fully engage in all positions of the seat track, and lock nuts and bolts of adequate length are not installed on the rear track lock bracket: Prior to further flight, install lock nuts and bolts of adequate length on the track lock bracket and verify proper seat movement and seat lock operation, in accordance with the applicable service bulletin.</P>
                            <NOTE>
                                <HD SOURCE="HED">
                                    <E T="04">Note 2:</E>
                                      
                                </HD>
                                <P>Boeing Alert Service Bulletin 737-25A1363, Revision 1, dated March 28, 2002, refers to IPECO Service Bulletin A001-25-47, dated January 13, 1992, as an additional source of service information for accomplishment of the actions required by paragraph (a) of this AD.</P>
                            </NOTE>
                            <HD SOURCE="HD1">Actions Accomplished Per Previous Issue of Service Bulletin</HD>
                            <P>(b) For Group 2 airplanes: Inspections and corrective actions accomplished before the effective date of this AD per Boeing Alert Service Bulletin 737-25A1363, dated November 5, 1998, are considered acceptable for compliance with the corresponding actions specified in this AD.</P>
                            <HD SOURCE="HD1">Alternative Methods of Compliance</HD>
                            <P>(c)(1) In accordance with 14 CFR 39.19, the Manager, Seattle Aircraft Certification Office (ACO), FAA, is authorized to approve alternative methods of compliance (AMOCs) for this AD.</P>
                            <P>(2) Alternative methods of compliance, approved previously per AD 2000-10-21, amendment 39-11745, are approved as alternative methods of compliance with the requirements of this AD.</P>
                        </EXTRACT>
                    </SECTION>
                    <SIG>
                        <DATED>Issued in Renton, Washington, on November 28, 2003.</DATED>
                        <NAME>Kevin Mullin,</NAME>
                        <TITLE>Acting Manager, Transport Airplane Directorate, Aircraft Certification Service.</TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30219 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <PRTPAGE P="67978"/>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. 2002-NM-215-AD]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; McDonnell Douglas Model DC-9-81 (MD-81), DC-9-82 (MD-82), DC-9-83 (MD-83), DC-9-87 (MD-87), and Model MD-88 Airplanes</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration, DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking (NPRM).</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document proposes the adoption of a new airworthiness directive (AD) that is applicable to certain McDonnell Douglas Model DC-9-81 (MD-81), DC-9-82 (MD-82), DC-9-83 (MD-83), DC-9-87 (MD-87), and Model MD-88 airplanes. This proposal would require replacement of certain freeze protection ribbon heaters in the lavatory water supply system, and flushing, cleaning, and sterilizing the potable water system; disconnecting, coiling, and stowing the wiring of the freeze protection ribbon heater; or removal of freeze protection heaters. This action is necessary to prevent failure of freeze protection ribbon heaters, which could result in the charring, scorching, smoking, and shorting out of freeze protection ribbon heaters in the lavatory water supply system. This condition, if not corrected, could also result in electrical arcing of freeze protection ribbon heaters, leading to fire and damage to water lines and components under the lavatory sink. This action is intended to address the identified unsafe condition.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received by January 20, 2004.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit comments in triplicate to the Federal Aviation Administration (FAA), Transport Airplane Directorate, ANM-114, Attention: Rules Docket No. 2002-NM-215-AD, 1601 Lind Avenue, SW., Renton, Washington 98055-4056. Comments may be inspected at this location between 9 a.m. and 3 p.m., Monday through Friday, except Federal holidays. Comments may be submitted via fax to (425) 227-1232. Comments may also be sent via the Internet using the following address: 
                        <E T="03">9-anm-nprmcomment@faa.gov</E>
                        . Comments sent via fax or the Internet must contain “Docket No. 2002-NM-215-AD” in the subject line and need not be submitted in triplicate. Comments sent via the Internet as attached electronic files must be formatted in Microsoft Word 97 or 2000 or ASCII text.
                    </P>
                    <P>The service information referenced in the proposed rule may be obtained from Boeing Commercial Aircraft Group, Long Beach Division, 3855 Lakewood Boulevard, Long Beach, California 90846, Attention: Data and Service Management, Dept. C1-L5A (D800-0024). This information may be examined at the FAA, Transport Airplane Directorate, 1601 Lind Avenue, SW., Renton, Washington; or at the FAA, Los Angeles Aircraft Certification Office, 3960 Paramount Boulevard, Lakewood, California.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Cheyenne Del Carmen, Aerospace Engineer, Systems and Equipment Branch, ANM-130L, FAA, Los Angeles Aircraft Certification Office, 3960 Paramount Boulevard, Lakewood, California 90712-4137; telephone (562) 627-5338; fax (562) 627-5210.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P> </P>
                <HD SOURCE="HD1">Comments Invited</HD>
                <P>Interested persons are invited to participate in the making of the proposed rule by submitting such written data, views, or arguments as they may desire. Communications shall identify the Rules Docket number and be submitted in triplicate to the address specified above. All communications received on or before the closing date for comments, specified above, will be considered before taking action on the proposed rule. The proposals contained in this action may be changed in light of the comments received.</P>
                <P>Submit comments using the following format:</P>
                <P>• Organize comments issue-by-issue. For example, discuss a request to change the compliance time and a request to change the service bulletin reference as two separate issues.</P>
                <P>• For each issue, state what specific change to the proposed AD is being requested.</P>
                <P>
                    • Include justification (
                    <E T="03">e.g.</E>
                    , reasons or data) for each request.
                </P>
                <P>Comments are specifically invited on the overall regulatory, economic, environmental, and energy aspects of the proposed rule. All comments submitted will be available, both before and after the closing date for comments, in the Rules Docket for examination by interested persons. A report summarizing each FAA-public contact concerned with the substance of this proposal will be filed in the Rules Docket.</P>
                <P>Commenters wishing the FAA to acknowledge receipt of their comments submitted in response to this action must submit a self-addressed, stamped postcard on which the following statement is made: “Comments to Docket Number 2002-NM-215-AD.” The postcard will be date stamped and returned to the commenter.</P>
                <HD SOURCE="HD1">Availability of NPRMs</HD>
                <P>Any person may obtain a copy of this NPRM by submitting a request to the FAA, Transport Airplane Directorate, ANM-114, Attention: Rules Docket No. 2002-NM-215-AD, 1601 Lind Avenue, SW., Renton, Washington 98055-4056.</P>
                <HD SOURCE="HD1">Discussion</HD>
                <P>The FAA has received reports of charring, scorching, smoking, and shorting out of freeze protection ribbon heaters in the lavatory water supply system of certain McDonnell Douglas Model DC-9-81 (MD-81), DC-9-82 (MD-82), DC-9-83 (MD-83), DC-9-87 (MD-87), and MD-88 airplanes. We also received reports of burning and scorching to water lines and components under the lavatory sink. Investigation revealed that the freeze protection ribbon heaters were failing. This condition, if not corrected, could result in electrical arcing of freeze protection ribbon heaters, leading to fire and damage to water lines and components under the lavatory sink.</P>
                <HD SOURCE="HD1">Explanation of Relevant Service Information</HD>
                <P>The FAA has reviewed and approved Boeing Alert Service Bulletin MD80-25A381, dated August 5, 2002. This service bulletin describes procedures for replacing the existing freeze protection ribbon heater in the lavatory water supply system with a new, reidentified heater hose assembly, and flushing, cleaning, and sterilizing the potable water system; disconnecting, coiling, and stowing the wiring of the freeze protection ribbon heater in the lavatory water supply system; or removing the freeze protection ribbon heater from the lavatory water supply system. Accomplishment of the actions specified in the Boeing service bulletin is intended to adequately address the identified unsafe condition.</P>
                <P>
                    Boeing Alert Service Bulletin MD80-25A381 refers to Jamco Corporation Service Bulletin MD080-25-829, dated February 14, 2002, as an additional source of service information for instructions on replacing the existing freeze protection ribbon heater with a new, reidentified heater hose assembly for Model DC-9-81 (MD-81), DC-9-82 (MD-82), DC-9-83 (MD-83), DC-9-87 (MD-87), and MD-88 airplanes.
                    <PRTPAGE P="67979"/>
                </P>
                <HD SOURCE="HD1">Explanation of Requirements of Proposed Rule</HD>
                <P>Since an unsafe condition has been identified that is likely to exist or develop on other products of this same type design, the proposed AD would require accomplishment of the actions specified in the Boeing service bulletin described previously.</P>
                <HD SOURCE="HD1">Cost Impact</HD>
                <P>There are approximately 1,180 airplanes of the affected design in the worldwide fleet. The FAA estimates that 724 airplanes of U.S. registry would be affected by this proposed AD, and that each airplane has approximately 3 lavatories, and that the average 1 labor rate is $65 per work hour. Table 1 shows the estimated cost impact, based upon the action taken, for airplanes affected by this proposed AD.</P>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s100,12,r50,r50,r50">
                    <TTITLE>Table 1.—Cost Impact </TTITLE>
                    <BOXHD>
                        <CHED H="1">Action </CHED>
                        <CHED H="1">Work hours per lavatory </CHED>
                        <CHED H="1">Parts cost per lavatory </CHED>
                        <CHED H="1">Cost per lavatory </CHED>
                        <CHED H="1">Total cost </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Replace the existing freeze protection ribbon heater with a new, reidentified heater hose assemply; and flush, clean, and sterilize the potable water system; or </ENT>
                        <ENT>6 </ENT>
                        <ENT>$2,344 to $3,208 (Depending on lavoratory module configuration) </ENT>
                        <ENT>$2,734 to $3,598 (Depending on lavoratory module configuration) </ENT>
                        <ENT>$5,938,248 to $7,814,856 (Depending on lavatory module configuration) or $8,202 to $10,794 per airplane. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Disconnect, coil, and stow the wiring of the freeze protection ribbon heater; or </ENT>
                        <ENT>2 </ENT>
                        <ENT>$0 </ENT>
                        <ENT>$130 </ENT>
                        <ENT>$282,360 or $390 per airplane. </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Remove the freeze protection ribbon heater </ENT>
                        <ENT>3 </ENT>
                        <ENT>$0 </ENT>
                        <ENT>$195 </ENT>
                        <ENT>$423,540 or $585 per airplane. </ENT>
                    </ROW>
                </GPOTABLE>
                <P>The cost impact figures discussed above are based on assumptions that no operator has yet accomplished any of the proposed requirements of this AD action, and that no operator would accomplish those actions in the future if this proposed AD were not adopted. The cost impact figures discussed in AD rulemaking actions represent only the time necessary to perform the specific actions actually required by the AD. These figures typically do not include incidental costs, such as the time required to gain access and close up, planning time, or time necessitated by other administrative actions.</P>
                <HD SOURCE="HD1">Regulatory Impact</HD>
                <P>The regulations proposed herein would not have a substantial direct effect on the States, on the relationship between the national Government and the States, or on the distribution of power and responsibilities among the various levels of government. Therefore, it is determined that this proposal would not have federalism implications under Executive Order 13132.</P>
                <P>
                    For the reasons discussed above, I certify that this proposed regulation (1) is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under the DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979); and (3) if promulgated, will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act. A copy of the draft regulatory evaluation prepared for this action is contained in the Rules Docket. A copy of it may be obtained by contacting the Rules Docket at the location provided under the caption 
                    <E T="02">ADDRESSES</E>
                    .
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Proposed Amendment</HD>
                <P>Accordingly, pursuant to the authority delegated to me by the Administrator, the Federal Aviation Administration proposes to amend part 39 of the Federal Aviation Regulations (14 CFR part 39) as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
                    <P>1. The authority citation for part 39 continues to read as follows:</P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>49 U.S.C. 106(g), 40113, 44701.</P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 39.13 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                        <P>2. Section 39.13 is amended by adding the following new airworthiness directive:</P>
                        <EXTRACT>
                            <FP SOURCE="FP-2">
                                <E T="04">McDonnell Douglas:</E>
                                 Docket 2002-NM-215-AD. 
                            </FP>
                            <P>
                                <E T="03">Applicability:</E>
                                 Model DC-9-81 (MD-81), DC-9-82 (MD-82), DC-9-83 (MD-83), DC-9-87 (MD-87), and MD-88 airplanes, as listed in Boeing Alert Service Bulletin MD80-25A381, dated August 5, 2002; certificated in any category.
                            </P>
                            <P>
                                <E T="03">Compliance:</E>
                                 Required as indicated, unless accomplished previously.
                            </P>
                            <P>To prevent failure of freeze protection ribbon heaters, which could result in the charring, scorching, smoking, and shorting out of freeze protection ribbon heaters in the lavatory water supply system and could also result in electrical arcing of freeze protection ribbon heaters, leading to fire and damage to water lines and components under the lavatory sink; accomplish the following:</P>
                            <HD SOURCE="HD1">Corrective Actions</HD>
                            <P>(a) Within 18 months of the effective date of this AD, do the actions specified in paragraph (a)(1), (a)(2), or (a)(3) of this AD per the Accomplishment Instructions of Boeing Alert Service Bulletin MD80-25A381, dated August 5, 2002.</P>
                            <P>(1) Replace the existing freeze protection ribbon heater in the lavatory water supply system with a new, reidentified heater hose assembly. Flush, clean, and sterilize the potable water system; or</P>
                            <P>(2) Disconnect, coil, and stow the wiring of the freeze protection ribbon heater in the lavatory water supply system; or</P>
                            <P>(3) Remove the freeze protection ribbon heater from the lavatory water supply system.</P>
                            <NOTE>
                                <HD SOURCE="HED">Note 1:</HD>
                                <P>Boeing Alert Service Bulletin MD80-25A381 refers to Jamco Corporation Service Bulletin MD080-25-829, dated February 14, 2002, as an additional source of service information for instructions on replacing the existing freeze protection ribbon heater with a new, reidentified heater hose assembly for Model DC-9-81 (MD-81), DC-9-82 (MD-82), DC-9-83 (MD-83), DC-9-87 (MD-87), and Model MD-88 airplanes. </P>
                            </NOTE>
                            <HD SOURCE="HD1">Alternative Methods of Compliance</HD>
                            <P>(b) In accordance with 14 CFR 39.19, the Manager, Los Angeles Aircraft Certification Office, FAA, is authorized to approve alternative methods of compliance for this AD.</P>
                        </EXTRACT>
                    </SECTION>
                    <SIG>
                        <DATED>Issued in Renton, Washington, on November 28, 2003.</DATED>
                        <NAME>Ali Bahrami,</NAME>
                        <TITLE>Acting Manager, Transport Airplane Directorate, Aircraft Certification Service.</TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30218 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <PRTPAGE P="67980"/>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. 2002-NM-226-AD]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; Dornier Model 328-100 Series Airplanes</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration, DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking (NPRM).</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document proposes the adoption of a new airworthiness directive (AD) that is applicable to certain Dornier Model 328-100 series airplanes. This proposal would require a one-time inspection of certain engine control cables to determine the batch number on the end fitting, and replacement of affected cables with new cables. This action is necessary to prevent failure of defective engine control cables, which could result in loss of the engine controls, and consequent reduced controllability of the airplane. This action is intended to address the identified unsafe condition.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received by January 5, 2004.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit comments in triplicate to the Federal Aviation Administration (FAA), Transport Airplane Directorate, ANM-114, Attention: Rules Docket No. 2002-NM-226-AD, 1601 Lind Avenue, SW., Renton, Washington 98055-4056. Comments may be inspected at this location between 9 a.m. and 3 p.m., Monday through Friday, except Federal holidays. Comments may be submitted via fax to (425) 227-1232. Comments may also be sent via the Internet using the following address: 
                        <E T="03">9-anm-nprmcomment@faa.gov.</E>
                         Comments sent via fax or the Internet must contain “Docket No. 2002-NM-226-AD” in the subject line and need not be submitted in triplicate. Comments sent via the Internet as attached electronic files must be formatted in Microsoft Word 97 or 2000 or ASCII text.
                    </P>
                    <P>The service information referenced in the proposed rule may be obtained from AvCraft Aerospace GmbH, P.O. Box 1103, D-82230 Wessling, Germany. This information may be examined at the FAA, Transport Airplane Directorate, 1601 Lind Avenue, SW., Renton, Washington.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Dan Rodina, Aerospace Engineer, International Branch, ANM-116, FAA, Transport Airplane Directorate, 1601 Lind Avenue, SW., Renton, Washington 98055-4056; telephone (425) 227-2125; fax (425) 227-1149.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Comments Invited</HD>
                <P>Interested persons are invited to participate in the making of the proposed rule by submitting such written data, views, or arguments as they may desire. Communications shall identify the Rules Docket number and be submitted in triplicate to the address specified above. All communications received on or before the closing date for comments, specified above, will be considered before taking action on the proposed rule. The proposals contained in this action may be changed in light of the comments received.</P>
                <P>Submit comments using the following format: </P>
                <P>• Organize comments issue-by-issue. For example, discuss a request to change the compliance time and a request to change the service bulletin reference as two separate issues.</P>
                <P>• For each issue, state what specific change to the proposed AD is being requested.</P>
                <P>
                    • Include justification (
                    <E T="03">e.g.</E>
                    , reasons or data) for each request.
                </P>
                <P>Comments are specifically invited on the overall regulatory, economic, environmental, and energy aspects of the proposed rule. All comments submitted will be available, both before and after the closing date for comments, in the Rules Docket for examination by interested persons. A report summarizing each FAA-public contact concerned with the substance of this proposal will be filed in the Rules Docket.</P>
                <P>Commenters wishing the FAA to acknowledge receipt of their comments submitted in response to this action must submit a self-addressed, stamped postcard on which the following statement is made: “Comments to Docket Number 2002-NM-226-AD.” The postcard will be date stamped and returned to the commenter.</P>
                <HD SOURCE="HD1">Availability of NPRMs</HD>
                <P>Any person may obtain a copy of this NPRM by submitting a request to the FAA, Transport Airplane Directorate, ANM-114, Attention: Rules Docket No. 2002-NM-226-AD, 1601 Lind Avenue, SW., Renton, Washington 98055-4056.</P>
                <HD SOURCE="HD1">Discussion</HD>
                <P>The Luftfahrt-Bundesamt (LBA), which is the airworthiness authority for Germany, notified the FAA that an unsafe condition may exist on certain Dornier Model 328-100 series airplanes. The LBA advises that, during testing, the manufacturer of the engine control cables, SARMA, found evidence of cracking on the end fittings of two specific batches of parts, due to a manufacturing problem. Such cracking, if not corrected, could result in failure of the engine control cables, subsequent loss of the engine controls, and consequent reduced controllability of the airplane.</P>
                <HD SOURCE="HD1">Explanation of Relevant Service Information</HD>
                <P>Dornier has issued Service Bulletin SB-328-76-409, Revision 1, dated May 17, 2002, which describes procedures for inspecting engine control cables having part number 001A761A1130-016 to determine the manufacturing batch number, and replacing affected engine control cables with new cables. Accomplishment of the actions specified in the service bulletin is intended to adequately address the identified unsafe condition. The LBA classified this service bulletin as mandatory and issued German airworthiness directive 2002-252, dated September 5, 2002, to ensure the continued airworthiness of these airplanes in Germany.</P>
                <HD SOURCE="HD1">FAA's Conclusions</HD>
                <P>This airplane model is manufactured in Germany and is type certificated for operation in the United States under the provisions of § 21.29 of the Federal Aviation Regulations (14 CFR 21.29) and the applicable bilateral airworthiness agreement. Pursuant to this bilateral airworthiness agreement, the LBA has kept the FAA informed of the situation described above. The FAA has examined the findings of the LBA, reviewed all available information, and determined that AD action is necessary for products of this type design that are certificated for operation in the United States.</P>
                <HD SOURCE="HD1">Explanation of Requirements of Proposed AD</HD>
                <P>Since an unsafe condition has been identified that is likely to exist or develop on other airplanes of the same type design registered in the United States, the proposed AD would require accomplishment of the actions specified in the service bulletin described previously, except as discussed below.</P>
                <HD SOURCE="HD1">Differences Between the Service Bulletin and Proposed AD</HD>
                <P>
                    Although the service bulletin specifies to send any engine control cable removed from the airplane to the parts manufacturer, this proposed AD does not require that action.
                    <PRTPAGE P="67981"/>
                </P>
                <HD SOURCE="HD1">Clarification of Compliance Time</HD>
                <P>Operators should note that the service bulletin recommends doing the inspection at the “next scheduled maintenance event,” and replacing any affected engine control cable at “the next scheduled C-check (4,000 FH).” The German airworthiness directive recommends replacing any affected engine control cable “not later than the next scheduled C-check.” Because “C-check” schedules vary among operators, this proposed AD would require accomplishment of the inspection within 4,000 flight hours after the effective date of the AD, and replacement of any affected cable before further flight. We find that compliance within 4,000 flight hours after the effective date of this AD is appropriate for affected airplanes to continue to operate without compromising safety.</P>
                <HD SOURCE="HD1">Cost Impact</HD>
                <P>We estimate that 53 airplanes of U.S. registry would be affected by this proposed AD, that it would take approximately one work hour per airplane to accomplish the proposed actions, at an average labor rate of $65 per work hour. Based on these figures, the cost impact of the proposed AD on U.S. operators is estimated to be $3,445, or $65 per airplane.</P>
                <P>Replacement of an engine control cable, if required, would take approximately 8 work hours, at an average labor rate of $65 per work hour. Parts would be provided at no cost to operators. Based on these figures, the cost impact of the proposed replacement of the engine control cables is $520 per cable.</P>
                <P>The cost impact figures discussed above are based on assumptions that no operator has yet accomplished any of the proposed requirements of this AD action, and that no operator would accomplish those actions in the future if this AD were not adopted. The cost impact figures discussed in AD rulemaking actions represent only the time necessary to perform the specific actions actually required by the AD. These figures typically do not include incidental costs, such as the time required to gain access and close up, planning time, or time necessitated by other administrative actions.</P>
                <HD SOURCE="HD1">Regulatory Impact</HD>
                <P>The regulations proposed herein would not have a substantial direct effect on the States, on the relationship between the national Government and the States, or on the distribution of power and responsibilities among the various levels of government. Therefore, it is determined that this proposal would not have federalism implications under Executive Order 13132.</P>
                <P>
                    For the reasons discussed above, I certify that this proposed regulation (1) is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under the DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979); and (3) if promulgated, will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act. A copy of the draft regulatory evaluation prepared for this action is contained in the Rules Docket. A copy of it may be obtained by contacting the Rules Docket at the location provided under the caption 
                    <E T="02">ADDRESSES</E>
                    .
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Proposed Amendment</HD>
                <P>Accordingly, pursuant to the authority delegated to me by the Administrator, the Federal Aviation Administration proposes to amend part 39 of the Federal Aviation Regulations (14 CFR part 39) as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
                    <P>1. The authority citation for part 39 continues to read as follows:</P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>49 U.S.C. 106(g), 40113, 44701.</P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 39.13 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                        <P>2. Section 39.13 is amended by adding the following new airworthiness directive:</P>
                        <EXTRACT>
                            <FP SOURCE="FP-2">
                                <E T="04">Fairchild Dornier GMBH (Formerly Dornier Luftfahrt GmbH):</E>
                                Docket 2002-NM-226-AD.
                            </FP>
                            <P>
                                <E T="03">Applicability:</E>
                                 Model 328-100 series airplanes, as listed in Dornier Service Bulletin SB-328-76-409, Revision 1, dated May 17, 2002; certificated in any category.
                            </P>
                            <P>
                                <E T="03">Compliance:</E>
                                 Required as indicated, unless accomplished previously.
                            </P>
                            <P>To prevent failure of defective engine control cables, which could result in loss of the engine controls, and consequent reduced controllability of the airplane, accomplish the following:</P>
                            <HD SOURCE="HD1">Identification of Manufacturing Batch Number</HD>
                            <P>(a) Within 4,000 flight hours after the effective date of this AD, do a detailed inspection of the engine control cables for cables that have part number (P/N) 001A761A1130-016, engraved with manufacturing batch number (MBN) 1000125850 or 1000144210 installed. Inspect in accordance with the Accomplishment Instructions of Dornier Service Bulletin SB-328-76-409, Revision 1, dated May 17, 2002.</P>
                            <NOTE>
                                <HD SOURCE="HED">Note 1:</HD>
                                <P>For the purposes of this AD, a detailed inspection is defined as: “An intensive visual examination of a specific structural area, system, installation, or assembly to detect damage, failure, or irregularity. Available lighting is normally supplemented with a direct source of good lighting at intensity deemed appropriate by the inspector. Inspection aids such as mirror, magnifying lenses, etc., may be used. Surface cleaning and elaborate access procedures may be required.” </P>
                            </NOTE>
                            <P>(1) If no engine control cable has a P/N and an MBN specified in paragraph (a) of this AD, no further action is required by this paragraph.</P>
                            <P>(2) If any engine control cable having the P/N or an MBN specified in paragraph (a) of this AD is found, before further flight, replace the cable in accordance with the Accomplishment Instructions of the service bulletin. Although the service bulletin specifies to send any engine control cable that has been removed from the airplane to the part manufacturer, this AD does not require that action.</P>
                            <HD SOURCE="HD1">Parts Installation</HD>
                            <P>(b) As of the effective date of this AD, no person may install an engine control cable having P/N 001A761A1130-016, engraved with MBN 1000125850 or 1000144210, on any airplane.</P>
                            <HD SOURCE="HD1">Alternative Methods of Compliance</HD>
                            <P>(c) In accordance with 14 CFR 39.19, the Manager, International Branch, ANM-116, FAA, Transport Airplane Directorate, is authorized to approve alternative methods of compliance for this AD.</P>
                            <NOTE>
                                <HD SOURCE="HED">Note 2:</HD>
                                <P>The subject of this AD is addressed in German airworthiness directive 2002-252, dated September 5, 2002. </P>
                            </NOTE>
                        </EXTRACT>
                    </SECTION>
                    <SIG>
                        <DATED>Issued in Renton, Washington, on November 28, 2003.</DATED>
                        <NAME>Kevin Mullin,</NAME>
                        <TITLE>Acting Manager, Transport Airplane Directorate, Aircraft Certification Service.</TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30225 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. 2001-NM-333-AD]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; Fokker Model F.28 Mark 1000, 2000, 3000, and 4000 Series Airplanes</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration, DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking (NPRM).</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        This document proposes the adoption of a new airworthiness directive (AD) that is applicable to 
                        <PRTPAGE P="67982"/>
                        certain Fokker Model F.28 Mark 1000, 2000, 3000, and 4000 series airplanes. This proposal would require repetitive general visual inspections, lubrication, and tests of the release mechanism for the service/emergency door; and corrective actions if necessary. This proposal also provides an optional terminating action for the repetitive inspections and lubrication. This action is necessary to prevent failure of the release mechanism on the service/emergency door, which could result in the inability to open the service/emergency door during an emergency evacuation. This action is intended to address the identified unsafe condition.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received by January 5, 2004.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit comments in triplicate to the Federal Aviation Administration (FAA), Transport Airplane Directorate, ANM-114, Attention: Rules Docket No. 2001-NM-333-AD, 1601 Lind Avenue, SW., Renton, Washington 98055-4056. Comments may be inspected at this location between 9 a.m. and 3 p.m., Monday through Friday, except Federal holidays. Comments may be submitted via fax to (425) 227-1232. Comments may also be sent via the Internet using the following address: 
                        <E T="03">9-anm-nprmcomment@faa.gov.</E>
                         Comments sent via fax or the Internet must contain “Docket No. 2001-NM-333-AD” in the subject line and need not be submitted in triplicate. Comments sent via the Internet as attached electronic files must be formatted in Microsoft Word 97 or 2000 or ASCII text.
                    </P>
                    <P>The service information referenced in the proposed rule may be obtained from Fokker Services B.V., P.O. Box 231, 2150 AE Nieuw-Vennep, the Netherlands. This information may be examined at the FAA, Transport Airplane Directorate, 1601 Lind Avenue, SW., Renton, Washington.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Tom Rodriguez, Aerospace Engineer, International Branch, ANM-116, FAA, Transport Airplane Directorate, 1601 Lind Avenue, SW., Renton, Washington 98055-4056; telephone (425) 227-1137; fax (425) 227-1149.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Comments Invited</HD>
                <P>Interested persons are invited to participate in the making of the proposed rule by submitting such written data, views, or arguments as they may desire. Communications shall identify the Rules Docket number and be submitted in triplicate to the address specified above. All communications received on or before the closing date for comments, specified above, will be considered before taking action on the proposed rule. The proposals contained in this action may be changed in light of the comments received.</P>
                <P>Submit comments using the following format:</P>
                <P>• Organize comments issue-by-issue. For example, discuss a request to change the compliance time and a request to change the service bulletin reference as two separate issues.</P>
                <P>• For each issue, state what specific change to the proposed AD is being requested.</P>
                <P>
                    • Include justification (
                    <E T="03">e.g.</E>
                    , reasons or data) for each request.
                </P>
                <P>Comments are specifically invited on the overall regulatory, economic, environmental, and energy aspects of the proposed rule. All comments submitted will be available, both before and after the closing date for comments, in the Rules Docket for examination by interested persons. A report summarizing each FAA-public contact concerned with the substance of this proposal will be filed in the Rules Docket.</P>
                <P>Commenters wishing the FAA to acknowledge receipt of their comments submitted in response to this action must submit a self-addressed, stamped postcard on which the following statement is made: “Comments to Docket Number 2001-NM-333-AD.” The postcard will be date stamped and returned to the commenter.</P>
                <HD SOURCE="HD1">Availability of NPRMs</HD>
                <P>Any person may obtain a copy of this NPRM by submitting a request to the FAA, Transport Airplane Directorate, ANM-114, Attention: Rules Docket No. 2001-NM-333-AD, 1601 Lind Avenue, SW., Renton, Washington 98055-4056.</P>
                <HD SOURCE="HD1">Discussion</HD>
                <P>The Civil Aviation Authority—The Netherlands (CAA-NL), which is the airworthiness authority for the Netherlands, notified the FAA that an unsafe condition may exist on certain Fokker Model F.28 Mark 1000, 2000, 3000, and 4000 series airplanes. The CAA-NL advises that it has received reports that, during evacuation training, the service/emergency door release mechanism was unable to release the door rollers, which resulted in the inability to open the service/emergency door. Investigation revealed that the release mechanism did not operate properly due to lack of lubrication on the door rollers. Service experience has shown that the reliability of the release mechanism can degrade if it is not regularly maintained (inspected, lubricated, and tested). Improperly maintained service/emergency door release mechanisms, if not corrected, could result in the inability to open the service/emergency door during an emergency evacuation.</P>
                <HD SOURCE="HD1">Explanation of Relevant Service Information</HD>
                <P>Fokker Services B.V. has issued Fokker Service Bulletin F28/52-118, dated June 25, 2001, which describes procedures for repetitive inspections, lubrication, and tests of the release mechanism for the service/emergency door; and corrective actions if necessary. These procedures include inspection and lubrication of the four roller assemblies, actuating mechanism (including measurement of the torque of the torsion spring), and Bowden cables; adjustment of the Bowden cables; and measurement of the operating force for the emergency release button. The corrective actions include rework/repair or replacement of damaged or corroded parts with new parts of the same type.</P>
                <P>Fokker Service B.V. has also issued Fokker Service Bulletin F28/52-89, dated October 31, 1983, which describes procedures for replacing the service/emergency door by removing the Bowden cable-operated door and installing a push-pull rod-operated door. Accomplishment of this service bulletin eliminates the need for the repetitive inspections and lubrication. For certain airplanes, Fokker Service Bulletin F28/52-89 recommends prior or concurrent accomplishment of Part VII of Fokker Service Bulletin F28/52-55, Revision 1, dated February 28, 1977. Part VII describes procedures for modification of the roller assemblies in the service/emergency door by installing a second pull-up mechanism.</P>
                <P>Accomplishment of the actions specified in Service Bulletin F28/52-118, dated June 25, 2001, is intended to adequately address the identified unsafe condition. The CAA-NL classified Fokker Service Bulletin F28/52-118 as mandatory and issued Dutch airworthiness directive 2001-094, dated July 31, 2001, to ensure the continued airworthiness of these airplanes in the Netherlands.</P>
                <HD SOURCE="HD1">FAA's Conclusions</HD>
                <P>
                    This airplane model is manufactured in the Netherlands and is type certificated for operation in the United States under the provisions of § 21.29 of the Federal Aviation Regulations (14 CFR 21.29) and the applicable bilateral airworthiness agreement. Pursuant to this bilateral airworthiness agreement, the CAA-NL has kept the FAA informed of the situation described above. The FAA has examined the findings of the 
                    <PRTPAGE P="67983"/>
                    CAA-NL, reviewed all available information, and determined that AD action is necessary for products of this type design that are certificated for operation in the United States.
                </P>
                <HD SOURCE="HD1">Explanation of Requirements of Proposed Rule</HD>
                <P>Since an unsafe condition has been identified that is likely to exist or develop on other airplanes of the same type design registered in the United States, the proposed rule would require accomplishment of the actions specified in Fokker Service Bulletin F28/52-118, dated June 25, 2001, described previously, except as discussed below.</P>
                <HD SOURCE="HD1">Differences Between Dutch Airworthiness Directive, Service Bulletin, and Proposed Rule</HD>
                <P>Fokker Service Bulletin F28/52-118 and the Dutch airworthiness directive specify that if any discrepancy or corroded part is found during any inspection, the applicable corrective action must be accomplished within 1,500 flight hours or 18 months after finding the discrepancy or corroded part, whichever occurs first. We have determined that, because of the safety implications of a potentially inoperative emergency door, this proposed rule would require accomplishment of the applicable corrective action before further flight. This difference has been coordinated with the CAA-NL.</P>
                <P>Also, where the service bulletin and the Dutch airworthiness directive specify inspections of various parts of the release mechanism for the service/emergency door, this proposed rule identifies these as general visual inspections. A note has been added to the proposed rule to define that type of inspection.</P>
                <HD SOURCE="HD1">Cost Impact</HD>
                <P>The FAA estimates that 6 airplanes of U.S. registry would be affected by this proposed AD, that it would take approximately 15 work hours per airplane to accomplish the proposed actions, and that the average labor rate is $65 per work hour. Based on these figures, the cost impact of the proposed AD on U.S. operators is estimated to be $5,850, or $975 per inspection cycle.</P>
                <P>The cost impact figure discussed above is based on assumptions that no operator has yet accomplished any of the proposed requirements of this AD action, and that no operator would accomplish those actions in the future if this AD were not adopted. The cost impact figures discussed in AD rulemaking actions represent only the time necessary to perform the specific actions actually required by the AD. These figures typically do not include incidental costs, such as the time required to gain access and close up, planning time, or time necessitated by other administrative actions.</P>
                <HD SOURCE="HD1">Regulatory Impact</HD>
                <P>The regulations proposed herein would not have a substantial direct effect on the States, on the relationship between the national Government and the States, or on the distribution of power and responsibilities among the various levels of government. Therefore, it is determined that this proposal would not have federalism implications under Executive Order 13132.</P>
                <P>
                    For the reasons discussed above, I certify that this proposed regulation (1) is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under the DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979); and (3) if promulgated, will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act. A copy of the draft regulatory evaluation prepared for this action is contained in the Rules Docket. A copy of it may be obtained by contacting the Rules Docket at the location provided under the caption 
                    <E T="02">ADDRESSES.</E>
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Proposed Amendment</HD>
                <P>Accordingly, pursuant to the authority delegated to me by the Administrator, the Federal Aviation Administration proposes to amend part 39 of the Federal Aviation Regulations (14 CFR part 39) as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
                    <P>1. The authority citation for part 39 continues to read as follows:</P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>49 U.S.C. 106(g), 40113, 44701.</P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 39.13 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                        <P>2. Section 39.13 is amended by adding the following new airworthiness directive:</P>
                        <EXTRACT>
                            <FP SOURCE="FP-2">
                                <E T="04">Fokker Services B.V.:</E>
                                 Docket 2001-NM-333-AD.
                            </FP>
                            <P>
                                <E T="03">Applicability:</E>
                                 Model F.28 Mark 1000, 2000, 3000, and 4000 series airplanes as listed in the effectivity of Fokker Service Bulletin F28/52-118, dated June 25, 2001; certificated in any category.
                            </P>
                            <P>
                                <E T="03">Compliance:</E>
                                 Required as indicated, unless accomplished previously.
                            </P>
                            <P>To prevent failure of the release mechanism on the service/emergency door, which could result in the inability to open the service/emergency door during an emergency evacuation, accomplish the following:</P>
                            <HD SOURCE="HD1">Inspection, Lubrication, Testing, and Corrective Actions</HD>
                            <P>(a) Within 12 months after the effective date of this AD: Do a general visual inspection (including measurement of the torque for the actuating mechanism torsion spring), lubricate, and test to verify proper operation of the emergency release mechanism of the service/emergency door by accomplishing all of the actions specified in paragraphs A. through R. of the Accomplishment Instructions of Fokker Service Bulletin F28/52-118, dated June 25, 2001.</P>
                            <NOTE>
                                <HD SOURCE="HED">Note 1:</HD>
                                <P>For the purposes of this AD, a general visual inspection is defined as: “A visual examination of an interior or exterior area, installation, or assembly to detect obvious damage, failure, or irregularity. This level of inspection is made from within touching distance unless otherwise specified. A mirror may be necessary to enhance visual access to all exposed surfaces in the inspection area. This level of inspection is made under normally available lighting conditions such as daylight, hangar lighting, flashlight, or droplight and may require removal or opening of access panels or doors. Stands, ladders, or platforms may be required to gain proximity to the area being checked.” </P>
                            </NOTE>
                            <P>(1) If no discrepant or corroded part is found during the inspection required by paragraph (a) of this AD: Repeat the actions specified in paragraph (a) of this AD thereafter at intervals not to exceed 1,500 flight hours or 18 months, whichever occurs first.</P>
                            <P>(2) If any discrepancy (including a torque value which exceeds the limits specified in the applicable service bulletin, improperly installed part, or damaged part) is found, or if a corroded part is found, during any inspection required by paragraph (a) of this AD: Before further flight, do the applicable corrective action in accordance with the Accomplishment Instructions of the service bulletin. Repeat the actions specified in paragraph (a) of this AD thereafter at intervals not to exceed 1,500 flight hours or 18 months, whichever occurs first.</P>
                            <HD SOURCE="HD1">Optional Terminating Action and Concurrent Service Bulletin</HD>
                            <P>(b) Replacement of the Bowden cable-operated service/emergency door with a push-pull rod-operated service/emergency door, in accordance with Fokker Service Bulletin F28/52-89, dated October 31, 1983, constitutes terminating action for the repetitive inspections and lubrication required by paragraph (a) of this AD.</P>
                            <P>(c) For airplanes with serial numbers 11003 to 11051 inclusive, 11991, and 11992: Prior to or concurrent with paragraph (b) of this AD, accomplish the modification specified in part VII of Fokker Service Bulletin F28/52-55, Revision 1, dated February 28, 1977.</P>
                            <HD SOURCE="HD1">Alternative Methods of Compliance</HD>
                            <P>
                                (d) In accordance with 14 CFR 39.19, the Manager, International Branch, ANM-116, 
                                <PRTPAGE P="67984"/>
                                FAA, is authorized to approve alternative methods of compliance for this AD.
                            </P>
                            <NOTE>
                                <HD SOURCE="HED">Note 2:</HD>
                                <P>The subject of this AD is addressed in Dutch airworthiness directive 2001-094, dated July 31, 2001. </P>
                            </NOTE>
                        </EXTRACT>
                    </SECTION>
                    <SIG>
                        <DATED>Issued in Renton, Washington, on November 28, 2003.</DATED>
                        <NAME>Kevin Mullin,</NAME>
                        <TITLE>Acting Manager, Transport Airplane Directorate, Aircraft Certification Service.</TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30224 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Federal Aviation Administration</SUBAGY>
                <CFR>14 CFR Part 39</CFR>
                <DEPDOC>[Docket No. 2001-NM-284-AD]</DEPDOC>
                <RIN>RIN 2120-AA64</RIN>
                <SUBJECT>Airworthiness Directives; Airbus Model A330 and A340-200 and -300 Series Airplanes</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration, DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking (NPRM).</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document proposes the adoption of a new airworthiness directive (AD) that is applicable to certain Airbus Model A330 and A340-200 and -300 series airplanes. This proposal would require repetitive inspections for proper installation of the parachute pins located in the escape slides/rafts at the door 3 Type I emergency exits on the left and right sides of the airplane; a one-time inspection of the associated electrical harnesses for the escape slides/rafts for proper routing and installation; and corrective actions if necessary. This proposal also would require adjustment of the speed lacing for the soft covers of the escape slides/rafts, which would terminate the repetitive inspections. This action is necessary to prevent failure of the escape slides/rafts to deploy correctly at door 3 Type I emergency exits, which could result in the escape slides/rafts being unusable during an emergency evacuation, and consequent injury to passengers or crew members. This action is intended to address the identified unsafe condition.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received by January 5, 2004.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Submit comments in triplicate to the Federal Aviation Administration (FAA), Transport Airplane Directorate, ANM-114, Attention: Rules Docket No. 2001-NM-284-AD, 1601 Lind Avenue, SW., Renton, Washington 98055-4056. Comments may be inspected at this location between 9 a.m. and 3 p.m., Monday through Friday, except Federal holidays. Comments may be submitted via fax to (425) 227-1232. Comments may also be sent via the Internet using the following address: 
                        <E T="03">9-anm-nprmcomment@faa.gov.</E>
                         Comments sent via fax or the Internet must contain “Docket No. 2001-NM284-AD” in the subject line and need not be submitted in triplicate. Comments sent via the Internet as attached electronic files must be formatted in Microsoft Word 97 or 2000 or ASCII text.
                    </P>
                    <P>The service information referenced in the proposed rule may be obtained from Airbus, 1 Rond Point Maurice Bellonte, 31707 Blagnac Cedex, France. This information may be examined at the FAA, Transport Airplane Directorate, 1601 Lind Avenue, SW., Renton, Washington.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Tim Backman, Aerospace Engineer, International Branch, ANM-116, FAA, Transport Airplane Directorate, 1601 Lind Avenue, SW., Renton, Washington 98055-4056; telephone (425) 227-2797; fax (425) 227-1149.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P> </P>
                <HD SOURCE="HD1">Comments Invited</HD>
                <P>Interested persons are invited to participate in the making of the proposed rule by submitting such written data, views, or arguments as they may desire. Communications shall identify the Rules Docket number and be submitted in triplicate to the address specified above. All communications received on or before the closing date for comments, specified above, will be considered before taking action on the proposed rule. The proposals contained in this action may be changed in light of the comments received.</P>
                <P>Submit comments using the following format:</P>
                <P>• Organize comments issue-by-issue. For example, discuss a request to change the compliance time and a request to change the service bulletin reference as two separate issues.</P>
                <P>• For each issue, state what specific change to the proposed AD is being requested.</P>
                <P>
                    • Include justification (
                    <E T="03">e.g.</E>
                    , reasons or data) for each request.
                </P>
                <P>Comments are specifically invited on the overall regulatory, economic, environmental, and energy aspects of the proposed rule. All comments submitted will be available, both before and after the closing date for comments, in the Rules Docket for examination by interested persons. A report summarizing each FAA-public contact concerned with the substance of this proposal will be filed in the Rules Docket.</P>
                <P>Commenters wishing the FAA to acknowledge receipt of their comments submitted in response to this action must submit a self-addressed, stamped postcard on which the following statement is made: “Comments to Docket Number 2001-NM-284-AD.” The postcard will be date stamped and returned to the commenter.</P>
                <HD SOURCE="HD1">Availability of NPRMs</HD>
                <P>Any person may obtain a copy of this NPRM by submitting a request to the FAA, Transport Airplane Directorate, ANM-114, Attention: Rules Docket No. 2001-NM-284-AD, 1601 Lind Avenue, SW., Renton, Washington 98055-4056.</P>
                <HD SOURCE="HD1">Discussion</HD>
                <P>The Direction Generale de l'Aviation Civile (DGAC), which is the airworthiness authority for France, notified the FAA that an unsafe condition may exist on certain Airbus Model A330 and A340-200 and -300 series airplanes. The DGAC advises that, during a scheduled maintenance operation, an escape slide/raft at a door 3 Type I emergency exit did not deploy. Further investigation revealed that the parachute pin was not correctly installed and had rotated from its normal position and dropped through the first section of lacing on the soft cover of the escape slide/raft, which prevented the soft cover from opening the escape slide/raft. During another inspection it was discovered that the electrical harness associated with the escape slide/raft was not correctly installed and was not properly routed. Incorrect installation and/or routing of the electrical harness could prevent slide/raft detachment from the door after inflation. These conditions, if not corrected, could result in failure of the escape slides/rafts to deploy correctly at door 3 Type I emergency exits, on the left and right sides of the airplane, which could result in the escape slides/rafts being unusable during an emergency evacuation, and consequent injury to passengers or crew members.</P>
                <HD SOURCE="HD1">Explanation of Relevant Service Information</HD>
                <P>
                    Airbus has issued All Operator Telexes (AOT) A330-25A3154 (for Model A330 series airplanes) and A340-25A4172 (for Model A340-200 and -300 series airplanes), both dated July 26, 2001. These AOTs describe procedures for repetitive inspections for proper installation of the parachute pins located in the escape slides/rafts at the door 3 Type I emergency exits, on the 
                    <PRTPAGE P="67985"/>
                    left and right sides of the airplane, a one-time detailed inspection for proper installation and routing of the associated electrical harnesses; and corrective actions if necessary. Corrective actions for the parachute pins include adjustment of the speed lacing for the soft cover of the escape slides/rafts to prevent the parachute pins from moving from their original position. This action eliminates the need for the repetitive inspections of the parachute pins. Corrective actions for the electrical harnesses include relocating the quick-disconnect connectors. Accomplishment of the actions specified in the AOTs is intended to adequately address the identified unsafe condition. The DGAC classified these AOTs as mandatory and issued French airworthiness directives 2001-359(B) R3, dated October 30, 2002, and 2001-360(B) R1, dated February 6, 2002, to ensure the continued airworthiness of these airplanes in France.
                </P>
                <P>Both AOTs reference Goodrich Aircraft Evacuation Systems Alert Service Bulletin 7A1509-25A324, dated July 16, 2001, as an additional source of service information for adjusting the speed lacing.</P>
                <HD SOURCE="HD1">FAA's Conclusions</HD>
                <P>These airplane models are manufactured in France and are type certificated for operation in the United States under the provisions of § 21.29 of the Federal Aviation Regulations (14 CFR 21.29) and the applicable bilateral airworthiness agreement. Pursuant to this bilateral airworthiness agreement, the DGAC has kept the FAA informed of the situation described above. The FAA has examined the findings of the DGAC, reviewed all available information, and determined that AD action is necessary for products of this type design that are certificated for operation in the United States.</P>
                <HD SOURCE="HD1">Explanation of Requirements of Proposed Rule</HD>
                <P>Since an unsafe condition has been identified that is likely to exist or develop on other airplanes of the same type design registered in the United States, the proposed AD would require accomplishment of the actions specified in the applicable Airbus AOT described previously, except as discussed below.</P>
                <HD SOURCE="HD1">Difference Between Proposed Rule and Referenced AOTs</HD>
                <P>Operators should note that, although the referenced AOTs describe procedures for reporting inspection results to Airbus, this proposed AD would not require those actions. The FAA does not need this information from operators.</P>
                <HD SOURCE="HD1">Cost Impact</HD>
                <P>The FAA estimates that 14 Model A330 series airplanes of U.S. registry would be affected by this proposed AD, and that it would take approximately 1 work hour per airplane to accomplish the proposed inspections at the average labor rate of $65 per work hour. Based on these figures, the cost impact of the proposed inspections on U.S. operators is estimated to be $910, or $65 per airplane.</P>
                <P>It would take approximately 3 work hours per airplane to adjust the speed lacing for the escape slide/raft soft cover at an average labor rate of $65 per work hour. Based on these figures, the cost impact of the proposed adjustment of the speed lacing for the escape slide/raft soft cover on U.S. operators is estimated to be $2,730, or $195 per airplane.</P>
                <P>The cost impact figures discussed above are based on assumptions that no operator has yet accomplished any of the proposed requirements of this AD action, and that no operator would accomplish those actions in the future if this AD were not adopted. The cost impact figures discussed in AD rulemaking actions represent only the time necessary to perform the specific actions actually required by the AD. These figures typically do not include incidental costs, such as the time required to gain access and close up, planning time, or time necessitated by other administrative actions.</P>
                <P>Currently, there are no Model A340 series airplanes on the U.S. Register. However, should an affected airplane be imported and placed on the U.S. Register in the future, it would require 1 work hour per airplane to accomplish the proposed inspections and 3 work hours per airplane to accomplish the proposed adjustment of the speed lacing for the escape slide/raft soft cover, at an average labor rate of $65 per work hour. Based on these figures, the cost impact of the proposed AD for Model A340 operators would be $260 per airplane.</P>
                <HD SOURCE="HD1">Regulatory Impact</HD>
                <P>The regulations proposed herein would not have a substantial direct effect on the States, on the relationship between the national Government and the States, or on the distribution of power and responsibilities among the various levels of government. Therefore, it is determined that this proposal would not have federalism implications under Executive Order 13132.</P>
                <P>
                    For the reasons discussed above, I certify that this proposed regulation (1) is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under the DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979); and (3) if promulgated, will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act. A copy of the draft regulatory evaluation prepared for this action is contained in the Rules Docket. A copy of it may be obtained by contacting the Rules Docket at the location provided under the caption 
                    <E T="02">ADDRESSES.</E>
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39</HD>
                    <P>Air transportation, Aircraft, Aviation safety, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Proposed Amendment</HD>
                <P>Accordingly, pursuant to the authority delegated to me by the Administrator, the Federal Aviation Administration proposes to amend part 39 of the Federal Aviation Regulations (14 CFR part 39) as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
                    <P>1. The authority citation for part 39 continues to read as follows:</P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>49 U.S.C. 106(g), 40113, 44701.</P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 39.13 </SECTNO>
                        <SUBJECT>[Amended]</SUBJECT>
                        <P>2. Section 39.13 is amended by adding the following new airworthiness directive:</P>
                        <EXTRACT>
                            <FP SOURCE="FP-2">
                                <E T="04">Airbus:</E>
                                 Docket 2001-NM-284-AD.
                            </FP>
                            <P>
                                <E T="03">Applicability:</E>
                                 Model A330 and A340-200 and -300 series airplanes equipped with an escape slide/raft having any part ­number (P/N) 7A1509-101 through 7A1509-117 inclusive, and any serial number AD001 through AD0855 inclusive, at door 3 Type I emergency exits; certificated in any category.
                            </P>
                            <P>
                                <E T="03">Compliance:</E>
                                 Required as indicated, unless accomplished previously.
                            </P>
                            <P>To prevent failure of the escape slides/rafts to deploy correctly at door 3 Type I emergency exits, which could result in the escape slides/rafts being unusable during an emergency evacuation, and consequent injury to passengers or crew members, accomplish the following:</P>
                            <HD SOURCE="HD1">Inspections</HD>
                            <P>
                                (a) Within 550 flight hours after the effective date of this AD: Do a detailed inspection of the escape slides/rafts located at door 3 Type I emergency exits, on the left and right sides of the airplane, for correct installation of the parachute pins, and a one-time detailed inspection of the associated electrical harnesses for correct installation of the quick-disconnect connector, in accordance with paragraphs 4.1 and 4.2 of Airbus All Operator Telex (AOT) A330-25A3154 (for Model A330 series airplanes) or A340-25A4172 (for Model A340-200 and -300 series airplanes), dated July 26, 2001; as 
                                <PRTPAGE P="67986"/>
                                applicable. If any parachute pin or quick disconnect connector is incorrectly installed, before further flight, do the corrective actions per the applicable AOT. Repeat the inspections of the parachute pins thereafter at intervals not to exceed 1,000 flight hours until accomplishment of paragraph (b) of this AD.
                            </P>
                            <NOTE>
                                <HD SOURCE="HED">Note 1:</HD>
                                <P>For the purposes of this AD, a detailed inspection is defined as: “An intensive visual examination of a specific structural area, system, installation, or assembly to detect damage, failure, or irregularity. Available lighting is normally supplemented with a direct source of good lighting at intensity deemed appropriate by the inspector. Inspection aids such as mirror, magnifying lenses, etc., may be used. Surface cleaning and elaborate access procedures may be required.” </P>
                            </NOTE>
                            <NOTE>
                                <HD SOURCE="HED">Note 2:</HD>
                                <P>Repetitive inspections of the electrical harnesses are not required. </P>
                            </NOTE>
                            <HD SOURCE="HD1">Terminating Action for Repetitive Inspections</HD>
                            <P>(b) Within 18 months after the effective date of this AD: Adjust the speed lacing for the soft covers of the escape slides/rafts located at door 3 Type I emergency exits, in accordance with paragraph 4.3 of Airbus AOT A330-25A3154 (for Model A330 series airplanes) or A340-25A4172 (for Model A340-200 and -300 series airplanes), both dated July 26, 2001; as applicable. This adjustment terminates the repetitive inspections of the parachute pins required by paragraph (a) of this AD.</P>
                            <NOTE>
                                <HD SOURCE="HED">Note 3:</HD>
                                <P>The AOTs reference Goodrich Aircraft Evacuation Systems Alert Service Bulletin 7A1509-25A324, dated July 16, 2001, as an additional source of service information for adjusting the speed lacing. </P>
                            </NOTE>
                            <HD SOURCE="HD1">Parts Installation</HD>
                            <P>(c) As of the effective date of this AD, no person may install on any airplane an escape slide/raft having any P/N 7A1509-101 through 7A1509-117 inclusive unless the parachute pin has been inspected and the speed lacing has been adjusted in accordance with paragraphs (a) and (b) of this AD.</P>
                            <HD SOURCE="HD1">Alternative Methods of Compliance</HD>
                            <P>(d) In accordance with 14 CFR 39.19, the Manager, International Branch, ANM-116, FAA, Transport Airplane Directorate, is authorized to approve alternative methods of compliance for this AD.</P>
                            <NOTE>
                                <HD SOURCE="HED">Note 4:</HD>
                                <P>The subject of this AD is addressed in French airworthiness directives 2001-359(B) R3, dated October 30, 2002, and 2001-360(B) R1, dated February 6, 2002. </P>
                            </NOTE>
                        </EXTRACT>
                    </SECTION>
                    <SIG>
                        <DATED>Issued in Renton, Washington, on November 28, 2003.</DATED>
                        <NAME>Kevin Mullin,</NAME>
                        <TITLE>Acting Manager, Transport Airplane Directorate, Aircraft Certification Service.</TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30223 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Federal Aviation Administration </SUBAGY>
                <CFR>14 CFR Part 39 </CFR>
                <DEPDOC>[Docket No. 2001-NM-272-AD] </DEPDOC>
                <RIN>RIN 2120-AA64 </RIN>
                <SUBJECT>Airworthiness Directives; BAE Systems (Operations) Limited Model BAe 146-100A and -200A Series Airplanes </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration, DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking (NPRM). </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document proposes the adoption of a new airworthiness directive (AD) that is applicable to all BAE Systems (Operations) Limited Model BAe 146-100A and -200A series airplanes. This proposal would require an inspection to determine the part number of the inner links of the side stays for the main landing gear (MLG), and replacement of the inner links with new parts, if necessary. This action is necessary to prevent the failure of the MLG, which could result in damage to the airplane structure or injury to airplane occupants. This action is intended to address the identified unsafe condition. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received by January 5, 2004. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Submit comments in triplicate to the Federal Aviation Administration (FAA), Transport Airplane Directorate, ANM-114, Attention: Rules Docket No. 2001-NM-272-AD, 1601 Lind Avenue, SW., Renton, Washington 98055-4056. Comments may be inspected at this location between 9 a.m. and 3 p.m., Monday through Friday, except Federal holidays. Comments may be submitted via fax to (425) 227-1232. Comments may also be sent via the Internet using the following address: 9-anm-nprmcomment@faa.gov. Comments sent via fax or the Internet must contain “Docket No. 2001-NM-272-AD” in the subject line and need not be submitted in triplicate. Comments sent via the Internet as attached electronic files must be formatted in Microsoft Word 97 or 2000 or ASCII text. </P>
                    <P>The service information referenced in the proposed rule may be obtained from British Aerospace Regional Aircraft American Support, 13850 Mclearen Road, Herndon, Virginia 20171. This information may be examined at the FAA, Transport Airplane Directorate, 1601 Lind Avenue, SW., Renton, Washington. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Todd Thompson, Aerospace Engineer, International Branch, ANM-116, FAA, Transport Airplane Directorate, 1601 Lind Avenue, SW., Renton, Washington 98055-4056; telephone (425) 227-1175; fax (425) 227-1149. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Comments Invited </HD>
                <P>Interested persons are invited to participate in the making of the proposed rule by submitting such written data, views, or arguments as they may desire. Communications shall identify the Rules Docket number and be submitted in triplicate to the address specified above. All communications received on or before the closing date for comments, specified above, will be considered before taking action on the proposed rule. The proposals contained in this action may be changed in light of the comments received.</P>
                <P>Submit comments using the following format: </P>
                <P>• Organize comments issue-by-issue. For example, discuss a request to change the compliance time and a request to change the service bulletin reference as two separate issues. </P>
                <P>• For each issue, state what specific change to the proposed AD is being requested. </P>
                <P>
                    • Include justification (
                    <E T="03">e.g.</E>
                    , reasons or data) for each request. 
                </P>
                <P>Comments are specifically invited on the overall regulatory, economic, environmental, and energy aspects of the proposed rule. All comments submitted will be available, both before and after the closing date for comments, in the Rules Docket for examination by interested persons. A report summarizing each FAA-public contact concerned with the substance of this proposal will be filed in the Rules Docket. </P>
                <P>Commenters wishing the FAA to acknowledge receipt of their comments submitted in response to this action must submit a self-addressed, stamped postcard on which the following statement is made: “Comments to Docket Number 2001-NM-272-AD.” The postcard will be date stamped and returned to the commenter. </P>
                <HD SOURCE="HD1">Availability of NPRMs </HD>
                <P>Any person may obtain a copy of this NPRM by submitting a request to the FAA, Transport Airplane Directorate, ANM-114, Attention: Rules Docket No. 2001-NM-272-AD, 1601 Lind Avenue, SW., Renton, Washington 98055-4056. </P>
                <HD SOURCE="HD1">Discussion </HD>
                <P>
                    The Civil Aviation Authority (CAA), which is the airworthiness authority for 
                    <PRTPAGE P="67987"/>
                    the United Kingdom, notified the FAA that an unsafe condition may exist on all BAE Systems (Operations) Limited Model BAe 146-100A and -200A series airplanes. The CAA advises that the safe life for the inner links of the main landing gear (MLG) side stays is listed incorrectly in the Airworthiness Limitations section of the Aircraft Maintenance Manual (AMM) at Issue 73. The safe life is listed incorrectly in the AMM as 60,000 total landings, rather than the actual safe life of either 57,500 total landings for BAe 146-100A series airplanes, or 37,400 total landings for BAe 146-200A series airplanes. Inner links with certain part numbers could be subject to failure if allowed to remain in service past the actual safe life for the part. This condition, if not corrected, could result in the failure of the MLG and subsequent damage to the airplane structure or injury to airplane occupants. 
                </P>
                <HD SOURCE="HD1">Explanation of Relevant Service Information </HD>
                <P>BAE Systems (Operations) Limited has issued Service Bulletin ISB.32-166, dated May 28, 2001, which describes procedures for an inspection to determine the part number of the side stay inner links for the MLG, and replacement of the side stay inner links with new parts, if necessary. The CAA classified this service bulletin as mandatory and issued British airworthiness directive 005-05-2001 in order to assure the continued airworthiness of this airplane in the United Kingdom. </P>
                <P>The BAE Systems (Operations) Limited service bulletin references Messier-Dowty Service Bulletin 146-32-153, dated May 29, 2001, as an additional source of service information for accomplishment of the inspection and replacement, if necessary. </P>
                <HD SOURCE="HD1">FAA's Conclusions </HD>
                <P>These airplane models are manufactured in the United Kingdom and are type certificated for operation in the United States under the provisions of § 21.29 of the Federal Aviation Regulations (14 CFR 21.29) and the applicable bilateral airworthiness agreement. Pursuant to this bilateral airworthiness agreement, the CAA has kept the FAA informed of the situation described above. The FAA has examined the findings of the CAA, reviewed all available information, and determined that AD action is necessary for products of this type design that are certificated for operation in the United States. </P>
                <HD SOURCE="HD1">Explanation of Requirements of Proposed Rule </HD>
                <P>Since an unsafe condition has been identified that is likely to exist or develop on other airplanes of the same type design registered in the United States, the proposed AD would require accomplishment of the actions specified in the service bulletin described previously, except as discussed below. </P>
                <HD SOURCE="HD1">Differences Between Proposed Rule and Referenced Service Bulletins </HD>
                <P>Although Messier-Dowty Service Bulletin 146-32-153, and BAE Systems (Operations) Limited Service Bulletin ISB.32-166, specify to submit certain information to each manufacturer, this proposed AD does not include such requirements. </P>
                <P>Although Messier-Dowty Service Bulletin 146-32-153 specifies that operators may contact the manufacturer for information on the safe remaining life of side stays used at different operating weights, this proposed AD would require operators to determine the safe remaining life per a method approved by either the FAA or the CAA (or its delegated agent). In light of the type of action that would be required to address the unsafe condition, and consistent with existing bilateral airworthiness agreements, we have determined that, for this proposed AD, an appropriate action approved by either the FAA or the CAA would be acceptable for compliance with this proposed AD. </P>
                <HD SOURCE="HD1">Cost Impact </HD>
                <P>The FAA estimates that 15 airplanes of U.S. registry would be affected by this proposed AD, that it would take approximately 1 work hour per airplane to accomplish the proposed inspection, and that the average labor rate is $65 per work hour. Based on these figures, the cost impact of the proposed AD on U.S. operators is estimated to be $975, or $65 per airplane. </P>
                <P>The cost impact figure discussed above is based on assumptions that no operator has yet accomplished any of the proposed requirements of this AD action, and that no operator would accomplish those actions in the future if this AD were not adopted. The cost impact figures discussed in AD rulemaking actions represent only the time necessary to perform the specific actions actually required by the AD. These figures typically do not include incidental costs, such as the time required to gain access and close up, planning time, or time necessitated by other administrative actions. </P>
                <HD SOURCE="HD1">Regulatory Impact </HD>
                <P>The regulations proposed herein would not have a substantial direct effect on the States, on the relationship between the national Government and the States, or on the distribution of power and responsibilities among the various levels of government. Therefore, it is determined that this proposal would not have federalism implications under Executive Order 13132. </P>
                <P>
                    For the reasons discussed above, I certify that this proposed regulation (1) is not a “significant regulatory action” under Executive Order 12866; (2) is not a “significant rule” under the DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979); and (3) if promulgated, will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act. A copy of the draft regulatory evaluation prepared for this action is contained in the Rules Docket. A copy of it may be obtained by contacting the Rules Docket at the location provided under the caption 
                    <E T="02">ADDRESSES.</E>
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39 </HD>
                    <P>Air transportation, Aircraft, Aviation safety, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Proposed Amendment </HD>
                <P>Accordingly, pursuant to the authority delegated to me by the Administrator, the Federal Aviation Administration proposes to amend part 39 of the Federal Aviation Regulations (14 CFR part 39) as follows: </P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES </HD>
                    <P>1. The authority citation for part 39 continues to read as follows: </P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>49 U.S.C. 106(g), 40113, 44701. </P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 39.13 </SECTNO>
                        <SUBJECT>[Amended] </SUBJECT>
                        <P>2. Section 39.13 is amended by adding the following new airworthiness directive: </P>
                        <EXTRACT>
                            <FP SOURCE="FP-2">
                                <E T="04">BAE Systems (Operations) Limited (Formerly British Aerospace Regional Aircraft):</E>
                                 Docket 2001-NM-272-AD. 
                            </FP>
                            <P>
                                <E T="03">Applicability:</E>
                                 All Model BAe 146-100A and -200A series airplanes; certificated in any category. 
                            </P>
                            <P>
                                <E T="03">Compliance:</E>
                                 Required as indicated, unless accomplished previously. 
                            </P>
                            <P>To prevent the failure of the main landing gear (MLG), which could result in damage to the airplane structure or injury to airplane occupants, accomplish the following: </P>
                            <HD SOURCE="HD1">Inspection To Determine Part Number </HD>
                            <P>
                                (a) Within 50 landings or 31 days after the effective date of this AD, whichever occurs first: Inspect the inner link of the side stays 
                                <PRTPAGE P="67988"/>
                                of the main landing gear (MLG) to determine the part number, per the Accomplishment Instructions of BAE Systems (Operations) Limited Service Bulletin ISB.32-166, dated May 28, 2001. Although this service bulletin specifies to submit certain information to the manufacturer, this AD does not include such a requirement. 
                            </P>
                            <NOTE>
                                <HD SOURCE="HED">Note 1:</HD>
                                <P>BAE Systems (Operations) Limited Service Bulletin, ISB.32-166, dated May 28, 2001, references Messier-Dowty Service Bulletin 146-32-153, dated May 29, 2001, as an additional source of service information for accomplishment of the inspection and replacement required by this AD. Although the Messier-Dowty service bulletin specifies to submit certain information to the manufacturer, this AD does not include such a requirement. </P>
                            </NOTE>
                            <HD SOURCE="HD1">Replacement at New Reduced Safe Life </HD>
                            <P>(b) Replace any side stay which, during the inspection required by paragraph (a) of this AD, is found to have part number 200884319, 200884320, 200884331, 200884332, 200884342, or 200884343. Replace the side stay with a new side stay having the same part number, at the applicable compliance time specified in paragraph 1.D. “Compliance” of BAE Systems (Operations) Limited Service Bulletin ISB.32-166, dated May 28, 2001, as measured from the effective date of this AD. </P>
                            <HD SOURCE="HD1">Safe Remaining Life </HD>
                            <P>(c) If any side stay having part number 200884319, 200884320, 200884331, 200884332, 200884342, or 200884343 has been used at different operating weights, and the service bulletin recommends contacting Messier-Dowty for appropriate action based on the safe remaining life of the side stay; contact the Manager, International Branch, ANM-116, FAA, Transport Airplane Directorate; or the Civil Aviation Authority (CAA), which is the airworthiness authority for the United Kingdom, (or its delegated agent); for appropriate action. </P>
                            <HD SOURCE="HD1">Alternative Methods of Compliance </HD>
                            <P>(d) In accordance with 14 CFR 39.19, the Manager, International Branch, ANM-116, Transport Airplane Directorate, FAA, is authorized to approve alternative methods of compliance for this AD. </P>
                            <NOTE>
                                <HD SOURCE="HED">Note 2:</HD>
                                <P>The subject of this AD is addressed in British airworthiness directive 005-05-2001. </P>
                            </NOTE>
                        </EXTRACT>
                    </SECTION>
                    <SIG>
                        <DATED>Issued in Renton, Washington, on November 28, 2003. </DATED>
                        <NAME>Kevin Mullin, </NAME>
                        <TITLE>Acting Manager,  Transport Airplane Directorate, Aircraft Certification Service. </TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30222 Filed 12-4-03; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-13-P </BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION </AGENCY>
                <SUBAGY>Federal Aviation Administration </SUBAGY>
                <CFR>14 CFR Part 39 </CFR>
                <DEPDOC>[Docket No. 2003-CE-45-AD] </DEPDOC>
                <RIN>RIN 2120-AA64 </RIN>
                <SUBJECT>Airworthiness Directives; Pilatus Aircraft Ltd. Models PC-7, PC-12, and PC-12/45 Airplanes </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Aviation Administration (FAA), DOT. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of proposed rulemaking (NPRM). </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The FAA proposes to supersede Airworthiness Directive (AD) 2002-01-09, which applies to all Pilatus Aircraft Ltd. (Pilatus) Models PC-7, PC-12, and PC-12/45 airplanes that incorporate a certain engine-driven pump. AD 2002-01-09 currently requires you to inspect the joints between the engine-driven pump housing, the relief valve housing, and the relief valve cover for signs of fuel leakage and extruding gasket material; replace any engine-driven pump with any of the above problems; and ensure that the relief valve attachment screws are adequately torqued and re-torque as necessary. This proposed AD is the result of mandatory continuing airworthiness information (MCAI) issued by the airworthiness authority for Switzerland. This proposed AD would retain the actions from AD 2002-01-09, would add certain engine-driven pumps to the applicability, and would require eventual replacement of the pump with an improved design pump to assure that the unsafe condition does not recur. We are issuing this proposed AD to detect and correct gasket material extruding from the engine-driven pump housing and detect and correct relief valve attachment screws with inadequate torque. These conditions could lead to fuel leakage and result in a fire in the engine compartment. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>We must receive any comments on this proposed AD by January 6, 2004. </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Use one of the following to submit comments on this proposed AD: </P>
                    <P>
                        • 
                        <E T="03">By mail:</E>
                         FAA, Central Region, Office of the Regional Counsel, Attention: Rules Docket No. 2003-CE-45-AD, 901 Locust, Room 506, Kansas City, Missouri 64106. 
                    </P>
                    <P>
                        • 
                        <E T="03">By fax:</E>
                         (816) 329-3771. 
                    </P>
                    <P>
                        • 
                        <E T="03">By e-mail: 9-ACE-7-Docket@faa.gov</E>
                        . Comments sent electronically must contain “Docket No. 2003-CE-45-AD” in the subject line. If you send comments electronically as attached electronic files, the files must be formatted in Microsoft Word 97 for Windows or ASCII. 
                    </P>
                    <P>You may get the service information identified in this proposed AD from Pilatus Aircraft Ltd., Customer Liaison Manager, CH-6371 Stans, Switzerland; telephone: +41 41 619 63 19; facsimile: +41 41 619 6224; or from Pilatus Business Aircraft Ltd., Product Support Department, 11755 Airport Way, Broomfield, Colorado 80021; telephone: (303) 465-9099; facsimile: (303) 465-6040. </P>
                    <P>You may view the AD docket at FAA, Central Region, Office of the Regional Counsel, Attention: Rules Docket No. 2003-CE-45-AD, 901 Locust, Room 506, Kansas City, Missouri 64106. Office hours are 8 a.m. to 4 p.m., Monday through Friday, except Federal holidays. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Doug Rudolph, Aerospace Engineer, FAA, Small Airplane Directorate, 901 Locust, Room 301, Kansas City, Missouri 64106; telephone: (816) 329-4059; facsimile: (816) 329-4090. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Comments Invited </HD>
                <HD SOURCE="HD2">How Do I Comment on This Proposed AD? </HD>
                <P>
                    We invite you to submit any written relevant data, views, or arguments regarding this proposal. Send your comments to an address listed under 
                    <E T="02">ADDRESSES</E>
                    . Include “AD Docket No. 2003-CE-45-AD” in the subject line of your comments. If you want us to acknowledge receipt of your mailed comments, send us a self-addressed, stamped postcard with the docket number written on it. We will date-stamp your postcard and mail it back to you. 
                </P>
                <HD SOURCE="HD2">Are There Any Specific Portions of This Proposed AD I Should Pay Attention to? </HD>
                <P>We specifically invite comments on the overall regulatory, economic, environmental, and energy aspects of this proposed AD. If you contact us through a nonwritten communication and that contact relates to a substantive part of this proposed AD, we will summarize the contact and place the summary in the docket. We will consider all comments received by the closing date and may amend this proposed AD in light of those comments and contacts. </P>
                <HD SOURCE="HD1">Discussion </HD>
                <HD SOURCE="HD2">Has FAA Taken Any Action to This Point? </HD>
                <P>
                    Reports of fuel leaking from certain engine-driven pumps on Pilatus Models PC-7, PC-12, and PC-12/45 airplanes caused FAA to issue AD 2002-01-09, 
                    <PRTPAGE P="67989"/>
                    Amendment 39-12600 (67 FR 2323, January 17, 2002). AD 2002-01-09 currently requires the following on all Pilatus Models PC-7, PC-12, and PC-12/45 airplanes: 
                </P>
                <FP SOURCE="FP-1">—Inspecting the joints between the engine-driven pump housing, the relief valve housing, and the relief valve cover for signs of fuel leakage and extruding gasket material; </FP>
                <FP SOURCE="FP-1">—Replacing any engine-driven pump with signs of fuel leakage or extruding gasket material; and </FP>
                <FP SOURCE="FP-1">—Ensuring that the relief valve attachment screws are adequately torqued and re-torquing as necessary.</FP>
                <HD SOURCE="HD2">What Has Happened Since AD 2002-01-09 To Initiate This Proposed Action? </HD>
                <P>The Federal Office for Civil Aviation (FOCA), which is the airworthiness authority for Switzerland, recently notified FAA of the need to change AD 2002-01-09. The CAA reports that problems are occurring on other engine-driven pumps that could be installed on the affected airplanes, and that the affected airplanes should have a certain engine-driven pump installed to ensure this unsafe condition does not reoccur. </P>
                <HD SOURCE="HD2">What Are the Consequences if the Condition Is Not Corrected? </HD>
                <P>Gasket material extruding from the engine-driven pump housing and relief valve attachment screws with inadequate torque, if not detected and corrected, could lead to fuel leakage and result in a fire in the engine compartment. </P>
                <HD SOURCE="HD2">Is There Service Information That Applies to This Subject? </HD>
                <P>Pilatus has issued the following service information: </P>
                <FP SOURCE="FP-1">—Pilatus PC-7 Service Bulletin No. 28-007, Revision No. 1, dated October 1, 2002, which includes procedures for changing the diaphragm and valve housing assembly of the engine-driven pump, Lear Romec part number (P/N) RG9570M1 (Pilatus P/N 968.84.51.105) or Lear Romec P/N RG9570M (Pilatus P/N 968.84.51.103). This service bulletin also specifies incorporating Crane Lear Romec Service Bulletin SB9570-73-002 or Crane Lear Romec Service Bulletin RG9570-73-006; </FP>
                <FP SOURCE="FP-1">—Pilatus PC-12 Service Bulletin No. 28-010, dated September 16, 2002, which includes procedures for changing the diaphragm and valve housing assembly of the engine-driven pump, Lear Romec P/N RG9570R1 (Pilatus P/N 968.84.51.106). This service bulletin also specifies incorporating Crane Lear Romec Service Bulletin SB9570-73-002; and </FP>
                <FP SOURCE="FP-1">—Pilatus PC-7 Service Bulletin No. 28-008, Revision 1, dated September 24, 2002, which specifies procedures for inspecting the engine-driven pump, Lear Romec P/N RG9570M (Pilatus P/N 968.84.51.103) for signs of fuel leakage or extruding gasket material and correcting relief valve torque on the screws. </FP>
                <HD SOURCE="HD2">Does the Service Information From AD 2002-01-09 Still Apply?</HD>
                <P>Yes. Pilatus PC-7 Service Bulletin No. 28-006 and Pilatus PC-12 Service Bulletin No. 28-009, both dated August 10, 2001, are still valid and provide information on the inspection and replacement of the engine-driven pumps, Romec P/N RG9570M1 (Pilatus P/N 968.84.51.105) and Lear Romec P/N RG9570R1 (Pilatus P/N 968.84.51.106). </P>
                <HD SOURCE="HD2">What Action Did the FOCA Take? </HD>
                <P>The FOCA classified these service bulletins as mandatory and issued FOCA AD HB 2003-392, dated September 15, 2003; and FOCA AD HB 2003-251, dated June16, 2003, to ensure the continued airworthiness of these airplanes in Switzerland. </P>
                <HD SOURCE="HD2">Did the FOCA Inform the United States Per the Bilateral Airworthiness Agreement? </HD>
                <P>These Pilatus Models PC-7, PC-12, and PC-12/45 airplanes are manufactured in Switzerland and are type-certificated for operation in the United States under the provisions of section 21.29 of the Federal Aviation Regulations (14 CFR 21.29) and the applicable bilateral airworthiness agreement. </P>
                <P>Under this bilateral airworthiness agreement, the FOCA has kept us informed of the situation described above. </P>
                <HD SOURCE="HD1">FAA's Determination and Requirements of This Proposed AD </HD>
                <HD SOURCE="HD2">What Has FAA decided? </HD>
                <P>We have examined the FOCA's findings, reviewed all available information, and determined that AD action is necessary for products of this type design that are certificated for operation in the United States. </P>
                <P>Since the unsafe condition described previously is likely to exist or develop on other Pilatus Models PC-7, PC-12, and PC-12/45 airplanes of the same type design that are registered in the United States, we are proposing AD action to detect and correct gasket material extruding from the engine-driven pump housing and detect and correct relief valve attachment screws with inadequate torque. These conditions could lead to fuel leakage and result in a fire in the engine compartment. </P>
                <HD SOURCE="HD2">What Would This Proposed AD Require?</HD>
                <P>This proposed AD would supersede </P>
                <P>AD 2002-01-09 with a new AD that would: </P>
                <FP SOURCE="FP-1">—Retain the actions from AD 2002-01-09; </FP>
                <FP SOURCE="FP-1">—Add certain engine-driven pumps to the applicability; and </FP>
                <FP SOURCE="FP-1">—Require eventual replacement of the pump with an improved design pump to assure that the unsafe condition does not reoccur. </FP>
                <HD SOURCE="HD2">How Does the Revision to 14 CFR Part 39 Affect This Proposed AD? </HD>
                <P>On July 10, 2002, we published a new version of 14 CFR part 39 (67 FR 47997, July 22, 2002), which governs FAA's AD system. This regulation now includes material that relates to altered products, special flight permits, and alternative methods of compliance. This material previously was included in each individual AD. Since this material is included in 14 CFR part 39, we will not include it in future AD actions. </P>
                <HD SOURCE="HD1">Costs of Compliance </HD>
                <HD SOURCE="HD2">How Many Airplanes Would This Proposed AD Impact? </HD>
                <P>We estimate that this proposed AD affects 278 airplanes in the U.S. registry. </P>
                <HD SOURCE="HD2">What Would Be the Cost Impact of This Proposed AD on Owners/Operators of the Affected Airplanes? </HD>
                <P>We estimate the following costs to accomplish the proposed inspections and re-torque: </P>
                <GPOTABLE COLS="4" OPTS="L2,tp0,i1" CDEF="s50,r50,16,xs82">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">Labor cost </CHED>
                        <CHED H="1">Parts cost </CHED>
                        <CHED H="1">
                            Total cost per 
                            <LI>airplane </LI>
                        </CHED>
                        <CHED H="1">Total cost on U.S. operators </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">2 workhours × $65 per hour = $130</ENT>
                        <ENT>Not Applicable</ENT>
                        <ENT>$130</ENT>
                        <ENT>$130 × 278 = $36,140. </ENT>
                    </ROW>
                </GPOTABLE>
                <PRTPAGE P="67990"/>
                <P>We estimate the following costs to accomplish any necessary replacements that would be required based on the results of the inspection. We have no way of determining the number of airplanes that may need such replacement:</P>
                <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s50,r50,r50">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">Labor cost </CHED>
                        <CHED H="1">Parts cost </CHED>
                        <CHED H="1">Total cost per airplane </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">1 workhour × $65 per hour = $65</ENT>
                        <ENT>$3,900 per new pump</ENT>
                        <ENT>$3,965 per airplane. </ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD2">What Is the Difference Between the Cost Impact of This Proposed AD and the Cost Impact of AD 2002-01-09?</HD>
                <P>The only difference between this proposed AD and AD 2002-01-09 is the addition of affected engine-driven pumps. The number of airplanes that could have an affected pump installed and the costs associated with inspection and replacement are the same.</P>
                <HD SOURCE="HD1">Compliance Time of This Proposed AD </HD>
                <HD SOURCE="HD2">What Would Be the Compliance Time of the Proposed Inspection? </HD>
                <P>The compliance time of the inspections that would be required by this proposed AD is “within 20 hours time-in-service (TIS) after the effective date of this AD or within the next 30 days after the effective date of this AD, whichever occurs first.” </P>
                <P>Why Is the Compliance Time of the Proposed Inspection Presented in Both Hours TIS and Calendar Time?</P>
                <P>The deterioration and potential extrusion of the gasket occurs over time and is not a condition of repetitive airplane operation. However, the relief valve attachment screws becoming inadequately torqued occurs as a result of airplane operation if the compression set of the gasket and diaphragm after thermal cycling causes the gasket of the engine-driven pump to extrude between the relief valve housing and the engine-driven pump housing. </P>
                <P>Therefore, to ensure that the unsafe condition defined in this document is detected and corrected in a timely manner, we are stating the compliance in both calendar time and hours TIS. </P>
                <HD SOURCE="HD1">Regulatory Findings </HD>
                <HD SOURCE="HD2">Would This Proposed AD Impact Various Entities? </HD>
                <P>We have determined that this proposed AD would not have federalism implications under Executive Order 13132. This proposed AD would not have a substantial direct effect on the States, on the relationship between the national Government and the States, or on the distribution of power and responsibilities among the various levels of government. </P>
                <HD SOURCE="HD2">Would This Proposed AD Involve a Significant Rule or Regulatory Action? </HD>
                <P>For the reasons discussed above, I certify that this proposed AD: </P>
                <P>1. Is not a “significant regulatory action” under Executive Order 12866; </P>
                <P>2. Is not a “significant rule” under the DOT Regulatory Policies and Procedures (44 FR 11034, February 26, 1979); and </P>
                <P>3. Will not have a significant economic impact, positive or negative, on a substantial number of small entities under the criteria of the Regulatory Flexibility Act. </P>
                <P>
                    We prepared a summary of the costs to comply with this proposed AD and placed it in the AD Docket. You may get a copy of this summary by sending a request to us at the address listed under 
                    <E T="02">ADDRESSES.</E>
                     Include “AD Docket No.2003-CE-45-AD” in your request. 
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 14 CFR Part 39 </HD>
                    <P>Air transportation, Aircraft, Aviation safety, Safety.</P>
                </LSTSUB>
                <HD SOURCE="HD1">The Proposed Amendment </HD>
                <P>Accordingly, under the authority delegated to me by the Administrator, the Federal Aviation Administration proposes to amend 14 CFR part 39 as follows: </P>
                <PART>
                    <HD SOURCE="HED">PART 39—AIRWORTHINESS DIRECTIVES</HD>
                    <P>1. The authority citation for part 39 continues to read as follows: </P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>49 U.S.C. 106(g), 40113, 44701. </P>
                    </AUTH>
                    <SECTION>
                        <SECTNO>§ 39.13 </SECTNO>
                        <SUBJECT>[Amended] </SUBJECT>
                        <P>2. The FAA amends § 39.13 by removing Airworthiness Directive (AD) 2002-01-09, Amendment 39-12600 (67 FR 2323, January 17, 2002), and by adding a new AD to read as follows:</P>
                        <EXTRACT>
                            <FP SOURCE="FP-2">
                                <E T="04">Pilatus Aircraft Ltd.:</E>
                                 Docket No. 2003-CE-45-AD. 
                            </FP>
                            <HD SOURCE="HD1">When Is the Last Date I Can Submit Comments on This Proposed AD? </HD>
                            <P>(a) We must receive comments on this proposed airworthiness directive (AD) by January 6, 2004. </P>
                            <HD SOURCE="HD1">What Other ADs Are Affected By This Action? </HD>
                            <P>(b) This AD supersedes AD 2002-01-09, Amendment 39-12600. </P>
                            <HD SOURCE="HD1">What Airplanes Are Affected by This AD? </HD>
                            <P>(c) This AD affects the following airplane models and serial numbers that are certificated in any category: </P>
                            <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s100,r150">
                                <TTITLE>  </TTITLE>
                                <BOXHD>
                                    <CHED H="1">Model </CHED>
                                    <CHED H="1">Serial Nos.</CHED>
                                </BOXHD>
                                <ROW>
                                    <ENT I="01">(1) PC-7 </ENT>
                                    <ENT>All manufacturer serial numbers (MSN) equipped with either a Lear Romec part number (P/N) RG9570M (Pilatus P/N 968.84.51.103) engine-driven pump or a Lear Romec P/N RG9570M1 (Pilatus P/N 968.84.51.105) engine-driven pump. </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">(2) PC-12 and PC-12/45 </ENT>
                                    <ENT>All MSN equipped with a Lear Romec P/N RG9570R1 (Pilatus P/N 968.84.51.106) engine-driven pump. </ENT>
                                </ROW>
                            </GPOTABLE>
                            <NOTE>
                                <HD SOURCE="HED">Note:</HD>
                                <P>Pilatus installed these engine-driven pumps on MSN 101 through MSN 406 and MSN 408 through 419 of the Models PC-12 and PC-12/45 airplanes and MSN 101 through MSN 618 of the Model PC-7 airplanes. These engine-driven pumps could be installed through field approval on any MSN of the Models PC-7, PC-12, and PC-12/45 airplanes. </P>
                            </NOTE>
                            <HD SOURCE="HD1">What Is the Unsafe Condition Presented in This AD? </HD>
                            <P>(d) The actions specified in this AD are intended to detect and correct gasket material extruding from the engine-driven pump housing and detect and correct relief valve attachment screws with inadequate torque. These conditions could lead to fuel leakage and result in a fire in the engine compartment. </P>
                            <HD SOURCE="HD1">What Must I Do To Address This Problem? </HD>
                            <P>(e) To address this problem, you must do the following: </P>
                            <P>
                                (1) 
                                <E T="03">Inspection:</E>
                                 Inspect the joints between the engine-driven pump housing, the relief valve housing, and the relief valve cover for signs of fuel leakage and extruding gasket material as follows: 
                                <PRTPAGE P="67991"/>
                            </P>
                            <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s100,r100,r100">
                                <TTITLE>  </TTITLE>
                                <BOXHD>
                                    <CHED H="1">Engine-driven pump P/N </CHED>
                                    <CHED H="1">Compliance </CHED>
                                    <CHED H="1">Procedures </CHED>
                                </BOXHD>
                                <ROW>
                                    <ENT I="01">(i) Lear Romec P/N RG9570M1 (Pilatus P/N 968.84.51.105) or Lear Romec P/N RG9570R1 (Pilatus P/N 968.84.51.106)</ENT>
                                    <ENT>Within the next 20 hours time-in-service (TIS) after February 28, 2002 (the effective date of AD 2002-01-09) or within the next 30 days after February 28, 2002 (the effective date of AD 2002-01-09), whichever occurs first, unless already done</ENT>
                                    <ENT>Follow Pilatus PC-7 Service Bulletin No. 28-006 or Pilatus PC-12 Service Bulletin No. 28-009, both dated August 10, 2001, as applicable. </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">(ii) Lear Romec P/N RG9570M (Pilatus P/N 968.84.51.103)</ENT>
                                    <ENT>Within 20 hours TIS after the effective date of this AD or within 30 days after the effective date of this AD, whichever occurs first, unless already done</ENT>
                                    <ENT>Follow Pilatus PC-7 Service Bulletin No. 28-008, Revision 1, dated September 24, 2003. </ENT>
                                </ROW>
                            </GPOTABLE>
                            <P>
                                (2) 
                                <E T="03">Replacement/Modification:</E>
                                 Replace the engine-driven pump with one of the following prior to further flight after the inspection in paragraph (e)(1) of this AD if you find signs of fuel leakage or extruding gasket material or within 6 months after the effective date of this AD if you do not find signs of fuel leakage or extruding gasket material, whichever occurs first, unless already done: 
                            </P>
                            <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s100,r100,r100">
                                <TTITLE>  </TTITLE>
                                <BOXHD>
                                    <CHED H="1">Models </CHED>
                                    <CHED H="1">Pump replacement P/N</CHED>
                                    <CHED H="1">Procedures </CHED>
                                </BOXHD>
                                <ROW>
                                    <ENT I="01">(i) PC-7 </ENT>
                                    <ENT>Lear Romec P/N RG9570M1/M (Pilatus P/N 968.84.51.107)</ENT>
                                    <ENT>Pilatus PC-7 Service Bulletin No. 28-007, Revision No. 1, dated October 1, 2002. </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">(ii) PC-12 and PC-12/45</ENT>
                                    <ENT>Lear Romec P/N RG9570R1/M (Pilatus P/N 968.84.51.108)</ENT>
                                    <ENT>Pilatus PC-12 Service Bulletin No. 28-010, dated September 16, 2002. </ENT>
                                </ROW>
                            </GPOTABLE>
                            <P>
                                (3) 
                                <E T="03">Relief Valve Attachment Screw Torque:</E>
                                 Prior to further flight after the inspection (if you find no fuel leakage or extruding gasket material) and replacement required by this AD, ensure that the relief valve attachment screws are adequately torqued and re-torque as necessary using the following: 
                            </P>
                            <P>
                                (i) 
                                <E T="03">For Pilatus Model PC-7 Airplanes:</E>
                                 Pilatus PC-7 Service Bulletin No. 28-006, dated August 10, 2001, or Pilatus PC-7 Service Bulletin No. 28-008, Revision 1, dated September 24, 2002. 
                            </P>
                            <P>
                                (ii) 
                                <E T="03">For Pilatus Models PC-12 and PC-12/45 Airplanes:</E>
                                 Pilatus PC-12 Service Bulletin No. 28-009, both dated August 10, 2001. 
                            </P>
                            <P>
                                (4) 
                                <E T="03">Spares:</E>
                                 As of the effective date of this AD, only install an engine-driven pump that is of a part number referenced in paragraphs (e)(2)(i) and (e)(2)(ii) of this AD. Prior to further flight after installation, do the relief valve attachment screw torque check as required by paragraph (e)(3) of this AD. 
                            </P>
                            <P>
                                (5) 
                                <E T="03">Unless Already Done Credit:</E>
                                 This AD retains actions from AD 2002-01-09. 
                            </P>
                            <P>(i) You may take inspection credit if you have one of the engine-driven pumps installed affected by AD 2002-01-09 and the specific actions are already done. </P>
                            <P>(ii) The actions of this AD do not apply if you have one of the engine-driven pumps installed that is referenced in paragraphs (e)(2)(i) and (e)(2)(ii) of this AD. </P>
                            <HD SOURCE="HD1">May I Request an Alternative Method of Compliance? </HD>
                            <P>(f) You may request a different method of compliance or a different compliance time for this AD by following the procedures in 14 CFR 39.13. Send your request to the Manager, Standards Office, Small Airplane Directorate, FAA. For information on any already approved alternative methods of compliance, contact Doug Rudolph, Aerospace Engineer, FAA, Small Airplane Directorate, 901 Locust, Room 301, Kansas City, Missouri 64106; telephone: (816) 329-4059; facsimile: (816) 329-4090. </P>
                            <HD SOURCE="HD1">May I Get Copies of the Documents Referenced in This AD? </HD>
                            <P>(g) You may get copies of the documents referenced in this AD from Pilatus Aircraft Ltd., Customer Liaison Manager, CH-6371 Stans, Switzerland; telephone: +41 41 619 63 19; facsimile: +41 41 619 6224; or from Pilatus Business Aircraft Ltd., Product Support Department, 11755 Airport Way, Broomfield, Colorado 80021; telephone: (303) 465-9099; facsimile: (303) 465-6040. You may view these documents at FAA, Central Region, Office of the Regional Counsel, 901 Locust, Room 506, Kansas City, Missouri 64106. </P>
                            <HD SOURCE="HD1">Is There Other Information That Relates to This Subject? </HD>
                            <P>(h) FOCA (Switzerland) AD HB 2003-392, dated September 15, 2003; and FOCA (Switzerland) AD HB 2003-251, dated June 16, 2003, also address the subject of this AD. </P>
                        </EXTRACT>
                    </SECTION>
                    <SIG>
                        <DATED>Issued in Kansas City, Missouri, on November 26, 2003. </DATED>
                        <NAME>Michael Gallagher, </NAME>
                        <TITLE>Manager, Small Airplane Directorate, Aircraft Certification Service. </TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30256 Filed 12-4-03; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4910-13-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">NATIONAL CRIME PREVENTION AND PRIVACY COMPACT COUNCIL </AGENCY>
                <CFR>28 CFR Part 901 </CFR>
                <DEPDOC>[NCPPC 105] </DEPDOC>
                <SUBJECT>Proposed Amendments to the Fingerprint Submission Requirements Rule </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Crime Prevention and Privacy Compact Council. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed amendments to the rule, request for comments. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Compact Council, established pursuant to the National Crime Prevention and Privacy Compact (Compact), is amending its Fingerprint Submission Requirements Rule which interprets the Compact's fingerprint-submission requirements as they relate to the use of the Interstate Identification Index (III) System for noncriminal justice record checks during an emergency situation when the health and safety of a specified group may be endangered. In addition, pursuant to the rule, the Compact Council approved an amended proposal from a State requesting the delayed submission of fingerprints when conducting criminal history records checks in connection with the temporary placement of children with temporary custodians during exigent circumstances. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments must be submitted on or before January 5, 2004.</P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Send all written comments concerning the proposed amendments to the Compact Council Office, 1000 Custer Hollow Road, Module C3, Clarksburg, WV 26306; Attention: Todd C. Commodore. Comments may also be submitted by fax at (304) 625-5388 or by electronic mail at 
                        <E T="03">tcommodo@leo.gov.</E>
                         To ensure proper handling, please reference “Amended Fingerprint Submission Requirements” on your correspondence. 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Lt. Col. Jeffrey D. Harmon, Compact Council Chairman, Maine State Police, 36 Hospital Street, Augusta, Maine 
                        <PRTPAGE P="67992"/>
                        04333-0042, telephone number (207) 624-7060. 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The National Crime Prevention and Privacy Compact (Compact), 42 U.S.C. 14616, establishes uniform standards and processes for the interstate and Federal-State exchange of criminal history records for noncriminal justice purposes. The Compact eliminates barriers to the sharing of criminal history record information among the compact parties for noncriminal justice purposes. Article VI of the Compact provides for a Compact Council that has the authority to promulgate rules and procedures governing the use of the III System for noncriminal justice purposes. </P>
                <P>
                    The Compact requires that subject's fingerprints or other approved forms of positive identification “shall be submitted with all requests for criminal history record checks for noncriminal justice purposes.” 
                    <E T="03">See</E>
                     42 U.S.C. 14616, Article V(a). The Compact Council recognizes the extreme reliability of fingerprint-based identifications and believes that the above quoted provision requires that, whenever feasible, fingerprints should be submitted contemporaneously with search requests. In promulgating the Fingerprint Submission Requirements Rule (28 CFR Part 901), however, the Council acknowledged that there are exigent circumstances in which time is a critical factor in decision making and in which the immediate fingerprinting of the subject is not feasible. In such emergency circumstances, the Council interpreted the Compact to permit preliminary name searches of the III System for noncriminal justice purposes, provided that fingerprints are obtained and submitted within a time frame specified by the Council. This procedure allows access to criminal history record information in a timely manner in exigent circumstances with follow-up positive identification assured by fingerprint submissions. 
                </P>
                <P>Part 901 authorizes state criminal history record repositories and the FBI, upon approval by the Compact Council, to grant access to the III System in emergency situations on a delayed fingerprint submission basis, predicated upon a statute approved by the U.S. Attorney General pursuant to Public Law 92-544 and Article III (c) of the Compact. Access authorized by part 901 must adhere to both the Criminal Justice Information Services Security Policy and applicable state security policies. </P>
                <P>Subsequent to the publication of Part 901, states that were authorized to conduct the name-based checks articulated varying interpretations of the fingerprint submission time frame. In order to eliminate these disparate interpretations, the Compact Council is amending the rule to define the term “time frame” by adding a sentence at the end of Subsection 901.3(b). </P>
                <P>
                    Section 901.3 is also amended by adding paragraph (d) to clarify that part 901 is also applicable to Federal agencies authorized to access criminal history records pursuant to Federal statute or Executive Order for noncriminal justice purposes. The original rule identified only state agencies, and per the Compact's definition of “state”, an amendment to the rule is necessary. 
                    <E T="03">See</E>
                     42 U.S.C. 14616, Article I(22). 
                </P>
                <P>
                    Recently, the FBI CJIS Division expanded its Audit Unit programs to include reviews of noncriminal justice agencies with direct access to the III System for emergency placement of children. Though the Background section of the original 
                    <E T="04">Federal Register</E>
                     publication establishing part 901 included verbiage addressing audits and sanctions, no such language was included in the Rule. The Compact Council has now approved the addition of language in the rule addressing audits and sanctions in order to reduce the potential for misinterpretation. Section 901.4 identifies the State Compact Officer or, in nonparty states, the Chief Administrator of the Criminal History Record Repository, as the responsible party to ensure that audits are conducted of approved state agencies, and the responsible Federal Service Coordinator will ensure that similar audits are conducted of authorized Federal agencies. The audits will verify adherence to the provisions of part 901 and the FBI Criminal Justice Information Services Security Policy. Section 901.4 also includes the details of records an authorized agency must maintain related to this III access under part 901 and requires that mechanisms to calculate the specified time frame for fingerprint submissions be included in the audit and compliance reviews. 
                </P>
                <P>Sanctions for noncompliance as related to the audit methodology spelled out in section 901.4 are addressed in section 901.5. This section states that the Compact Council, or the FBI in consultation with the Compact Council, may impose sanctions according to rules, procedures, or standards established by the Council. Approved access to criminal history record information systems is subject to cancellation for violation of the National Crime Prevention and Privacy Compact Act or for failure to comply with part 901 or the FBI Criminal Justice Information Services Security Policy. The state's Compact Officer, the Chief Administrator of the Criminal History Record Repository in a nonparty state, or the Federal Service Coordinator may take similar actions, as applicable, against a State or Federal agency for failure to comply with applicable security policies. </P>
                <HD SOURCE="HD1">Administrative Procedures and Executive Orders </HD>
                <HD SOURCE="HD2">Administrative Procedures Act </HD>
                <P>
                    This rule is published by the Compact Council as authorized by the National Crime Prevention and Privacy Compact (Compact), an interstate/Federal compact which was approved and enacted into law by Congress pursuant to Pub. L. 105-251. The Compact Council is composed of 15 members (with 11 state and local governmental representatives), and is authorized by the Compact to promulgate rules and procedures for the effective and proper use of the Interstate Identification Index (III) System for noncriminal justice purposes. The Compact specifically provides that the Council shall prescribe rules and procedures for the effective and proper use of the III System for noncriminal justice purposes, and mandates that such rules, procedures, or standards established by the Council shall be published in the 
                    <E T="04">Federal Register</E>
                    . 
                    <E T="03">See</E>
                     42 U.S.C. 14616, Articles II(4), VI(a)(1), and VI(e). This publication complies with those requirements. 
                </P>
                <HD SOURCE="HD2">Executive Order 12866 </HD>
                <P>The Compact Council is not an executive department or independent regulatory agency as defined in 44 U.S.C. 3502; accordingly, Executive Order 12866 is not applicable. </P>
                <HD SOURCE="HD2">Executive Order 13132 </HD>
                <P>The Compact Council is not an executive department or independent regulatory agency as defined in 44 U.S.C. 3502; accordingly, Executive Order 13132 is not applicable. Nonetheless, this rule fully complies with the intent that the national government should be deferential to the States when taking action that affects the policymaking discretion of the States.</P>
                <HD SOURCE="HD2">Executive Order 12988 </HD>
                <P>
                    The Compact Council is not an executive agency or independent establishment as defined in 5 U.S.C. 105; accordingly, Executive Order 12988 is not applicable. 
                    <PRTPAGE P="67993"/>
                </P>
                <HD SOURCE="HD2">Unfunded Mandates Reform Act </HD>
                <P>Approximately 75 percent of the Compact Council members are representatives of state and local governments; accordingly, rules prescribed by the Compact Council are not Federal mandates. Accordingly, no actions are deemed necessary under the provisions of the Unfunded Mandates Reform Act of 1995. </P>
                <HD SOURCE="HD2">Small Business Regulatory Enforcement Fairness Act of 1996 </HD>
                <P>
                    The Small Business Regulatory Enforcement Fairness Act (Title 5, U.S.C. 801-804) is not applicable to the Council's rule because the Compact Council is not a “Federal agency” as defined by 5 U.S.C. 804(1). Likewise, the reporting requirement of the Congressional Review Act (Subtitle E of the Small Business Regulatory Enforcement Fairness Act) does not apply. 
                    <E T="03">See</E>
                     5 U.S.C. 804. 
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 28 CFR Part 901 </HD>
                    <P>Crime, Health, Privacy, Safety.</P>
                </LSTSUB>
                <P>Accordingly, the Compact Council proposes to amend part 901 as follows: </P>
                <PART>
                    <HD SOURCE="HED">PART 901—FINGERPRINT SUBMISSION REQUIREMENTS </HD>
                    <P>1. The authority citation for part 901 continues to read as follows; </P>
                    <AUTH>
                        <HD SOURCE="HED">Authority:</HD>
                        <P>42 U.S.C. 14616. </P>
                    </AUTH>
                    <P>2. Amend § 901.3 as follows; </P>
                    <P>a. By redesignationg paragraph (c) as paragraph (d); </P>
                    <P>b. By designating the text following paragraph (b) as new paragraph (c) and adding a sentence to the end of the paragraph; </P>
                    <P>c. By adding a new paragraph (e). </P>
                    <P>The added text reads as follows: </P>
                    <SECTION>
                        <SECTNO>§ 901.3 </SECTNO>
                        <SUBJECT>Approval of delayed fingerprint submission request. </SUBJECT>
                        <STARS/>
                        <P>(c) * * * For the purposes of this rule, “time frame” means the number of days that elapse between the date on which the name search was conducted and the date on which the state repository either positively identifies the fingerprint subject or forwards the fingerprints to the FBI or the date a Federal agency forwards the fingerprints to the FBI. </P>
                        <STARS/>
                        <P>(e) Part 901 is also applicable to any federal agency authorized to access criminal history records pursuant to Federal statute or Executive Order for noncriminal justice purposes. </P>
                        <P>3. Amend part 901 by adding §§ 901.4 and 901.5 to read as follows: </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 901.4 </SECTNO>
                        <SUBJECT>Audits. </SUBJECT>
                        <P>(a) Audits of authorized State agencies that access the III System shall be conducted by the State's Compact Officer or, in absence of a Compact Officer, the chief administrator for the criminal history record repository. The responsible Federal service coordinator shall ensure that similar audits are conducted of authorized Federal agencies. Such audits shall be conducted to verify adherence to the provisions of part 901 and the FBI's Criminal Justice Information Services (CJIS) Security Policy. </P>
                        <P>(b) Authorized agencies shall cause to be collected an appropriate record of each instance of III System access through a manual or electronic log. The log shall be maintained for a minimum one-year period to facilitate the audits and compliance reviews. Such records shall be maintained in accordance with the CJIS Security Policy. (For information on this security policy, contact your State Control Terminal Officer or Federal Service Coordinator.) </P>
                        <P>(c) The audit and compliance reviews must include mechanisms to determine whether fingerprints were submitted within the time frame specified by the Compact Council. </P>
                        <P>(d) In addition to the audits as stated above, the FBI CJIS Audit staff shall also conduct routine systematic compliance reviews of State repositories, Federal agencies, and as necessary other authorized III System user agencies. </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>§ 901.5 </SECTNO>
                        <SUBJECT>Sanction for noncompliance. </SUBJECT>
                        <P>
                            The Compact Council, or the FBI in consultation with the Compact Council, may impose sanctions in accordance with rules, procedures, or standards as established by the Council. The approval for access to criminal history record information systems for noncriminal justice purposes is subject to cancellation or discontinuance for violation of the National Crime Prevention and Privacy Compact Act, failure to comply with the provisions of part 901, or failure to comply with the FBI Criminal Justice Information Services Security Policy (
                            <E T="03">See</E>
                             § 901.4(b)). The State's Compact Officer, the chief administrator of the criminal history record repository or the Federal Service Coordinator may take similar actions, as applicable, against a State or Federal agency for failure to comply with applicable security policies. 
                        </P>
                    </SECTION>
                    <SIG>
                        <DATED>Dated: November 5, 2003. </DATED>
                        <NAME>Jeffrey D. Harmon, </NAME>
                        <TITLE>Compact Council Chairman. </TITLE>
                    </SIG>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-29567 Filed 12-4-03; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 4410-02-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY </AGENCY>
                <CFR>40 CFR Part 52 </CFR>
                <DEPDOC>[DE072 1042b; FRL-7593-4] </DEPDOC>
                <SUBJECT>Approval and Promulgation of Air Quality Implementation Plans; Delaware; MOBILE6-based Motor Vehicle Emission Budgets for the Delaware Portion of the Philadelphia-Wilmington-Trenton Ozone Nonattainment Area </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        EPA proposes to approve a revision to the Delaware State Implementation Plan (SIP). Specifically, EPA is proposing approving amendments to the 2005 highway (on road) motor vehicle emission inventory for the Delaware portion of the Philadelphia-Wilmington-Trenton area's (the Philadelphia area) 1-hour ozone attainment plan as a revision to the Delaware SIP. This revision also serves to amend the 2005 motor vehicle emission budgets (MVEBs) used for determining transportation conformity under the Clean Air Act. The revised MVEBs were developed using MOBILE6, the most recent version of EPA's mobile source emission factor model. Revision of the MVEBs was a requirement of EPA's prior approval of Delaware's 1-hour ozone attainment demonstration plan for the Philadelphia severe ozone nonattainment area. In the final rules section of this 
                        <E T="04">Federal Register</E>
                        , EPA is approving Delaware's SIP submittal as a direct final rule without prior proposal because the Agency views this as a noncontroversial submittal and anticipates no adverse comments. A detailed rationale for the approval is set forth in the direct final rule. If no adverse comments are received in response to this action, no further activity is contemplated. If EPA receives adverse comments, the direct final rule will be withdrawn and public comments received will be addressed in a subsequent final rule based on this proposed rule. EPA will not institute a second comment period. Any parties interested in commenting on this action should do so at this time. 
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received in writing by January 5, 2004. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments may be submitted either by mail or electronically. Written comments should be mailed to Robert Kramer, Chief, Energy, Radiation and Indoor Environment Branch, Mailcode 3AP23, 
                        <PRTPAGE P="67994"/>
                        U.S. Environmental Protection Agency, Region III, 1650 Arch Street, Philadelphia, Pennsylvania 19103. Electronic comments should be sent either to 
                        <E T="03">kramer.robert@epa.gov</E>
                         or to 
                        <E T="03">http://www.regulations.gov,</E>
                         which is an alternative method for submitting electronic comments to EPA. To submit comments, please follow the detailed instructions described in the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section. Copies of the documents relevant to this action are available for public inspection during normal business hours at the Air Protection Division, U.S. Environmental Protection Agency, Region III, 1650 Arch Street, Philadelphia, Pennsylvania 19103; and at the Delaware Department of Natural Resources and Environmental Control, 156 South State Street, Dover, Delaware 19901. 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Larry Budney, (215) 814-2184, or by e-mail at 
                        <E T="03">budney.larry@epa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    For further information, please see the information provided in the direct final action, with the same title, that is located in the “Rules and Regulations” section of this 
                    <E T="04">Federal Register</E>
                     publication. You may submit comments either electronically or by mail. To ensure proper receipt by EPA, identify the appropriate rulemaking identification number DE072-1042 in the subject line on the first page of your comment. Please ensure that your comments are submitted within the specified comment period. Comments received after the close of the comment period will be marked “late.” EPA is not required to consider these late comments. 
                </P>
                <P>
                    <E T="03">1. Electronically.</E>
                     If you submit an electronic comment as prescribed below, EPA recommends that you include your name, mailing address, and an e-mail address or other contact information in the body of your comment. Also include this contact information on the outside of any disk or CD ROM you submit, and in any cover letter accompanying the disk or CD ROM. This ensures that you can be identified as the submitter of the comment and allows EPA to contact you in case EPA cannot read your comment due to technical difficulties or needs further information on the substance of your comment. EPA's policy is that EPA will not edit your comment, and any identifying or contact information provided in the body of a comment will be included as part of the comment that is placed in the official public docket. If EPA cannot read your comment due to technical difficulties and cannot contact you for clarification, EPA may not be able to consider your comment. 
                </P>
                <P>
                    <E T="03">i. E-mail.</E>
                     Comments may be sent by electronic mail (e-mail) to 
                    <E T="03">kramer.robert@epa.gov,</E>
                     attention DE072-1042. EPA's e-mail system is not an “anonymous access” system. If you send an e-mail comment directly without going through Regulations.gov, EPA's e-mail system automatically captures your e-mail address. E-mail addresses that are automatically captured by EPA's e-mail system are included as part of the comment that is placed in the official public docket. 
                </P>
                <P>
                    <E T="03">ii. Regulations.gov.</E>
                     Your use of Regulation.gov is an alternative method of submitting electronic comments to EPA. Go directly to 
                    <E T="03">http://www.regulations.gov,</E>
                     then select “Environmental Protection Agency” at the top of the page and use the “go” button. The list of current EPA actions available for comment will be listed. Please follow the online instructions for submitting comments. The system is an “anonymous access” system, which means EPA will not know your identity, e-mail address, or other contact information unless you provide it in the body of your comment. 
                </P>
                <P>
                    <E T="03">iii. Disk or CD ROM.</E>
                     You may submit comments on a disk or CD ROM that you mail to the mailing address identified in the 
                    <E T="02">ADDRESSES</E>
                     section of this document. These electronic submissions will be accepted in WordPerfect, Word or ASCII file format. Avoid the use of special characters and any form of encryption. 
                </P>
                <P>
                    <E T="03">2. By Mail.</E>
                     Written comments should be addressed to the EPA Regional office listed in the 
                    <E T="02">ADDRESSES</E>
                     section of this document. 
                </P>
                <P>For public commenters, it is important to note that EPA's policy is that public comments, whether submitted electronically or in paper, will be made available for public viewing at the EPA Regional Office, as EPA receives them and without change, unless the comment contains copyrighted material, confidential business information (CBI), or other information whose disclosure is restricted by statute. When EPA identifies a comment containing copyrighted material, EPA will provide a reference to that material in the version of the comment that is placed in the official public rulemaking file. The entire printed comment, including the copyrighted material, will be available at the Regional Office for public inspection. </P>
                <HD SOURCE="HD1">Submittal of CBI Comments </HD>
                <P>
                    Do not submit information that you consider to be CBI electronically to EPA. You may claim information that you submit to EPA as CBI by marking any part or all of that information as CBI (if you submit CBI on disk or CD ROM, mark the outside of the disk or CD ROM as CBI and then identify electronically within the disk or CD ROM the specific information that is CBI). Information so marked will not be disclosed except in accordance with procedures set forth in 40 CFR part 2. In addition to one complete version of the comment that includes any information claimed as CBI, a copy of the comment that does not contain the information claimed as CBI must be submitted for inclusion in the official public regional rulemaking file. If you submit the copy that does not contain CBI on disk or CD ROM, mark the outside of the disk or CD ROM clearly that it does not contain CBI. Information not marked as CBI will be included in the public file and available for public inspection without prior notice. If you have any questions about CBI or the procedures for claiming CBI, please consult the person identified in the 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     section. 
                </P>
                <HD SOURCE="HD1">Considerations When Preparing Comments to EPA </HD>
                <P>You may find the following suggestions helpful for preparing your comments: </P>
                <P>1. Explain your views as clearly as possible. </P>
                <P>2. Describe any assumptions that you used. </P>
                <P>3. Provide any technical information and/or data you used that support your views. </P>
                <P>4. If you estimate potential burden or costs, explain how you arrived at your estimate. </P>
                <P>5. Provide specific examples to illustrate your concerns. </P>
                <P>6. Offer alternatives. </P>
                <P>7. Make sure to submit your comments by the comment period deadline identified. </P>
                <P>
                    8. To ensure proper receipt by EPA, identify the appropriate regional file/rulemaking identification number in the subject line on the first page of your response. It would also be helpful if you provided the name, date, and 
                    <E T="04">Federal Register</E>
                     citation related to your comments. 
                </P>
                <P>Please note that if EPA receives adverse comment on an amendment, paragraph, or section of this rule and if that provision may be severed from the remainder of the rule, EPA may adopt as final those provisions of the rule that are not the subject of an adverse comment. </P>
                <SIG>
                    <PRTPAGE P="67995"/>
                    <DATED>Dated: November 20, 2003. </DATED>
                    <NAME>Thomas Voltaggio, </NAME>
                    <TITLE>Acting Regional Administrator, Region III. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30042 Filed 12-4-03; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="N">NATIONAL AERONAUTICS AND SPACE ADMINISTRATION </AGENCY>
                <CFR>48 CFR Parts 1809, 1837, and 1852 </CFR>
                <RIN>RIN 2700-AC60 </RIN>
                <SUBJECT>Contractor Access to Confidential Information </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Aeronautics and Space Administration (NASA). </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This rule proposes to amend the NASA Federal Acquisition Regulation (FAR) Supplement (NFS) to provide guidance on how NASA will acquire services to support management activities and administrative functions, when performing those services requires the contractor to have access to confidential information submitted by other contractors. NASA's increased use of contractors to support management activities and administrative functions, coupled with implementing Agency-wide electronic information systems, requires establishing consistent procedures for protecting confidential information from unauthorized use or disclosure. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments should be submitted on or before February 3, 2004 to be considered in the formulation of a final rule. </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Interested parties should submit written comments to David Forbes, NASA Headquarters, Office of Procurement, Contract Management Division (Code HK), Washington, DC 20546. Comments may also be submitted by e-mail to: 
                        <E T="03">David.P.Forbes@nasa.gov</E>
                        . 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        David Forbes, (202) 358-2051, e-mail: 
                        <E T="03">David.P.Forbes@nasa.gov</E>
                        . 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">A. Background </HD>
                <P>In accomplishing its mission, NASA expends about eighty-five percent of its appropriations through contracts. As part of the process of awarding and performing contracts, offerors and contractors must provide information, some of which they claim to have developed at private expense and that may embody trade secrets or constitute commercial or financial and confidential information (“confidential information”). Confidential information includes technical, financial, proprietary, commercial, privileged, or otherwise sensitive business information. As a result, NASA receives and retains a substantial amount of confidential information, contained in paper files and electronic administrative systems. </P>
                <P>Generally, the information in question is not in the public domain and may be subject to the Trade Secrets Act, the Procurement Integrity Act (FAR 3.104), and other laws and regulations relating to ethics, organizational conflicts of interest, and corruption in the Federal procurement process. To the extent that an exception to the Freedom of Information Act applies, government agencies may also generate confidential information, including pre-negotiation analyses and positions and pre-decisional advice on a variety of subjects. NASA has long recognized a responsibility to protect this type of information from unauthorized use and disclosure. To this end, NASA has traditionally allowed only civil servants to have access to confidential information in the Government's possession. Practical realities, coupled with new policy initiatives compel NASA to reconsider its approach to managing contractor-related information. </P>
                <P>The practical pressure to reconsider NASA's approach has emerged from years of “downsizing” the civil service workforce. Simply put, NASA no longer has enough employees to manage and safeguard all of the information in question. Of necessity, NASA is increasing its use of service contractors to assist in performing many administrative, financial, and technical functions that had been performed previously by government employees only. The types of services NASA will be procuring run the gamut from routine clerical support such as data entry and invoice processing, to more complex in-plant reviews, contract closeout processing, system administration, and safety and quality assurance activities. Service contractors may soon be supporting most of these activities and functions throughout the Agency. NASA must, therefore, find new, more streamlined ways to receive from offerors and contractors confidential information that may be entitled to protection and to disclose it to third party service providers, without compromising the information received. </P>
                <P>As NASA releases more confidential information provided by offerors or contractors to other contractors, the risk increases that unauthorized uses and disclosures will occur. One aspect of this increased risk is the potential that organizational conflicts of interest may arise when the Agency discloses one contractor's confidential information to another contractor. FAR Subpart 9.5 prescribes general rules for managing organizational conflicts of interest and gives four specific examples of situations that may give rise to problems. One of those examples deals directly with NASA's current dilemma, that is, providing one contractor access to other contractors' confidential information. Specifically, when one contractor gains access to other companies' “proprietary” information, FAR 9.505-4 directs the service provider to enter into agreement(s) with the other companies to protect their information from unauthorized use or disclosure and to refrain from using the information for any purpose other than that for which it was furnished. Additionally, FAR 9.505-4 requires the contracting officer to obtain copies of these third party agreements and ensure that they are properly executed. </P>
                <P>In the past, NASA contracts rarely required access to another contractor's proprietary or other forms of confidential information, making this FAR procedure quite manageable. The current environment, however, raises the question whether use of FAR 9.505-4 continues to be workable for NASA. For example, in providing contract closeout services, the contractor and its employees may have access to hundreds of contract files, each of which should document all pre and post award activities for a particular contract. Typically, the contracts to be closed out will include multiple subcontractors. Many subcontractors will also have lower-tier subcontracts. To ensure that all of these companies have properly executed “non-disclosure agreements” among themselves could result in a huge number of interrelated agreements. Moreover, the contract closeout function is but one example of the types of services that may require one NASA contractor to have access to another contractor's confidential information before performance can proceed. Without obtaining even more support services, NASA cannot be responsible for managing this potentially enormous universe of interrelated non-disclosure agreements. </P>
                <P>
                    In today's environment, NASA must rely heavily on private sector service contractors for support in performing essential management activities and administrative functions. For contracts requiring this type of support, the Assistant Administrator for Procurement has determined that it is not in the NASA's interest to follow the 
                    <PRTPAGE P="67996"/>
                    general rule stated in FAR 9.505-4(b) and, in accordance with FAR 9.503, has waived its application. Rather than demand an unworkable mass of interrelated third party non-disclosure agreements, NASA will implement the policy and procedures described in the proposed 1837.203-70 to manage the risks associated with one contractor having access to another contractor's confidential information and to assure those that submit this type of information that NASA will protect it from unauthorized use or disclosure.
                </P>
                <P>As one element of this new approach, 1837.203-70(d)(1) requires that contractors receiving access to confidential information must have developed a comprehensive organizational conflicts of interest avoidance plan. Recognizing that developing this plan may take considerable time and effort, proposals need only summarize the offeror's analysis of the potential organizational conflicts of interest that may arise from having access to another contractor's confidential information, or to Government-generated information that is subject to an exception to the Freedom of Information Act. Each offeror's analysis, together with the other elements of each proposal, will be considered in selecting a contractor for award. After award, the contractor must develop and submit to the contracting officer for review and approval a comprehensive organizational conflict of interest avoidance plan that identifies all potential problems and proposes specific methods to control, mitigate, or eliminate any organizational or ethical concerns noted. This plan must also commit the contractor to take all corrective actions necessary to address any failures to protect confidential information from unauthorized use or disclosure. Once the contracting officer approves this plan, he/she will incorporate the document into the resulting contract. </P>
                <P>NASA proposes two clauses to implement the above policies in solicitations and contracts. The first clause at 1852.237-72, Access to Confidential Information, would go into service contracts that involve access to information in the Government's possession that is necessary to support NASA's management activities and administrative functions. This clause would delineate the service contractor's responsibilities to limit to the purposes specified in the contract its use of any of this information that is confidential, to safeguard the information from unauthorized outside disclosure, and to train employees and obtain their written commitments to handle the information in an authorized manner, only. </P>
                <P>The second clause at 1852.237-73, Release of Confidential Information, would go in all solicitations and contracts to notify offerors and contractors that NASA may release their confidential information to other contractors supporting NASA's management activities and administrative functions. Recognizing that this announcement may cause concerns for these offerors and contractors, the clause recites the protections embodied in the receiving, support service contract through the new clause at 1852.237-72. Essentially, the clause at 1852.237-73 announces NASA's intent to release companies' confidential information to support service contractors. But, in announcing this intent, the clause also promises that the support contractors will implement specific and enumerated safeguards and procedures to protect the information. </P>
                <HD SOURCE="HD1">B. Regulatory Flexibility Act </HD>
                <P>
                    NASA certifies that this proposed rule will not have a significant economic impact on a substantial number of small business entities within the meaning of the Regulatory Flexibility Act (5 U.S.C. 601, 
                    <E T="03">et. seq</E>
                    .), because the proposed new, streamlined approach of having each service contractor implement specific safeguards and procedures should offer the same or better protection for confidential information belonging to small business entities than does the current system of third party agreements, envisioned by FAR 9.505-4. This proposed rule should ease the burden on small business entities by not requiring them to enter multiple, interrelated third party agreements with the numerous service contractors that support NASA's management activities and administrative functions. 
                </P>
                <HD SOURCE="HD1">C. Paperwork Reduction Act </HD>
                <P>
                    The Paperwork Reduction Act does not apply because the proposed changes to the NFS do not impose any recordkeeping or information collection requirements, or collections of information from offerors, contractors, or members of the public that require the approval of the Office of Management and Budget under 44 USC 3501, 
                    <E T="03">et. seq</E>
                    . 
                </P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 48 CFR Parts 1809, 1837, and 1852 </HD>
                    <P>Government Procurement.</P>
                </LSTSUB>
                <SIG>
                    <NAME>Tom Luedtke, </NAME>
                    <TITLE>Assistant Administrator for Procurement.</TITLE>
                </SIG>
                <P>Accordingly, 48 CFR parts 1809, 1837, and 1852 are proposed to be amended as follows: </P>
                <P>1. The authority citation for 48 CFR parts 1809, 1837, and 1852 continues to read as follows: </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>42 U.S.C. 2473(c)(1). </P>
                </AUTH>
                <PART>
                    <HD SOURCE="HED">PART 1809—CONTRACTOR QUALIFICATIONS </HD>
                    <P>2. Add section 1809.505-4 to read as follows: </P>
                    <SECTION>
                        <SECTNO>1809.505-4 </SECTNO>
                        <SUBJECT>Obtaining access to confidential information. </SUBJECT>
                        <P>(b) In accordance with FAR 9.503, the Assistant Administrator for Procurement has determined that it would not be in the Government's interests for NASA to comply strictly with FAR 9.505-4(b) when acquiring services to support management activities and administrative functions. The Assistant Administrator for Procurement has, therefore, waived the requirement that before gaining access to other companies' proprietary or confidential (see 1837.203-70) information contractors must enter specific agreements with each of those other companies to protect their information from unauthorized use or disclosure. Accordingly, NASA will not require contractors and subcontractors and their employees in procurements that support management activities and administrative functions to enter into separate, interrelated third party agreements to protect confidential information from unauthorized use or disclosure. As an alternative to numerous, separate third party agreements, 1837.203-70 prescribes detailed policy and procedures to protect contractors from unauthorized use or disclosure of its confidential information. Nothing in this section waives the requirements of FAR 37.204 and 1837.204. </P>
                    </SECTION>
                </PART>
                <PART>
                    <HD SOURCE="HED">PART 1837—SERVICE CONTRACTING </HD>
                    <P>3. Add sections 1837.203-70, 1837.203-71, and 1837.203-72 to read as follows: </P>
                    <SECTION>
                        <SECTNO>1837.203-70 </SECTNO>
                        <SUBJECT>Providing contractors access to confidential information. </SUBJECT>
                        <P>
                            (a)(1) As used in this subpart, “confidential information” refers to information that the contractor has developed at private expense or that the Government has generated that qualifies 
                            <PRTPAGE P="67997"/>
                            for an exception to the Freedom of Information Act, which is not currently in the public domain, may embody trade secrets or commercial or financial information, and may be confidential or privileged. 
                        </P>
                        <P>(2) As used in this subpart, “requiring organization” refers to the NASA organizational element or activity that requires specified services to be provided. </P>
                        <P>(3) As used in this subpart, “receiving entity” refers to the service-providing contractor that receives confidential information from NASA to provide services to the requiring organization. </P>
                        <P>(b) To support management activities and administrative functions, NASA relies on the services of numerous contractors. Contractors providing these services may require access to confidential information in the Government's possession, which may be entitled to protection from unauthorized use or disclosure. NASA shall require any service contractor that receives access to confidential information to take the steps contained in the clause at 1852.237-72, Access to Confidential Information, to protect it from unauthorized use or disclosure. </P>
                        <P>(c) The requiring organization is responsible for identifying when a requirement will require access to confidential information and making the determination that providing access is necessary for accomplishing the Agency's mission. The requiring organization is responsible for reviewing any contractor requests for access to information to determine whether the access is necessary and whether the information requested is considered confidential as defined in paragraph (a) of this section. </P>
                        <P>(d)(1) Solicitations for services that require contractor access to confidential information shall require each offeror (potential receiving entity) to submit with its proposal a preliminary analysis of possible organizational conflicts of interest that might flow from the award of a contract. After selection, the new service contractor must submit for approval a comprehensive organizational conflict of interest avoidance plan, based on the preliminary analysis. This plan should thoroughly analyze all organizational conflicts of interest that might arise because the service contractor has access to other companies' confidential information. This analysis should propose specific methods to control, mitigate, or eliminate all problems identified. The contracting officer shall incorporate the approved plan into the resulting contract, as a compliance document. </P>
                        <P>(2) If the contractor will be operating an information technology system for NASA that contains confidential information, the operating contract shall include the clause at 1852.204-76, Security Requirements for Unclassified Information Technology Resources, which requires the implementation of an Information Technology Security Plan to protect information processed, stored, or transmitted from unauthorized access, alteration, disclosure, or use. </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>1837.203-71 </SECTNO>
                        <SUBJECT>Release of contractors' confidential information. </SUBJECT>
                        <P>(a) By submitting offers or performing contracts, offerors and contractors agree that NASA may provide non-NASA employees access to their confidential information, subject to the safeguards and protections delineated in the clause at 1852.237-72, Access to Confidential Information. </P>
                        <P>(b) As required by the clause at 1852.237-73, Release of Confidential Information, or another contract clause or solicitation provision, contractors must identify confidential information submitted as part of a proposal or in performance of a contract. The contracting officer shall evaluate the contractor's claim to have submitted “confidential information” in deciding whether NASA and its service contractors must expend time and resources to protect and safeguard the information in accordance with the clause at 1852.237-72. </P>
                    </SECTION>
                    <SECTION>
                        <SECTNO>1837.203-72 </SECTNO>
                        <SUBJECT>NASA contract clauses. </SUBJECT>
                        <P>(a) The contracting officer shall insert the clause at 1852.237-72, Access to Confidential Information, in all solicitations and contracts for services that require access to confidential information belonging to other companies or generated by the Government. </P>
                        <P>(b) The contracting officer shall insert the clause at 1852.237-73, Release of Confidential Information, in all solicitations, contracts, and basic ordering agreements . </P>
                    </SECTION>
                </PART>
                <PART>
                    <HD SOURCE="HED">PART 1852—SOLICITATION PROVISIONS AND CONTRACT CLAUSES </HD>
                    <P>4. Add sections 1852.237-72 and 1852.237-73 to read as follows: </P>
                    <SECTION>
                        <SECTNO>1852.237-72 </SECTNO>
                        <SUBJECT>Access to Confidential Information. </SUBJECT>
                        <P>As prescribed in 1837.203-72(a), insert the following clause:</P>
                        <EXTRACT>
                            <HD SOURCE="HD1">ACCESS TO CONFIDENTIAL INFORMATION (XX/XX) </HD>
                            <P>(a) As used in this clause, “confidential information” refers to information that a contractor has developed at private expense, or that the Government has generated that qualifies for an exception to the Freedom of Information Act, which is not currently in the public domain, and may embody trade secrets or commercial or financial information, and may be confidential or privileged. </P>
                            <P>(b) To assist NASA in accomplishing management activities and administrative functions, the Contractor shall provide the services specified elsewhere in this contract. Performing these services may require access to confidential information that other companies have furnished to the Government in the course of providing supplies or services, or that the Government has generated. </P>
                            <P>(c) In performing this contract, the Contractor agrees to— </P>
                            <P>(1) Utilize any confidential information coming into its possession only for the purposes of performing the services specified in this contract, and never to improve its own competitive position in another procurement. </P>
                            <P>(2) Safeguard confidential information coming into its possession from unauthorized use and disclosure. </P>
                            <P>(3) Allow access to confidential information only to those employees that need it to perform services under this contract. </P>
                            <P>(4) Preclude access and disclosure of confidential information to persons and entities outside of the Contractor's organization. </P>
                            <P>(5) Train employees who may require access to confidential information about their obligations to utilize it only to perform the services specified in this contract and to safeguard it from unauthorized use and disclosure. </P>
                            <P>(6) Obtain an express, binding written agreement from each employee who receives access to confidential information to protect it from unauthorized use or disclosure and to utilize it only for the purposes of performing this contract. </P>
                            <P>(7) Establish a monitoring process to ensure that employees comply with all reasonable security procedures, report any breaches to the Contracting Officer, and implement any necessary corrective actions. </P>
                            <P>(d) The Contractor will comply with all procedures and obligations specified in its Organizational Conflict of Interest Avoidance Plan, which the Contracting Officer has approved and incorporated into this contract. </P>
                            <P>(e) The nature of the work on this contract may subject the Contractor and its employees a variety of laws and regulations relating to ethics, conflicts of interest, corruption, and other criminal or civil matters relating to the award and administration of government contracts. Recognizing that this contract establishes a high standard of accountability and trust, the Government will carefully review the Contractor's performance in relation to the mandates and restrictions found in these laws and regulations. </P>
                            <P>
                                (f) The Contractor shall include the substance of this clause, including this 
                                <PRTPAGE P="67998"/>
                                paragraph (f), suitably modified to reflect the relationship of the parties, in all subcontracts that may involve access to confidential information. 
                            </P>
                            <FP>(End of clause)</FP>
                        </EXTRACT>
                    </SECTION>
                    <SECTION>
                        <SECTNO>1852.237-73 </SECTNO>
                        <SUBJECT>Release of Confidential Information. </SUBJECT>
                        <P>As prescribed in 1837.203-72(b), insert the following clause:</P>
                        <EXTRACT>
                            <HD SOURCE="HD1">RELEASE OF CONFIDENTIAL INFORMATION (XX/XX) </HD>
                            <P>(a) As used in this clause, “confidential information” refers to information, not currently in the public domain, that the Contractor has developed at private expense, may embody trade secrets or commercial or financial information, and that may be confidential or privileged. </P>
                            <P>(b) In accomplishing management activities and administrative functions, NASA relies heavily on the services of various contractors. To perform these services, contractors, as well as their subcontractors and their individual employees, may need access to confidential information submitted by the Contractor under this contract. </P>
                            <P>(c)(1) The Contractor shall mark or otherwise identify any confidential information submitted in support of this proposal or in performing this contract. The Contracting Officer will evaluate the Contractor's claim to have submitted “confidential information,” as defined above, in deciding whether NASA and its service contractors must protect and safeguard the information in accordance with the clause at 1852.237-72, Access to Confidential Information. Unless the Contracting Officer decides to challenge the Contractor's “confidential information” marking, NASA and its service contractors and their employees shall apply all of the conditions and safeguards listed in the clause at 1852.237-72. </P>
                            <P>(2) For information already in NASA's possession, the Contracting Officer shall attempt to identify the owner and afford that entity a reasonable opportunity to assert confidentiality in accordance with the principles and criteria delineated in the FAR. For purposes of asserting confidentiality, the parties may agree to use the procedures delineated in the clause at FAR 52.227-14 as a guide. </P>
                            <P>(d) Any entity that receives access to confidential information needed to assist NASA in accomplishing management activities and administrative functions must be operating under a contract that contains the clause at 1852.237-72, Access to Confidential Information. This clause obligates the receiving entity to do the following: </P>
                            <P>(1) Comply with all procedures and obligations specified in its contract, including the Organizational Conflict of Interest Avoidance Plan, which the Contracting Officer has approved and incorporated into its contract. </P>
                            <P>(2) Utilize any confidential information coming into its possession only for the purposes of performing the services specified in its contract. </P>
                            <P>(3) Safeguard confidential information coming into its possession from unauthorized use and disclosure. </P>
                            <P>(4) Allow access to confidential information only to those employees that need it to perform services under its contract. </P>
                            <P>(5) Preclude access and disclosure of confidential information to persons and entities outside of the contractor's organization. </P>
                            <P>(6) Train employees who may require access to confidential information about their obligations to utilize it only to perform the services specified in its contract and to safeguard it from unauthorized use and disclosure. </P>
                            <P>(7) Obtain an express, binding written agreement from each employee who receives access to confidential information to protect it from unauthorized use or disclosure and to utilize it only for the purposes of performing the contract. </P>
                            <P>(8) Establish a monitoring process to ensure that employees comply with all reasonable security procedures, report any breaches to the Contracting Officer, and implement any necessary corrective actions. </P>
                            <P>(e) When the receiving entity will have primary operational responsibility for an information technology system for NASA that contains confidential information, the entity's contract shall include the clause at 1852.204-76, Security Requirements for Unclassified Information Technology Resources. The Security Requirements clause requires the receiving entity to implement an Information Technology Security Plan to protect information processed, stored, or transmitted from unauthorized access, alteration, disclosure, or use. Receiving entity personnel requiring privileged access or limited privileged access to these information technology systems are subject to screening using the standard National Agency Check (NAC) forms appropriate to the level of risk for all. The Contracting Officer may allow the receiving entity to conduct its own screening, provided this entity employs substantially equivalent screening procedures. </P>
                            <P>(f) This clause does not affect NASA's responsibilities under the Freedom of Information Act. </P>
                            <P>(g) The Contractor shall insert this clause, including this paragraph (g), suitably modified to reflect the relationship of the parties, in all subcontracts that may require the furnishing of confidential information. </P>
                            <FP>(End of clause)</FP>
                        </EXTRACT>
                    </SECTION>
                </PART>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-29930 Filed 12-4-03; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 7510-01-U</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration</SUBAGY>
                <CFR>50 CFR Part 660</CFR>
                <DEPDOC>[Docket No. 031125288-3288-01; I.D. 110303A]</DEPDOC>
                <RIN>RIN 0648-AR35</RIN>
                <SUBJECT>Fisheries Off West Coast States and in the Western Pacific; Pacific Coast Groundfish Fishery; Amendment 16-2</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed rule; request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>NMFS issues this proposed rule to implement Amendment 16-2 to the Pacific Coast Groundfish Fishery Management Plan (FMP). Amendment 16-2 amends the FMP to include overfished species rebuilding plans for lingcod, canary rockfish, darkblotched rockfish, and Pacific ocean perch (POP) within the FMP. Amendment 16-2 is intended to address the requirements of the Magnuson-Stevens Fishery Conservation and Management Act (Magnuson-Stevens Act) to protect and rebuild overfished species managed under a Federal FMP. Amendment 16-2 is also intended to partially respond to a Court order, in which NMFS was ordered to provide Pacific Coast groundfish rebuilding plans as FMPs, FMP amendments, or regulations, per the Magnuson-Stevens Act.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted in writing by January 5, 2004.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments on Amendment 16-2 or supporting documents should be sent to D. Robert Lohn, Administrator, Northwest Region, NMFS, Sand Point Way NE., BIN C15700, Seattle, WA 98115-0070. Attn: Becky Renko.</P>
                    <P>Copies of Amendment 16-2 and its associated environmental impact statement/regulatory impact analysis/initial regulatory flexibility analysis (EIS/RIR/IRFA) are available from Donald McIsaac, Executive Director, Pacific Fishery Management Council, 7700 NE Ambassador Place, Portland, OR 97220, phone: 503-820-2280.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Becky Renko (Northwest Region, NMFS), phone: 206-526-6150; fax: 206-526-6736 and; e-mail: becky.renko@noaa.gov.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <PRTPAGE P="67999"/>
                <HD SOURCE="HD1">Electronic Access</HD>
                <P>
                    This 
                    <E T="04">Federal Register</E>
                     document is also accessible via the internet at the website of the Office of the 
                    <E T="04">Federal Register</E>
                    's website at: 
                    <E T="03">http://www.gpoaccess.gov/fr/index.html</E>
                    .
                </P>
                <P>Amendment 16-2 revises the FMP to include overfished species rebuilding plans for lingcod, canary rockfish, darkblotched rockfish, and POP and adds specific rebuilding parameters to the Code of Federal Regulations (CFR) at 50 CFR 660.370, for each overfished species. This rulemaking is necessary to implement the rebuilding plans specified by Amendment 16-2.</P>
                <P>
                    Amendment 16-2 address the requirements of the Magnuson-Stevens Act) to protect and rebuild overfished species managed under a Federal FMP. Amendment 16-2 is also intended to partially respond to a Court order in 
                    <E T="03">Natural Resources Defense Council, Inc</E>
                    . v. 
                    <E T="03">Evans</E>
                    , 168 F. Supp. 2d 1149 (N.D. Cal 2001,), in which NOAA Fisheries was ordered to provide Pacific Coast groundfish rebuilding plans as FMPs, FMP amendments, or regulations, per the Magnuson-Stevens Act. A Notice of Availability for Amendment 16-2 was published on November 7, 2003 (68 FR 63053).
                </P>
                <P>This proposed rule is based on recommendations of the Council, under the authority of the Pacific Coast Groundfish FMP and the Magnuson-Stevens Act. Background information and the Council's recommendations are summarized below. Further detail appears in the EIS/RIR/IRFA prepared by Council staff for Amendment 16-2.</P>
                <HD SOURCE="HD1">Background</HD>
                <P>In the fall of 2000, NMFS had approved the first three rebuilding plans for lingcod, boccacio, and POP (September 5, 2000, 65 FR 53646). Subsequently, requirements for developing overfished species rebuilding plans were addressed in Amendment 12 to the FMP, which were submitted for public review (September 8, 2000, 65 FR 54475) and approved by NMFS on December 7, 2000.</P>
                <P>During NMFS's review of Amendment 12, the agency considered whether the three previously approved rebuilding plans met the requirements of Amendment 12 and concluded that the plans did not. As a result, NMFS instructed the Council to re-submit the rebuilding plans for lingcod, boccacio, and POP. The final rule to implement Amendment 12 describes NMFS's revocation of the lingcod, boccacio, and POP rebuilding plans (December 29, 2000, 65 FR 82947). In the absence of final rebuilding plans approved by NMFS, the groundfish fishery has continued to operate under interm rebuilding measures for these species.</P>
                <P>While NMFS and the Council were developing rebuilding plans that were consistent with the requirements of Amendment 12, NMFS notified the Council that canary rockfish and cowcod were overfished and that Council must submit rebuilding plans for these species (On January 4, 2000 65 FR 221). On January 11, 2001 (66 FR 2338), NMFS notified the Council that darkblotched and widow rockfish were overfished and that Council must submit rebuilding plans for these species.</P>
                <P>
                    On August 20, 2001, a Federal magistrate ruled in 
                    <E T="03">National Resources Defense Council, Inc.</E>
                     v. 
                    <E T="03">Evans</E>
                     (N.D. Cal. 2001) that rebuilding plans under the FMP must be in the form of a plan amendment or proposed regulations as specified by the Magnuson-Stevens Act, 16 U.S.C. 1854 (e)(3). In accordance with the Court ruling, the magistrate issued an order setting aside those portions of Amendment 12 dealing with rebuilding plans (Amendment 12 provided a framework for rebuilding plans that were not themselves plan amendments or proposed regulations). As a result of the magistrate's decision, the Council was required to amend the FMP to make rebuilding plans consistent with the Magnuson-Stevens Act.
                </P>
                <P>On January 11, 2002 (67 FR 1555), NMFS notified the Council that yelloweye rockfish was overfished and that the Council must submit a rebuilding plan. On April 15, 2002 (67 FR 18117), NMFS notified the Council that Pacific whiting was overfished and that the Council must submit a rebuilding plan.</P>
                <P>
                    Amendment 16-1 was prepared in part to respond to the court order. Amendment 16 1 establishes a process for and standards by which the Council will specify rebuilding plans for groundfish stocks that are declared overfished. Amendment 16-1 also amends the FMP to require that Pacific Coast groundfish overfished species rebuilding plans be added into the FMP via FMP amendment, and implemented through Federal regulations. Amendment 16 1 is intended to ensure that overfished species rebuilding plans meet the requirements of the Magnuson-Stevens Act, in particular National Standard 1 on overfishing and section 304(e), which addresses rebuilding of overfished fisheries. NMFS approved Amendment 16-1 on November 14, 2003. A proposed rule to codify provisions of Amendment 16-1 was published in the 
                    <E T="04">Federal Register</E>
                     on September 5, 2003 (68 FR 52732).
                </P>
                <P>
                    For each approved overfished species rebuilding plan, the following parameters will be specified in the FMP: estimates of unfished biomass (B
                    <E T="8142">0</E>
                    ) and target biomass (B
                    <E T="8142">MSY</E>
                    ), the year the stock would be rebuilt in the absence of fishing (T
                    <E T="8142">MIN</E>
                    ), the year the stock would be rebuilt if the maximum time period permissible under National Standard Guidelines were applied (T
                    <E T="8142">MAX</E>
                    ) and the target year in which the stock would be rebuilt under the adopted rebuilding plan (T
                    <E T="8142">Target</E>
                    ). Other relevant information listed in Amendment 16-1 will also be included in the FMP, including the probability of the stock attaining B
                    <E T="8142">MSY</E>
                     by T
                    <E T="8142">MAX</E>
                     (P
                    <E T="8142">MAX</E>
                    ). These estimated rebuilding parameters will serve as management benchmarks in the FMP and the FMP will not be amended if the values for these parameters change after new stock assessments are completed, as is likely to happen.
                </P>
                <P>
                    As required by the standards established by Amendment 16-1, the rebuilding plans being adopted under Amendment 16-2 for lingcod, canary rockfish, darkblotched rockfish, and POP include B
                    <E T="8142">0</E>
                    , B
                    <E T="8142">MSY</E>
                    , T
                    <E T="8142">MIN</E>
                    , T
                    <E T="8142">MAX</E>
                    , and T
                    <E T="8142">Target</E>
                     for each species. If adopted, Amendment 16-2 would add these parameters to section 4.5.4. of the FMP. Other relevant information on each of these overfished stocks, such as stock distribution, fishery interaction, and the rebuilding strategy would also be added to section 4.5.4 of the FMP if the rebuilding plans proposed under Amendment 16-2 are adopted.
                </P>
                <P>Amendment 16-1 specified two rebuilding parameters that are to be codified in Federal regulations for individual species rebuilding plans. This proposed rule adds these rebuilding parameters to the Code of Federal Regulations (CFR) at 50 CFR 660.370. These parameters are the target year for rebuilding and the harvest control rule that is to be used during the rebuilding period. The target rebuilding year is the year in which there is a 50 percent likelihood that the stock will have been rebuilt with a given mortality rate. The harvest control rule expresses a given fishing mortality rate that is to be used over the course of rebuilding. These parameters would be used to establish the annual optimum yields (OYs). Conservation and management goals defined in the FMP require the Council and NMFS to manage to the appropriate harvest levels for a species or species groups, including those harvest levels established for rebuilding overfished species.</P>
                <P>
                    If, after a new stock assessment, the Council and NMFS conclude that either 
                    <PRTPAGE P="68000"/>
                    or both of the parameters defined in regulation should be revised, the revision will be implemented through the Federal rulemaking process, and the updated values codified in the Federal regulation. Generally, the target year should only be changed in unusual circumstances. Two such unusual circumstances include (1) if, it is determined, based on new information, that the existing target year is later that the maximum rebuilding time (T
                    <E T="8142">MAX</E>
                    ), (2) or if the harvest control rule calculated from the new information is estimated to result in such a low OY as to cause substantial socio-economic impacts. Any change to a harvest control rule must be fully supported by a corresponding analysis and updated through the Federal rulemaking process which would include opportunity for public notice and comment.
                </P>
                <P>An approved rebuilding plan will be implemented through setting OYs and establishing management measures necessary to maintain the fishing mortality within the OYs to achieve objectives related to rebuilding requirements.</P>
                <P>At the Council's June 2003 meeting, rebuilding plans for lingcod, canary rockfish, darkblotched rockfish, and POP were adopted and include the parameters listed below. When making the recommendation to implement these rebuilding plans, the Council sought to balance the rebuilding risks to each stock with the short and long-term socio-economic costs borne by groundfish buyers, commercial harvesters, and recreational operators as a result of constraining the fisheries to reduce total mortality of these overfished species.</P>
                <P>Amendment 16-2 will be followed by Amendment 16-3. A notice of intent to prepare an Environmental Impact Statement (EIS) was published on September 12, 2003 (68 FR 53712) for Amendment 16-3. If approved, Amendment 16-3 will contain rebuilding plans for bocaccio, cowcod, widow rockfish and yelloweye rockfish. The Council is scheduled to take final action on the Amendment 16-3 rebuilding plans at its April 2004 meeting. A Draft EIS is scheduled for publication in June 2004.</P>
                <HD SOURCE="HD1">Lingcod</HD>
                <P>Lingcod are irregularly distributed coastwide in hard bottom areas and around rocky reefs and are encountered in a variety of commercial and recreational fisheries. Lingcod is also an important recreational species coastwide. North of 40°10′ N. lat., limited entry trawl and limited entry fixed gear vessels have historically landed a substantial portion of the lingcod landings in that area. The open access sector, which is comprised of many types of fixed gear and uses a variety of strategies, has also accounted for a substantial portion of the lingcod mortality.</P>
                <P>Date declared overfished: March 3, 1999.</P>
                <P>Status of the stock when declared overfished: In 1999 the biomass was believed to be at 10 percent of its unfished biomass level. A coastwide assessment was conducted in 2000 and confirmed that the stock was overfished coastwide.</P>
                <P>
                    B
                    <E T="8142">0</E>
                    : 22,882 mt north and 20,971 mt south
                </P>
                <P>
                    B
                    <E T="8142">MSY</E>
                    : 9,153 mt north and 8,389 south
                </P>
                <P>
                    T
                    <E T="8142">MIN</E>
                    : 2007
                </P>
                <P>
                    T
                    <E T="8142">MAX</E>
                    : 2009
                </P>
                <P>
                    P
                    <E T="8142">MAX</E>
                    : 60 percent
                </P>
                <P>
                    T
                    <E T="8142">TARGET</E>
                    : 2009
                </P>
                <P>Harvest control rule: F=0.00531 north and F=0.061 south</P>
                <P>Rebuilding strategy at the time of rebuilding plan adoption: Management measures intended to limit bycatch of lingcod include the use of Rockfish Conservation Areas (RCAs) to restrict fishing in areas where overfished species are most likely to occur, and the use of cumulative trip limits. Small trip limits are allowed in the trawl fishery to accommodate true incidental catch. Lingcod landings by the limited entry fixed gear and open access fisheries are severely limited during the summer months and have been prohibited during the winter months. Lingcod are vulnerable to these gears during the winter nesting period, but have a high rate of survival when released alive. In addition to recreational bag limits, similar season restrictions have been used in the California and Washington recreational fisheries during the winter months.</P>
                <HD SOURCE="HD1">Canary rockfish</HD>
                <P>Canary rockfish prefer rocky areas on the continental shelf (shelf) and are encountered in a wide variety of commercial and recreational fisheries. Limited entry vessels targeting flatfish and arrowtooth flounder have accounted for a large portion of the landed catch north of 40°10′ N. lat. Smaller amounts are taken during the primary whiting season and DTS (Dover sole-thornyhead-sablefish complex) trawl fishery, as well as by fixed gear vessels targeting groundfish on the shelf. Recreational vessels, mainly off the coast of northern California, account for most of the recreational catch of canary rockfish.</P>
                <P>Date declared overfished: January 4, 2000 (65 FR 221)</P>
                <P>Status of the stock when declared overfished: 22 percent of its unfished biomass level north of Cape Blanco and 8 percent of its unfished biomass level south of Cape Blanco.</P>
                <P>
                    B
                    <E T="8142">0</E>
                    : 31,550 mt
                </P>
                <P>
                    B
                    <E T="8142">MSY</E>
                    : 12,620 mt
                </P>
                <P>
                    T
                    <E T="8142">MIN</E>
                    : 2057
                </P>
                <P>
                    T
                    <E T="8142">MAX</E>
                    : 2076
                </P>
                <P>
                    P
                    <E T="8142">MAX</E>
                    : 60 percent
                </P>
                <P>
                    T
                    <E T="8142">TARGET</E>
                    : 2074
                </P>
                <P>Harvest control rule: F=0.022</P>
                <P>Rebuilding strategy at the time of rebuilding plan adoption: Management measures intended to limit bycatch of canary rockfish include the use of RCAs and cumulative trip limits. Bottom trawling is prohibited in the trawl RCA, which covers depths where canary rockfish have been most frequently caught. Cumulative limits are structured to discourage targeting while allowing very low levels of incidental take to be landed. In addition, differential trip limits have been used for large and small footrope trawl gear. By allowing greater limits for large footrope gear and prohibiting its use in nearshore areas, there is an incentive for vessels to fish in deeper waters, beyond the range of canary rockfish.</P>
                <P>Recreational fisheries are managed through bag limits, size limits and seasons. As necessary, seasons can be shortened and bag limits reduced to stay within the OY.</P>
                <P>Darkblotched rockfish</P>
                <P>Darkblotched rockfish occurs on the outer shelf and continental slope (slope), mainly north of Point Reyes (38° N. lat.). Because of their deeper distribution, they are caught exclusively by commercial vessels. Most landings have been made by bottom trawl vessels targeting flatfish on the shelf, and rockfish and the DTS species on the slope.</P>
                <P>Date declared overfished: January 11, 2001 (66 FR 2338)</P>
                <P>Status of the stock when declared overfished: following a 2000 stock assessment the coastwide stock was believed to be at 22 percent of its unfished biomass level.</P>
                <P>
                    B
                    <E T="8142">0</E>
                    : 29,044 mt
                </P>
                <P>
                    B
                    <E T="8142">MSY</E>
                    : 11,618 mt
                </P>
                <P>
                    T
                    <E T="8142">MIN</E>
                    : 2014
                </P>
                <P>
                    T
                    <E T="8142">MAX</E>
                    : 2047
                </P>
                <P>
                    P
                    <E T="8142">MAX</E>
                    : 80 percent
                </P>
                <P>
                    T
                    <E T="8142">TARGET</E>
                    : 2030
                </P>
                <P>Harvest control rule: F=0.027</P>
                <P>
                    Rebuilding strategy at the time of rebuilding plan adoption: Management measures intended to limit bycatch of darkblotched rockfish include the use of RCAs and cumulative trip limits. The boundaries of the RCAs vary by season and fishing sector and may be modified in response to new information about 
                    <PRTPAGE P="68001"/>
                    geographical and seasonal distribution of bycatch. The seaward boundary of the trawl RCA was set at a depth that was likely to keep fishing effort in deeper waters and away from areas where the bycatch of darkblotched rockfish was highest. During the winter months, modifications to the line allow for the harvest of flatfish while minimizing the impacts on darkblotched rockfish.
                </P>
                <P>Cumulative limits for the minor slope rockfish species (the complex that darkblotched rockfish is managed under) north of 40°10′ N. lat. and splitnose rockfish were lowered to reduce the potential take of darkblotched rockfish. As needed, trip limits for other co-occurring species may be adjusted to reduce darkblotched rockfish bycatch.</P>
                <HD SOURCE="HD1">POP</HD>
                <P>POP tend to occur in similar depths as darkblotched rockfish, although they have a more northern geographic distribution. POP are caught in similar fisheries as darkblotched rockfish north of 40°10′ N. lat. Limited entry trawl vessels targeting flatfish, including petrale sole and arrowtooth flounder, account for more than 90 percent of all POP landings. POP are not an important component of the recreational fisheries.</P>
                <P>Date declared overfished: March 3, 1999</P>
                <P>Status of the stock when declared overfished: following a 1998 stock assessment of POP in the Vancouver and Columbia area, the stock was believed to be at 13 percent of unfished biomass level.</P>
                <P>
                    B
                    <E T="8142">0</E>
                    : 60,212 units of spawning output
                </P>
                <P>
                    B
                    <E T="8142">MSY</E>
                    : 24,084 units of spawning output
                </P>
                <P>
                    T
                    <E T="8142">MIN</E>
                    : 2012
                </P>
                <P>
                    T
                    <E T="8142">MAX</E>
                    : 2042
                </P>
                <P>
                    P
                    <E T="8142">MAX</E>
                    : 70 percent
                </P>
                <P>
                    T
                    <E T="8142">TARGET</E>
                    : 2027
                </P>
                <P>Harvest control rule: F=0.0082</P>
                <P>Rebuilding strategy at the time of rebuilding plan adoption: Management measures intended to limit the bycatch of POP include the use of RCAs to restrict fishing in areas where overfished species are found and cumulative trip limits. Because POP co-occur with darkblotched rockfish, measures to reduce the incidental catch of darkblotched rockfish benefit POP. These measures include seaward trawl RCA boundaries that are established to keep fishing effort in deeper water where POP are less abundant, and cumulative limits for POP and minor slope rockfish that are intended to discourage targeting while allowing low levels of incidental catch to be landed. As needed, trip limits for other co-occurring species may be adjusted to reduce darkblotched rockfish bycatch.</P>
                <HD SOURCE="HD1">Classification</HD>
                <P>At this time, NMFS has not determined whether Amendment 16-2, which this proposed rule would implement, is consistent with the national standards of the Magnuson-Stevens Act and other applicable laws. NMFS, in making that determination, will take into account the data, views, and comments received during the comment period.</P>
                <P>
                    The Council prepared a draft Environmental Impact Statement (EIS) that discusses the effects on the environment as a result of this action. A notice of availability was published on September 19, 2003 (68 FR 54900). A copy of the EIS is available from the Council office. (see 
                    <E T="02">ADDRESSES</E>
                    )
                </P>
                <P>This proposed rule has been determined to be not significant for purposes of Executive Order 12866.</P>
                <P>
                    The Council has prepared an IRFA, as required by section 603 of the Regulatory Flexibility Act. The IRFA describes the economic impact this proposed rule, if adopted, would have on small entities. A copy of the full analysis is available from the Council office (see 
                    <E T="02">ADDRESSES</E>
                    ). A summary of the analysis follows.
                </P>
                <P>The purpose of this proposed action is to implement rebuilding plans for four overfished species, lingcod, canary rockfish, darkblotched rockfish and POP. This action is necessary to meet the Magnuson-Seven Act requirements for overfished stocks which are defined in the National Standard Guidelines (50 CFR 600.310). National Standard 1 requires that remedial action be taken by preparing an FMP, FMP amendment or proposed regulation to end overfishing if it is occurring, rebuild overfished stocks to the maximum sustainable yield (MSY) level within an appropriate time frame, and to prevent stocks from becoming overfished if they are approaching an overfished threshold. The objective of this proposed rule is to implement rebuilding parameters that will result in lingcod, canary rockfish, darkblotched rockfish and POP stocks returning to their MSY biomass levels.</P>
                <P>There are no recordkeeping, reporting, or other compliance issues forthcoming from this proposed rule. This proposed rule does not duplicate, overlap, or conflict with other Federal rules.</P>
                <P>The EIS/RIR/IRFA for this rule defines six alternative actions that were considered for each of the four overfished species. The alternatives present a range of rebuilding strategies in terms of rebuilding probabilities for each species. The no action alternative would be based on the “40-10 harvest policy”, which is the default rebuilding policy for setting OYs. Under the 40-10 harvest policy, stocks with biomass levels below B40% have OYs set in relation to the biomass level. At B40%, an OY may be set equal to the ABC. However, if a stock's spawning biomass declines below B40%, the OY is scaled downward until at 10 percent (B10%) the harvest OY is set at zero unless modified for a species-specific rebuilding plan. In comparison to the other alternatives, (except the maximum conservation alternative) the 40-10 policy can result in lower OYs in the short term, when a stock is at a low biomass level, but allow greater harvests when a stock is at higher biomass levels. For further information on the 40-10 policy see the preamble for the annual specifications and management measures published on January 8, 1999 (64 FR 1316) or Section 5.3 of the FMP. The 40-10 policy alternative could require short-term reductions in OYs for stocks at lower biomass levels than would be required under the other alternatives, except the maximum conservation alternative. Such reductions could result in reduced profits, income, and employment in a wide range of groundfish fisheries over a longer period of time than would occur with the other alternatives.</P>
                <P>The maximum conservation alternative, based on a harvest mortality rate of zero, would be in place for each stock until the individual stock was rebuilt, resulting in the target rebuilding period for each stock being equal to TMIN. Each stock could be expected to rebuild fastest under this alternative, but at considerable socioeconomic cost. Because canary and darkblotched rockfish are caught in a wide range of other fisheries, a zero harvest mortality rate would likely result in the closure of other fisheries. The rebuilding of these stocks, even in the absence of fishing, is likely to result in many current participants in the commercial recreational fisheries as well as supporting businesses going out of business.</P>
                <P>
                    The maximum harvest alternative for each overfished species was based on a 50 percent probability of rebuilding the stocks to their MSY biomass levels by T
                    <E T="8142">MAX</E>
                    . This alternative would delay rebuilding for the longest period of time with the intent of keeping harvests at the highest allowable levels for the duration of rebuilding. As a result, this alternative would have the least socioeconomic impact, in the short-term. Delaying the rebuilding period under the maximum harvest alternative 
                    <PRTPAGE P="68002"/>
                    can also be expressed as the level of risk to the overfished stocks. Further delay in rebuilding could have a greater socioeconomic impact than the other alternatives, if currently healthy stocks were overfished.
                </P>
                <P>
                    Intermediate alternatives were defined for each overfished species and were based on 60-,70-and 80-percent probabilities of rebuilding the stocks to their MSY biomass by T
                    <E T="8142">MAX</E>
                    . The socio-economic impacts of the intermediate values fall within the range of the other alternatives that were fully analyzed in EIS analysis. Quantifying the differences between these alternatives is difficult given the lack of detailed socio-economic data.
                </P>
                <P>The mixed stock exception alternative would allow higher harvests of canary rockfish and could be combined with any of alternatives (except the no action alternative). Since the demands of rebuilding canary rockfish will affect a range of fisheries, (because it constrains stocks), relaxing this constraint under any of the alternatives would allow a higher harvest level in some fisheries. However, fisheries with little or no canary rockfish bycatch, but with bycatch of other overfished species, would not necessarily benefit. This alternative was not considered for POP or lingcod, since they do not constrain stocks in fisheries where they are targeted or incidentally caught.</P>
                <P>
                    The last set of alternatives considered were the Council's preferred alternatives for each species and are as follows: lingcod - 60 percent probability of rebuilding the stock to its MSY biomass by T
                    <E T="8142">max</E>
                     with a T
                    <E T="8142">TARGET</E>
                     of 2009 and a harvest rate of 0.0531 in the North and 0.0610 in the south; canary rockfish - 60 percent probability of rebuilding the stock to its MSY biomass by T
                    <E T="8142">MAX</E>
                     with a T
                    <E T="8142">TARGET</E>
                     of 2074 and a harvest rate of 0.0220, darkblotched rockfish - 80-percent probability of rebuilding the stock to its MSY biomass by T
                    <E T="8142">MAX</E>
                     with a T
                    <E T="8142">TARGET</E>
                     of 2030 and a harvest rate of 0.027, and POP - 70-percent probability of rebuilding the stock to its MSY biomass by T
                    <E T="8142">MAX</E>
                     with a T
                    <E T="8142">TARGET</E>
                     of 2027 and a harvest rate of 0.0082. The Council's preferred alternatives, were taken from the range of intermediate alternatives for each species.
                </P>
                <P>A fish-harvesting business is considered a “small” business by the Small Business Administration (SBA) if it has annual receipts not in excess of $3.5 million. The economic impacts of implementing these rebuilding plans will be shared among the participants. Approximately 1,560 vessels participate in the West Coast groundfish fisheries. Of those, about 410 vessels are registered to limited entry permits issued for either trawl, longline, or pot gear. About 1,150 vessels land groundfish against open access limits while either directly targeting groundfish or taking groundfish incidentally in fisheries directed at non-groundfish species. All but 10-20 of those vessels are considered small businesses by the SBA. Of the 450 groundfish buyers that regularly purchase groundfish, 38 buyers purchased groundfish product in excess of $1,000,000 in 2002. In the 2001 recreational fisheries, there were 106 Washington charter vessels engaged in salt water fishing outside of Puget Sound, 232 charter vessels active on the Oregon coast and 415 charter vessels active on the California coast. NMFS does not know the proportion of recreational charter vessel operations that would be considered large businesses, but the agency believes that the majority of these businesses would be considered “small” businesses by the SBA. This proposed rule is not expected to yield disproportionate economic impacts between those small and large entities.</P>
                <P>
                    Implementation of specific rebuilding plans may entail substantial economic impacts on some groundfish buyers, commercial harvesters, and recreational operators. The Council preferred rebuilding alternatives specify annual OY levels for the overfished species that are sufficient to mitigate some of the adverse economic impacts on these entities, while not compromising the statutory requirement for timely rebuilding. NMFS welcomes comments on this issue (see 
                    <E T="02">ADDRESSES</E>
                    ) and will notify the public of its final determination as to whether the action will result in a significant impact on a substantial number of small entities and will advise the SBA in the final rule for this action.
                </P>
                <P>This action was developed after meaningful consultation and collaboration with tribal representatives on the Council who have agreed with the provisions that apply to tribal vessels and is, therefore, compliant with Executive Order 13175 (Consultation and coordination with Indian tribal governments).</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects in 50 CFR Part 660</HD>
                    <P>Administrative practice and procedure, American Samoa, Fisheries, Fishing, Guam, Hawaiian Natives, Indians, Northern Mariana Islands, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <SIG>
                    <DATED>Dated: December 2, 2003.</DATED>
                    <NAME>William T. Hogarth,</NAME>
                    <TITLE>Assistant Administrator for Fisheries, National Marine Fisheries Service.</TITLE>
                </SIG>
                <P>For the reasons set out in the preamble, 50 CFR part 660 is proposed to be amended as follows:</P>
                <PART>
                    <HD SOURCE="HED">PART 660—FISHERIES OFF WEST COAST STATES AND IN THE WESTERN PACIFIC</HD>
                </PART>
                <P>l. The authority citation for part 660 continues to read as follows:</P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>
                        16 U.S.C. 1801 
                        <E T="03">et seq.</E>
                    </P>
                </AUTH>
                <P>2. Section 660.370, “Overfished species rebuilding plans” is added to read as follows:</P>
                <SECTION>
                    <SECTNO>§ 660.370</SECTNO>
                    <SUBJECT>Overfished species rebuilding plans.</SUBJECT>
                    <P>
                        (a) 
                        <E T="03">Canary rockfish</E>
                        . The target date for rebuilding the canary rockfish stock to B
                        <E T="8142">MSY</E>
                         is 2074. The harvest control rule to be used to rebuild the canary rockfish stock is an annual harvest rate of F=0.022.
                    </P>
                    <P>
                        (b) 
                        <E T="03">Darkblotched rockfish</E>
                        . The target year for rebuilding the darkblotched rockfish stock to B
                        <E T="8142">MSY</E>
                         is 2030. The harvest control rule to be used to rebuild the darkblotched rockfish stock is an annual harvest rate of F=0.027.
                    </P>
                    <P>
                        (c) 
                        <E T="03">Lingcod</E>
                        . The target year for rebuilding the lingcod stock to B
                        <E T="8142">MSY</E>
                         is 2009. The harvest control rule to be used to rebuild the lingcod stock is an annual harvest rate of F=0.0531 in the area north of 40°10 N. lat. and F=0.061 for the area south of 40°10 N. lat.
                    </P>
                    <P>
                        (d) 
                        <E T="03">Pacific ocean perch (POP)</E>
                        . The target year for rebuilding the POP stock to B
                        <E T="8142">MSY</E>
                         is 2027. The harvest control rule to be used to rebuild the POP stock is an annual harvest rate of F=0.0082.
                    </P>
                </SECTION>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30284 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-S</BILCOD>
        </PRORULE>
        <PRORULE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE </AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration </SUBAGY>
                <CFR>50 CFR Part 679 </CFR>
                <DEPDOC>[Docket No. 031125292-3292-01; I.D. 111703E] </DEPDOC>
                <SUBJECT>Fisheries of the Exclusive Economic Zone Off Alaska; Gulf of Alaska; Proposed 2004 Harvest Specifications for Groundfish </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Marine Fisheries Service (NMFS), National Oceanic and Atmospheric Administration (NOAA), Commerce. </P>
                </AGY>
                <ACT>
                    <PRTPAGE P="68003"/>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed 2004 harvest specifications for groundfish; request for comments. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>NMFS proposes 2004 harvest specifications for groundfish, reserves and apportionment thereof, Pacific halibut prohibited species catch (PSC) limits, for the groundfish fishery of the Gulf of Alaska (GOA). This action is necessary to establish harvest limits for groundfish during the 2004 fishing year. The intended effect of this action is to conserve and manage the groundfish resources in the GOA in accordance with the Magnuson-Stevens Fishery Conservation and Management Act (Magnuson-Stevens Act). </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be received by January 5, 2004. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments must be sent to Sue Salveson, Assistant Regional Administrator, Sustainable Fisheries Division, Alaska Region, NMFS, P.O. Box 21668, Juneau, AK 99802, Attn: Lori Durall, or delivered to room 401 of the Federal Building, 709 West 9th Street, Juneau, AK. Comments also may be sent via facsimile (fax) to 907-586-7557. Comments will not be accepted if submitted via e-mail or Internet. </P>
                    <P>
                        Copies of the final 2002 Stock Assessment and Fishery Evaluation (SAFE) reports, dated November 2002, are available from the North Pacific Fishery Management Council, West 4th Avenue, Suite 306, Anchorage, AK, 99510 or from its home page at 
                        <E T="03">http://www.fakr.noaa.gov/npfmc.</E>
                         Copies of the draft Environmental Assessment/Initial Regulatory Flexibility Analysis (EA/IRFA) prepared for this action are available from NMFS (see 
                        <E T="02">ADDRESSES</E>
                        ) and comments must be received by January 5, 2004. 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Tom Pearson, Sustainable Fisheries Division, Alaska Region, 907-481-1780 or e-mail at 
                        <E T="03">tom.pearson@noaa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background </HD>
                <P>
                    NMFS manages the groundfish fisheries in the exclusive economic zone off Alaska under the Fishery Management Plan (FMP) for Groundfish of the GOA. The North Pacific Fishery Management Council (Council) prepared the FMP under the authority of the Magnuson-Stevens Act, 16 U.S.C. 1801, 
                    <E T="03">et seq.</E>
                     Regulations governing U.S. fisheries and implementing the FMP appear at 50 CFR parts 600 and 679. 
                </P>
                <P>
                    The FMP and implementing regulations require NMFS, after consultation with the Council, to specify annually the total allowable catch (TAC) for each target species and for the “other species” category, the sum of which must be within the optimum yield (OY) range of 116,000 to 800,000 metric tons (mt) (§ 679.20(a)(1)(ii)). Regulations at § 679.20(c)(1) further require NMFS to publish annually, and solicit public comment on, proposed annual TACs, halibut PSC amounts, and seasonal allowances of pollock, and inshore/offshore Pacific cod. The proposed specifications set forth in Tables 1 through 9 of this document satisfy these requirements. For 2004, the sum of the proposed TAC amounts is 277,797 mt. Under § 679.20(c)(3), NMFS will publish the final specifications for 2004 after (1) considering comments received within the comment period (see 
                    <E T="02">DATES</E>
                    ), (2) consulting with the Council at its December 2003 meeting, and (3) considering new information presented in the EA and the final 2003 SAFE reports prepared for the 2004 fisheries. 
                </P>
                <P>
                    Regulations at § 679.20(c)(2)(i) provide that one-fourth of each proposed TAC and apportionment thereof (not including the reserves and the first seasonal allowances of pollock and Pacific cod), one-fourth of the proposed halibut PSC amounts, and the proposed first seasonal allowances of pollock and Pacific cod will become effective 0001 hours, Alaska local time (A.l.t.) January 1, 2004, on an interim basis and remain in effect until superseded by the final harvest specifications, which will be published in the 
                    <E T="04">Federal Register</E>
                    . Without interim specifications in effect on January 1, the groundfish fisheries would not be able to open on that date, which would result in disruption to the fishing industry. The interim harvest specifications will be published by NMFS in the 
                    <E T="04">Federal Register</E>
                     prior to January 1, 2004. 
                </P>
                <HD SOURCE="HD1">Proposed Acceptable Biological Catch (ABC) and TAC Specifications </HD>
                <P>The proposed ABC and TAC for each species or species group are based on the best available biological and socioeconomic information, including projected biomass trends, information on assumed distribution of stock biomass, and revised methods used to calculate stock biomass. The Council, its Advisory Panel (AP), and its Scientific and Statistical Committee (SSC) reviewed current biological and harvest information about the condition of groundfish stocks in the GOA in October 2003. Most of this information was initially compiled by the Council's GOA Plan Team (Plan Team) and is presented in the final 2002 SAFE report for the GOA groundfish fisheries, dated November 2002. The Plan Team annually produces such a document as the first step in the process of specifying TACs. The SAFE report contains a review of the latest scientific analyses and estimates of each species' biomass and other biological parameters, as well as summaries of the available information on the GOA ecosystem and the economic condition of the groundfish fisheries off Alaska. From these data and analyses, the Plan Team estimates an ABC for each species category. The 2002 SAFE report will be updated to include new information collected during 2003. Revised stock assessments will be made available by the Plan Team in November 2003 and will be included in the final 2003 SAFE report, which will be available in December 2003.</P>
                <P>Based on the recommendations from the SSC for overfishing levels (OFLs) and from the SSC and AP for ABCs, the Council recommended the OFLs and ABCs for stocks in tiers 3 and above, except for pollock, be based on biomass projections as set forth in the 2002 SAFE report and estimates of groundfish harvests through the 2003 fishing year. The Council recommended that OFL and ABC levels for those stocks in tiers 4 and below, for which projections cannot be made, remain unchanged from 2003 levels (Table 1). </P>
                <P>The SSC adopted the OFL and ABC recommendations from the Plan Team for all groundfish species. In the 2002 SAFE report, the ABC projection for 2004 is 65,400 mt for the combined Western, Central, and West Yakutat (W/C/WYK) GOA stock of pollock. The Plan Team did not endorse the ABC projection because the NMFS 2003 winter Shelikof survey estimates indicate that the biomass level is lower than projected and because it represents a substantial increase from the 2003 ABC. The Plan Team recommended that the 2003 ABC of 47,890 mt for the W/C/WYK pollock stock be rolled over in the proposed specifications given the apparent pessimistic survey results from the NMFS winter survey in the GOA. The SSC concurred with the pollock assessment recommendation that OFL and ABC levels be unchanged from 2003 levels until a formal stock assessment can be completed. </P>
                <P>
                    As in 2003, the SSC's, AP's and Council's recommendation for the method of apportioning the sablefish ABC among management areas includes commercial fishery and survey data. NMFS stock assessment scientists believe that the use of unbiased commercial fishery data reflecting catch-per-unit effort provides a desirable input for stock distribution assessments. The use of commercial 
                    <PRTPAGE P="68004"/>
                    fishery data is evaluated annually to assure that unbiased information is included in stock distribution models. The Council's recommendation for sablefish area apportionments also takes into account the prohibition on the use of trawl gear in the Southeast Outside (SEO) District of the Eastern GOA and makes available 5 percent of the combined Eastern GOA ABCs to trawl gear for use as incidental catch in other directed groundfish fisheries in the West Yakutat District. 
                </P>
                <P>
                    The AP and Council recommended that the ABC for Pacific cod in the GOA be apportioned among regulatory areas based on the three most recent NMFS summer trawl surveys. As in previous years, the Plan Team, SSC, and Council recommended that total removals of Pacific cod from the GOA not exceed ABC recommendations. Accordingly, the Council recommended that the TACs be adjusted downward from the ABCs by amounts equal to the 2004 guideline harvest levels (GHL) established for Pacific cod by the State of Alaska (State) for the state managed fisheries in the GOA. The effect of the State's GHL on the Pacific cod TAC is discussed in greater detail below. For 2004, NMFS proposes to establish an A season directed fishing allowance (DFA) for the Pacific cod fisheries in the GOA based on the management area TACs less the recent average A season incidental catch of Pacific cod in each management area before June 10 (
                    <E T="03">see</E>
                     § 679.20(d)(1)). The DFA and incidental catch before June 10 will be managed such that harvest in the A season will be no more than 60 percent of the annual TAC. Incidental catch taken after June 10 will continue to be taken from the B season TAC. NMFS believes that this action would better reflect the intention behind management measures analyzed in the 2001 Steller Sea Lion Protection Measures Supplemental Environmental Impact Statement to achieve temporal dispersion of the Pacific cod fisheries. NMFS believes that this action would reduce the likelihood of harvest exceeding 60 percent of the annual TAC in the A season (January 1 through June 10). The Council will continue to explore and analyze management alternatives for the Pacific cod fisheries through its Steller Sea Lion Mitigation Committee and in the development of its Gulf Rationalization Plan. 
                </P>
                <P>For 2004, the Councils recommended and NMFS proposed the ABCs listed in Table 1. These amounts reflect harvest amounts that are less than the specified overfishing amounts. The sum of 2004 ABCs for all assessed groundfish is 409,690 mt, which is lower than the 2003 ABC total of 416,600 mt. </P>
                <HD SOURCE="HD1">Specification and Apportionment of TAC Amounts </HD>
                <P>The Council adopted the AP's proposals for the 2004 GOA TAC amounts. The Council recommended TACs that are equal to ABCs for pollock, deep-water flatfish, rex sole, sablefish, shortraker and rougheye rockfish, northern rockfish, pelagic shelf rockfish, thornyhead rockfish, demersal shelf rockfish, and Atka mackerel. The Council-recommended TACs that are less than the ABCs for Pacific cod, flathead sole, shallow-water flatfish, arrowtooth flounder, Pacific ocean perch, and other rockfish. </P>
                <P>The apportionment of annual pollock TAC among the Western and Central Regulatory Areas of the GOA reflects the seasonal biomass distribution and is discussed in greater detail below. The annual pollock TAC in the Western and Central Regulatory Areas of the GOA is divided into four equal seasonal apportionments. Twenty-five percent of the annual TAC in the Western and Central Regulatory Areas of the GOA is apportioned to each of the A season (January 20 through February 25), the B season (March 10 through May 31), the C season (August 25 through September 15), and the D season (October 1 through November 1) in Statistical Areas 610, 620, and 630 of the GOA (see § 679.23(d)(2)(i) through (iv) and § 679.20(a)(5)(iii)(B)). </P>
                <P>The 2004 Pacific cod TAC is affected by the state's developing fishery for Pacific cod in state waters in the Central and Western GOA, as well as in Prince William Sound (PWS). The SSC, AP, and Council recommended that the sum of all state and Federal water Pacific cod removals should not exceed the ABC. Accordingly, the Council recommended that Pacific cod TAC be reduced from ABC levels to account for State GHLs in each regulatory area of the GOA so that the TAC for (1) the Eastern GOA be lower than the ABC by 290 mt, (2) the Central GOA be lower than the ABC by 6,038 mt, and (3) the Western GOA be lower than the ABC by 4,662 mt. These amounts reflect the sum of State's 2004 GHLs in these areas, which are 10 percent, 23 percent, and 25 percent of the Eastern, Central, and Western GOA ABCs, respectively.</P>
                <P>
                    NMFS is also establishing seasonal apportionments of the annual Pacific cod TAC in the Western and Central Regulatory Areas at 60 percent of the annual TAC to the A season for hook-and-line, pot or jig gear from January 1 through June 10 and for trawl gear from January 20 through June 10; and at 40 percent of the annual TAC to the B season for hook-and-line, pot or jig gear from September 1 through December 31 and for trawl gear from September 1 through November 1 (
                    <E T="03">see</E>
                     §§ 679.23(d)(3) and 679.20(a)(11)). These seasonal apportionments of the annual Pacific cod TAC are discussed in greater detail below. 
                </P>
                <P>The FMP specifies that the TAC for the “other species” category is calculated as 5 percent of the combined TAC amounts for target species. The 2004 GOA-wide “other species” TAC is 10,847 mt, which is 5 percent of the sum of the combined TAC amounts (216,950 mt) for the assessed target species. The sum of the TACs for all GOA groundfish is 227,797 mt, which is within the OY range specified by the FMP. The sum of the 2004 TACs is lower than the 2003 TAC sum of 236,440 mt. NMFS finds that the Council's recommendations for proposed OFL, ABC, and TAC amounts are consistent with the biological condition of groundfish stocks as adjusted for other biological and socioeconomic considerations, including maintaining the total TAC within the required OY range of 116,000 to 800,000 mt. The proposed 2004 ABCs, TACs, and OFLs are shown in Table 1. </P>
                <P>
                    In October 2003, the Council took final action on Amendment 63 to the GOA FMP. This action, if approved, would remove skates from the “other species” assemblage in the GOA and establish OFL and ABC levels for skates on an annual basis. The EA/RIR/IRFA for Amendment 63 is included in the EA/IRFA for the annual specifications and is available from NMFS (
                    <E T="03">see</E>
                     ADDRESSES). The EA for Amendment 63 examines a range of alternatives for the management of skates in the GOA. The alternatives range from a single gulfwide OFL, ABC, and TAC for all skate species in the GOA to multiple OFLs, ABCs, and TACs by management area (the Western, Central, and Eastern GOA) and by skate species targeted in directed fisheries (big skate, longnose skate, and all other skate species). At its October meeting, the Council did not recommend specific amounts for the 2004 OFL, ABC, and TAC levels for skates in the GOA pending an updated skate assessment using the most recent data collected in 2003. The updated skate assessment will be included in the final 2003 SAFE report, which will not be available for the Council's consideration until December 2003. At that time, the Council will make final recommendations for skate OFL, ABC, and TAC amounts in the GOA for the 2004 fishing year. These will be 
                    <PRTPAGE P="68005"/>
                    reflected in the final harvest specifications for the 2004 fishing year. 
                </P>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s100,10,10,10">
                    <TTITLE>Table 1.—Proposed 2004 ABCs, TACs, and Overfishing Levels of Groundfish for the Western/Central/West Yakutat (W/C/WYK), Western (W), Central (C), Eastern (E) Regulatory Areas, and in the West Yakutat (WYK), Southeast Outside (SEO), and Gulf-Wide (GW) Districts of the Gulf of Alaska </TTITLE>
                    <TDESC>[Values are rounded to the nearest metric ton] </TDESC>
                    <BOXHD>
                        <CHED H="1">
                            Species/Area 
                            <SU>1</SU>
                        </CHED>
                        <CHED H="1">ABC </CHED>
                        <CHED H="1">TAC </CHED>
                        <CHED H="1">Overfishing </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="11">
                            Pollock:
                            <SU>2</SU>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Shumagin (610) </ENT>
                        <ENT>16,788 </ENT>
                        <ENT>16,788 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">Chirikof (620) </ENT>
                        <ENT>19,685 </ENT>
                        <ENT>19,685 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">Kodiak (630) </ENT>
                        <ENT>10,339 </ENT>
                        <ENT>10,339 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="03">WYK (640) </ENT>
                        <ENT>1,078 </ENT>
                        <ENT>1,078 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="06">Subtotal: W/C/WYK </ENT>
                        <ENT>47,890 </ENT>
                        <ENT>47,890 </ENT>
                        <ENT>90,900 </ENT>
                    </ROW>
                    <ROW RUL="n,d">
                        <ENT I="03">SEO (650) </ENT>
                        <ENT>6,460 </ENT>
                        <ENT>6,460 </ENT>
                        <ENT>8,610 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="06">Total </ENT>
                        <ENT>54,350 </ENT>
                        <ENT>54,350 </ENT>
                        <ENT>99,510 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11">
                            Pacific cod:
                            <SU>3</SU>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">W</ENT>
                        <ENT>18,649 </ENT>
                        <ENT>13,987 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">C </ENT>
                        <ENT>26,254 </ENT>
                        <ENT>20,215 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="03">E </ENT>
                        <ENT>2,897 </ENT>
                        <ENT>2,607 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="06">Total </ENT>
                        <ENT>47,800 </ENT>
                        <ENT>36,809 </ENT>
                        <ENT>63,700 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11">
                            Flatfish 
                            <SU>4</SU>
                             (deep-water): 
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">W </ENT>
                        <ENT>180 </ENT>
                        <ENT>180 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">C </ENT>
                        <ENT>2,220 </ENT>
                        <ENT>2,220 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">WYK </ENT>
                        <ENT>1,330 </ENT>
                        <ENT>1,330 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="03">SEO </ENT>
                        <ENT>1,150 </ENT>
                        <ENT>1,150 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="06">Total </ENT>
                        <ENT>4,880 </ENT>
                        <ENT>4,880 </ENT>
                        <ENT>6,430 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11">Rex sole: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">W </ENT>
                        <ENT>1,280 </ENT>
                        <ENT>1,280 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">C </ENT>
                        <ENT>5,540 </ENT>
                        <ENT>5,540 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">WYK </ENT>
                        <ENT>1,600</ENT>
                        <ENT>1,600 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="03">SEO </ENT>
                        <ENT>1,050 </ENT>
                        <ENT>1,050 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="06">Total </ENT>
                        <ENT>9,470 </ENT>
                        <ENT>9,470 </ENT>
                        <ENT>12,320 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11">Flathead sole: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">W </ENT>
                        <ENT>14,916 </ENT>
                        <ENT>2,000 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">C </ENT>
                        <ENT>18,914 </ENT>
                        <ENT>5,000 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">WYK </ENT>
                        <ENT>2,634 </ENT>
                        <ENT>2,634 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="03">SEO </ENT>
                        <ENT>1,136 </ENT>
                        <ENT>1,136 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="06">Total </ENT>
                        <ENT>37,600 </ENT>
                        <ENT>10,770 </ENT>
                        <ENT>46,600 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11">
                            Flatfish 
                            <SU>5</SU>
                             (shallow-water): 
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">W </ENT>
                        <ENT>23,480 </ENT>
                        <ENT>4,500 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">C </ENT>
                        <ENT>21,740 </ENT>
                        <ENT>13,000 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">WYK </ENT>
                        <ENT>1,160 </ENT>
                        <ENT>1,160 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="03">SEO </ENT>
                        <ENT>2,960 </ENT>
                        <ENT>2,960 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="06">Total </ENT>
                        <ENT>49,340 </ENT>
                        <ENT>21,620 </ENT>
                        <ENT>61,810 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11">Arrowtooth flounder: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">W </ENT>
                        <ENT>18,670 </ENT>
                        <ENT>8,000 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">C </ENT>
                        <ENT>117,320 </ENT>
                        <ENT>25,000 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">WYK </ENT>
                        <ENT>18,877 </ENT>
                        <ENT>2,500 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="03">SEO </ENT>
                        <ENT>6,133 </ENT>
                        <ENT>2,500 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="06">Total </ENT>
                        <ENT>161,000 </ENT>
                        <ENT>38,000 </ENT>
                        <ENT>188,300 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11">
                            Sablefish 
                            <SU>6</SU>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">W </ENT>
                        <ENT>1,968 </ENT>
                        <ENT>1,968 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">C </ENT>
                        <ENT>4,931 </ENT>
                        <ENT>4,931 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">WYK </ENT>
                        <ENT>1,776 </ENT>
                        <ENT>1,776 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="03">SEO </ENT>
                        <ENT>2,726 </ENT>
                        <ENT>2,726 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,d">
                        <ENT I="06">Subtotal E </ENT>
                        <ENT>4,502 </ENT>
                        <ENT>4,502 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="06">Total </ENT>
                        <ENT>11,400 </ENT>
                        <ENT>11,400 </ENT>
                        <ENT>16,500 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11">
                            Pacific 
                            <SU>7</SU>
                             ocean perch: 
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">W </ENT>
                        <ENT>2,728 </ENT>
                        <ENT>2,700 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">C </ENT>
                        <ENT>8,597 </ENT>
                        <ENT>8,510 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">WYK </ENT>
                        <ENT>818 </ENT>
                        <ENT>810 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="03">SEO </ENT>
                        <ENT>1,657 </ENT>
                        <ENT>1,640 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,d">
                        <PRTPAGE P="68006"/>
                        <ENT I="06">Subtotal E </ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="06">Total </ENT>
                        <ENT>13,800 </ENT>
                        <ENT>13,660 </ENT>
                        <ENT>16,400 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11">
                            Short raker/rougheye: 
                            <SU>8</SU>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">W </ENT>
                        <ENT>220 </ENT>
                        <ENT>220 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">C </ENT>
                        <ENT>840 </ENT>
                        <ENT>840 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="03">E </ENT>
                        <ENT>560 </ENT>
                        <ENT>560 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="06">Total </ENT>
                        <ENT>1,620 </ENT>
                        <ENT>1,620 </ENT>
                        <ENT>2,340 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11">
                            Other rockfish 
                            <E T="51">9,10</E>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">W </ENT>
                        <ENT>90 </ENT>
                        <ENT>90 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">C </ENT>
                        <ENT>550 </ENT>
                        <ENT>550 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">WYK </ENT>
                        <ENT>270 </ENT>
                        <ENT>150 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="03">SEO </ENT>
                        <ENT>4,140 </ENT>
                        <ENT>200 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="06">Total </ENT>
                        <ENT>5,050 </ENT>
                        <ENT>990 </ENT>
                        <ENT>6,610 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11">
                            Northern rockfish:
                            <E T="51">10,12,15</E>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">W </ENT>
                        <ENT>789 </ENT>
                        <ENT>789 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">C </ENT>
                        <ENT>4,111 </ENT>
                        <ENT>4,111 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="03">E </ENT>
                        <ENT>N/A </ENT>
                        <ENT>N/A </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="06">Total </ENT>
                        <ENT>4,900 </ENT>
                        <ENT>4,900 </ENT>
                        <ENT>5,800 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11">
                            Pelagic shelf rockfish:
                            <SU>13</SU>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">W </ENT>
                        <ENT>510</ENT>
                        <ENT>510 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">C </ENT>
                        <ENT>3,480</ENT>
                        <ENT>3,480 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">WYK </ENT>
                        <ENT>640 </ENT>
                        <ENT>640 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="03">SEO </ENT>
                        <ENT>860 </ENT>
                        <ENT>860 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="06">Total </ENT>
                        <ENT>5,490 </ENT>
                        <ENT>5,490 </ENT>
                        <ENT>8,220 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11">Thornyhead rockfish: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">W </ENT>
                        <ENT>360 </ENT>
                        <ENT>360 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="03">C </ENT>
                        <ENT>840 </ENT>
                        <ENT>840 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="03">E </ENT>
                        <ENT>800 </ENT>
                        <ENT>800 </ENT>
                        <ENT/>
                    </ROW>
                    <ROW>
                        <ENT I="06">Total </ENT>
                        <ENT>2,000</ENT>
                        <ENT>2,000 </ENT>
                        <ENT>3,050 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">
                            Demersal self rockfish:
                            <SU>11</SU>
                             SEO 
                        </ENT>
                        <ENT>390 </ENT>
                        <ENT>390 </ENT>
                        <ENT>540 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Atka mackerel: GW </ENT>
                        <ENT>600 </ENT>
                        <ENT>600 </ENT>
                        <ENT>6,200 </ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">
                            Other 
                            <SU>14</SU>
                             species:
                        </ENT>
                        <ENT>GW </ENT>
                        <ENT>N/A </ENT>
                        <ENT>10,847 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="04">
                            Total 
                            <SU>16</SU>
                              
                        </ENT>
                        <ENT>409,690 </ENT>
                        <ENT>227,797 </ENT>
                        <ENT>544,330 </ENT>
                    </ROW>
                    <TNOTE>
                        <SU>1</SU>
                         Regulatory areas and districts are defined at § 679.2. 
                    </TNOTE>
                    <TNOTE>
                        <SU>2</SU>
                         Pollock is apportioned in the Western/Central Regulatory areas among three statistical areas. During the A season, the apportionment is based on an adjusted estimate of the relative distribution of pollock biomass at 25 percent, 56 percent, and 19 percent in Statistical Areas 610, 620, and 630, respectively. During the B season, the apportionment is based on the relative distribution of pollock biomass at 25 percent, 66 percent, and 9 percent in Statistical Areas 610, 620, and 630, respectively. During the C and D seasons, the apportionment is based on the relative distribution of pollock biomass at 47 percent, 23 percent, and 30 percent in Statistical Areas 610, 620, and 630, respectively. These seasonal apportionments are shown in Table 3. In the West Yakutat and Southeast Outside Districts of the Eastern Regulatory Area, pollock is not divided into seasonal allowances. 
                    </TNOTE>
                    <TNOTE>
                        <SU>3</SU>
                         The annual Pacific cod TAC is apportioned 60 percent to an A season and 40 percent to a B season in the Western and Central Regulatory Areas of the GOA. Pacific cod is allocated 90 percent for processing by the inshore component and 10 percent for processing by the offshore component. Seasonal apportionments and component allocations of TAC are shown in Table 4. 
                    </TNOTE>
                    <TNOTE>
                        <SU>4</SU>
                         “Deep water flatfish” means Dover sole, Greenland turbot, and deepsea sole. 
                    </TNOTE>
                    <TNOTE>
                        <SU>5</SU>
                         “Shallow water flatfish” means flatfish not including “deep water flatfish,” flathead sole, rex sole, or arrowtooth flounder. 
                    </TNOTE>
                    <TNOTE>
                        <SU>6</SU>
                         Sablefish is allocated to trawl and hook-and-line gears (Table 2). 
                    </TNOTE>
                    <TNOTE>
                        <SU>7</SU>
                         “Pacific ocean perch” means 
                        <E T="03">Sebastes alutus.</E>
                    </TNOTE>
                    <TNOTE>
                        <SU>8</SU>
                         “Shortraker/rougheye rockfish” means 
                        <E T="03">Sebastes borealis</E>
                         (shortraker) and 
                        <E T="03">S. aleutianus</E>
                         (rougheye). 
                    </TNOTE>
                    <TNOTE>
                        <SU>9</SU>
                         “Other rockfish” in the Western and Central Regulatory Areas and in the West Yakutat District means slope rockfish and demersal shelf rockfish. The category “other rockfish” in the Southeast Outside District means Slope rockfish. 
                    </TNOTE>
                    <TNOTE>
                        <SU>10</SU>
                         “Slope rockfish” means 
                        <E T="03">Sebastes aurora</E>
                         (aurora), 
                        <E T="03">S. melanostomus</E>
                         (blackgill), 
                        <E T="03">S. paucispinis</E>
                         (bocaccio), 
                        <E T="03">S. goodei</E>
                         (chilipepper), 
                        <E T="03">S. crameri</E>
                         (darkblotch), 
                        <E T="03">S. elongatus</E>
                         (greenstriped), 
                        <E T="03">S. variegatus</E>
                         (harlequin), 
                        <E T="03">S. wilsoni</E>
                         (pygmy), 
                        <E T="03">S. babcocki</E>
                         (redbanded), 
                        <E T="03">S. proriger</E>
                         (redstripe), 
                        <E T="03">S. zacentrus</E>
                         (sharpchin), 
                        <E T="03">S. jordani</E>
                         (shortbelly), 
                        <E T="03">S. brevispinis</E>
                         (silvergrey), 
                        <E T="03">S. diploproa</E>
                         (splitnose), 
                        <E T="03">S. saxicola</E>
                         (stripetail), 
                        <E T="03">S. miniatus</E>
                         (vermilion), and 
                        <E T="03">S. reedi</E>
                         (yellowmouth). In the Eastern GOA only, “slope rockfish” also includes northern rockfish, 
                        <E T="03">S. polyspinous.</E>
                    </TNOTE>
                    <TNOTE>
                        <SU>11</SU>
                         “Demersal shelf rockfish” means 
                        <E T="03">Sebastes pinniger</E>
                         (canary), 
                        <E T="03">S. nebulosus</E>
                         (china), 
                        <E T="03">S. caurinus</E>
                         (copper), 
                        <E T="03">S. maliger</E>
                         (quillback), 
                        <E T="03">S. helvomaculatus</E>
                         (rosethorn), 
                        <E T="03">S. nigrocinctus</E>
                         (tiger), and 
                        <E T="03">S. ruberrimus</E>
                         (yelloweye). 
                    </TNOTE>
                    <TNOTE>
                        <SU>12</SU>
                         “Northern rockfish” means 
                        <E T="03">Sebastes polyspinis.</E>
                    </TNOTE>
                    <TNOTE>
                        <SU>13</SU>
                         “Pelagic shelf rockfish” means 
                        <E T="03">Sebastes ciliatus</E>
                         (dusky), 
                        <E T="03">S. entomelas</E>
                         (widow), and 
                        <E T="03">S. flavidus</E>
                         (yellowtail). 
                    </TNOTE>
                    <TNOTE>
                        <SU>14</SU>
                         “Other species” means sculpins, sharks, skates, squid, and octopus. The TAC for “other species” equals 5 percent of the TACs of assessed target species. 
                    </TNOTE>
                    <TNOTE>
                        <SU>15</SU>
                         N/A means not applicable. 
                    </TNOTE>
                    <TNOTE>
                        <SU>16</SU>
                         The total ABC and OFL is the sum of the ABCs and OFLs for assessed target species. 
                    </TNOTE>
                </GPOTABLE>
                <PRTPAGE P="68007"/>
                <HD SOURCE="HD1">Proposed Apportionment of Reserves </HD>
                <P>
                    Regulations implementing the FMP require 20 percent of each TAC for pollock, Pacific cod, flatfish, and the “other species” category be set aside in reserves for possible apportionment at a later date (
                    <E T="03">see</E>
                     § 679.20(b)(2)). In 2003, NMFS reapportioned all of the reserves in the final harvest specifications. Between 1997 and 2000, NMFS retained the Pacific cod reserve to provide for a management buffer to account for excessive fishing effort and incomplete or late catch reporting. NMFS believes this is no longer necessary as estimates of catch and incidental catch needs in other directed fisheries have improved in recent years. For 2004, NMFS proposes apportionment of all of the reserve for pollock, Pacific cod, flatfish, and “other species”. Specifications of TAC shown in Table 1 reflect apportionment of reserve amounts for these species and species groups. 
                </P>
                <HD SOURCE="HD1">Proposed Allocations of the Sablefish TAC Amounts to Vessels Using Hook-and-Line and Trawl Gear </HD>
                <P>Under § 679.20(a)(4)(i) and (ii), sablefish TACs for each of the regulatory areas and districts are allocated to hook-and-line and trawl gear. In the Western and Central Regulatory Areas, 80 percent of each TAC is allocated to hook-and-line gear and 20 percent of each TAC is allocated to trawl gear. In the Eastern Regulatory Area, 95 percent of the TAC is allocated to hook-and-line gear and 5 percent is allocated to trawl gear. The trawl gear allocation in the Eastern Regulatory Area may only be used to support incidental catch of sablefish in directed fisheries for other target species. In recognition of the trawl ban in the SEO District of the Eastern Regulatory Area, the Council recommended that 5 percent of the combined Eastern GOA sablefish be allocated to trawl gear in the WYK District and the remainder to vessels using hook-and-line gear. In the SEO District, 100 percent of the sablefish TAC is allocated to vessels using hook-and-line gear. This recommendation results in an allocation of 225 mt to trawl gear and 1,551 mt to hook-and-line gear in the WYK District and 2,726 mt to hook-and-line gear in the SEO District. Table 2 shows the allocations of the proposed 2004 sablefish TACs between hook-and-line gear and trawl gear. </P>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s100,10,10,10">
                    <TTITLE>Table 2.—Proposed 2004 Sablefish TAC Specifications in the Gulf of Alaska and Allocations Thereof to Hook-and-Line and Trawl Gear </TTITLE>
                    <TDESC>[Values are rounded to the nearest metric ton] </TDESC>
                    <BOXHD>
                        <CHED H="1">Area/District </CHED>
                        <CHED H="1">TAC </CHED>
                        <CHED H="1">Hook-and-line allocation </CHED>
                        <CHED H="1">Trawl allocation </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Western </ENT>
                        <ENT>1,968 </ENT>
                        <ENT>1,574 </ENT>
                        <ENT>394 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Central </ENT>
                        <ENT>4,931 </ENT>
                        <ENT>3,945 </ENT>
                        <ENT>986 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">West Yakutat </ENT>
                        <ENT>1,776 </ENT>
                        <ENT>1,551 </ENT>
                        <ENT>225 </ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Southeast Outside </ENT>
                        <ENT>2,726 </ENT>
                        <ENT>2,726 </ENT>
                        <ENT>0 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="04">Total </ENT>
                        <ENT>11,400 </ENT>
                        <ENT>9,796 </ENT>
                        <ENT>1,605 </ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Proposed Apportionments of Pollock TAC Among Seasons and Regulatory Areas, and Allocations for Processing by Inshore and Offshore Components </HD>
                <P>In the GOA, pollock is apportioned by season and area, and is further allocated for processing by inshore and offshore components. Under regulations at § 679.20(a)(5)(iii)(B), the annual pollock TAC specified for the Western and Central Regulatory Areas of the GOA is apportioned into four equal seasonal allowances of 25 percent. As established by § 679.23(d)(2)(i) through (iv), the A, B, C, and D season allowances are available from January 20 through February 25, March 10 through May 31, August 25 through September 15, and October 1 through November 1, respectively. </P>
                <P>Pollock TACs in the Western and Central Regulatory Areas of the GOA in the A and B seasons are apportioned among statistical areas 610, 620, and 630 in proportion to the distribution of pollock biomass as determined by a composite of NMFS winter surveys and in the C and D seasons in proportion to the distribution of pollock biomass as determined by the four most recent NMFS summer surveys. As in 2003, the Council recommended that during the A season, the winter and summer distribution of pollock be averaged in the Central Regulatory Area to better reflect the distribution of pollock and the performance of the fishery in the area during the A season. Within any fishing year, the underage or overage of a seasonal apportionment may be added to or subtracted from subsequent seasonal apportionments in a manner to be determined by the Regional Administrator, Alaska Region, NMFS, provided that the sum of the revised seasonal allowances does not exceed 30 percent of the annual TAC apportionment for the Central and Western Regulatory Areas in the GOA (§ 679.20(a)(5)(iii)(B)). For 2004, 30 percent of the proposed annual TAC for the Central and Western Regulatory Areas is 14,044 mt. The WYK and SEO District pollock TACs of 1,078 mt and 6,460 mt, respectively, are not allocated seasonally. </P>
                <P>Regulations at § 679.20(a)(6)(i) require that 100 percent of the pollock TAC in all regulatory areas and all seasonal allowances thereof be allocated to vessels catching pollock for processing by the inshore component after subtraction of amounts that are projected by the Regional Administrator to be caught by, or delivered to, the offshore component incidental to directed fishing for other groundfish species. The amount of pollock available for harvest by vessels harvesting pollock for processing by the offshore component is that amount actually taken as incidental catch during directed fishing for groundfish species other than pollock, up to the maximum retainable amounts allowed under regulations at § 679.20(e) and (f). At this time, these incidental catch amounts are unknown and will be determined during the fishing year. </P>
                <P>
                    The proposed seasonal biomass distribution of pollock in the Western and Central GOA, area apportionments, and seasonal allowances for the A, B, C, and D seasons are summarized in Table 3. 
                    <PRTPAGE P="68008"/>
                </P>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s100,xls50,xls50,xls50,xls50">
                    <TTITLE>Table 3.—Proposed Distribution of Pollock in the Central and Western Regulatory Areas of the Gulf of Alaska; Seasonal Biomass Distribution, Area Apportionments; and Seasonal Allowances of Annual TAC in 2004 </TTITLE>
                    <TDESC>[Values are rounded to the nearest metric ton] </TDESC>
                    <BOXHD>
                        <CHED H="1">Season </CHED>
                        <CHED H="1">Shumagin (Area 610) (biomass distribution) </CHED>
                        <CHED H="1">Chirikof (Area 620) (biomass distribution) </CHED>
                        <CHED H="1">Kodiak (Area 630) (biomass distribution) </CHED>
                        <CHED H="1">Total (biomass distribution) </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">A </ENT>
                        <ENT>2,894 (25%) </ENT>
                        <ENT>6,535 (56%) </ENT>
                        <ENT>2,274 (19%) </ENT>
                        <ENT>11,703 (100%) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">B </ENT>
                        <ENT>2,894 (25%) </ENT>
                        <ENT>7,778 (66%) </ENT>
                        <ENT>1,031 (9%) </ENT>
                        <ENT>11,703 (100%) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">C </ENT>
                        <ENT>5,500 (47%) </ENT>
                        <ENT>2,686 (23%) </ENT>
                        <ENT>3,517 (30%) </ENT>
                        <ENT>11,703 (100%) </ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">D </ENT>
                        <ENT>5,500 (47%) </ENT>
                        <ENT>2,686 (23%) </ENT>
                        <ENT>3,517 (30%) </ENT>
                        <ENT>11,703 (100%) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="04">Annual Total </ENT>
                        <ENT>16,788 </ENT>
                        <ENT>19,685 </ENT>
                        <ENT>10,339 </ENT>
                        <ENT>46,812 </ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Proposed Seasonal Apportionments of Pacific Cod TAC and Allocations for Processing of Pacific Cod TAC Between Inshore and Offshore Components </HD>
                <P>Pacific cod fishing is divided into two seasons in the Western and Central Regulatory Areas of the GOA. For hook-and-line, pot and jig gear, the A season is January 1 through June 10, and the B season is September 1 through December 31. For trawl gear, the A season is January 20 through June 10, and the B season is September 1 through November 1, (§ 679.23(d)(3)). After subtraction of incidental catch, 60 percent and 40 percent of the annual TAC will be available for harvest during the A and B seasons, respectively, and will be apportioned between the inshore and offshore processing components as provided in § 679.20(a)(6)(ii). Between the A and the B seasons, directed fishing for Pacific cod is closed and fishermen participating in other directed fisheries may retain Pacific cod up to the maximum retainable amounts allowed under regulations at § 679.20(e) and (f). For purposes of clarification, NMFS points out that the dates for the A season and the B season Pacific cod fisheries differ from those of the A, B, C, and D seasons for the pollock fisheries. In accordance with § 679.20(a)(11)(ii), any overage or underage of Pacific cod harvest from the A season may be subtracted from or added to the subsequent B season. </P>
                <P>Regulations at § 679.20(a)(6)(ii) require that the TAC apportionment of Pacific cod in all regulatory areas be allocated to vessels catching Pacific cod for processing by the inshore and offshore components. Ninety percent of the Pacific cod TAC in each regulatory area is allocated to vessels catching Pacific cod for processing by the inshore component. The remaining 10 percent of the TAC is allocated to vessels catching Pacific cod for processing by the offshore component. These seasonal apportionments and allocations of the proposed 2004 Pacific cod TAC are shown in Table 4. </P>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s100,r100,10,10,10">
                    <TTITLE>Table 4.—Proposed 2004 Seasonal Apportionments and Allocation of Pacific cod TAC Amounts in the Gulf of Alaska; Allocations for Processing by the Inshore and Offshore Components </TTITLE>
                    <TDESC>[Values are rounded to the nearest metric ton] </TDESC>
                    <BOXHD>
                        <CHED H="1">Season </CHED>
                        <CHED H="1">Regulatory area </CHED>
                        <CHED H="1">TAC </CHED>
                        <CHED H="1">Component allocation </CHED>
                        <CHED H="2">Inshore (90%) </CHED>
                        <CHED H="2">Offshore (10%) </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>Western </ENT>
                        <ENT>13,987 </ENT>
                        <ENT>12,588 </ENT>
                        <ENT>1,399 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">A Season (60%) </ENT>
                        <ENT>  </ENT>
                        <ENT>8,392 </ENT>
                        <ENT>7,553 </ENT>
                        <ENT>839 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">B Season (40%) </ENT>
                        <ENT>  </ENT>
                        <ENT>5,595 </ENT>
                        <ENT>5,035 </ENT>
                        <ENT>560 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">  </ENT>
                        <ENT>Central </ENT>
                        <ENT>20,215 </ENT>
                        <ENT>18,193 </ENT>
                        <ENT>2,022 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">A Season (60%) </ENT>
                        <ENT>  </ENT>
                        <ENT>12,129 </ENT>
                        <ENT>10,916 </ENT>
                        <ENT>1,213 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">B Season (40%) </ENT>
                        <ENT>  </ENT>
                        <ENT>8,086 </ENT>
                        <ENT>7,277 </ENT>
                        <ENT>809 </ENT>
                    </ROW>
                    <ROW RUL="n,n,s">
                        <ENT I="22">  </ENT>
                        <ENT>Eastern </ENT>
                        <ENT>2,607 </ENT>
                        <ENT>2,346 </ENT>
                        <ENT>261 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="04">Total </ENT>
                        <ENT>  </ENT>
                        <ENT>36,809 </ENT>
                        <ENT>33,127 </ENT>
                        <ENT>3,682 </ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">“Other Species” TAC </HD>
                <P>The FMP specifies that the amount for the “other species” category is calculated as 5 percent of the combined TAC amounts for target species. The GOA-wide “other species” TAC is calculated as 10,847 mt, which is 5 percent of the sum of combined TAC amounts for the target species. As discussed above, if Amendment 63 is approved, skates would be removed from the “other species” assemblage and the Council would recommend final OFL, ABC, and TAC amounts for skates and an adjusted TAC for the “other species” category for the 2004 fishing year in the final 2004 harvest specifications for groundfish in the GOA. </P>
                <HD SOURCE="HD1">Proposed Pacific Halibut PSC Mortality Limits </HD>
                <P>
                    Under § 679.21(d), annual Pacific halibut PSC limits are established and apportioned to trawl and hook-and-line gear and may be established for pot gear. In October 2003, the Council 
                    <PRTPAGE P="68009"/>
                    recommended to maintain the 2003 halibut PSC limits of 2,000 mt for the trawl fisheries and 300 mt for the hook-and-line fisheries, with 10 mt of the hook-and-line limit allocated to the demersal shelf rockfish (DSR) fishery in the Southeast Outside District and the remainder to the remaining hook-and-line fisheries. NMFS concurs with this recommendation. The DSR fishery is defined at § 679.21(d)(4)(iii)(A) and historically has been apportioned this amount in recognition of its small scale harvests. Although observer data are not available to verify actual bycatch amounts because most vessels in the DSR fishery are less than 60 ft (18.3 m) length overall (LOA) and are exempt from observer coverage, halibut bycatch in the DSR fishery is assumed to be low because of the short gear soak times and duration of the DSR fishery. Also, the DSR fishery occurs in the winter when less overlap occurs in the distribution of DSR and halibut. If Amendment 63, which removes skates from the “other species” assemblage is approved, the Council, at its December 2003 meeting, may recommend a separate halibut PSC allowance for hook-and-line gear in the skates fishery for 2004. 
                </P>
                <P>Regulations at § 679.21(d)(4) authorize exemption of specified nontrawl fisheries from the halibut PSC limit. The Council recommended that pot gear, jig gear, and the hook-and-line sablefish fishery be exempted from the nontrawl halibut limit for 2004. The Council recommended these exemptions because the low halibut bycatch mortality experienced in the pot gear fisheries (4 mt in 2001, 2 mt in 2002, and 14 mt in 2003), and because of the 1995 implementation of the sablefish and halibut Individual Fishing Quota (IFQ) program that requires legal-sized halibut to be retained by vessels using hook-and-line gear if a halibut IFQ permit holder is aboard and is holding unused halibut IFQ. This provision results in reduced halibut discard in the sablefish fishery. Halibut mortality for the jig gear fleet cannot be estimated because these vessels do not carry observers. However, halibut mortality is assumed to be very low given the small amount of groundfish harvested by this gear type (336 mt in 2001, 277 mt in 2002, and 294 mt in 2003) and the assumed high survival rate of any halibut that are incidentally taken by jig gear and released. Because of these reasons, NMFS concurs with the Council's recommendations. </P>
                <P>Under § 679.21(d)(5), NMFS seasonally apportions the halibut PSC limits based on recommendations from the Council. The FMP and regulations require that the following information be considered by the Council and NMFS in seasonally apportioning halibut PSC limits: (1) Seasonal distribution of halibut, (2) seasonal distribution of target groundfish species relative to halibut distribution, (3) expected halibut bycatch needs on a seasonal basis relative to changes in halibut biomass and expected catch of target groundfish species, (4) expected bycatch rates on a seasonal basis, (5) expected changes in directed groundfish fishing seasons, (6) expected actual start of fishing effort, and (7) economic effects of establishing seasonal halibut allocations on segments of the target groundfish industry. </P>
                <P>The final rule establishing the final 2003 groundfish and PSC specifications (68 FR 9924, March 3, 2003) summarizes Council and NMFS findings with respect to each of the FMP considerations set forth above. At this time, the Council's and NMFS’ findings are unchanged from those set forth in 2003. Proposed Pacific halibut PSC limits, and apportionments thereof, are presented in Table 5. Regulations at § 679.21(d)(5)(iii) and (iv) specify that any overages or shortfalls in a seasonal apportionment of a PSC limit will be deducted from or added to the next respective seasonal apportionment within the 2004 fishing year. </P>
                <GPOTABLE COLS="6" OPTS="L2,i1" CDEF="s50,13,r50,12,r50,12">
                    <TTITLE>Table 5.—Proposed 2004 Pacific Halibut PSC Limits, Allowances, and Apportionments </TTITLE>
                    <TDESC>[The Pacific halibut PSC limit for hook-and-line gear is allocated to the demersal shelf rockfish (DSR) fishery and fisheries other than DSR. The hook-and-line sablefish fishery is exempt from halibut PSC limits. (Values are in metric tons)] </TDESC>
                    <BOXHD>
                        <CHED H="1">Trawl gear </CHED>
                        <CHED H="2">Dates </CHED>
                        <CHED H="2">Amount </CHED>
                        <CHED H="1">Hook-and-line gear </CHED>
                        <CHED H="2">Other than DSR </CHED>
                        <CHED H="3">Dates </CHED>
                        <CHED H="3">Amount </CHED>
                        <CHED H="2">DSR </CHED>
                        <CHED H="3">Dates </CHED>
                        <CHED H="3">Amount </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">January 20-April 1</ENT>
                        <ENT>550 (27.5%)</ENT>
                        <ENT>January 1-June 10 </ENT>
                        <ENT>250 (86%)</ENT>
                        <ENT>January-December 31</ENT>
                        <ENT>10 (100%) </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">April 1-July 4</ENT>
                        <ENT>400 (20%) </ENT>
                        <ENT>June 10-September 1</ENT>
                        <ENT>5 (2%) </ENT>
                        <ENT O="xl"/>
                        <ENT>  </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">July 4-September 1</ENT>
                        <ENT>600 (30%) </ENT>
                        <ENT>September 1 -December 31 </ENT>
                        <ENT>35 (12%) </ENT>
                        <ENT O="xl"/>
                        <ENT>  </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">September 1-October 1</ENT>
                        <ENT>150 (7.5%) </ENT>
                        <ENT O="xl"/>
                        <ENT> </ENT>
                        <ENT O="xl"/>
                        <ENT>  </ENT>
                    </ROW>
                    <ROW RUL="n,s,n,s,n,s">
                        <ENT I="01">October 1-December 31</ENT>
                        <ENT>300 (15%) </ENT>
                        <ENT O="xl"/>
                        <ENT> </ENT>
                        <ENT O="xl"/>
                        <ENT>  </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Total </ENT>
                        <ENT>2,000 (100%) </ENT>
                        <ENT O="xl"/>
                        <ENT>290 (100%) </ENT>
                        <ENT O="xl"/>
                        <ENT>10 (100%) </ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    Regulations at § 679.21(d)(3)(ii) authorize apportionments of the trawl halibut PSC limit to be further apportioned to trawl fishery categories, based on each category's proportional share of the anticipated halibut bycatch mortality during a fishing year and the need to optimize the amount of total groundfish harvest under the halibut PSC limit. The fishery categories for the trawl halibut PSC limits are: deep-water species complex, comprised of sablefish, rockfish, deep-water flatfish, rex sole and arrowtooth flounder; and shallow-water species complex, comprised of pollock, Pacific cod, shallow-water flatfish, flathead sole, Atka mackerel, and “other species” (§ 679.21(d)(3)(iii)). The proposed apportionment for these two fishery complexes is presented in Table 6. 
                    <PRTPAGE P="68010"/>
                </P>
                <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s100,10,10,10">
                    <TTITLE>Table 6.—Proposed 2004 Apportionment of Pacific Halibut PSC Trawl Limits Between the Trawl Gear Deep-Water Species Complex and the Shallow-Water Species Complex </TTITLE>
                    <TDESC>[Values are in metric tons] </TDESC>
                    <BOXHD>
                        <CHED H="1">Season </CHED>
                        <CHED H="1">Shallow-water </CHED>
                        <CHED H="1">Deep-water </CHED>
                        <CHED H="1">Total </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">January 20-April 1 </ENT>
                        <ENT>450 </ENT>
                        <ENT>100 </ENT>
                        <ENT>550 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">April 1-July 4 </ENT>
                        <ENT>100 </ENT>
                        <ENT>300 </ENT>
                        <ENT>400 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">July 4-September 1 </ENT>
                        <ENT>200 </ENT>
                        <ENT>400 </ENT>
                        <ENT>600 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">September 1-October 1 </ENT>
                        <ENT>150 </ENT>
                        <ENT>
                            (
                            <SU>1</SU>
                            ) 
                        </ENT>
                        <ENT>150 </ENT>
                    </ROW>
                    <ROW RUL="n,s,s,n">
                        <ENT I="11">Subtotal: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">January 20-October 1 </ENT>
                        <ENT>900 </ENT>
                        <ENT>800 </ENT>
                        <ENT>1,700 </ENT>
                    </ROW>
                    <ROW RUL="n,n,n,s">
                        <ENT I="01">October 1-December 31</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>300 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="07">Total </ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>2,000 </ENT>
                    </ROW>
                    <TNOTE>
                        <SU>1</SU>
                         No apportionment between shallow-water and deep-water fishery complexes during the 5th season (October 1-December 31). 
                    </TNOTE>
                </GPOTABLE>
                <P>Based on public comment and information contained in the final 2003 SAFE report, which will be available in December 2003, the Council may recommend, or NMFS may make, some changes in the seasonal, gear-type, and fishing-complex apportionments of halibut PSC limits for the final 2004 harvest specifications. NMFS will consider the following types of information in setting final halibut PSC limits. </P>
                <HD SOURCE="HD2">(A) Estimated Halibut Bycatch in Prior Years </HD>
                <P>The best available information on estimated halibut bycatch is data collected by observers during 2003. The calculated halibut bycatch mortality by trawl, hook-and-line, and pot gear through October 11, 2003, is 1,915 mt, 294 mt, and 14 mt, respectively, for a total halibut mortality of 2,223 mt. </P>
                <P>Halibut bycatch restrictions seasonally constrained trawl and hook-and-line gear fisheries during the 2003 fishing year. Trawling was closed during the second season for the shallow-water complex on June 19 (68 FR 37094, June 23, 2003), during the fourth season for the shallow-water complex on September 12 (68 FR 54395, September 17, 2003), during the second season for the deep-water fishery complex on May 16 (68 FR 27479, May 20, 2003), and during the fifth season for all trawling on October 15 (68 FR 59889, October 20, 2003). The use of hook-and-line gear for groundfish other than DSR and sablefish closed during the second season on August 1 (68 FR 46502, August 6, 2003) and for the remainder of the year on September 28 (68 FR 56788, October 2, 2003). </P>
                <P>The amount of the groundfish TACs that vessels using trawl gear might have harvested if halibut catch limitations had not restricted the season in 2003 is unknown. </P>
                <HD SOURCE="HD2">(B) Expected Changes in Groundfish Stocks </HD>
                <P>Proposed 2004 ABCs for arrowtooth flounder and Pacific ocean perch are higher than those established for 2003. Proposed 2004 ABCs are lower for Pacific cod, flathead sole, sablefish, and northern rockfish than those established for 2003. Proposed 2004 ABC levels for the remaining target species are unchanged from 2003. More information on these changes is included in the final SAFE report (November 2002) and in the Council and SSC October 2003 meeting minutes. </P>
                <HD SOURCE="HD2">(C) Expected Changes in Groundfish Catch </HD>
                <P>The total of the proposed 2004 TACs for the GOA is 227,797 mt, a decrease of 3.7 percent from the 2003 TAC total of 236,440 mt. Those fisheries for which the 2004 TACs are lower than in 2003 are Pacific cod (decreased to 36,809 mt from 40,540 mt), flathead sole (decreased to 10,770 mt from 11,150 mt), sablefish (decreased to 11,400 mt from 14,890 mt), northern rockfish (decreased to 4,900 mt from 5,530 mt), and “other species” (decreased to 10,847 mt from 11,260 mt). There are no species for which the proposed 2004 TACs are higher than in 2003. </P>
                <HD SOURCE="HD2">(D) Current Estimates of Halibut Biomass and Stock Condition </HD>
                <P>The International Pacific Halibut Commission (IPHC) conducted the most recent halibut stock assessment in December 2002. The halibut resource is considered to be healthy, with total catch near record levels. The current exploitable halibut biomass for 2003 is estimated to be 263,086 mt. This is similar to the estimate of 273,950 mt in 2002. </P>
                <P>The exploitable biomass of the Pacific halibut stock apparently peaked at 326,520 mt in 1988. According to the IPHC, the long-term average reproductive biomass for the Pacific halibut resource was estimated at 118,000 mt. Long-term average yield was estimated at 26,980 mt, round weight. The species is fully utilized. Recent average catches (1994-96) were 33,580 mt for the U.S. and 6,410 mt for Canada, for a combined total of 39,990 mt for the entire Pacific halibut resource. This catch was 48 percent higher than long-term potential yield, which reflects the good condition of the Pacific halibut resource. In January 2003, the IPHC recommended commercial catch limits totaling 36,812 mt (round weight) for Alaska in 2003, the same as in 2002. Through December 31, 2002, commercial hook-and-line harvests of halibut in Alaska total 37,219 mt (round weight). </P>
                <P>
                    At its January 2003 meeting, IPHC staff reported on the assessment of the halibut stock in 2002. There were some significant technological changes in the assessment as a result of changes in the underlying data being analyzed and the persistence of smaller sizes at age in the central portion of the halibut range. Analyses were conducted for the 2002 assessment to ensure that the stock is not being overharvested. However, the IPHC staff intends to resolve these technical issues with the assessment in 2003. In addition, IPHC staff are investigating a new harvest policy that may result in greater stability in the yield from the fishery and insulate the process of setting catch limits from technological changes in the assessment. This harvest policy will also be reviewed by the IPHC. The resolution of technical issues of the assessment may indicate a larger estimate of biomass in the central region of the stock distribution, but application of the proposed harvest policy might dictate slightly lower yields. Because these two processes may be somewhat 
                    <PRTPAGE P="68011"/>
                    counterbalancing, IPHC staff intend to complete their investigations before recommending any changes to the present catch limits or the harvest policy. While the trajectory of the halibut stock biomass is downward, the biomass is still above the long-term average level and is expected to remain above this level for the next several years. 
                </P>
                <P>
                    Additional information on the Pacific halibut stock assessment and the proposed harvest policy may be found in the IPHC's 2002 Pacific halibut stock assessment (December 2002), available from the IPHC on its Web site at 
                    <E T="03">http:///www.iphc.washington.edu/hal.com.</E>
                     IPHC will consider the 2003 Pacific halibut stock assessment for 2004 at its January 2004 annual meeting when it sets the 2004 commercial halibut fishery quotas. 
                </P>
                <HD SOURCE="HD2">(E) Other Factors </HD>
                <P>The allowable commercial catch of halibut will be adjusted to account for the overall halibut PSC mortality limit established for groundfish fisheries. The 2004 groundfish fisheries are expected to use the entire proposed halibut PSC limit of 2,300 mt. The allowable directed commercial catch is determined by accounting for the recreational and subsistence catch, waste, and bycatch mortality and then providing the remainder to the directed fishery. Groundfish fishing is not expected to adversely affect the halibut stocks. </P>
                <P>Methods available for reducing halibut bycatch include:</P>
                <P>
                    (1) Reducing halibut bycatch rates through the Vessel Incentive Program (described below); (2) publication of individual vessel bycatch rates on the NMFS Alaska Region home page at 
                    <E T="03">www.fakr.noaa.gov;</E>
                     (3) modifications to gear; (4) changes in groundfish fishing seasons; (5) individual transferable quota programs; and (6) time/area closures. 
                </P>
                <P>Reductions in groundfish TAC amounts provide no incentive for fishermen to reduce bycatch rates. Costs that would be imposed on fishermen as a result of reducing TAC amounts depend on the species and amounts of groundfish foregone. </P>
                <P>Trawl vessels carrying observers for purposes of complying with observer coverage requirements (§ 679.50) are subject to the Vessel Incentive Program. This program encourages trawl fishermen to avoid high halibut bycatch rates while conducting groundfish fisheries by specifying bycatch rate standards for various target fisheries. </P>
                <P>
                    Current regulations (
                    <E T="03">see</E>
                     § 679.2 Authorized fishing gear, number 12) specify requirements for biodegradable panels and tunnel openings for groundfish pots to reduce halibut bycatch. As a result, low bycatch and mortality rates of halibut in pot fisheries have justified exempting pot gear from PSC limits. 
                </P>
                <P>The regulations also define pelagic trawl gear in a manner intended to reduce bycatch of halibut by displacing fishing effort off the bottom of the sea floor when certain halibut bycatch levels are reached during the fishing year. The definition provides standards for physical conformation (§ 679.2, see Authorized fishing gear number (11)) and performance of the trawl gear in terms of crab bycatch (§ 679.7(a)(14)). Furthermore, all hook-and-line vessel operators are required to employ careful release measures when handling halibut bycatch (§ 679.7(a)(13)). These measures are intended to reduce handling mortality, thereby lowering overall halibut bycatch mortality in the groundfish fisheries, and to increase the amount of groundfish harvested under the available halibut mortality bycatch limits. </P>
                <P>NMFS and the Council will review the methods available for reducing halibut bycatch listed here to determine their effectiveness, and will initiate changes, as necessary, in response to this review or to public testimony and comment. </P>
                <HD SOURCE="HD1">Halibut Discard Mortality Rates </HD>
                <P>The Council recommended that the recommended halibut discard mortality rates (DMRs) developed by the staff of the IPHC for the 2003 GOA groundfish fisheries be used to monitor halibut bycatch mortality limits established for the 2004 GOA groundfish fisheries. NMFS concurs with this recommendation. The IPHC recommended use of long-term average DMRs for the 2001-2003 groundfish fisheries. The IPHC also recommended a provision that DMRs could be revised should analysis indicate that a fishery's annual DMR diverges substantially (up or down) from the long-term average. Most of the IPHC's assumed DMRs were based on an average of mortality rates determined from NMFS observer data collected between 1990 and 1999. DMRs were lacking for some fisheries, so rates from the most recent years were used. For the “other species” fishery, where insufficient mortality data are available, the mortality rate of halibut caught in trawl, hook-and-line, and pot gear Pacific cod fisheries were recommended as a default rate. The DMRs proposed for 2004 are unchanged from those used in 2003 in the GOA. The proposed DMRs for hook-and-line targeted fisheries range from 8 to 24 percent. The proposed DMRs for trawl targeted fisheries range from 58 to 72 percent. The proposed DMRs for all pot targeted fisheries is 14 percent. The proposed 2004 DMRs are listed in Table 7. The justification for these proposed DMRs is discussed in Appendix A of the final SAFE report dated November 2002.</P>
                <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s25,8">
                    <TTITLE>Table 7.—Proposed 2004 Pacific Halibut Discard Mortality Rates for Vessels Fishing in the Gulf of Alaska </TTITLE>
                    <TDESC>[Listed values are percent of halibut bycatch assumed to be dead] </TDESC>
                    <BOXHD>
                        <CHED H="1">Gear/Target </CHED>
                        <CHED H="1">Mortality rate </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="11">Hook-and-line: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Pacific cod </ENT>
                        <ENT>14 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Rockfish </ENT>
                        <ENT>8 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Other species </ENT>
                        <ENT>14 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Sablefish </ENT>
                        <ENT>24 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11">Trawl: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Pelagic pollock </ENT>
                        <ENT>72 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Rockfish </ENT>
                        <ENT>69 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Shallow-water flatfish</ENT>
                        <ENT>69 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Pacific cod </ENT>
                        <ENT>61 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Deep-water flatfish </ENT>
                        <ENT>60 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Flathead sole </ENT>
                        <ENT>58 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Rex sole </ENT>
                        <ENT>61 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Non pelagic pollock </ENT>
                        <ENT>61 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Arrowtooth flounder </ENT>
                        <ENT>62 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Atka mackerel </ENT>
                        <ENT>70 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Sablefish </ENT>
                        <ENT>66 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Other species </ENT>
                        <ENT>61 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11">Pot: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Pacific cod </ENT>
                        <ENT>14 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="02">Other species </ENT>
                        <ENT>14 </ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Non-exempt American Fisheries Act (AFA) Catcher Vessel Groundfish Harvest and PSC Limitations </HD>
                <P>
                    One of the provisions implemented by AFA regulations was to place groundfish harvesting and processing limitations, also called sideboards, on AFA catcher/processors and catcher vessels in the GOA. These limitations are considered necessary for fishermen and processors who have received exclusive harvesting and processing privileges under the AFA to protect the interests of fishermen and processors who have not directly benefitted from the AFA. Under the AFA regulations, AFA catcher/processors (§ 679.4 (l)(2)(i)) are prohibited from fishing for any species of fish (§ 679.7(k)(1)(ii)) and from processing any groundfish harvested in Statistical Area 630 of the GOA (§ 679.7(k)(1)(iv)). The Council recommended that certain AFA catcher vessels in the GOA be exempt from groundfish harvest limitations. Exempted AFA catcher vessels in the GOA are those less than 125 ft (38.1 m) LOA whose annual Bering Sea and 
                    <PRTPAGE P="68012"/>
                    Aleutian Islands management area (BSAI) pollock landings totaled less than 5,100 mt and that made 40 or more GOA groundfish landings from 1995 through 1997 (§ 679.64(b)(2)(ii)). 
                </P>
                <P>For non-exempt AFA catcher vessels in the GOA, harvest limitations are based on their traditional harvest levels of TAC in groundfish fisheries covered by the GOA FMP. The amounts of the groundfish harvest limits in the GOA are based on the retained catch of non-exempt AFA catcher vessels of each sideboard species from 1995 through 1997 divided by the TAC for that species over the same period (§ 679.64(b)(3)(iii)). These amounts are listed in Table 8. All harvests of sideboard species made by non-exempt AFA catcher vessels, whether as targeted catch or bycatch, will be deducted from the sideboard limits in Table 8. </P>
                <GPOTABLE COLS="4" OPTS="L2,i1,s100" CDEF="10,10,10,">
                    <TTITLE>Table 8.—Proposed 2004 GOA Non-Exempt American Fisheries Act Catcher Vessel (CV) Groundfish Harvest Sideboard Limitations </TTITLE>
                    <TDESC>[Values are in metric tons] </TDESC>
                    <BOXHD>
                        <CHED H="1">Species/apportionments and allocations by area-season-processor-gear </CHED>
                        <CHED H="1">Ratio of 1995-1997 non-exempt AFA CV catch to 1995-1997 TAC </CHED>
                        <CHED H="1">2004 TAC </CHED>
                        <CHED H="1">2004 non-exempt AFA catcher vessel sideboard </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="11">Pollock: </ENT>
                        <ENT I="13">A Season (W/C areas only) January 20-February 25: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">Shumagin (610) </ENT>
                        <ENT>0.6112 </ENT>
                        <ENT>2,894 </ENT>
                        <ENT>1,769 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">Chirikof (620) </ENT>
                        <ENT>0.1427 </ENT>
                        <ENT>6,535</ENT>
                        <ENT>933 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">Kodiak (630) </ENT>
                        <ENT>0.2438 </ENT>
                        <ENT>2,274</ENT>
                        <ENT>554 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="13">B Season (W/C areas only) March 10-June 1: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">Shumagin (610) </ENT>
                        <ENT>0.6112 </ENT>
                        <ENT>2,894</ENT>
                        <ENT>1,769 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">Chirikof (620) </ENT>
                        <ENT>0.1427 </ENT>
                        <ENT>7,778</ENT>
                        <ENT>1,110 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">Kodiak (630) </ENT>
                        <ENT>0.2438 </ENT>
                        <ENT>1,031</ENT>
                        <ENT>251 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="13">C Season (W/C areas only) August 25-September 15: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">Shumagin (610) </ENT>
                        <ENT>0.6112 </ENT>
                        <ENT>5,500</ENT>
                        <ENT>3,362 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">Chirikof (620) </ENT>
                        <ENT>0.1427 </ENT>
                        <ENT>2,686</ENT>
                        <ENT>383 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">Kodiak (630) </ENT>
                        <ENT>0.2438 </ENT>
                        <ENT>3,517</ENT>
                        <ENT>857 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="13">D Season (W/C areas only) October 1-November 1: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">Shumagin (610) </ENT>
                        <ENT>0.6112 </ENT>
                        <ENT>5,550</ENT>
                        <ENT>3,362 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">Chirikof (620) </ENT>
                        <ENT>0.1427 </ENT>
                        <ENT>2,686</ENT>
                        <ENT>383 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">Kodiak (630) </ENT>
                        <ENT>0.2438 </ENT>
                        <ENT>3,517</ENT>
                        <ENT>857 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="13">Annual: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">WYK (640) </ENT>
                        <ENT>0.3499 </ENT>
                        <ENT>1,078</ENT>
                        <ENT>377 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">SEO (650) </ENT>
                        <ENT>0.3499 </ENT>
                        <ENT>6,460</ENT>
                        <ENT>2,260 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11">Pacific cod: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="13">
                            A Season 
                            <SU>1</SU>
                            , January 1-June 10: 
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">W inshore </ENT>
                        <ENT>0.1423 </ENT>
                        <ENT>7,553 </ENT>
                        <ENT>1,075 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">W offshore </ENT>
                        <ENT>0.1026 </ENT>
                        <ENT>839 </ENT>
                        <ENT>86 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">C inshore </ENT>
                        <ENT>0.0722 </ENT>
                        <ENT>10,916 </ENT>
                        <ENT>788 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">C offshore </ENT>
                        <ENT>0.0721 </ENT>
                        <ENT>1,213 </ENT>
                        <ENT>87 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="13">
                            B Season 
                            <SU>2</SU>
                            , September 1-December 31: 
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">W inshore </ENT>
                        <ENT>0.1423 </ENT>
                        <ENT>5,035</ENT>
                        <ENT>716 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">W offshore </ENT>
                        <ENT>0.1026 </ENT>
                        <ENT>560</ENT>
                        <ENT>57 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">C inshore </ENT>
                        <ENT>0.0722 </ENT>
                        <ENT>7,277</ENT>
                        <ENT>525 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">C offshore </ENT>
                        <ENT>0.0721 </ENT>
                        <ENT>809</ENT>
                        <ENT>58 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="13">Annual: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">E inshore </ENT>
                        <ENT>0.0079 </ENT>
                        <ENT>2,346</ENT>
                        <ENT>19 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="05">E offshore </ENT>
                        <ENT>0.0078 </ENT>
                        <ENT>261</ENT>
                        <ENT>2 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11">Flatfish deep-water: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">W </ENT>
                        <ENT>0.0000 </ENT>
                        <ENT>180 </ENT>
                        <ENT>0 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">C </ENT>
                        <ENT>0.0670 </ENT>
                        <ENT>2,220 </ENT>
                        <ENT>149 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">E </ENT>
                        <ENT>0.0171 </ENT>
                        <ENT>2,480 </ENT>
                        <ENT>42 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11">Rex sole: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">W </ENT>
                        <ENT>0.0010 </ENT>
                        <ENT>1,280</ENT>
                        <ENT>1 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">C </ENT>
                        <ENT>0.0402 </ENT>
                        <ENT>5,540 </ENT>
                        <ENT>223 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">E </ENT>
                        <ENT>0.0153 </ENT>
                        <ENT>2,650 </ENT>
                        <ENT>41 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11">Flathead sole : </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">W </ENT>
                        <ENT>0.0036 </ENT>
                        <ENT>2,000 </ENT>
                        <ENT>7 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">C </ENT>
                        <ENT>0.0261 </ENT>
                        <ENT>5,000 </ENT>
                        <ENT>131 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">E </ENT>
                        <ENT>0.0048 </ENT>
                        <ENT>3,770 </ENT>
                        <ENT>18 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11">Flatfish shallow-water: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">W </ENT>
                        <ENT>0.0156 </ENT>
                        <ENT>4,500 </ENT>
                        <ENT>70 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">C </ENT>
                        <ENT>0.0598 </ENT>
                        <ENT>13,000 </ENT>
                        <ENT>777 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">E </ENT>
                        <ENT>0.0126 </ENT>
                        <ENT>4,120 </ENT>
                        <ENT>52 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11">Arrowtooth flounder: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">W </ENT>
                        <ENT>0.0021 </ENT>
                        <ENT>8,000 </ENT>
                        <ENT>17 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">C </ENT>
                        <ENT>0.0309 </ENT>
                        <ENT>25,000 </ENT>
                        <ENT>773 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">E </ENT>
                        <ENT>0.0020 </ENT>
                        <ENT>5,000 </ENT>
                        <ENT>10 </ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="68013"/>
                        <ENT I="11">Sablefish: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">W trawl gear </ENT>
                        <ENT>0.0000 </ENT>
                        <ENT>394 </ENT>
                        <ENT>0 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">C trawl gear </ENT>
                        <ENT>0.0720 </ENT>
                        <ENT>986 </ENT>
                        <ENT>71 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">E trawl gear </ENT>
                        <ENT>0.0488 </ENT>
                        <ENT>225 </ENT>
                        <ENT>11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11">Pacific ocean perch: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">W </ENT>
                        <ENT>0.0623 </ENT>
                        <ENT>2,700 </ENT>
                        <ENT>168 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">C </ENT>
                        <ENT>0.0866 </ENT>
                        <ENT>8,510 </ENT>
                        <ENT>737 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">E </ENT>
                        <ENT>0.0466 </ENT>
                        <ENT>2,450 </ENT>
                        <ENT>114 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11">Shortraker/Rougheye </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">W </ENT>
                        <ENT>0.0000 </ENT>
                        <ENT>220</ENT>
                        <ENT>0 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">C </ENT>
                        <ENT>0.0237 </ENT>
                        <ENT>840 </ENT>
                        <ENT>20 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">E </ENT>
                        <ENT>0.0124 </ENT>
                        <ENT>560 </ENT>
                        <ENT>7 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11">Other rockfish: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">W </ENT>
                        <ENT>0.0034 </ENT>
                        <ENT>90 </ENT>
                        <ENT>0 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">C </ENT>
                        <ENT>0.2065 </ENT>
                        <ENT>550 </ENT>
                        <ENT>114 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">E </ENT>
                        <ENT>0.0000 </ENT>
                        <ENT>350 </ENT>
                        <ENT>0 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11">Northern rockfish: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">W </ENT>
                        <ENT>0.0003 </ENT>
                        <ENT>789 </ENT>
                        <ENT>0 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">C </ENT>
                        <ENT>0.0336 </ENT>
                        <ENT>4,111 </ENT>
                        <ENT>150 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11">Pelagic shelf rockfish: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">W </ENT>
                        <ENT>0.0001 </ENT>
                        <ENT>510 </ENT>
                        <ENT>0 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">C </ENT>
                        <ENT>0.0000 </ENT>
                        <ENT>3,480 </ENT>
                        <ENT>0 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">E </ENT>
                        <ENT>0.0067 </ENT>
                        <ENT>1,500 </ENT>
                        <ENT>10 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11">Thornyhead rockfish: </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">W </ENT>
                        <ENT>0.0308 </ENT>
                        <ENT>360 </ENT>
                        <ENT>11 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">C </ENT>
                        <ENT>0.0308 </ENT>
                        <ENT>840 </ENT>
                        <ENT>26 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">E </ENT>
                        <ENT>0.0308 </ENT>
                        <ENT>800 </ENT>
                        <ENT>25 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Demersal shelf rockfish: SEO </ENT>
                        <ENT>0.0020 </ENT>
                        <ENT>390 </ENT>
                        <ENT>1 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Atka mackerel: Gulfwide </ENT>
                        <ENT>0.0309 </ENT>
                        <ENT>600 </ENT>
                        <ENT>19 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Other species: Gulfwide </ENT>
                        <ENT>0.0090 </ENT>
                        <ENT>10,847 </ENT>
                        <ENT>98 </ENT>
                    </ROW>
                    <TNOTE>
                        <SU>1</SU>
                         The Pacific cod A season for trawl gear does not open until January 20. 
                    </TNOTE>
                    <TNOTE>
                        <SU>2</SU>
                         The Pacific cod B season for trawl gear closes November 1. 
                    </TNOTE>
                </GPOTABLE>
                <P>PSC bycatch limits for non-exempt AFA catcher vessels in the GOA are based on the ratio of aggregate retained groundfish catch by non-exempt AFA catcher vessels in each PSC target category from 1995 through 1997 relative to the retained catch of all vessels in that fishery from 1995 through 1997 (§ 679.64(b)(4)). These amounts are shown in Table 9. </P>
                <GPOTABLE COLS="5" OPTS="L2,i1" CDEF="s100,xs150,12,8,10">
                    <TTITLE>Table 9.—Proposed 2004 Non-Exempt American Fisheries Act Catcher Vessel Prohibited Species Catch (PSC) Limits for the GOA </TTITLE>
                    <TDESC>[Values are in metric tons] </TDESC>
                    <BOXHD>
                        <CHED H="1">PSC species/Season </CHED>
                        <CHED H="1">Target fishery </CHED>
                        <CHED H="1">Ratio of 1995-1997 non-exempt AFA CV retained catch to total retained catch </CHED>
                        <CHED H="1">2004 PSC limit </CHED>
                        <CHED H="1">2004 non-exempt AFA catcher vessel PSC limit </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="11">Halibut (mortality in mt): </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Trawl 1st Seasonal Allowance</ENT>
                        <ENT>Shallow water targets</ENT>
                        <ENT>0.340</ENT>
                        <ENT>450</ENT>
                        <ENT>153 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">January 20-April 1</ENT>
                        <ENT>Deep water targets</ENT>
                        <ENT>0.070</ENT>
                        <ENT>100</ENT>
                        <ENT>7 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Trawl 2nd Seasonal Allowance</ENT>
                        <ENT>Shallow water targets</ENT>
                        <ENT>0.340</ENT>
                        <ENT>100</ENT>
                        <ENT>34 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">April 1-July 4</ENT>
                        <ENT>Deep water targets</ENT>
                        <ENT>0.070</ENT>
                        <ENT>300</ENT>
                        <ENT>21 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Trawl 3rd Seasonal Allowance</ENT>
                        <ENT>Shallow water targets</ENT>
                        <ENT>0.340</ENT>
                        <ENT>200</ENT>
                        <ENT>68 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">July 4-September 1</ENT>
                        <ENT>Deep water targets</ENT>
                        <ENT>0.070</ENT>
                        <ENT>400</ENT>
                        <ENT>38 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Trawl 4th Seasonal Allowance</ENT>
                        <ENT>Shallow water targets</ENT>
                        <ENT>0.340</ENT>
                        <ENT>150</ENT>
                        <ENT>51 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">September 1-October 1</ENT>
                        <ENT>Deep water targets</ENT>
                        <ENT>0.070</ENT>
                        <ENT>0</ENT>
                        <ENT>0 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Trawl 5th Seasonal Allowance</ENT>
                        <ENT>All targets</ENT>
                        <ENT>0.205</ENT>
                        <ENT>300</ENT>
                        <ENT>61 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">October 1-December 31</ENT>
                        <ENT>......do</ENT>
                        <ENT>0.205</ENT>
                        <ENT>300</ENT>
                        <ENT>61 </ENT>
                    </ROW>
                </GPOTABLE>
                <PRTPAGE P="68014"/>
                <HD SOURCE="HD1">Classification </HD>
                <P>This action is authorized under 50 CFR 679.20 and is exempt from review under Executive Order 12866. </P>
                <P>
                    NMFS prepared an IRFA for this action in accordance with the provisions of the Regulatory Flexibility Act (RFA) of 1980, as amended by the Small Business Regulatory Enforcement Fairness Act of 1996 (5 U.S.C. Section 603(b)). A copy of this analysis is available from the Council (
                    <E T="03">see</E>
                      
                    <E T="02">ADDRESSES</E>
                    ). This IRFA evaluates the effects of the proposed action on regulated small entities. The reasons for the action, a statement of the objectives of the action, and the legal basis for the proposed rule, are discussed earlier in the preamble. 
                </P>
                <P>The small entities affected by this action are those that commercially harvest groundfish under the GOA FMP. Data in the IRFA indicates that 1,115 catcher vessels and 21 catcher-processors may be “small entities” under the terms of the RFA. </P>
                <P>Using the sectoral first wholesale gross revenue changes as an index the preferred alternative seems to have adverse impacts in the GOA sablefish and Pacific cod sectors. There do not appear to be other adverse impacts associated with the preferred alternative. The model suggests that there will be revenue reductions for flathead sole, rockfish, and other species. However, as reported in the IRFA, the projected revenue reductions for these species appear to be relatively small percentages of the prior year (2003) gross revenue estimates. Given the large confidence intervals believed to be associated with these estimates, these are thought to be minor impacts. </P>
                <P>Harvest records indicate that 498 vessels harvested sablefish in the GOA in excess of the minimum harvest threshold adopted to select vessels for the analysis. Of these, 482 were small entities, with revenues under the $3.5 million gross revenues threshold used by the Small Business Administration (SBA) for catcher vessels. These small vessels harvested about 12,395 mt of sablefish in all their sablefish fisheries (some of this tonnage may have come from operations in the BSAI). Another 56 vessels harvested amounts of sablefish below the minimum harvest threshold; these vessels only harvested a total of about 10 mt of sablefish. The 482 small vessels above the threshold averaged about $439,000 in all their fisheries (groundfish, crab, scallops, salmon and herring) in Alaska, and about $121,000 from all their sablefish in Alaska. If the small entity revenue reduction is proportionate to the overall first wholesale “index” reduction in the area, and if the small entities catch all of their sablefish in the GOA, the small entity revenue reduction would be about $28,000. This would be about 23.4 percent of their sablefish revenues, and about 6.5 percent of their overall revenues. </P>
                <P>Harvest records indicate that 578 vessels harvested Pacific cod in the GOA in excess of the minimum harvest criterion adopted to select vessels for the analysis. Of these, 562 were small entities according to the $3.5 million in gross revenues criteria used by the SBA for catcher vessels. These small vessels harvested about 51,000 mt of Pacific cod in all their Pacific cod fisheries (some of these revenues may have come from operations in the BSAI). Another 263 vessels harvested amounts of Pacific cod below the minimum harvest threshold; these vessels only harvested a total of about 40 mt of Pacific cod. The 562 vessels above the threshold averaged about $331,000 in all their fisheries (groundfish, crab, scallops, salmon and herring) in Alaska, and about $98,000 from all their Pacific cod in Alaska. If the small entity revenue reduction is proportionate to the overall first wholesale “index” reduction in the area, and if the small entities catch all of their Pacific cod in the GOA, the small entity revenue reduction would be about $9,000. This would be about 9.2 percent of their Pacific cod revenues, and about 2.7 percent of their overall revenues. </P>
                <P>The preferred alternative was compared to the four other alternatives evaluated during the specifications process. These alternatives are defined by TACs set so as to generate different harvest rates (F values). Alternative 1 sets TAC to generate the harvest rate associated with the maximum ABC for each species, Alternative 2 is the preferred alternative, Alternative 3 sets TACs to generate fishing rates that are half those of Alternative 1, Alternative 4 sets TACs to generate fishing rates equal to the most recent five year average rates, and Alternative 5 sets TACs equal to zero. Only Alternative 1 had a smaller adverse impact on small entities than the preferred alternative. However, Alternative 1 would have increased sablefish and Pacific cod harvests and would have failed to meet the objective of protecting the long run health of these stocks. </P>
                <P>The action does not impose new recordkeeping or reporting requirements on small entities. The analysis did not reveal any Federal rules that duplicate, overlap or conflict with the proposed action. </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>
                        16 U.S.C. 773 
                        <E T="03">et seq.</E>
                         16 U.S.C 1801 
                        <E T="03">et seq.</E>
                        , and 3631 
                        <E T="03">et seq.</E>
                    </P>
                </AUTH>
                <SIG>
                    <DATED>Dated: December 1, 2003. </DATED>
                    <NAME>William T. Hogarth, </NAME>
                    <TITLE>Assistant Administrator for Fisheries, National Marine Fisheries Service. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30283 Filed 12-4-03; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3510-22-P</BILCOD>
        </PRORULE>
    </PRORULES>
    <VOL>68</VOL>
    <NO>234</NO>
    <DATE>Friday, December 5, 2003</DATE>
    <UNITNAME>Notices</UNITNAME>
    <NOTICES>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="68015"/>
                <AGENCY TYPE="F">DEPARTMENT OF AGRICULTURE </AGENCY>
                <SUBAGY>Animal and Plant Health Inspection Service </SUBAGY>
                <DEPDOC>[Docket No. 03-107-1] </DEPDOC>
                <SUBJECT>Notice of Request for Extension of Approval of an Information Collection </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Animal and Plant Health Inspection Service, USDA. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Extension of approval of an information collection; comment request. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Paperwork Reduction Act of 1995, this notice announces the Animal and Plant Health Inspection Service's intention to request an extension of approval of an information collection in support of regulations that provide for the payment of compensation to owners of commercial stone fruit orchards and fruit tree nurseries whose trees or nursery stock were destroyed to eradicate plum pox. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>We will consider all comments that we receive on or before February 3, 2004. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may submit comments by postal mail/commercial delivery or by e-mail. If you use postal mail/commercial delivery, please send four copies of your comment (an original and three copies) to: Docket No. 03-107-1, Regulatory Analysis and Development, PPD, APHIS, Station 3C71, 4700 River Road Unit 118, Riverdale, MD 20737-1238. Please state that your comment refers to Docket No. 03-107-1. If you use e-mail, address your comment to 
                        <E T="03">regulations@aphis.usda.gov.</E>
                         Your comment must be contained in the body of your message; do not send attached files. Please include your name and address in your message and  “Docket No. 03-107-1” on the subject line. 
                    </P>
                    <P>You may read any comments that we receive on this docket in our reading room. The reading room is located in room 1141 of the USDA South Building, 14th Street and Independence Avenue SW., Washington, DC. Normal reading room hours are 8 a.m. to 4:30 p.m., Monday through Friday, except holidays. To be sure someone is there to help you, please call (202) 690-2817 before coming. </P>
                    <P>
                        APHIS documents published in the 
                        <E T="04">Federal Register</E>
                        , and related information, including the names of organizations and individuals who have commented on APHIS dockets, are available on the Internet at 
                        <E T="03">http://www.aphis.usda.gov/ppd/rad/webrepor.html.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>For information regarding the plum pox regulations, contact Mr. Stephen Poe, Operations Officer, Pest Detection and Management Programs, PPQ, APHIS, 4700 River Road Unit 134, Riverdale, MD 20737-1231; (301) 734-8899. For copies of more detailed information on the information collection, contact Mrs. Celeste Sickles, APHIS' Information Collection Coordinator, at (301) 734-7477. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    <E T="03">Title:</E>
                     Plum Pox Compensation. 
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     0579-0159. 
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Extension of approval of an information collection. 
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The Plant Protection Act (7 U.S.C. 7701-7772) authorizes the Secretary of Agriculture, either independently or in cooperation with the States, to carry out operations or measures to detect, eradicate, suppress, control, prevent, or retard the spread of plant pests, such as plum pox, that are new to or not widely distributed within the United States. 
                </P>
                <P>
                    Plum pox is an extremely serious viral disease of plants that can affect many 
                    <E T="03">Prunus</E>
                     (stone fruit) species, including plum, peach, apricot, almond, nectarine, and sweet and tart cherry. A number of wild and ornamental 
                    <E T="03">Prunus</E>
                     species may also be susceptible to this disease. Infection eventually results in severely reduced fruit production, and the fruit that is produced is often misshapen and blemished. Plum pox virus is transmitted locally by a variety of aphid species, as well as by budding and grafting with infected plant material, and spreads over longer distances through movement of infected budwood, nursery stock, and other plant parts. 
                </P>
                <P>There are no known effective methods for treating trees or other plant material infected with plum pox, nor are there any known effective prophylactic treatments to prevent the disease from occurring in trees exposed to the disease due to their proximity to infected trees or other plant material. Without effective treatments, the only option for preventing the spread of the disease is the destruction of infected and exposed trees and other plant material. </P>
                <P>The regulations in “Subpart—Plum Pox” (7 CFR 301.74-301.74-5) quarantine areas of the United States where plum pox has been detected, restrict the interstate movement of host material from quarantined areas, and provide for compensation to owners of commercial stone fruit orchards and fruit tree nurseries whose trees or nursery stock were destroyed to eradicate plum pox. </P>
                <P>Section 310.74-5 requires applicants for the payment of compensation to complete a form. </P>
                <P>We are asking the Office of Management and Budget (OMB) to approve our use of this information collection activity for an additional 3 years. </P>
                <P>The purpose of this notice is to solicit comments from the public (as well as affected agencies) concerning our information collection. These comments will help us: </P>
                <P>(1) Evaluate whether the collection of information is necessary for the proper performance of the functions of the Agency, including whether the information will have practical utility; </P>
                <P>(2) Evaluate the accuracy of our estimate of the burden of the information collection, including the validity of the methodology and assumptions used; </P>
                <P>(3) Enhance the quality, utility, and clarity of the information to be collected; and </P>
                <P>(4) Minimize the burden of the information collection on those who are to respond, through use, as appropriate, of automated, electronic, mechanical, and other collection technologies, e.g., permitting electronic submission of responses. </P>
                <P>
                    <E T="03">Estimate of burden:</E>
                     The public reporting burden for this collection of information is estimated to average 0.16666 hours per response. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Eligible owners of stone fruit orchards and fruit tree nurseries in Pennsylvania. 
                    <PRTPAGE P="68016"/>
                </P>
                <P>
                    <E T="03">Estimated annual number of respondents:</E>
                     6. 
                </P>
                <P>
                    <E T="03">Estimated annual number of responses per respondent:</E>
                     1. 
                </P>
                <P>
                    <E T="03">Estimated annual number of responses:</E>
                     6. 
                </P>
                <P>
                    <E T="03">Estimated total annual burden on respondents:</E>
                     1 hour. (Due to averaging, the total annual burden hours may not equal the product of the annual number of responses multiplied by the reporting burden per response.) 
                </P>
                <P>All responses to this notice will be summarized and included in the request for OMB approval. All comments will also become a matter of public record. </P>
                <SIG>
                    <DATED>Done in Washington, DC, this 1st day of December 2003. </DATED>
                    <NAME>Kevin Shea, </NAME>
                    <TITLE>Acting Administrator, Animal and Plant Health Inspection Service. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30231 Filed 12-4-03; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3410-34-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE </AGENCY>
                <SUBAGY>Animal and Plant Health Inspection Service </SUBAGY>
                <DEPDOC>[Docket No. 03-108-1] </DEPDOC>
                <SUBJECT>Notice of Request for Extension of Approval of an Information Collection </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Animal and Plant Health Inspection Service, USDA. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Extension of approval of an information collection; comment request. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Paperwork Reduction Act of 1995, this notice announces the Animal and Plant Health Inspection Service's intention to request an extension of approval of an information collection in support of regulations for the importation of unshu oranges from Kyushu Island and Honshu Island, Japan, into the United States. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>We will consider all comments that we receive on or before February 3, 2004. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may submit comments by postal mail/commercial delivery or by e-mail. If you use postal mail/commercial delivery, please send four copies of your comment (an original and three copies) to: Docket No. 03-108-1, Regulatory Analysis and Development, PPD, APHIS, Station 3C71, 4700 River Road Unit 118, Riverdale, MD 20737-1238. Please state that your comment refers to Docket No. 03-108-1. If you use e-mail, address your comment to 
                        <E T="03">regulations@aphis.usda.gov.</E>
                         Your comment must be contained in the body of your message; do not send attached files. Please include your name and address in your message and “Docket No. 03-108-1” on the subject line. 
                    </P>
                    <P>You may read any comments that we receive on this docket in our reading room. The reading room is located in room 1141 of the USDA South Building, 14th Street and Independence Avenue SW., Washington, DC. Normal reading room hours are 8 a.m. to 4:30 p.m., Monday through Friday, except holidays. To be sure someone is there to help you, please call (202) 690-2817 before coming. </P>
                    <P>
                        APHIS documents published in the 
                        <E T="04">Federal Register</E>
                        , and related information, including the names of organizations and individuals who have commented on APHIS dockets, are available on the Internet at 
                        <E T="03">http://www.aphis.usda.gov/ppd/rad/webrepor.html.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>For information regarding regulations for the importation of unshu oranges from Kyushu Island and Honshu Island, Japan, contact Mr. Alan S. Green, Assistant Director, Quarantine Policy, Analysis and Support, PPQ, APHIS, 4700 River Road Unit 60, Riverdale, MD 20737-1236; (301) 734-8311. For copies of more detailed information on the information collection, contact Mrs. Celeste Sickles, APHIS' Information Collection Coordinator, at (301) 734-7477. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    <E T="03">Title:</E>
                     Importation of Unshu Oranges. 
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     0579-0173. 
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Extension of approval of an information collection. 
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The Plant Protection Act (7 U.S.C. 7701-7772) authorizes the Secretary of Agriculture to regulate the importation of plants, plant products, and other articles into the United States to prevent the introduction of plant pests and noxious weeds. 
                </P>
                <P>The regulations in “Subpart-Citrus Fruit” (7 CFR 319.28) allow the importation of unshu oranges from Kyushu Island and Honshu Island, Japan, into the United States under certain conditions. Among other things, the individual boxes in which the oranges are shipped must be stamped or printed with a statement specifying the States into which the oranges may be imported and from which they are prohibited removal under a Federal plant quarantine. The unshu oranges must also be accompanied by a certificate from the Japanese plant protection service certifying that the fruit is apparently free of citrus canker. </P>
                <P>We are asking the Office of Management and Budget (OMB) to approve our use of these information collection activities for an additional 3 years. </P>
                <P>The purpose of this notice is to solicit comments from the public (as well as affected agencies) concerning our information collection. These comments will help us: </P>
                <P>(1) Evaluate whether the collection of information is necessary for the proper performance of the functions of the Agency, including whether the information will have practical utility; </P>
                <P>(2) Evaluate the accuracy of our estimate of the burden of the information collection, including the validity of the methodology and assumptions used; </P>
                <P>(3) Enhance the quality, utility, and clarity of the information to be collected; and </P>
                <P>
                    (4) Minimize the burden of the information collection on those who are to respond, through use, as appropriate, of automated, electronic, mechanical, and other collection technologies, 
                    <E T="03">e.g.</E>
                    , permitting electronic submission of responses. 
                </P>
                <P>
                    <E T="03">Estimate of burden:</E>
                     The public reporting burden for this collection of information is estimated to average 1.0 hour per response. 
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Full-time, salaried plant health officials of Japan's plant protection service and growers of unshu oranges. 
                </P>
                <P>
                    <E T="03">Estimated annual number of respondents:</E>
                     10. 
                </P>
                <P>
                    <E T="03">Estimated annual number of responses per respondent:</E>
                     1. 
                </P>
                <P>
                    <E T="03">Estimated annual number of responses:</E>
                     10. 
                </P>
                <P>
                    <E T="03">Estimated total annual burden on respondents:</E>
                     10 hours. (Due to averaging, the total annual burden hours may not equal the product of the annual number of responses multiplied by the reporting burden per response.) 
                </P>
                <P>All responses to this notice will be summarized and included in the request for OMB approval. All comments will also become a matter of public record. </P>
                <SIG>
                    <DATED>Done in Washington, DC, this 1st day of December 2003. </DATED>
                    <NAME>Kevin Shea, </NAME>
                    <TITLE>Acting Administrator, Animal and Plant Health Inspection Service. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30232 Filed 12-4-03; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3410-34-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="68017"/>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBAGY>Animal and Plant Health Inspection Service</SUBAGY>
                <DEPDOC>[Docket No. 03-090-1]</DEPDOC>
                <SUBJECT>Notice of Request for Extension of Approval of an Information Collection</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Animal and Plant Health Inspection Service, USDA.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Extension of approval of an information collection; comment request.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Paperwork Reduction Act of 1995, this notice announces the Animal and Plant Health Inspection Service's intention to request an extension of approval of an information collection in support of regulations intended to prevent the interstate spread of fruit flies from Hawaii.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>We will consider all comments that we receive on or before February 3, 2004.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may submit comments by postal mail/commercial delivery or by e-mail. If you use postal mail/commercial delivery, please send four copies of your comment (an original and three copies) to: Docket No. 03-090-1, Regulatory Analysis and Development, PPD, APHIS, Station 3C71, 4700 River Road Unit 118, Riverdale, MD 20737-1238. Please state that your comment refers to Docket No. 03-090-1. If you use e-mail, address your comment to 
                        <E T="03">regulations@aphis.usda.gov.</E>
                         Your comment must be contained in the body of your message; do not send attached files. Please include your name and address in your message and “Docket No. 03-090-1” on the subject line.
                    </P>
                    <P>You may read any comments that we receive on this docket in our reading room. The reading room is located in room 1141 of the USDA South Building, 14th Street and Independence Avenue, SW., Washington, DC. Normal reading room hours are 8 a.m. to 4:30 p.m., Monday through Friday, except holidays. To be sure someone is there to help you, please call (202) 690-2817 before coming.</P>
                    <P>
                        APHIS documents published in the 
                        <E T="04">Federal Register</E>
                        , and related information, including the names of organizations and individuals who have commented on APHIS dockets, are available on the Internet at 
                        <E T="03">http://www.aphis.usda.gov/ppd/rad/webrepor.html.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>For information regarding regulations to prevent the interstate spread of fruit flies from Hawaii, contact Mr. Alan S. Green, Assistant Director, Quarantine Policy, Analysis and Support, PPQ, APHIS, 4700 River Road Unit 60, Riverdale, MD 20737-1236; (301) 734-8311. For copies of more detailed information on the information collection, contact Mrs. Celeste Sickles, APHIS' Information Collection Coordinator, at (301) 734-7477.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    <E T="03">Title:</E>
                     Fruit from Hawaii.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     0579-0123.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Extension of approval of an information collection.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     In accordance with the Plant Protection Act (7 U.S.C. 7701-7772), the Animal and Plant Health Inspection Service regulates the interstate movement of fruits and vegetables from Hawaii to prevent the interstate spread of fruit flies, including the Mediterranean fruit fly, the melon fly, and the Oriental fruit fly, pests that occur in Hawaii and can cause millions of dollars in damage to U.S. agriculture. The regulations are contained in Subpart—Hawaiian Fruit and Vegetables (7 CFR 318.13 through 318.13-17).
                </P>
                <P>Among other things, the regulations allow the movement of atemoya, longan, rambutan, sapodilla, papaya, carambola, litchi, and other fruits from Hawaii if the fruit is irradiated, either before the interstate movement or at certain locations on the mainland United States.</P>
                <P>The provisions of the regulations regarding irradiation require a number of information collection activities, including the use of certificates, limited permits, compliance agreements, requests for treatment facility approval, requests for certification and recertification of testing equipment, and recordkeeping systems.</P>
                <P>We are asking the Office of Management and Budget (OMB) to approve our use of these information collection activities for an additional 3 years.</P>
                <P>The purpose of this notice is to solicit comments from the public (as well as affected agencies) concerning our information collection. These comments will help us:</P>
                <P>(1) Evaluate whether the collection of information is necessary for the proper performance of the functions of the Agency, including whether the information will have practical utility;</P>
                <P>(2) Evaluate the accuracy of our estimate of the burden of the information collection, including the validity of the methodology and assumptions used;</P>
                <P>(3) Enhance the quality, utility, and clarity of the information to be collected; and</P>
                <P>
                    (4) Minimize the burden of the information collection on those who are to respond, through use, as appropriate, of automated, electronic, mechanical, and other collection technologies, 
                    <E T="03">e.g.</E>
                    , permitting electronic submission of responses.
                </P>
                <P>
                    <E T="03">Estimate of burden:</E>
                     The public reporting burden for this collection of information is estimated to average 0.1190 hours per response.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Fruit producers, shippers, irradiation facility personnel, and State plant regulatory officials.
                </P>
                <P>
                    <E T="03">Estimated annual number of respondents:</E>
                     300.
                </P>
                <P>
                    <E T="03">Estimated annual number of responses per respondent:</E>
                     9.15333.
                </P>
                <P>
                    <E T="03">Estimated annual number of responses:</E>
                     2,746.
                </P>
                <P>
                    <E T="03">Estimated total annual burden on respondents:</E>
                     327 hours. (Due to averaging, the total annual burden hours may not equal the product of the annual number of responses multiplied by the reporting burden per response.)
                </P>
                <P>All responses to this notice will be summarized and included in the request for OMB approval. All comments will also become a matter of public record.</P>
                <SIG>
                    <DATED>Done in Washington, DC, this 1st day of December, 2003.</DATED>
                    <NAME>Kevin Shea,</NAME>
                    <TITLE>Acting Administrator, Animal and Plant Health Inspection Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30233 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3410-34-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBAGY>Animal and Plant Health Inspection Service</SUBAGY>
                <DEPDOC>[Docket No. 03-095-1]</DEPDOC>
                <SUBJECT>Notice of Request for Extension of Approval of an Information Collection</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Animal and Plant Health Inspection Service, USDA.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Extension of approval of an information collection; comment request.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Paperwork Reduction Act of 1995, this notice announces the Animal and Plant Health Inspection Service's intention to request an extension of approval of an information collection in support of regulations for importation of seed and screenings.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>We will consider all comments that we receive on or before February 3, 2004.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may submit comments by postal mail/commercial delivery or by e-mail. If you use postal mail/
                        <PRTPAGE P="68018"/>
                        commercial delivery, please send four copies of your comment (an original and three copies) to: Docket No. 03-095-1, Regulatory Analysis and Development, PPD, APHIS, Station 3C71, 4700 River Road Unit 118, Riverdale, MD 20737-1238. Please state that your comment refers to Docket No. 03-095-1. If you use e-mail, address your comment to 
                        <E T="03">regulations@aphis.usda.gov.</E>
                         Your comment must be contained in the body of your message; do not send attached files. Please include your name and address in your message and “Docket No. 03-095-1” on the subject line.
                    </P>
                    <P>You may read any comments that we receive on this docket in our reading room. The reading room is located in room 1141 of the USDA South Building, 14th Street and Independence Avenue, SW., Washington, DC. Normal reading room hours are 8 a.m. to 4:30 p.m., Monday through Friday, except holidays. To be sure someone is there to help you, please call (202) 690-2817 before coming.</P>
                    <P>
                        APHIS documents published in the 
                        <E T="04">Federal Register</E>
                        , and related information, including the names of organizations and individuals who have commented on APHIS dockets, are available on the Internet at 
                        <E T="03">http://www.aphis.usda.gov/ppd/rad/webrepor.html.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>For information regarding regulations for importation of seed and screenings, contact Ms. Polly Lehtonen, Botanist, Biological and Technical Services, PPQ, APHIS, 4700 River Road Unit 133, Riverdale, MD 20737-1236; (301) 734-4394. For copies of more detailed information on the information collection, contact Mrs. Celeste Sickles, APHIS’ Information Collection Coordinator, at (301) 734-7477.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    <E T="03">Title:</E>
                     Imported Seed and Screenings.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     0579-0124.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Extension of approval of an information collection.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Under the authority of the Federal Seed Act (FSA) of 1939, as amended (7 U.S.C. 1551 
                    <E T="03">et seq.</E>
                    ), the U.S. Department of Agriculture (USDA) regulates the importation and interstate movement of certain agricultural and vegetable seeds and screenings. Title III of the FSA, “Foreign Commerce,” requires shipments of imported agricultural and vegetable seeds to be labeled correctly and to be tested for the presence of the seeds of certain noxious weeds as a condition of entry into the United States. The Animal and Plant Health Inspection Service's regulations implementing the provisions of title III of the FSA are found in 7 CFR part 361.
                </P>
                <P>The regulations require the use of a number of information collection activities, including declaration of importation, container labeling, notification of seed location, a seed return request, seed analysis certificates, seed identity maintenance, and associated recordkeeping.</P>
                <P>We are asking OMB to approve our use of these information collection activities for an additional 3 years.</P>
                <P>The purpose of this notice is to solicit comments from the public (as well as affected agencies) concerning our information collection. These comments will help us:</P>
                <P>(1) Evaluate whether the collection of information is necessary for the proper performance of the functions of the Agency, including whether the information will have practical utility;</P>
                <P>(2) Evaluate the accuracy of our estimate of the burden of the information collection, including the validity of the methodology and assumptions used;</P>
                <P>(3) Enhance the quality, utility, and clarity of the information to be collected; and</P>
                <P>
                    (4) Minimize the burden of the information collection on those who are to respond, through use, as appropriate, of automated, electronic, mechanical, and other collection technologies, 
                    <E T="03">e.g.</E>
                    , permitting electronic submission of responses.
                </P>
                <P>
                    <E T="03">Estimate of burden:</E>
                     The public reporting burden for this collection of information is estimated to average 0.37816 hours per response.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Importers of seed and screenings, seed cleaning/processing facility personnel, officials of the Canadian Food Inspection Agency (CFIA), and private seed laboratories accredited by CFIA.
                </P>
                <P>
                    <E T="03">Estimated annual number of respondents:</E>
                     1,200.
                </P>
                <P>
                    <E T="03">Estimated annual number of responses per respondent:</E>
                     25.
                </P>
                <P>
                    <E T="03">Estimated annual number of responses:</E>
                     30,000.
                </P>
                <P>
                    <E T="03">Estimated total annual burden on respondents:</E>
                     11,345 hours. (Due to averaging, the total annual burden hours may not equal the product of the annual number of responses multiplied by the reporting burden per response.)
                </P>
                <P>All responses to this notice will be summarized and included in the request for OMB approval. All comments will also become a matter of public record.</P>
                <SIG>
                    <DATED>Done in Washington, DC, this 2nd day of December, 2003.</DATED>
                    <NAME>Kevin Shea,</NAME>
                    <TITLE>Acting Administrator, Animal and Plant Health Inspection Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30234 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3410-34-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBAGY>Animal and Plant Health Inspection Service</SUBAGY>
                <DEPDOC>[Docket No. 03-096-1]</DEPDOC>
                <SUBJECT>Notice of Request for Extension of Approval of an Information Collection</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Animal and Plant Health Inspection Service, USDA.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Extension of approval of an information collection; comment request.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Paperwork Reduction Act of 1995, this notice announces the Animal and Plant Health Inspection Service's intention to request an extension of approval of an information collection in support of regulations under which eligible owners may receive payments to replace trees removed because of citrus canker.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>We will consider all comments that we receive on or before February 3, 2004.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may submit comments by postal mail/commercial delivery or by e-mail. If you use postal mail/commercial delivery, please send four copies of your comment (an original and three copies) to: Docket No. 03-096-1, Regulatory Analysis and Development, PPD, APHIS, Station 3C71, 4700 River Road Unit 118, Riverdale, MD 20737-1238. Please state that your comment refers to Docket No. 03-096-1. If you use e-mail, address your comment to 
                        <E T="03">regulations@aphis.usda.gov.</E>
                         Your comment must be contained in the body of your message; do not send attached files. Please include your name and address in your message and “Docket No. 03-096-1” on the subject line.
                    </P>
                    <P>You may read any comments that we receive on this docket in our reading room. The reading room is located in room 1141 of the USDA South Building, 14th Street and Independence Avenue, SW., Washington, DC. Normal reading room hours are 8 a.m. to 4:30 p.m., Monday through Friday, except holidays. To be sure someone is there to help you, please call (202) 690-2817 before coming.</P>
                    <P>
                        APHIS documents published in the 
                        <E T="04">Federal Register</E>
                        , and related information, including the names of organizations and individuals who have commented on APHIS dockets, are available on the Internet at 
                        <E T="03">http://www.aphis.usda.gov/ppd/rad/webrepor.html.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For information regarding the citrus canker regulations, contact Mr. Stephen Poe, Operations Officer, Pest Detection and 
                        <PRTPAGE P="68019"/>
                        Management Programs, PPQ, APHIS, 4700 River Road Unit 134, Riverdale, MD 20737-1231; (301) 734-8899. For copies of more detailed information on the information collection, contact Mrs. Celeste Sickles, APHIS' Information Collection Coordinator, at (301) 734-7477.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P SOURCE="NPAR">
                    <E T="03">Title:</E>
                     Citrus Canker; Commercial Citrus Tree Replacement Program.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     0579-0163.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Extension of approval of an information collection.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The Plant Protection Act (7 U.S.C. 7701-7772) authorizes the Secretary of Agriculture, either independently or in cooperation with States, to carry out operations or measures to detect, eradicate, suppress, control, prevent, or retard the spread of plant pests, such as citrus canker, that are new to or not widely distributed within the United States.
                </P>
                <P>
                    Citrus canker is a plant disease that affects plant and plant parts, including fresh fruit of citrus and citrus relatives (
                    <E T="03">Family Rutaceae</E>
                    ). Citrus canker can cause defoliation and other serious damage to the leaves and twigs of susceptible plants. It can also cause lesions on the fruit of infected plants that render the fruit unmarketable and cause infected fruit to drop from the trees before reaching maturity. The aggressive A (
                    <E T="03">Asiatic</E>
                    ) strain of citrus canker can infect susceptible plants rapidly and lead to extensive economic losses in commercial citrus-producing areas.
                </P>
                <P>Regulations to prevent the interstate spread of citrus canker are contained in 7 CFR 301.75 through 301.75-16. Under § 301.75-15, owners of commercial citrus groves in Florida who have had citrus trees destroyed because of citrus canker may be eligible to receive funds to replace the trees. Owners must complete a form to apply for the funds.</P>
                <P>We are asking OMB to approve our use of this information collection activity for an additional 3 years.</P>
                <P>The purpose of this notice is to solicit comments from the public (as well as affected agencies) concerning our information collection. These comments will help us:</P>
                <P>(1) Evaluate whether the collection of information is necessary for the proper performance of the functions of the Agency, including whether the information will have practical utility;</P>
                <P>(2) Evaluate the accuracy of our estimate of the burden of the information collection, including the validity of the methodology and assumptions used;</P>
                <P>(3) Enhance the quality, utility, and clarity of the information to be collected; and</P>
                <P>
                    (4) Minimize the burden of the information collection on those who are to respond, through use, as appropriate, of automated, electronic, mechanical, and other collection technologies, 
                    <E T="03">e.g.</E>
                    , permitting electronic submission of responses.
                </P>
                <P>
                    <E T="03">Estimate of burden:</E>
                     The public reporting burden for this collection of information is estimated to average 0.35 hours per response.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Eligible commercial citrus growers in Florida.
                </P>
                <P>
                    <E T="03">Estimated annual number of respondents:</E>
                     20.
                </P>
                <P>
                    <E T="03">Estimated annual number of responses per respondent:</E>
                     1.
                </P>
                <P>
                    <E T="03">Estimated annual number of responses:</E>
                     20.
                </P>
                <P>
                    <E T="03">Estimated total annual burden on respondents:</E>
                     7 hours. (Due to averaging, the total annual burden hours may not equal the product of the annual number of responses multiplied by the reporting burden per response.)
                </P>
                <P>All responses to this notice will be summarized and included in the request for OMB approval. All comments will also become a matter of public record.</P>
                <SIG>
                    <DATED>Done in Washington, DC, this 1st day of December, 2003.</DATED>
                    <NAME>Kevin Shea,</NAME>
                    <TITLE>Acting Administrator, Animal and Plant Health Inspection Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30235 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3410-34-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBAGY>Animal and Plant Health Inspection Service</SUBAGY>
                <DEPDOC>[Docket No. 03-097-1]</DEPDOC>
                <SUBJECT>Notice of Request for Extension of Approval of an Information Collection</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Animal and Plant Health Inspection Service, USDA.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Extension of approval of an information collection; comment request.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Paperwork Reduction Act of 1995, this notice announces the Animal and Plant Health Inspection Service's intention to request an extension of approval of an information collection in support of regulations for the importation of artificially dwarfed plants.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>We will consider all comments that we receive on or before February 3, 2004.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may submit comments by postal mail/commercial delivery or by e-mail. If you use postal mail/commercial delivery, please send four copies of your comment (an original and three copies) to: Docket No. 03-097-1, Regulatory Analysis and Development, PPD, APHIS, Station 3C71, 4700 River Road Unit 118, Riverdale, MD 20737-1238. Please state that your comment refers to Docket No. 03-097-1. If you use e-mail, address your comment to 
                        <E T="03">regulations@aphis.usda.gov.</E>
                         Your comment must be contained in the body of your message; do not send attached files. Please include your name and address in your message and “Docket No. 03-097-1” on the subject line.
                    </P>
                    <P>You may read any comments that we receive on this docket in our reading room. The reading room is located in room 1141 of the USDA South Building, 14th Street and Independence Avenue, SW., Washington, DC. Normal reading room hours are 8 a.m. to 4:30 p.m., Monday through Friday, except holidays. To be sure someone is there to help you, please call (202) 690-2817 before coming.</P>
                    <P>
                        APHIS documents published in the 
                        <E T="04">Federal Register</E>
                        , and related information, including the names of organizations and individuals who have commented on APHIS dockets, are available on the Internet at 
                        <E T="03">http://www.aphis.usda.gov/ppd/rad/webrepor.html.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>For information regarding regulations for the importation of artificially dwarfed plants, contact Mr. Alan S. Green, Assistant Director, Quarantine Policy, Analysis and Support, PPQ, APHIS, 4700 River Road Unit 60, Riverdale, MD 20737-1236; (301) 734-8311. For copies of more detailed information on the information collection, contact Mrs. Celeste Sickles, APHIS’ Information Collection Coordinator, at (301) 734-7477.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P/>
                <P SOURCE="NPAR">
                    <E T="03">Title:</E>
                     Importation of Artificially Dwarfed Plants.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     0579-0176.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Extension of approval of an information collection.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The Plant Protection Act (7 U.S.C. 7701-7772) authorizes the Secretary of Agriculture to prohibit or restrict the importation, entry, or interstate movement of plants, plant products, and other articles to prevent the introduction of plant pests into the United States or their dissemination within the United States.
                </P>
                <P>
                    The regulations contained in “Subpart—Nursery Stock, Plants, Roots, Bulbs, Seeds, and Other Plant Products” (7 CFR 319.37 through 319.37-14) prohibit or restrict the importation of 
                    <PRTPAGE P="68020"/>
                    living plants, plant parts, and seeds for propagation.
                </P>
                <P>Among other things, the regulations require artificially dwarfed plants imported into the United States to be accompanied by a phytosanitary certificate issued by the government of the country of origin. This certificate must contain declarations that certain conditions were met in the country of origin to protect against the infestation of the plants by longhorned beetles and other plant pests.</P>
                <P>We are asking OMB to approve our use of these information collection activities for an additional 3 years.</P>
                <P>The purpose of this notice is to solicit comments from the public (as well as affected agencies) concerning our information collection. These comments will help us:</P>
                <P>(1) Evaluate whether the collection of information is necessary for the proper performance of the functions of the Agency, including whether the information will have practical utility;</P>
                <P>(2) Evaluate the accuracy of our estimate of the burden of the information collection, including the validity of the methodology and assumptions used;</P>
                <P>(3) Enhance the quality, utility, and clarity of the information to be collected; and</P>
                <P>
                    (4) Minimize the burden of the information collection on those who are to respond, through use, as appropriate, of automated, electronic, mechanical, and other collection technologies, 
                    <E T="03">e.g.</E>
                    , permitting electronic submission of responses.
                </P>
                <P>
                    <E T="03">Estimate of burden:</E>
                     The public reporting burden for this collection of information is estimated to average 0.25 hours per response.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Plant health officials of exporting countries.
                </P>
                <P>
                    <E T="03">Estimated annual number of respondents :</E>
                     20.
                </P>
                <P>
                    <E T="03">Estimated annual number of responses per respondent:</E>
                     5.
                </P>
                <P>
                    <E T="03">Estimated annual number of responses:</E>
                     100.
                </P>
                <P>
                    <E T="03">Estimated total annual burden on respondents:</E>
                     25 hours. (Due to averaging, the total annual burden hours may not equal the product of the annual number of responses multiplied by the reporting burden per response.)
                </P>
                <P>All responses to this notice will be summarized and included in the request for OMB approval. All comments will also become a matter of public record.</P>
                <SIG>
                    <DATED>Done in Washington, DC, this 1st day of December, 2003.</DATED>
                    <NAME>Kevin Shea,</NAME>
                    <TITLE>Acting Administrator, Animal and Plant Health Inspection Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30236 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3410-34-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBAGY>Animal and Plant Health Inspection Service</SUBAGY>
                <DEPDOC>[Docket No. 03-111-1]</DEPDOC>
                <SUBJECT>Double-Crested Cormorant Management in the United States; Record of Decision</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Animal and Plant Health Inspection Service, USDA.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice advises the public of the Animal and Plant Health Inspection Service's record of decision for the Double-Crested Cormorant Management in the United States final environmental impact statement.</P>
                </SUM>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Copies of the record of decision and the final environmental impact statement on which the record of decision is based are available for public inspection at USDA, room 1141, South Building, 14th Street and Independence Avenue SW., Washington, DC, between 8 a.m. and 4:30 p.m., Monday through Friday, except holidays. To be sure someone is there to help you, please call (202) 690-2817 before coming.</P>
                    <P>
                        The record of decision may be viewed on the Wildlife Services Web site at 
                        <E T="03">http://www.aphis.usda.gov/ws/pubs.html.</E>
                         The final environmental impact statement may also be viewed on the Internet at 
                        <E T="03">http://migratorybirds.fws.gov/issues/cormorant/cormorant.html.</E>
                    </P>
                    <P>
                        Copies of the record of decision and the final environmental impact statement may be obtained from the person listed under 
                        <E T="02">FOR FURTHER INFORMATION CONTACT.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mr. David S. Reinhold, Environmental Coordinator, Operational Support Staff, WS, APHIS, 4700 River Road Unit 87, Riverdale, MD 20737-1235; (301) 734-7921.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    This notice advises the public that the Animal and Plant Health Inspection Service (APHIS) has prepared a record of decision based on the Double-Crested Cormorant Management in the United States final environmental impact statement (EIS) prepared by the U.S. Fish and Wildlife Service (USFWS). APHIS was a cooperating agency in the preparation of the EIS. The USFWS published the notice of availability for the final EIS in the 
                    <E T="04">Federal Register</E>
                     on August 11, 2003 (68 FR 47603) and published its Record of Decision on October 8, 2003 (68 FR 58022). APHIS has independently reviewed the EIS and has concluded its comments and suggestions have been satisfied. APHIS has now prepared a record of decision on the adopted EIS and is making it available to the public. This record of decision has been prepared in accordance with: (1) The National Environmental Policy Act of 1969 (NEPA), as amended (42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ), (2) regulations of the Council on Environmental Quality for implementing the procedural provisions of NEPA (40 CFR parts 1500-1508), (3) USDA regulations implementing NEPA (7 CFR part 1), and (4) APHIS' NEPA Implementing Procedures (7 CFR part 372).
                </P>
                <SIG>
                    <DATED>Done in Washington, DC, this 2nd day of December 2003.</DATED>
                    <NAME>Kevin Shea,</NAME>
                    <TITLE>Acting Administrator, Animal and Plant Health Inspection Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30229 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3410-34-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBAGY>Animal and Plant Health Inspection Service</SUBAGY>
                <DEPDOC>[Docket No. 03-112-1]</DEPDOC>
                <SUBJECT>Vaccination of Wild Bison; Availability of an Environmental Assessment and Finding of No Significant Impact</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Animal and Plant Health Inspection Service, USDA.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>We are advising the public that an environmental assessment and finding of no significant impact have been prepared by the Animal and Plant Health Inspection Service relative to subcutaneous vaccination of wild, free-ranging bison in the Greater Yellowstone Area with Strain RB51 vaccine to help prevent the spread of brucellosis. The environmental assessment documents our review and analysis of environmental impacts associated with the vaccination and provides a basis for our conclusion that vaccination of the bison will not have a significant impact on the quality of the human environment. We are making the environmental assessment and finding of no significant impact available to the public for review and comment.</P>
                </SUM>
                <DATES>
                    <PRTPAGE P="68021"/>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>We will consider all comments that we receive on or before January 5, 2004.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        You may submit comments by postal mail/commercial delivery or by e-mail. If you use postal mail/commercial delivery, please send four copies of your comment (an original and three copies) to: Docket No. 03-112-1, Regulatory Analysis and Development, PPD, APHIS, Station 3C71, 4700 River Road Unit 118, Riverdale, MD 20737-1238. Please state that your comment refers to Docket No. 03-112-1. If you use e-mail, address your comment to 
                        <E T="03">regulations@aphis.usda.gov.</E>
                         Your comment must be contained in the body of your message; do not send attached files. Please include your name and address in your message and “Docket No. 03-112-1” on the subject line.
                    </P>
                    <P>
                        To obtain copies of the environmental assessment and finding of no significant impact, contact the National Center for Animal Health Programs, Veterinary Services, APHIS, 4700 River Road Unit 43, Riverdale, MD 20737-1231; (301) 734-4923. The documents are also available on the Internet at 
                        <E T="03">http://www.aphis.usda.gov/ppd/es/vsdocs.html.</E>
                    </P>
                    <P>You may also read the environmental assessment and finding of no significant impact, and any comments we receive on those documents, in our reading room. The reading room is located in room 1141 of the USDA South Building, 14th Street and Independence Avenue SW., Washington, DC. Normal reading room hours are 8 a.m. to 4:30 p.m., Monday through Friday, except holidays. To be sure someone is there to help you, please call (202) 690-2817 before coming.</P>
                    <P>
                        APHIS documents published in the 
                        <E T="04">Federal Register</E>
                        , and related information, including the names of organizations and individuals who have commented on APHIS dockets, are available on the Internet at 
                        <E T="03">http://www.aphis.usda.gov/ppd/rad/webrepor.html.</E>
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Dr. Arnold Gertonson, Yellowstone Brucellosis Coordinator, National Center for Animal Health Programs, VS, APHIS, Building B MSC 3E13, 2150 Centre Avenue, Fort Collins, CO 80526-8117; (970) 494-7363.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    Brucellosis is a contagious disease caused by 
                    <E T="03">Brucella</E>
                     bacteria. It can infect cattle, bison, elk, other animals, and humans. In cattle, bison, and elk, the specific disease organism is 
                    <E T="03">Brucella abortus</E>
                    . In infected cattle and bison, the disease organism localizes in lymph nodes, reproductive organs, and/or the udder, causing abortion in females and systemic effects in both males and females. Brucellosis is transmitted through contaminated and untreated milk and milk products and through direct contact with an infected aborted fetus or calf, afterbirth, or other reproductive tract discharges.
                </P>
                <P>Brucellosis is considered one of the most serious diseases of livestock. While its hallmark symptom is abortion, brucellosis can also result in decreased milk production, weight loss in animals, infertility, and lameness. The Animal and Plant Health Inspection Service (APHIS) has worked for years to eliminate this disease from the United States.</P>
                <P>
                    The only known reservoir of 
                    <E T="03">Brucella abortus</E>
                     in the United States occurs in wild, free-ranging populations of bison and elk in the Greater Yellowstone Area (GYA), which comprises areas of Idaho, Montana, and Wyoming. The significance of wildlife in the GYA as a reservoir of brucellosis and potential source of infection for cattle in the GYA has been widely recognized. Additionally, free-ranging bison herds in the GYA are a natural resource of great importance.
                </P>
                <P>To address the issue of brucellosis in the GYA, the U.S. Department of the Interior's National Park Service, the State of Montana, and their cooperators (including the U.S. Department of Agriculture) developed an Interagency Bison Management Plan for the bison herd in Yellowstone National Park (YNP). One of the disease management requirements of the plan is for eligible bison to be vaccinated against brucellosis.</P>
                <P>The Montana Department of Livestock (MDOL) has requested APHIS's assistance with the vaccination against brucellosis of wild, free-ranging bison calves and non-pregnant yearlings that leave YNP and migrate onto State, private, or other Federal lands. The MDOL anticipates starting bison vaccination as early as this winter, using Strain RB51 vaccine, when bison begin to leave YNP in search of vegetation.</P>
                <P>APHIS has completed an environmental assessment (EA) that examines the potential environmental effects of APHIS's involvement in the vaccination described above. Our review and analysis are documented in detail in an EA entitled “Subcutaneous Vaccination of Wild, Free-Ranging Bison in the Greater Yellowstone Area; Environmental Assessment (November 2003).” Based on that EA, APHIS has determined that subcutaneous vaccination of wild, free-ranging bison of the GYA with Strain RB51 vaccine will not significantly impact human health or the environment. That determination is set forth in a document titled “Finding of No Significant Impact for Subcutaneous Vaccination of Wild, Free-Ranging Bison in the Greater Yellowstone Area; Environmental Assessment (November 2003).”</P>
                <P>
                    We are making the EA and finding of no significant impact (FONSI) available to the public for review and comment. (Instructions for obtaining copies of the EA and FONSI are included under the heading 
                    <E T="02">ADDRESSES</E>
                     at the beginning of this notice.) We will consider all comments on the EA and FONSI that we receive on or before the date listed under the heading 
                    <E T="02">DATES</E>
                     at the beginning of this notice. Following the close of the comment period, we will publish a notice in the 
                    <E T="04">Federal Register</E>
                     in which we will discuss any issues raised by commenters.
                </P>
                <P>
                    The EA and FONSI have been prepared in accordance with: (1) The National Environmental Policy Act of 1969 (NEPA), as amended (42 U.S.C. 4321 
                    <E T="03">et seq.</E>
                    ), (2) regulations of the Council on Environmental Quality for implementing the procedural provisions of NEPA (40 CFR parts 1500-1508), (3) USDA regulations implementing NEPA (7 CFR part 1), and
                </P>
                <P>(4) APHIS' NEPA Implementing Procedures (7 CFR part 372).</P>
                <SIG>
                    <DATED>Done in Washington, DC, this 2nd day of December, 2003.</DATED>
                    <NAME>Kevin Shea,</NAME>
                    <TITLE>Acting Administrator, Animal and Plant health Inspection Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30237 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3410-34-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF AGRICULTURE</AGENCY>
                <SUBAGY>Forest Service</SUBAGY>
                <SUBJECT>South Fork Wildfire Salvage Project, Boise National Forest, ID</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Forest Service, USDA.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of Intent to Prepare Environmental Impact Statement.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Cascade Ranger District of the Boise National Forest will prepare an environmental impact statement (EIS) for a resource management project in the South Fork Salmon River. The entire project area is located within watersheds that drain directly into the South Fork Salmon River or its tributaries, downstream of Warm Lake. The project area is located 25 miles northeast of Cascade, Idaho, and about 120 miles north of Boise, Idaho.
                        <PRTPAGE P="68022"/>
                    </P>
                    <P>The agency invites written comments and suggestions on the scope of the analysis. The agency also hereby gives notices of the environmental analysis and decision-making process that will occur on the proposal so interested and affected people are aware of how they may participate and contribute to the final decision. At this time no public meetings to discuss the project are planned.</P>
                    <P>
                        <E T="03">Proposed Action:</E>
                         The primary objective of the project is to capture the value of fire-killed and imminently dead timber not needed to maintain or improve post-fire ecological function in the short (3-15 years) and long term (15+ years). To further the achievement of Forest Plan goals, road maintenance and decommissioning activities have been integrated with the salvage proposal to support identified aquatic and watershed restoration activities. Revenue generated from the salvage operation would be used to accomplish all or some of these road-related activities.
                    </P>
                    <P>The Proposed Action would harvest fire-killed and imminently dead trees from a total of 2,536 acres in the 6,822-acre project area. Only those trees not needed to maintain or improve post-fire ecological function in the short (3-15 years) and long term (15+ years) would be harvested. An estimated 5.0 MMBF of timber would be available for harvest using ground-based (780 acres) and helicopter (1,756 acres) yarding systems. The Proposed Action would employ the salvage prescription only.</P>
                    <P>No new road construction or reconstruction, as defined in the Revised Forest Plan, would occur. An estimated 0.1 mile of road 401, 0.9 mile of road 467, and 0.4 mile of road 488 would be restored through maintenance activities to their approved road management objectives to improve fish habitat and hydrologic conditions, and reduce sedimentation. Specifically, three additional culverts and one hardened drive-through dip would be installed and two existing culverts replaced on road 401; eight additional culverts installed and 0.5 mile of the surface graveled on road 467, and; 0.4 mile of the surface graveled on road 488.</P>
                    <P>An estimated 0.3 mile of existing roads (401C, 487, and 467A), currently closed year-round to motorized traffic, would be decommissioned to prevent unauthorized use. These three roads (401C, 487, and 467A) and their associated arterial roads (487A, 487B, 487B1, 487D, 467A1, and 467A2) would be removed from the transportation system. Decommissioning of this 0.3 mile would effectively prevent unauthorized access on roughly 10 miles of road.</P>
                    <P>
                        <E T="03">Preliminary Issues:</E>
                         Preliminary concerns with the Proposed Action include potential impacts on: (1) Fish habitat and water quality; (2) inventoried roadless areas; (3) visual quality of the area, and; (4) the suitable Wild and Scenic River corridor.
                    </P>
                    <P>
                        <E T="03">Possible Alternatives To The Proposed Action:</E>
                         One alternative to the Proposed Action that has been discussed thus far is a no action alternative. Other alternatives will likely be developed as issues are identified and information received.
                    </P>
                    <P>
                        <E T="03">Decisions To Be Made:</E>
                         The Boise National Forest Supervisor will decide the following. What amount, type, and distribution of dead and imminently dead trees within the wildfire area should be retained to improve or maintain post-fire ecological conditions? If dead and imminently dead trees within the wildfire area are found not to be needed to improve or maintain ecosystem functions, how should they be harvested while still protecting post-fire ecological conditions? Should existing classified roads within the project area receive maintenance activities to improve fish habitat and hydrologic conditions and reduce sedimentation, and if so, where within the project area? Should portions of roads currently closed year-round to motorized traffic be decommissioned to prevent unauthorized use, and if so, which roads? What design features and/or mitigation measures should be applied to proposed activities to help ensure the activities do not retard attainment of post-fire ecological recovery in the short and long term?
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Substantive comments concerning the proposed project and analysis are encouraged and should be postmarked or received within 30 days following publication of this announcement in the 
                        <E T="04">Federal Register</E>
                        .
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Substantive comments should be addressed to the Cascade Ranger District, ATTN: Keith Dimmett, P.O. Box 696, Cascade, ID 83611 or sent electronically to 
                        <E T="03">comments-intermtn-boise-cascade@fs.fed.us</E>
                        . Electronic comments must be submitted in plain text or another format compatible with Microsoft Word. Substantive comments are those within the scope of, are specific to, and have a direct relationship to the proposed action and include supporting reasons that the Responsible Official should consider in reaching a decision. Comments received in response to this request will be available for public inspection and will be released in their entirety if requested pursuant to the Freedom of Information Act.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Further information can be obtained from Keith Dimmett at the address mentioned above or by calling 208-382-7400.</P>
                    <P>
                        <E T="03">Schedule:</E>
                         Draft Environmental Impact Statement (DEIS), February 2004. Final Environmental Impact Statement (FEIS), May 2004.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Roughly half of the project area has been inventoried as roadless, including portions of both the Reeves Creek and Caton Lake Inventoried Roadless Areas. None of the activities associated with the Proposed Action would occur within any inventoried roadless area. With the exception of trees already felled within the powerline corridor, harvest would not occur within streamside riparian conservation areas (RCAs).</P>
                <P>The entire project area lies within Management Area 19 (Warm Lake), discussed on pages III-316 through III-331 in the Revised Boise National Land and Resource Management Plan. Several management prescription categories apply within this management area, however only Management Prescription Categories 2.1, 3.2, and 4.2 occur within the project area.</P>
                <P>
                    The comment period on the DEIS will be 45 days from the date the Environmental Protection Agency publishes the notice of availability in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <P>
                    The Forest Service believes, at this early stage, it is important to give reviewers notice of several court rulings related to public participation in the environmental review process. First, reviewers of the DEIS must structure their participation in the environmental review of the proposal so that it is meaningful and alerts an agency to the reviewer's position and contentions. 
                    <E T="03">Vermont Yankee Nuclear Power Corp.</E>
                     v. 
                    <E T="03">NRDC</E>
                    , 435 U.S. 519, 553 (1978). Also, environmental objections that could be raised at the DEIS stage but are not raised until after completion of the FEIS may be waived or dismissed by the courts. 
                    <E T="03">City of Angoon</E>
                     v. 
                    <E T="03">Hodel</E>
                    , 803 F. 2d 1016, 1002 (9th Cir., 1986) and 
                    <E T="03">Wisconsin Heritages, Inc.</E>
                     v. 
                    <E T="03">Harris</E>
                    , 490 F. Supp. 1334, 1338 (E.D. Wis. 1980). Because of these court rulings, it is very important that those interested in this proposed action participate by the close of the DEIS 45-day comment period so that substantive comments and objections are made available to the Forest Service at a time when it can meaningfully consider them and respond to them in the FEIS.
                    <PRTPAGE P="68023"/>
                </P>
                <P>To assist the Forest Service in identifying and considering issues and concerns on the proposed action, comments on the DEIS should be as specific as possible. It is also helpful if comments refer to specific pages or chapters of the draft statement. Reviewers may wish to refer to the Council on Environmental Quality Regulations for implementing the procedural provisions of the National Environmental Policy Act at 40 CFR 1503.3 in addressing these points.</P>
                <P>
                    <E T="03">Responsible Official:</E>
                     Richard A. Smith, Forest Supervisor, Boise National Forest, 1249 South Vinnell Way, Suite 200, Boise, ID 83709.
                </P>
                <SIG>
                    <DATED>Dated: November 26, 2003.</DATED>
                    <NAME>Richard A. Smith,</NAME>
                    <TITLE>Forest Supervisor.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30066  Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3410-11-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">COMMITTEE FOR PURCHASE FROM PEOPLE WHO ARE  BLIND OR SEVERELY DISABLED </AGENCY>
                <SUBJECT>Procurement List; Proposed Additions and Deletions </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Committee for Purchase from People Who Are Blind or Severely Disabled. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed additions to and deletions from Procurement List. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Committee is proposing to add to the Procurement List services to be furnished by nonprofit agencies employing persons who are blind or have other severe disabilities, and to delete products previously furnished by such agencies. </P>
                    <P>
                        <E T="03">Comments Must Be Received on or Before:</E>
                         January 4, 2004. 
                    </P>
                </SUM>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Committee for Purchase From People Who Are Blind or Severely Disabled,  Jefferson Plaza 2, Suite 10800, 1421 Jefferson Davis Highway, Arlington, Virginia, 22202-3259. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Sheryl D. Kennerly, (703) 603-7740. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This notice is published pursuant to 41 U.S.C 47(a)(2) and 41 CFR 51-2.3. Its purpose is to provide interested persons an opportunity to submit comments on the proposed actions. </P>
                <HD SOURCE="HD1">Additions </HD>
                <P>If the Committee approves the proposed additions, the entities of the Federal Government identified in this notice for each product or service will be required to procure the services listed below from nonprofit agencies employing persons who are blind or have other severe disabilities. </P>
                <HD SOURCE="HD2">Regulatory Flexibility Act Certification </HD>
                <P>I certify that the following action will not have a significant impact on a substantial number of small entities. The major factors considered for this certification were: </P>
                <P>1. If approved, the action will not result in any additional reporting, recordkeeping or other compliance requirements for small entities other than the small organizations that will furnish the services to the Government. </P>
                <P>2. If approved, the action will result in authorizing small entities to furnish the services to the Government. </P>
                <P>3. There are no known regulatory alternatives which would accomplish the objectives of the Javits-Wagner-O'Day Act (41 U.S.C. 46-48c) in connection with the services proposed for addition to the Procurement List. Comments on this certification are invited. </P>
                <P>Commenters should identify the statement(s) underlying the certification on which they are providing additional information. </P>
                <HD SOURCE="HD1">End of Certification </HD>
                <P>The following services are proposed for addition to Procurement List for production by the nonprofit agencies listed: </P>
                <EXTRACT>
                    <HD SOURCE="HD2">Services </HD>
                    <FP SOURCE="FP-2">
                        <E T="03">Service Type/Location:</E>
                         Document Destruction, At the following Locations and for the Nonprofit Agencies Indicated:  Camarillo Office, IRS (Including the Criminal Investigation Division), 751 Daily Drive, Camarillo, California. 
                    </FP>
                    <FP SOURCE="FP-2">NPA: Goodwill Industries of Southern California, Los Angeles, CA, El Centro Office, IRS,  1699 W. Main Street, El Centro, California. </FP>
                    <FP SOURCE="FP-2">NPA: Landmark Services, Inc., Santa Ana, California, El Monte Office, IRS (Including the Criminal Investigation Division),  9350 E. Flair Drive, El Monte, California. </FP>
                    <FP SOURCE="FP-2">NPA: Goodwill Industries of Southern California, Los Angeles, California, El Segundo Office, IRS (Including the Criminal Investigation Division), 222 N. Sepulveda Blvd., El Segundo, California. </FP>
                    <FP SOURCE="FP-2">NPA: Goodwill Industries of Southern California, Los Angeles, California, Glendale Office, IRS (Including the Criminal Investigation Division),  225 W. Broadway, Glendale, California. </FP>
                    <FP SOURCE="FP-2">NPA: Goodwill Industries of Southern California, Los Angeles, California, Laguna Niguel Office, IRS (Including the Criminal Investigation Division), 24000 Avila Road, Laguna Niguel, California. </FP>
                    <FP SOURCE="FP-2">NPA: Landmark Services, Inc., Santa Ana, California, Long Beach Office, IRS (Including the Criminal Investigation Division), 501 W. Ocean Blvd., Long Beach, California. </FP>
                    <FP SOURCE="FP-2">NPA: Landmark Services, Inc., Santa Ana, California, Los Angeles Office, IRS (Including the Criminal Investigation Division), 300 N. Los Angeles Street, Los Angeles, California. </FP>
                    <FP SOURCE="FP-2">NPA: Goodwill Industries of Southern California, Los Angeles, California, Norwalk Office, IRS, 12440 E. Imperial Highway,  Norwalk, California. </FP>
                    <FP SOURCE="FP-2">NPA: Goodwill Industries of Southern California, Los Angeles, California, Palm Springs Office, IRS, 980 E. Tahquitz Canyon Way,  Palm Springs, California.</FP>
                    <FP SOURCE="FP-2">NPA: Goodwill Industries of Southern California, Los Angeles, California, San Bernardino Office, IRS (Including the Criminal nvestigation Division), 290 N. “D” Street, San Bernardino, California. </FP>
                    <FP SOURCE="FP-2">NPA: Goodwill Industries of Southern California, Los Angeles, California, San Diego Office, IRS (Including the Criminal Investigation Division),  880 Front Street, and 701 “B” Street, San Diego, California. </FP>
                    <FP SOURCE="FP-2">NPA: Landmark Services, Inc., Santa Ana, California, San Marcos Office, IRS,  1 Civic Center Drive, San Marcos, California. </FP>
                    <FP SOURCE="FP-2">NPA: Landmark Services, Inc., Santa Ana, California, Santa Ana Office, IRS (Including the Criminal Investigation Division),  34 Civic Center Plaza, Santa Ana, California. </FP>
                    <FP SOURCE="FP-2">NPA: Landmark Services, Inc., Santa Ana, California, Van Nuys Office, IRS (Including the Criminal Investigation Division),  6230 Van Nuys Blvd., Van Nuys, California. </FP>
                    <FP SOURCE="FP-2">NPA: Goodwill Industries of Southern California, Los Angeles, California, Woodland Hills Office, IRS,  6340 Variel Ave, Woodlands Hills, California. </FP>
                    <FP SOURCE="FP-2">NPA: Goodwill Industries of Southern California, Los Angeles, California. </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contract Activity:</E>
                         IRS-Western Area Procurement Branch-APFW, San Francisco, California. 
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Service Type/Location:</E>
                         Mailing Services, Theodore Levin U.S. Courthouse, U.S. District Court, Eastern District of Michigan, Detroit, Michigan. 
                    </FP>
                    <FP SOURCE="FP-2">NPA: Jewish Vocational Service and Community Workshop, Southfield, Michigan. </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contract Activity:</E>
                         U.S. District Court, Detroit, Michigan.
                    </FP>
                </EXTRACT>
                <HD SOURCE="HD1">Deletions </HD>
                <HD SOURCE="HD2">Regulatory Flexibility Act Certification </HD>
                <P>I certify that the following action will not have a significant impact on a substantial number of small entities. The major factors considered for this certification were: </P>
                <P>1. If approved, the action may result in additional reporting, recordkeeping or other compliance requirements for small entities. </P>
                <P>2. If approved, the action may result in authorizing small entities to furnish the products to the Government. </P>
                <P>
                    3. There are no known regulatory alternatives which would accomplish 
                    <PRTPAGE P="68024"/>
                    the objectives of the Javits-Wagner-O'Day Act (41 U.S.C. 46-48c) in connection with the products proposed for deletion from the Procurement List. 
                </P>
                <HD SOURCE="HD2">End of Certification </HD>
                <P>The following products are proposed for deletion from the Procurement List:</P>
                <EXTRACT>
                    <HD SOURCE="HD1">Products </HD>
                    <FP SOURCE="FP-2">
                        <E T="03">Product/NSN:</E>
                         Detergent, General Purpose, 
                    </FP>
                    <FP SOURCE="FP1-2">7930-01-055-6121. </FP>
                    <FP SOURCE="FP-2">NPA: Lighthouse for the Blind, St. Louis, Missouri. </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contract Activity:</E>
                         GSA, Southwest Supply Center, Fort Worth, Texas. 
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Product/NSN:</E>
                         Holder, Desk Memorandum, 
                    </FP>
                    <FP SOURCE="FP1-2">7520-00-139-3802,</FP>
                    <FP SOURCE="FP1-2">7520-00-290-6445.</FP>
                    <FP SOURCE="FP-2">NPA: Dallas Lighthouse for the Blind, Inc., Dallas, Texas. </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contract Activity:</E>
                         Office Supplies &amp; Paper Products Acquisition Center, New York, New York. 
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Product/NSN:</E>
                         Sponge, Cellulose, 
                    </FP>
                    <FP SOURCE="FP1-2">7920-00-559-8462. </FP>
                    <FP SOURCE="FP-2">NPA: Mississippi Industries for the Blind, Jackson, Mississippi. </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contract Activity:</E>
                         GSA, Southwest Supply Center, Fort Worth, Texas. 
                    </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Product/NSN:</E>
                         Strap Set, Webbing, 
                    </FP>
                    <FP SOURCE="FP1-2">5342-00-922-2480. </FP>
                    <FP SOURCE="FP-2">NPA: Huntsville Rehabilitation Foundation, Huntsville, Alabama. </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contract Activity:</E>
                         Defense Supply Center Richmond, Richmond, Virginia. 
                    </FP>
                </EXTRACT>
                <SIG>
                    <NAME>Sheryl D. Kennerly, </NAME>
                    <TITLE>Director, Information Management. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30288 Filed 12-4-03; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6353-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">COMMITTEE FOR PURCHASE FROM PEOPLE WHO ARE BLIND OR SEVERELY DISABLED </AGENCY>
                <SUBJECT>Procurement List; Additions and Deletions </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Committee for Purchase From People Who Are Blind or Severely Disabled. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Additions to and deletions from Procurement List. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This action adds to the Procurement List products and services to be furnished by nonprofit agencies employing persons who are blind or have other severe disabilities, and deletes from the Procurement List products previously furnished by such agencies. </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>January 4, 2004. </P>
                </EFFDATE>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Committee for Purchase From People Who Are Blind or Severely Disabled, Jefferson Plaza 2, Suite 10800, 1421 Jefferson Davis Highway, Arlington, Virginia 22202-3259. </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Sheryl D. Kennerly, (703) 603-7740. </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Additions </HD>
                <P>On August 29, October 3, and October 10, 2003, the Committee for Purchase From People Who Are Blind or Severely Disabled published notice (68 FR 51962, 57403, and 58651) of proposed additions to the Procurement List. </P>
                <P>After consideration of the material presented to it concerning capability of qualified nonprofit agencies to provide the products and services and impact of the additions on the current or most recent contractors, the Committee has determined that the products and services listed below are suitable for procurement by the Federal Government under 41 U.S.C. 46-48c and 41 CFR 51-2.4. </P>
                <HD SOURCE="HD2">Regulatory Flexibility Act Certification </HD>
                <P>I certify that the following action will not have a significant impact on a substantial number of small entities. The major factors considered for this certification were: </P>
                <P>1. The action will not result in any additional reporting, recordkeeping or other compliance requirements for small entities other than the small organizations that will furnish the products and services to the Government. </P>
                <P>2. The action will result in authorizing small entities to furnish the products and services to the Government. </P>
                <P>3. There are no known regulatory alternatives which would accomplish the objectives of the Javits-Wagner-O'Day Act (41 U.S.C. 46-48c) in connection with the products and services proposed for addition to the Procurement List. </P>
                <HD SOURCE="HD1">End of Certification </HD>
                <P>Accordingly, the following products and services are added to the Procurement List: </P>
                <EXTRACT>
                    <HD SOURCE="HD2">Products </HD>
                    <FP SOURCE="FP-2">Product/NSN: Fluorescent Highlighter </FP>
                    <FP SOURCE="FP1-2">M.R. 1776 </FP>
                    <FP SOURCE="FP-2">Product/NSN: Permanent Marker </FP>
                    <FP SOURCE="FP1-2">M.R. 1780 </FP>
                    <FP SOURCE="FP-2">NPA: Dallas Lighthouse for the Blind, Inc., Dallas, Texas </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contract Activity:</E>
                         Defense Commissary Agency, Fort Lee, Virginia 
                    </FP>
                    <FP SOURCE="FP-2">Product/NSN: Polyethylene Waste Disposable Asbestos Bag </FP>
                    <FP SOURCE="FP1-2">8105-LL-S04-7842 </FP>
                    <FP SOURCE="FP1-2">8105-LL-S04-7843 </FP>
                    <FP SOURCE="FP1-2">8105-LL-S05-0018 </FP>
                    <FP SOURCE="FP-2">NPA: Open Door Center, Valley City, North Dakota </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contract Activity:</E>
                         Fleet and Industrial Supply Center, Bremerton, Washington 
                    </FP>
                    <FP SOURCE="FP-2">Product/NSN: Safety-Walk, Tapes &amp; Treads </FP>
                    <FP SOURCE="FP1-2">7220-00-NIB-0022, 710 Black Coarse Tape </FP>
                    <FP SOURCE="FP1-2">7220-00-NIB-0031, 710 Black Coarse Tape </FP>
                    <FP SOURCE="FP1-2">7220-00-NIB-0032, 610 Black General Purpose </FP>
                    <FP SOURCE="FP1-2">7220-00-NIB-0046, 630 Yellow General Purpose </FP>
                    <FP SOURCE="FP1-2">7220-00-NIB-0053, 510 Black Conformable </FP>
                    <FP SOURCE="FP1-2">7220-00-NIB-0054, 510 Black Conformable </FP>
                    <FP SOURCE="FP1-2">7220-00-NIB-0061, 530 Yellow Conformable </FP>
                    <FP SOURCE="FP1-2">7220-00-NIB-0065, 310 Black Medium Resilient </FP>
                    <FP SOURCE="FP1-2">7220-00-NIB-0075, 370 Gray Medium Resilient </FP>
                    <FP SOURCE="FP1-2">7220-00-NIB-0136, 710 Black Coarse Tape </FP>
                    <FP SOURCE="FP1-2">7220-00-NIB-0137, 610 Black General Purpose </FP>
                    <FP SOURCE="FP1-2">7220-00-NIB-0138, 620 Clear General Purpose </FP>
                    <FP SOURCE="FP1-2">7220-00-NIB-0139, 630 Yellow General Purpose </FP>
                    <FP SOURCE="FP1-2">7220-00-NIB-0140, 660 Brown General Purpose </FP>
                    <FP SOURCE="FP1-2">7220-00-NIB-0141, 510 Black Conformable </FP>
                    <FP SOURCE="FP1-2">7220-00-NIB-0142, 520 Yellow Conformable </FP>
                    <FP SOURCE="FP1-2">7220-00-NIB-0143, 310 Black Medium Resilient </FP>
                    <FP SOURCE="FP1-2">7220-00-NIB-0144, 370 Gray Medium Resilient </FP>
                    <FP SOURCE="FP-2">NPA: Louisiana Association for the Blind, Shreveport, Louisiana </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contract Activity:</E>
                         Office Supplies &amp; Paper Products Acquisition Center, New York, New York 
                    </FP>
                    <FP SOURCE="FP-2">Product/NSN: Telephone Cards </FP>
                    <FP SOURCE="FP1-2">M.R. 987 (200 Minutes) </FP>
                    <FP SOURCE="FP1-2">M.R. 988 (300 Minutes) </FP>
                    <FP SOURCE="FP1-2">M.R. 993 (400 Minutes) </FP>
                    <FP SOURCE="FP-2">NPA: Winston-Salem Industries for the Blind, Winston-Salem, North Carolina </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contract Activity:</E>
                         Defense Commissary Agency (DeCA), Ft. Lee, Virginia 
                    </FP>
                    <HD SOURCE="HD2">Services </HD>
                    <FP SOURCE="FP-2">Service Type/Location: Administrative Services, Federal Protective Service, Southern Field Operation Branch, Los Angeles, California </FP>
                    <FP SOURCE="FP-2">NPA: Pacific Coast Community Services, Truckee, California </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contract Activity:</E>
                         GSA/PBS, Region 9 PMS, San Francisco, California 
                    </FP>
                    <FP SOURCE="FP-2">Service Type/Location: Custodial Services, U.S. Courthouse (Federal Building), Charlottesville, Virginia </FP>
                    <FP SOURCE="FP-2">NPA: WorkSource Enterprises, Charlottesville, Virginia </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contract Activity:</E>
                         GSA, Public Buildings Service, Region 3 (3PMT), Philadelphia, Pennsylvania 
                    </FP>
                    <FP SOURCE="FP-2">Service Type/Location: Custodial Services U.S. Mint, West Point, New York </FP>
                    <FP SOURCE="FP-2">NPA: New Dynamics Corporation, Middletown, New York </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contract Activity:</E>
                         Department of the Treasury, Washington, DC 
                    </FP>
                </EXTRACT>
                <HD SOURCE="HD1">Deletions </HD>
                <P>
                    On October 10, 2003, the Committee for Purchase From People Who Are Blind or Severely Disabled published notice (68 F.R. 58651/58652) of 
                    <PRTPAGE P="68025"/>
                    proposed deletions to the Procurement List. After consideration of the relevant matter presented, the Committee has determined that the products listed below are no longer suitable for procurement by the Federal Government under 41 U.S.C. 46-48c and 41 CFR 51-2.4. 
                </P>
                <HD SOURCE="HD2">Regulatory Flexibility Act Certification </HD>
                <P>I certify that the following action will not have a significant impact on a substantial number of small entities. The major factors considered for this certification were: </P>
                <P>1. The action may result in additional reporting, recordkeeping or other compliance requirements for small entities. </P>
                <P>2. The action may result in authorizing small entities to furnish the products to the Government. </P>
                <P>3. There are no known regulatory alternatives which would accomplish the objectives of the Javits-Wagner-O'Day Act (41 U.S.C. 46-48c) in connection with the products deleted from the Procurement List. </P>
                <HD SOURCE="HD2">End of Certification </HD>
                <P>Accordingly, the following products are deleted from the Procurement List: </P>
                <EXTRACT>
                    <HD SOURCE="HD2">Products </HD>
                    <FP SOURCE="FP-2">Product/NSN: Computer Accessories </FP>
                    <FP SOURCE="FP1-2">7045-01-483-7451 </FP>
                    <FP SOURCE="FP1-2">7045-01-483-7844 </FP>
                    <FP SOURCE="FP-2">NPA: Wiscraft Inc.—Wisconsin Enterprises for the Blind, Milwaukee, Wisconsin </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contract Activity:</E>
                         Office Supplies &amp; Paper Products Acquisition Center, New York, New York 
                    </FP>
                    <FP SOURCE="FP-2">Product/NSN: Dropcloth, Heavy Duty </FP>
                    <FP SOURCE="FP1-2">8340-00-NIB-0010 </FP>
                    <FP SOURCE="FP-2">NPA: East Texas Lighthouse for the Blind, Tyler, Texas </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contract Activity:</E>
                         GSA, Southwest Supply Center, Fort Worth, Texas 
                    </FP>
                    <FP SOURCE="FP-2">Product/NSN: Fixture, Lighting Industrial </FP>
                    <FP SOURCE="FP1-2">6210-00-688-4929 </FP>
                    <FP SOURCE="FP-2">NPA: The Chicago Lighthouse for People who are Blind or Visually Impaired, Chicago, Illinois </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contract Activity:</E>
                         GSA, Southwest Supply Center, Fort Worth, Texas 
                    </FP>
                    <FP SOURCE="FP-2">Product/NSN: Pad, Scouring </FP>
                    <FP SOURCE="FP1-2">7920-01-383-7928 </FP>
                    <FP SOURCE="FP-2">NPA: Beacon Lighthouse, Inc., Wichita Falls, Texas </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contract Activity:</E>
                         GSA, Southwest Supply Center, Fort Worth, Texas 
                    </FP>
                    <FP SOURCE="FP-2">Product/NSN: Tape, Electronic Data </FP>
                    <FP SOURCE="FP1-2">7045-01-438-7086 </FP>
                    <FP SOURCE="FP-2">NPA: North Central Sight Services, Inc., Williamsport, Pennsylvania </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contract Activity:</E>
                         Defense Supply Center Philadelphia, Philadelphia, Pennsylvania 
                    </FP>
                    <FP SOURCE="FP-2">Product/NSN: Tape, Electronic Data Processing </FP>
                    <FP SOURCE="FP1-2">7045-01-123-0367 </FP>
                    <FP SOURCE="FP-2">NPA: North Central Sight Services, Inc., Williamsport, Pennsylvania </FP>
                    <FP SOURCE="FP-2">
                        <E T="03">Contract Activity:</E>
                         Defense Supply Center Columbus, Columbus, Ohio 
                    </FP>
                    <FP SOURCE="FP-1">Product/NSN: Towel, Paper </FP>
                    <FP SOURCE="FP1-2">8540-01-494-0910 </FP>
                    <FP SOURCE="FP-2">NPA: The Lighthouse for the Blind in New Orleans, New Orleans, Louisiana </FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Contract Activity:</E>
                         Office Supplies &amp; Paper Products Acquisition Center, New York, New York 
                    </FP>
                </EXTRACT>
                <SIG>
                    <NAME>Sheryl D. Kennerly, </NAME>
                    <TITLE>Director, Information Management. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30289 Filed 12-4-03; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6353-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">BROADCASTING BOARD OF GOVERNORS</AGENCY>
                <SUBJECT>Sunshine Act Meeting</SUBJECT>
                <PREAMHD>
                    <HD SOURCE="HED">Date and Time:</HD>
                    <P>December 10, 2003; 1 p.m.-4:30 p.m.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">Place:</HD>
                    <P>Broadcasting Board of Governors, 330 Independence Avenue, SW, Washington, DC 20237.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">Closed Meeting:</HD>
                    <P>The members of the Broadcasting Board of Governors (BBG) will meet in closed session to review and discuss a number of issues relating to U.S. Government-funded non-military international broadcasting. They will address internal procedural, budgetary, and personnel issues, as well as sensitive foreign policy issues relating to potential options in the U.S. international broadcasting field. This meeting is closed because if open it likely would either disclose matters that would be properly classified to be kept secret in the interest of foreign policy under the appropriate executive order (5 U.S.C. 552b. (c)(1)) or would disclose information the premature disclosure of which would be likely to significantly frustrate implementation of a proposed agency action. (5 U.S.C. 552. (c)(9)(B)) In addition, part of the discussion will relate solely to the internal personnel and organizational issues of the BBG or the International Broadcasting Bureau. (5 U.S.C. 552b (c)(2) and (6))</P>
                </PREAMHD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Persons interested in obtaining more information should contact either Brenda Hardnett or Carol Booker at (202) 401-3736.</P>
                    <SIG>
                        <DATED>Dated: December 2, 2003.</DATED>
                        <NAME>Carol Booker,</NAME>
                        <TITLE>Legal Counsel.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30339  Filed 12-3-03; 10:14 am]</FRDOC>
            <BILCOD>BILLING CODE 8230-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
                <P>DOC has submitted to the Office of Management and Budget (OMB) for clearance the following proposal for collection of information under the provision of the Paperwork Reduction Act of 1995, Public Law 104-13.</P>
                <P>
                    <E T="03">Bureau:</E>
                     International Trade Administration.
                </P>
                <P>
                    <E T="03">Title:</E>
                     U.S. Government Trade Event Information Request.
                </P>
                <P>
                    <E T="03">Agency Form Number:</E>
                     ITA-4136P.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     0625-0238.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Regular Submission.
                </P>
                <P>
                    <E T="03">Burden:</E>
                     50 hours.
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     50.
                </P>
                <P>
                    <E T="03">Avg. Hours Per Response:</E>
                     1 hour.
                </P>
                <P>
                    <E T="03">Needs and Uses:</E>
                     The International Trade Administration's Advocacy Center marshals federal resources to assist U.S. firms competing for foreign government procurements worldwide. The Advocacy Center is under the umbrella of the Trade Promotion Coordinating Committee (TPCC), which is chaired by the Secretary of Commerce and includes 19 federal agencies involved in export promotion. The mission of the Advocacy Center is to promote U.S. exports and create U.S. jobs and coordinate U.S. Government (USG) advocacy among the TPCC. The purpose of the questionnaire is to collect the necessary information to make an evaluation as to whether a firm qualifies for senior-level USG support, in the form of attendance at an event including witnessing a commercial agreement signing. The event could be a company sponsored activity or a foreign or USG sponsored event to highlight a commercial trade success for more than one firm. Without this information we will be unable to determine if a U.S. firm is eligible for USG support for the firm's role in the event.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Businesses or other for-profit.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     On occasion.
                </P>
                <P>
                    <E T="03">Respondent's Obligation:</E>
                     Required to obtain or retain a benefit; voluntary.
                </P>
                <P>
                    <E T="03">OMB Desk Officer:</E>
                     David Roster, (202) 395-7340.
                </P>
                <P>
                    Copies of the above information collection proposal can be obtained by calling or writing Diana Hynek, Departmental Paperwork Clearance Officer, (202) 482-0266, Department of Commerce, Room 6625, 14th Street and Constitution Ave., NW., Washington, DC 20230. E-mail: 
                    <E T="03">dHynek@doc.gov</E>
                    .
                </P>
                <P>
                    Written comments and recommendations for the proposed information collection should be sent to 
                    <PRTPAGE P="68026"/>
                    David Roster, OMB Desk Officer, Room 10202, New Executive Office Building, Washington, DC 20503 within 30 days of the publication of this notice in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <SIG>
                    <DATED>Dated: December 1, 2003.</DATED>
                    <NAME>Madeleine Clayton,</NAME>
                    <TITLE>Management Analyst, Office of the Chief Information Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30238 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DR-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <DEPDOC>[I.D. 120203A]</DEPDOC>
                <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
                <P>The Department of Commerce has submitted to the Office of Management and Budget (OMB) for clearance the following proposal for collection of information under the emergency provisions of the Paperwork Reduction Act (44 U.S.C. Chapter 35).</P>
                <P>
                    <E T="03">Agency</E>
                    : National Oceanic and Atmospheric Administration (NOAA).
                </P>
                <P>Title: Scup Gear Restricted Area (GRA) Access Program Authorization.</P>
                <P>
                    <E T="03">Form Number(s)</E>
                    : None.
                </P>
                <P>
                    <E T="03">OMB Approval Number</E>
                    : 0648-0469.
                </P>
                <P>
                    <E T="03">Type of Request</E>
                    : Emergency submission.
                </P>
                <P>
                    <E T="03">Burden Hours</E>
                    : 887.
                </P>
                <P>
                    <E T="03">Number of Respondents</E>
                    : 72.
                </P>
                <P>
                    <E T="03">Average Hours Per Response:</E>
                     2 minutes for a telephone call to request a GRA authorization; 2 minutes for a notification call at least 5 days prior to a trip; 2 minutes for a transmission for declaring into a GRA when the vessel leaves port; 15 seconds per automated position report from a vessel monitoring system; and 10 minutes for a daily manual vessel monitoring system report of discards (including null reports).
                </P>
                <P>
                    <E T="03">Needs and Uses</E>
                    : This collection of information involves a number of requirements needed to manage the Scup GRA Access Program. The information will be used for enforcement of regulations and for future analysis of the fishery.
                </P>
                <P>
                    <E T="03">Affected Public</E>
                    : Business or other for-profit organizations, and individuals or households.
                </P>
                <P>
                    <E T="03">Frequency</E>
                    : On occasion, daily, hourly.
                </P>
                <P>
                    <E T="03">Respondent's Obligation</E>
                    : Required to obtain or retain a benefit.
                </P>
                <P>
                    <E T="03">OMB Desk Officer</E>
                    : David Rostker, (202) 395-3897.
                </P>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Copies of the above information collection proposal can be obtained by calling or writing Diana Hynek, Departmental Paperwork Clearance Officer, (202) 482-0266, Department of Commerce, Room 6625, 14th and Constitution Avenue, NW, Washington, DC 20230 (or via the Internet at 
                    <E T="03">dHynek@doc.gov</E>
                    ).
                </P>
                <P>
                    Written comments and recommendations for the proposed information collection should be sent within December 19, 2003 to David Rostker, OMB Desk Officer, FAX number (202) 395-7285, or 
                    <E T="03">David_Rostker@omb.eop.gov</E>
                    .
                </P>
                <SIG>
                    <DATED>Dated: November 26, 2003.</DATED>
                    <NAME>Gwellnar Banks,</NAME>
                    <TITLE>Management Analyst, Office of the Chief Information Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30285 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <DEPDOC>[I.D. 120203B]</DEPDOC>
                <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
                <P>The Department of Commerce has submitted to the Office of  Management and Budget (OMB) for clearance the following proposal for collection of information under the provisions of the Paperwork  Reduction Act (44 U.S.C. Chapter 35).</P>
                <P>
                    <E T="03">Agency:</E>
                     National Oceanic and Atmospheric Administration (NOAA).
                </P>
                <P>
                    <E T="03">Title:</E>
                     Human Dimensions of Marine Resource Management.
                </P>
                <P>
                    <E T="03">Form Number(s):</E>
                     None.
                </P>
                <P>
                    <E T="03">OMB Approval Number:</E>
                     None.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Regular submission.
                </P>
                <P>
                    <E T="03">Burden Hours:</E>
                     3,000.
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     4,800.
                </P>
                <P>
                    <E T="03">Average Hours Per Response:</E>
                     0.625.
                </P>
                <P>
                    <E T="03">Needs and Uses:</E>
                     This request is for a generic clearance for social science research related to the human dimensions of the utilization of living marine resources.  This process has been initiated in order to expedite the approval process for future specific data collections.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Individuals or households; business or other for-profit organizations; not-for-profit institutions; Federal government; and State, Local, or Tribal Government.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     On occasion.
                </P>
                <P>
                    <E T="03">Respondent's Obligation:</E>
                     Voluntary.
                </P>
                <P>
                    <E T="03">OMB Desk Officer:</E>
                     David Rostker, (202) 395-3897.
                </P>
                <P>
                    Copies of the above information collection proposal can be obtained by calling or writing Diana Hynek, Departmental Paperwork Clearance Officer,  (202) 482-0266, Department of Commerce, Room 6625, 14th and Constitution Avenue, NW, Washington, DC 20230 (or via the Internet at 
                    <E T="03">dHynek@doc.gov</E>
                    ).
                </P>
                <P>
                    Written comments and recommendations for the proposed information collection should be sent within 30 days of publication of this notice to David Rostker, OMB Desk Officer, FAX number 202-395-7285, or 
                    <E T="03">David_Rostker@omb.eop.gov</E>
                    .
                </P>
                <SIG>
                    <DATED>Dated: November 26, 2003.</DATED>
                    <NAME>Gwellnar Banks,</NAME>
                    <TITLE>Management Analyst, Office of the Chief Information Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30286 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-22-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE </AGENCY>
                <SUBAGY>Census Bureau </SUBAGY>
                <SUBJECT>Construction Progress Reporting Surveys (CPRS) </SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed collection; comment request.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of Commerce, as part of its continuing effort to reduce paperwork and respondent burden, invites the general public and other Federal agencies to take this opportunity to comment on proposed and/or continuing information collections, as required by the Paperwork Reduction Act of 1995, Public Law 104-13 (44 U.S.C. 3506(c)(2)(A)). </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments must be submitted on or before February 3, 2004. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Direct all written comments to Diana Hynek, Departmental Paperwork Clearance Officer, Department of Commerce, Room 6625, 14th and Constitution Avenue, NW., Washington, DC 20230 (or via the Internet at 
                        <E T="03">dhynek@doc.gov</E>
                        ). 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Requests for additional information or copies of the information collection instrument(s) and instructions should be directed to Michael Davis, U.S. Census Bureau, Room 2125, FOB 4, Washington, DC 20233-6900, (301) 763-1605 (or via the Internet at 
                        <E T="03">michael.davis@census.gov</E>
                        ). 
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Abstract </HD>
                <P>
                    The Census Bureau plans to request a revision of a currently approved collection for forms C-700, Private Construction Projects; C-700(R), Multifamily Residential Projects; and C-700(SL), State and Local Government Projects. These forms are used to conduct the Construction Progress Reporting Surveys (CPRS) to collect information on the dollar value of construction put in place by private 
                    <PRTPAGE P="68027"/>
                    companies, individuals, private multifamily residential buildings, and state and local governments. Due to the significant growth in construction activity during the past few years and in order to facilitate the publication of construction spending data in more detail by new types of construction, we plan to increase the number of respondents/projects. 
                </P>
                <P>The Census Bureau is the preeminent collector and provider of timely, relevant and quality data about the people and economy of the United States. Economic data are the Census Bureau's primary program commitment during nondecennial census years. The Form C-700, Private Construction Projects collects construction put in place data for nonresidential projects owned by private companies or individuals. The Form C-700(R), Multifamily Residential Projects collects construction put in place data for private multifamily residential buildings. Form C-700(SL), State and Local Government Projects, collects construction put in place data for state and local government projects. </P>
                <P>The Census Bureau uses the information from these surveys to publish the value of construction put in place series. Published estimates are used by a variety of private business and trade associations to estimate the demand for building materials and to schedule production, distribution, and sales efforts. They also provide various governmental agencies with a tool to evaluate economic policy and to measure progress towards established goals. For example, Bureau of Economic Analysis staff use data to develop the construction components of gross private domestic investment in the gross domestic product. The Federal Reserve Board and the Department of Treasury use the value in place data to predict the gross domestic product, which is presented to the Board of Governors and has an impact on monetary policy. </P>
                <HD SOURCE="HD1">II. Method of Collection </HD>
                <P>An independent systematic sample of projects is selected each month according to predetermined sampling rates. Once a project is selected it remains in the sample until completion of the project. Preprinted forms are mailed monthly to respondents to fill in current month data and any revisions to previous months. Some respondents are later called by a Census interviewer and report the data over the phone. Having the information available from a database at the time of the interview greatly helps reduce the time respondents spend on the phone. Interviews are scheduled at the convenience of the respondent, further reducing their burden. </P>
                <HD SOURCE="HD1">III. Data </HD>
                <P>
                    <E T="03">OMB Number:</E>
                     0607-0153. 
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     C-700, C-700(R), C-700(SL). 
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Regular submission. 
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Individuals, businesses or other for profit, non profit institutions, small businesses or organizations, and State or local governments. 
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     C-700 = 8,500, C-700(R) = 2,500, C-700(SL) = 8,500, Total = 19,500. 
                </P>
                <P>
                    <E T="03">Estimated Time Per Response:</E>
                     15 minutes per month. 
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     C-700 = 25,500, C-700(R) = 7,500, C-700(SL) = 25,500, Total = 58,500. 
                </P>
                <P>
                    <E T="03">Estimated Total Annual Cost:</E>
                     3.5 million. 
                </P>
                <P>
                    <E T="03">Respondent's Obligation:</E>
                     Voluntary. 
                </P>
                <P>
                    <E T="03">Legal Authority:</E>
                     Title 13, United States Code, Section 182. 
                </P>
                <HD SOURCE="HD1">IV. Request for Comments </HD>
                <P>Comments are invited on: (a) Whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information shall have practical utility; (b) the accuracy of the agency's estimate of the burden (including hours and cost) of the proposed collection of information; (c) ways to enhance the quality, utility, and clarity of the information to be collected; and (d) ways to minimize the burden of the collection of information on respondents, including through the use of automated collection techniques or other forms of information technology. </P>
                <P>Comments submitted in response to this notice will be summarized and/or included in the request for OMB approval of this information collection; they also will become a matter of public record. </P>
                <SIG>
                    <DATED>Dated: December 1, 2003. </DATED>
                    <NAME>Madeleine Clayton, </NAME>
                    <TITLE>Management Analyst, Office of the Chief Information Officer. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30240 Filed 12-4-03; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 3510-07-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>Bureau of Industry and Security</SUBAGY>
                <SUBJECT>Short Supply Regulations, Unprocessed Western Red Cedar</SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Proposed collection; comment request.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Department of Commerce, as part of its continuing effort to reduce paperwork and respondent burden, invites the general public and other Federal agencies to take this opportunity to comment on proposed and/or continuing information collections, as required by the Paperwork Reduction Act of 1995, Public Law 104-13 (44 U.S.C. 3506(c)(2)(A)).</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments must be submitted on or before February 3, 2004.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Direct all written comments to Diana Hynek, Departmental Paperwork Clearance Officer, Department of Commerce, Office of the Chief Information Officer, 202-482-0266, Room 6625, 14th and Constitution Avenue, NW., Washington, DC 20230.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Requests for additional information or copies of the information collection instrument(s) and instructions should be directed to Marna Dove, BIS ICB Liaison, Department of Commerce, BIS Office of the Chief Information Officer, Room 6622, 14th and Constitution Avenue, NW., Washington, DC 20230.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. Abstract</HD>
                <P>The information is collected as supporting documentation for license applications to export western red cedar logs to enforce the Export Administration Act's prohibition against the export of such logs from state or Federal lands.</P>
                <HD SOURCE="HD1">II. Method of Collection</HD>
                <P>Written submission.</P>
                <HD SOURCE="HD1">III. Data</HD>
                <P>
                    <E T="03">OMB Number:</E>
                     0694-0025.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     BXA-748P.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Regular submission for extension of a currently approved collection.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Individuals, businesses or other for-profit and not-for-profit institutions.
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     35.
                </P>
                <P>
                    <E T="03">Estimated Time Per Response:</E>
                     30 to 105 minutes per response.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden Hours:</E>
                     36.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Cost:</E>
                     No start-up capital expenditures.
                </P>
                <HD SOURCE="HD1">IV. Request for Comments</HD>
                <P>
                    Comments are invited on: (a) Whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information shall have practical utility; (b) the accuracy of the 
                    <PRTPAGE P="68028"/>
                    agency's estimate of the burden (including hours and cost) of the proposed collection of information; (c) ways to enhance the quality, utility, and clarity of the information to be collected; and (d) ways to minimize the burden of the collection of information on respondents, including through the use of automated collection techniques or other forms of information technology.
                </P>
                <P>Comments submitted in response to this notice will be summarized and/or included in the request for OMB approval of this information collection; they will also become a matter of public record.</P>
                <SIG>
                    <DATED>Dated: December 1, 2002.</DATED>
                    <NAME>Madeleine Clayton,</NAME>
                    <TITLE>Management Analyst, Office of the Chief Information Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30239 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-33-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>International Trade Administration</SUBAGY>
                <DEPDOC>[A-570-848]</DEPDOC>
                <SUBJECT>Notice of Final Rescission of Antidumping Duty New Shipper Review:  Freshwater Crawfish Tail Meat from the People's Republic of China</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Import Administration, International Trade Administration, U.S. Department of Commerce.</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>On September 5, 2003, the Department published a preliminary intent to rescind the new shipper review of Zhoushan Huading Seafood Co., Ltd. (Zhoushan Huading) under the antidumping duty order on freshwater crawfish tail meat from the People's Republic of China (68 FR 52745).  The review covers one sale of the subject merchandise entered into the United States during the period September 1, 2001 through August 31, 2002.</P>
                    <P>
                        Based on our analysis of the record, including factual information obtained since the preliminary notice of intent to rescind, the Department has determined that Zhoushan Huading's new shipper sale is not 
                        <E T="03">bona fide</E>
                         and, as a result, we are rescinding this new shipper review. 
                        <E T="03">See</E>
                         “Rescission of New Shipper Review” section below.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P> December 5, 2003.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Douglas Kirby or Thomas Gilgunn, Office of AD/CVD Enforcement VII, Import Administration, International Trade Administration, U.S. Department of Commerce, 14th Street and Constitution Avenue, N.W., Washington D.C.  20230; telephone:  (202) 482-3782 or (202) 482-4236, respectively.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    We published the preliminary notice of intent to rescind this new shipper review on September 5, 2003. 
                    <E T="03">See Freshwater Crawfish Tail Meat From the People's Republic of China:  Preliminary Notice of Intent to Rescind New Shipper Administrative Review</E>
                    , 68 FR 52745 (
                    <E T="03">Preliminary Notice</E>
                    ).  In the 
                    <E T="03">Preliminary Notice</E>
                    , the Department found that the sale made by Zhoushan Huading in this new shipper review was not 
                    <E T="03">bona fide</E>
                     based on the following:  1) the price and quantity for Zhoushan Huading's sale of crawfish tail meat were atypical vis-a-vis other exports from the PRC of the subject merchandise into the United States during the period of review; 2) there were conflicting accounts as to who purchased the crawfish tail meat and who paid Zhoushan Huading for the shipment; 3) there remained uncertainty in regard to the commercial reasonableness of the sale; 4) there were inconsistencies in the terms of sale; and, 5) the Department was unable to establish that the importing parties were actual commercial entities. 
                    <E T="03">See also Memorandum to Barbara E. Tillman, Acting Deputy Assistant Secretary for Import Administration, Group III:   Freshwater Crawfish Tail Meat from the People's Republic of China:  Analysis of Zhoushan Huading's New Shipper Transaction</E>
                    , dated August 28, 2003 (
                    <E T="03">Zhoushan Huading Memo</E>
                    ).  A public version of this memorandum is on file in the Central Records Unit, room B-099 of the main Commerce Building.
                </P>
                <P>
                    On September 2, 2003, the Department issued a fourth supplemental questionnaire to Zhoushan Huading, and on September 3, 2003, issued supplemental questionnaires to both the reported buyer and the importer of record in order to clarify the terms of sale and payment documentation for the new shipper sale under review.  On September 12, 2003, Zhoushan Huading, the reported buyer, and the importer of record submitted their responses to the Department's supplemental questionnaires.  Their responses are discussed in the “Analysis of the 
                    <E T="03">Bona Fides</E>
                     of the New Shipper Sale” section below.
                </P>
                <HD SOURCE="HD1">Comments</HD>
                <P>
                    On October 6, 2003, petitioners
                    <FTREF/>
                    <SU>1</SU>
                     submitted comments.  On October 14, 2003, Zhoushan Huading submitted rebuttal comments.  The parties raised only one issue in their briefs:  “Whether The New Shipper Review of Zhoushan Huading Should Be Rescinded for Lack of a 
                    <E T="03">Bona Fide</E>
                     Sale.”  All arguments raised in the case and rebuttal briefs filed by parties to this new shipper review are addressed in the 
                    <E T="03">Issues and Decision Memorandum for the Final Rescission of the New Shipper Review of Freshwater Crawfish Tail Meat from the People's Republic of China for Zhoushan Huading Seafood Co., Ltd.</E>
                    , dated November 25, 2003 (
                    <E T="03">Decision Memo</E>
                    ), which is hereby adopted by this notice.  Parties can find a complete discussion of all issues raised in this review and the corresponding recommendation in this public memorandum, which is on file in the Central Records Unit, room B-099 of the main Commerce Building.  In addition, a complete version of the 
                    <E T="03">Decision Memo</E>
                     can be accessed directly on the internet at 
                    <E T="03">http://ia.ita.doc.gov</E>
                    .  The paper copy and electronic version of the 
                    <E T="03">Decision Memo</E>
                     are identical in content.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         The Crawfish Processors Alliance, its members (together with the Louisiana Department of Agriculture and Forestry and Bob Odom, Commissioner), and several individual crawfish producers, collectively called the Domestic Parties.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">Scope of the Antidumping Duty Order</HD>
                <P>The product covered by this order is freshwater crawfish tail meat, in all its forms (whether washed or with fat on, whether purged or unpurged), grades, and sizes; whether frozen, fresh, or chilled; and regardless of how it is packed, preserved, or prepared.  Excluded from the scope of the order are live crawfish and other whole crawfish, whether boiled, frozen, fresh, or chilled.  Also excluded are saltwater crawfish of any type, and parts thereof.  Freshwater crawfish tail meat is currently classifiable in the Harmonized Tariff Schedule of the United States (HTS) under item numbers 1605.40.10.10 and 1605.40.10.90, which are the new HTS numbers for prepared foodstuffs, indicating peeled crawfish tail meat and other, as introduced by U.S. Customs and Border Protection (CBP) in 2000, and HTS items 0306.19.00.10 and 0306.29.00, which are reserved for fish and crustaceans in general.  The HTS subheadings are provided for convenience and CBP purposes only.  The written description of the scope of this order is dispositive.</P>
                <HD SOURCE="HD1">
                    Analysis of the 
                    <E T="03">Bona Fides</E>
                     of the New Shipper Sale
                </HD>
                <P>
                    The Department has not acquired nor received any additional information that would alter our preliminary determination that the extremely high price and the unusually low quantity of 
                    <PRTPAGE P="68029"/>
                    Zhoushan Huading's new shipper sale were not consistent with other imports of freshwater crawfish tail meat entered into the U.S. during the period of review. 
                    <E T="03">See Preliminary Notice; see also Zhoushan Huading Memo</E>
                    .
                </P>
                <P>
                    Furthermore, since the publication of the 
                    <E T="03">Preliminary Notice</E>
                    , the Department solicited additional information through the issuance of supplemental questionnaires to all three parties that were involved in this new shipper sale.  The Department's goal in seeking additional information was to address the issues identified in the 
                    <E T="03">Preliminary Notice</E>
                    , particularly, who paid whom, and to seek clarification of the terms of sale for the shipment of subject merchandise under review.  All parties responded to the supplemental questionnaires issued.
                </P>
                <P>
                    In regard to payment information, both Zhoushan Huading and the reported buyer, in their questionnaire responses, provided documents demonstrating a wire transfer from the reported buyer to Zhoushan Huading.  Both responses also provide a copy of a cashier's check as evidence of payment by the importer of record to the reported buyer.  This documentation overcomes the uncertainty regarding who paid whom for the merchandise, and establishes that Zhoushan Huading was paid in the manner, and by the party, identified in the questionnaire responses.  However, this documentation also provides evidence that the sale was commercially unreasonable, due to the fact that the dollar amounts on the cashier's check and the wire transfer documentation are identical.  Therefore, since the amounts paid by the reported buyer and the importer of record are identical, the record indicates that the reported buyer sold Zhoushan Huading's shipment of subject merchandise to the importer of record at a loss, 
                    <E T="03">i.e.</E>
                    , by selling the subject merchandise for the exact same dollar amount as they purchased it for, the reported buyer must have absorbed all of the administrative and selling costs associated with executing both transactions (the purchase and the sale).
                </P>
                <P>
                    Moreover, prior to the publication of the 
                    <E T="03">Preliminary Notice</E>
                    , as part of our analysis of whether the sale was commercially reasonable, we issued supplemental questionnaires that asked the reported buyer and the importer of record to provide information on the commercial structure of their business, and their business relationship to each other.  The Department also attempted to gather information from the importer of record in regard to the identity of its customers and supporting sales documentation.  The Department also asked Zhoushan Huading for this information.  None of the requested information was provided by Zhoushan Huading, the reported buyer, or the importer of record.
                </P>
                <P>
                    In addition, Zhoushan Huading, in its September 12, 2003 supplemental questionnaire response, stated which party was responsible for all inland freight, brokerage and handling, and international freight expenses related to the new shipper sale under review.  However, the bill of lading provided by Zhoushan Huading in its January 6, 2003, questionnaire response contradicts the terms of sale as reported by Zhoushan Huading, and indicates that these costs may have been borne by a party other than the one Zhoushan Huading indicated.  As such, without reliable information establishing the terms of sale, including which party was responsible for which costs, it is not possible for the Department to determine that Zhoushan Huading's sale is a commercially reasonable transaction.  Some of the information concerning the party responsible for movement expenses is business proprietary.  This information is discussed more fully in a 
                    <E T="03">Memorandum to the File:  Crawfish Tail Meat from the People's Republic of China:  Analysis of Zhoushan Huading's Reported Terms of Sale;</E>
                     dated November 25, 2003.
                </P>
                <P>
                    Having reviewed the totality of circumstances surrounding this sale, we conclude that Zhoushan Huading's new shipper sale was commercially unreasonable and therefore not 
                    <E T="03">bona fide</E>
                     for the following reasons:   1) the price was extremely high and the quantity was unusually low vis-a-vis other imports from the PRC of the subject merchandise into the United States during the period of review; 2) the merchandise was apparently resold by the reported buyer at a loss; and, 3) Zhoushan Huading provided contradictory information and documentation regarding the terms of sale and movement expenses.
                </P>
                <HD SOURCE="HD1">Rescission of New Shipper Review</HD>
                <P>
                    Because we find the new shipper sale not 
                    <E T="03">bona fide</E>
                    , and because this was the only sale made during the new shipper review period, there is no 
                    <E T="03">bona fide</E>
                     sale to review.  As such, we are rescinding this new shipper review.  Accordingly, the PRC-wide antidumping duty margin of 223.01 percent still applies for  shipments of freshwater crawfish tail meat produced and/or exported by Zhoushan Huading for the period September 1, 2001 through August 31, 2002 and beyond.  The Department will issue cash deposit and assessment instructions directly to CBP.
                </P>
                <HD SOURCE="HD1">Cash Deposits</HD>
                <P>
                    Bonding will no longer be permitted to fulfill security requirements for shipments from Zhoushan Huading of freshwater crawfish tail meat from the PRC entered, or withdrawn from warehouse, for consumption in the United States on or after the publication of this notice in the 
                    <E T="04">Federal Register</E>
                    .  Effective upon publication of these final results for this new shipper review, we will instruct CBP to continue the suspension of liquidation of entries of freshwater crawfish tail meat that is produced and/or exported by Zhoushan Huading, and entered on or after the date of publication of these final results.  For entries of freshwater crawfish tail meat that are produced and/or exported by Zhoushan Huading, cash deposits will be required at the PRC-wide rate in effect on the date of entry.  The PRC-wide rate currently in effect is 223.01 percent.  There are no changes to the rates applicable to any other company under this order.
                </P>
                <HD SOURCE="HD1">Assessment of Antidumping Duties</HD>
                <P>The Department shall determine, and CBP shall assess, antidumping duties on all appropriate entries.  Since we are rescinding this new shipper review, the PRC-wide rate of 223.01 percent applies to all exports of freshwater crawfish tail meat produced and/or exported by Zhoushan Huading.  The Department will issue appropriate assessment instructions directly to CBP within 15 days of publication of this notice of rescission of antidumping duty new shipper review.</P>
                <HD SOURCE="HD1">Notification to Interested Parties</HD>
                <P>This notice serves as a final reminder to importers of their responsibility under 19 CFR 351.402(f) to file a certificate regarding the reimbursement of antidumping duties prior to liquidation of the relevant entries during this review period.  Failure to comply with this requirement could result in the Secretary's presumption that reimbursement of antidumping duties occurred and subsequent assessment of double antidumping duties.</P>
                <P>
                    This notice also serves as a reminder to parties subject to administrative protective order (APO) of their responsibility concerning the disposition of proprietary information disclosed under APO in accordance with section 351.305(a)(3) of the Department's regulations.  Timely written notification of the return/destruction of APO materials or conversion to judicial protective order is hereby requested.  Failure to comply 
                    <PRTPAGE P="68030"/>
                    with the regulations and the terms of an APO is a sanctionable violation.
                </P>
                <P>This new shipper review and notice are in accordance with sections 751(a)(2)(B) and 777(i)(1) of the Act.</P>
                <SIG>
                    <DATED>Dated: November 25, 2003.</DATED>
                    <NAME>James J. Jochum,</NAME>
                    <TITLE>Assistant Secretary Import Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30263 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>International Trade Administration</SUBAGY>
                <DEPDOC>[A-570-847]</DEPDOC>
                <SUBJECT>Persulfates from the People's Republic of China: Final Results of Antidumping Duty Administrative Review</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Import Administration, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of Final Results of Antidumping Duty Administrative Review.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>On July 31, 2003, the Department of Commerce published the preliminary results of the 2001-2002 administrative review of the antidumping duty order on persulfates from the People's Republic of China. This review covers one manufacturer/exporter of the subject merchandise to the United States. The merchandise covered by this order are persulfates, including ammonium, potassium, and sodium persulfates. The period of review is July 1, 2001, through June 30, 2002.</P>
                    <P>
                        Based on our analysis of the comments received, we have made certain changes in the margin calculations. 
                        <E T="03">See</E>
                         the section entitled “Changes Since the Preliminary Results” listed below. The final weighted-average dumping margin is listed below in the section entitled “Final Results of the Review.”
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>December 5, 2003.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mike Strollo or Greg Kalbaugh, AD/CVD Enforcement, Group I, Office 2, Import Administration, International Trade Administration, U.S. Department of Commerce, 14th Street and Constitution Avenue, N.W., Washington, D.C. 20230; telephone: (202) 482-0629 and (202) 482-3693, respectively.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On July 31, 2003, the Department published the preliminary results of the 2001-2002 administrative review of the antidumping duty order on persulfates from the People's Republic of China (PRC). 
                    <E T="03">See Persulfates from the People's Republic of China: Preliminary Results of Antidumping Duty Administrative Review, and Partial Rescission of Administrative Review</E>
                    , 68 FR 44921 (July 31, 2003) (
                    <E T="03">Preliminary Results</E>
                    ). This review covers one exporter, Shanghai Ai Jian Import &amp; Export Corporation (Ai Jian).
                </P>
                <P>We invited interested parties to comment on the preliminary results of review. The Department has conducted this administrative review in accordance with section 751 of the Tariff Act of 1930, as amended (the Act).</P>
                <HD SOURCE="HD1">Scope of Review</HD>
                <P>The products covered by this review are persulfates, including ammonium, potassium, and sodium persulfates. The chemical formula for these persulfates are, respectively, (NH4)2S2O8, K2S2O8, and Na2S2O8. Ammonium and potassium persulfates are currently classifiable under subheading 2833.40.60 of the Harmonized Tariff Schedule of the United States (HTSUS). Sodium persulfate is classifiable under HTSUS subheading 2833.40.20. Although the HTSUS subheadings are provided for convenience and customs purposes, the written description of the scope of this review is dispositive.</P>
                <HD SOURCE="HD1">Separate Rates</HD>
                <P>Ai Jian has requested a separate, company-specific antidumping duty rate. In our preliminary results, we found that Ai Jian had met the criteria for the application of a separate antidumping duty rate. See Preliminary Results, 68 FR at 44921. We have not received any other information since the preliminary results which would warrant reconsideration of our separate rates determination with respect to this company. We therefore determine that Ai Jian should be assigned an individual dumping margin in this administrative review.</P>
                <HD SOURCE="HD1">Analysis of Comments Received</HD>
                <P>All issues raised in the case briefs by parties to this administrative review are addressed in the “Issues and Decision Memorandum” (Decision Memo) from Jeffrey May, Deputy Assistant Secretary, Group I, to James Jochum, Assistant Secretary for Import Administration, dated November 28, 2003, which is adopted by this notice. A list of the issues which parties have raised and to which we have responded, all of which are in the Decision Memo, is attached to this notice as an Appendix. Parties can find a complete discussion of all issues raised in this review and the corresponding recommendations in this public memorandum, which is on file in the Central Records Unit in Room B-099 of the main Commerce Building.</P>
                <P>
                    In addition, a complete version of the Decision Memo can be accessed directly on the Web at 
                    <E T="03">http://ia.ita.doc.gov</E>
                    . The paper copy and electronic version of the Decision Memo are identical in content.
                </P>
                <HD SOURCE="HD1">Changes Since the Preliminary Results</HD>
                <P>For purposes of the final results, we have made certain changes in the margin calculation for Ai Jian. For a discussion of these changes, see the “Margin Calculations” section of the Decision Memo.</P>
                <FP SOURCE="FP1-2">• We removed a figure which was inadvertently included in the denominators of both the selling, general and administrative expense, and profit ratio calculations. See Comment 1 of the Decision Memo.</FP>
                <FP SOURCE="FP1-2">• We eliminated the purity adjustment applied to one of the inputs used by Ai Jian in the production of persulfates because Ai Jian failed to provide adequate support for that adjustment. See Comment 5 of the Decision Memo.</FP>
                <HD SOURCE="HD1">Final Results of the Review</HD>
                <P>We determine that the following percentage weighted-average margin exists for the period July 1, 2001 through June 30, 2002:</P>
                <GPOTABLE COLS="2" OPTS="L2,i1" CDEF="s80,10">
                    <BOXHD>
                        <CHED H="1">Manufacturer/exporter</CHED>
                        <CHED H="1">Margin</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Shanghai Ai Jian Import &amp; ­Export Corporation</ENT>
                        <ENT>0.00 percent</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Assessment Rates</HD>
                <P>
                    The Department will determine, and Customs and Border Protection (CBP) shall assess, antidumping duties on all appropriate entries. For assessment purposes, we do not have the information to calculate entered value because Ai Jian is not the importer of record for the subject merchandise. Accordingly, we have calculated customer-specific duty assessment rates for the merchandise in question by aggregating the dumping margins calculated for all U.S. sales to each customer and dividing this amount by the total quantity of those sales. To determine whether the duty assessment rates were 
                    <E T="03">de minimis</E>
                    , in accordance with the requirement set forth in 19 CFR 351.106(c)(2), we calculated customer-specific 
                    <E T="03">ad valorem</E>
                     ratios based on export prices. We will direct CBP to assess the resulting assessment rates uniformly on all entries of that particular customer made during the period of review. Pursuant to 19 CFR 351.106(c)(2), we will instruct CBP to liquidate without regard to antidumping 
                    <PRTPAGE P="68031"/>
                    duties any entries for which the assessment rate is 
                    <E T="03">de minimis</E>
                    . The Department will issue appropriate assessment instructions directly to CBP within 15 days of publication of these final results of review.
                </P>
                <HD SOURCE="HD1">Cash Deposit Requirements</HD>
                <P>The following deposit requirements will be effective upon publication of this notice of final results of this antidumping duty administrative review for all shipments of persulfates from the PRC entered, or withdrawn from warehouse, for consumption on or after the date of publication, as provided by section 751(a)(1) of the Act: (1) for Ai Jian, the cash deposit rate will be zero; (2) for previously reviewed or investigated companies not listed above that have separate rates, the cash deposit rate will continue to be the company-specific rate published for the most recent period; (3) the cash deposit rate for all other PRC exporters will be 119.02 percent, the PRC-wide rate established in the less than fair value investigation; and (4) the cash deposit rate for non-PRC exporters of subject merchandise from the PRC will be the rate applicable to the PRC supplier of that exporter.</P>
                <P>These deposit requirements shall remain in effect until publication of the final results of the next administrative review.</P>
                <P>This notice also serves as a final reminder to importers of their responsibility under 19 CFR 351.402(f) to file a certificate regarding the reimbursement of antidumping duties prior to liquidation of the relevant entries during this review period. Failure to comply with this requirement could result in the Secretary's presumption that reimbursement of antidumping duties occurred and the subsequent assessment of doubled antidumping duties.</P>
                <P>This notice serves as the only reminder to parties subject to administrative protective order (APO) of their responsibility concerning the disposition of proprietary information disclosed under APO in accordance with 19 CFR 351.305(a)(3). Timely written notification of return/destruction of APO materials or conversion to judicial protective order is hereby requested. Failure to comply with the regulations and the terms of an APO is a sanctionable violation.</P>
                <P>We are issuing and publishing this determination and notice in accordance with sections section 751(a)(1) and 777(i) of the Act.</P>
                <SIG>
                    <DATED>Dated: November 28, 2003.</DATED>
                    <NAME>James Jochum,</NAME>
                    <TITLE>Assistant Secretary for Import Administration.</TITLE>
                </SIG>
                <HD SOURCE="HD1">Appendix Issues in Decision Memo</HD>
                <FP>
                    <E T="03">Comment 1:</E>
                     Production Process of the Proposed Surrogate Producer and Whether National Peroxide Limited is a More Appropriate Surrogate Producer
                </FP>
                <FP>
                    <E T="03">Comment 2:</E>
                     Experience of Other Chemical Producers As Compared to that of the Proposed Surrogate Producer
                </FP>
                <FP>
                    <E T="03">Comment 3:</E>
                     Whether the Proposed Surrogate's Receipt of Government Subsidies Distorts Its SG&amp;A Ratio
                </FP>
                <FP>
                    <E T="03">Comment 4:</E>
                     Reported Scope of the Proposed Surrogate's Business
                </FP>
                <FP>
                    <E T="03">Comment 5:</E>
                     Whether to Apply a Specificity Ratio to one of Ai Jian's Factor Input Usage
                </FP>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30259 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>International Trade Administration</SUBAGY>
                <DEPDOC>[A-570-847]</DEPDOC>
                <SUBJECT>Persulfates from the People's Republic of China: Notice of Final Results of Changed Circumstances Review</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Import Administration, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>December 5, 2003.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mike Strollo or Patrick Connolly at (202) 482-0629 or (202) 482-1779, respectively, Office of AD/CVD Enforcement, Office 2, Import Administration, International Trade Administration, U.S. Department of Commerce, 14th Street and Constitution Avenue, NW, Washington, DC 20230.</P>
                </FURINF>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>On October 10, 2003, the Department published a notice of preliminary results of changed circumstances review and preliminarily found that the factors of production of Degussa-AJ (Shanghai) Initiators Co., Ltd. (Degussa-AJ) had not changed substantially since Degussa AG's investment in Shanghai Ai Jian Reagent Works (AJ Works). Therefore, the Department determined at the preliminary results that it will consider in any relevant future revocation inquiry any administrative reviews in which Shanghai Ai Jian Import and Export Corporation (Ai Jian) procured its products exported to the United States from AJ Works. On October 14, 2003, the petitioner, FMC Corporation (FMC), submitted a case brief. After considering these comments, we continue to find that Degussa-AJ's factors of production have not changed substantially since Degussa AG's investment in AJ Works. As a result, the Department will consider in any future revocation inquiry any administrative reviews in which Ai Jian procured its products exported to the United States from AJ Works.</P>
                </SUM>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On October 10, 2003, the Department published in the 
                    <E T="04">Federal Register</E>
                     a notice of preliminary results of changed circumstances review for persulfates from the People's Republic of China (PRC). 
                    <E T="03">See Persulfates from the People's Republic of China: Notice of Preliminary Results of Changed Circumstances Review</E>
                    , 68 FR 58658 (Oct. 10, 2003). We gave interested parties 14 days to comment on our preliminary results. On October 24, 2003, FMC submitted a case brief. We received no other comments from interested parties on the Department's preliminary results.
                </P>
                <HD SOURCE="HD1">Scope of Review</HD>
                <P>
                    The products covered by this review are persulfates, including ammonium, potassium, and sodium persulfates. The chemical formula for these persulfates are, respectively, (NH4)2S2O8, K2S2O8, and Na2S2O8. Potassium persulfates are currently classifiable under subheading 2833.40.10 of the 
                    <E T="03">Harmonized Tariff Schedule of the United States</E>
                     (HTSUS). Sodium persulfates are classifiable under HTSUS subheading 2833.40.20. Ammonium and other persulfates are classifiable under HTSUS subheadings 2833.40.50 and 2833.40.60. Although the HTSUS subheadings are provided for convenience and customs purposes, the written description of the scope of this review is dispositive.
                </P>
                <HD SOURCE="HD1">Analysis of Comments Received</HD>
                <P>All issues raised in the case briefs by parties to this changed circumstances review are addressed in the “Issues and Decision Memorandum” (Decision Memo) from Jeffrey May, Deputy Assistant Secretary, Group I, to James Jochum, Assistant Secretary for Import Administration, dated November 28, 2003, which is adopted by this notice. A list of the issues which parties have raised and to which we have responded, all of which are in the Decision Memo, is attached to this notice as an Appendix. Parties can find a complete discussion of all issues raised in this review and the corresponding recommendations in this public memorandum, which is on file in the Central Records Unit in Room B-099 of the main Commerce Building.</P>
                <PRTPAGE P="68032"/>
                <P>
                    In addition, a complete version of the Decision Memo can be accessed directly on the Web at 
                    <E T="03">http://ia.ita.doc.gov</E>
                    . The paper copy and electronic version of the Decision Memo are identical in content.
                </P>
                <HD SOURCE="HD1">Final Results</HD>
                <P>After our analysis of the comments received, we determine that Degussa-AJ's factors of production have not changed substantially since Degussa AG's investment in AJ Works. As a result, the Department will consider in any relevant future revocation inquiry any administrative reviews in which Ai Jian procured its products exported to the United States from AJ Works.</P>
                <P>This notice is published in accordance with sections 751(b)(1) and (d) and 777(i) of the Act, and with 19 CFR 351.221(c)(3).</P>
                <SIG>
                    <DATED>Dated: November 28, 2003.</DATED>
                    <NAME>James J. Jochum,</NAME>
                    <TITLE>Assistant Secretary for Import Administration.</TITLE>
                </SIG>
                <HD SOURCE="HD1">Appendix—Issues in Decision Memo</HD>
                <FP>
                    <E T="03">Comment 1:</E>
                     Whether the Department Must Make a Successor-in-Interest Determination in this Changed Circumstances Review
                </FP>
                <FP>
                    <E T="03">Comment 2:</E>
                     Whether Ai Jian May Use Reviews In Which it Sourced its Merchandise from AJ Works to Support a Revocation Request
                </FP>
                <FP>
                    <E T="03">Comment 3:</E>
                     Whether Ai Jian is Subject to a Combination Antidumping Duty Rate Based on the Exporter-Producer Combination of Ai Jian and AJ Works
                </FP>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30260 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>International Trade Administration</SUBAGY>
                <DEPDOC>[A-489-813]</DEPDOC>
                <SUBJECT>Notice of Initiation of Antidumping Investigation:  Certain Processed Hazelnuts from Turkey</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Import Administration, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P> December 5, 2003.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>John Drury at (202) 482-0195, Michael Ferrier at (202) 482-1394, or Abdelali Elouaradia at (202) 482-1374, Import Administration, International Trade Administration, U.S. Department of Commerce, 14th Street and Constitution Avenue, NW., Washington, DC 20230.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">The Petition</HD>
                <P>
                    On October 21, 2003, the Department of Commerce (“Department”) received an antidumping duty petition (“Petition”) filed in proper form by Westnut LLC, Northwest Hazelnut Company, Hazelnut Growers of Oregon, Willamette Filbert Growers, Evergreen Orchards, and Evonuk Orchards (“Petitioners”).  Petitioners are domestic producers of certain processed hazelnuts (“hazelnuts”).  On October 28, 2003, and October 29, 2003 inclusive, Petitioners submitted information to supplement the Petition (“First Petition Amendment”).  Additionally, on October 30, 2003, counsel for the Petitioners met with Department officials, at which time Department officials notified Petitioners that the Petition to date was insufficient. 
                    <E T="03">See Memorandum to the File from John Drury, Case Analyst:  Ex-parte meeting with Counsel for Petitioners</E>
                    , dated October 31, 2003.  On November 4, 2003, Petitioners submitted further information to supplement the Petition (“Second Petition Amendment”).  On November 24, 2003, Petitioners submitted additional information to supplement their Petition at the request of the Department (“Third Petition Amendment”).  On November 10, 2003, and November 26, 2003, the Istanbul Hazelnut and Hazelnut Products Exporters Union and the Black Sea Hazelnut and Hazelnut Products Exporters Union filed comments regarding industry support.  On November 28, 2003, Petitioners filed additional comments regarding industry support.  In accordance with section 732(b) of the Tariff Act of 1930, as amended (“the Act”), Petitioners allege imports of certain processed hazelnuts from Turkey are being, or are likely to be, sold in the United States at less than fair value within the meaning of section 731 of the Act, and that such imports are materially injuring, or threatening material injury to, the U.S. industry.
                </P>
                <P>
                    The Department finds that Petitioners filed their Petition on behalf of the domestic industry because they are interested parties as defined in section 771(9)(C) of the Act, and they have demonstrated sufficient industry support with respect to the investigation they are presently seeking. 
                    <E T="03">See Determination of Industry Support for the Petition</E>
                     section below.
                </P>
                <HD SOURCE="HD1">Scope of the Investigation</HD>
                <P>The scope of this investigation covers certain processed hazelnuts, including kernels, and kernels that have been roasted, blanched, sliced, diced, chopped, or in the following other forms:   paste, meal, flour, croquant, and butter.  In-shell hazelnuts are excluded from the scope of the order.</P>
                <P>The merchandise subject to this investigation is classified in the Harmonized Tariff Schedule of the United States (“HTSUS”) at subheadings 0802.22 and 2008.19.2000.  The tariff classifications are provided for convenience and Customs purposes; however, the written description of the scope of these investigations is dispositive.</P>
                <P>
                    As discussed in the preamble to the Department's regulations, we are setting aside a period for parties to raise issues regarding the scope of the investigation. 
                    <E T="03">See Antidumping Duties; Countervailing Duties; Final Rule</E>
                    , 62 FR 27296, 27323 (May 19, 1997).  The Department encourages all interested parties to submit such comments within 20 days of publication of this notice.  Comments should be addressed to Import Administration's Central Records Unit, Room 1870, U.S. Department of Commerce, 14th Street and Constitution Avenue NW., Washington, DC 20230.  This period of scope consultations is intended to provide the Department with ample opportunity to consider all comments and consult with parties prior to the issuance of the preliminary determination.
                </P>
                <HD SOURCE="HD1">Determination of Industry Support for the Petition</HD>
                <P>Section 732(b)(1) of the Act requires that a petition be filed on behalf of the domestic industry.  Section 732(c)(4)(A) of the Act provides that the Department's industry support determination, which is to be made before the initiation of the investigation, be based on whether a minimum percentage of the relevant industry supports the petition.  A petition meets this requirement if the domestic producers or workers who support the petition account for:  (i) at least 25 percent of the total production of the domestic like product; and (ii) more than 50 percent of the production of the domestic like product produced by that portion of the industry expressing support for, or opposition to, the petition.  Moreover, section 732(c)(4)(D) of the Act provides that, if the petition does not establish support of domestic producers or workers accounting for more than 50 percent of the total production of the domestic like product, the Department shall:  (i) poll the industry or rely on other information in order to determine if there is support for the petition, as required by subparagraph (A), or (ii) determine industry support using a statistically valid sampling method.</P>
                <P>
                    Section 771(4)(A) of the Act defines the “industry” as the producers of a domestic like product.  Thus, to determine whether a petition has the requisite industry support, the statute 
                    <PRTPAGE P="68033"/>
                    directs the Department to look to producers and workers who produce the domestic like product. The International Trade Commission (“ITC”), which is responsible for determining whether “the domestic industry” has been injured, must also determine what constitutes a domestic like product in order to define the industry.  While both the Department and the ITC must apply the same statutory definition regarding the domestic like product (section 771(10) of the Act), they do so for different purposes and pursuant to a separate and distinct authority.  In addition, the Department's determination is subject to limitations of time and information.  Although this may result in different definitions of the like product, such differences do not render the decision of either agency contrary to law. 
                    <E T="03">See USEC, Inc. v. United States</E>
                    , 132 F. Supp. 2d 1, 8 (Ct. Int'l Trade 2001), citing 
                    <E T="03">Algoma Steel Corp. Ltd. v. United States</E>
                    , 688 F. Supp. 639, 642-44 (Ct. Int'l Trade 1988).
                </P>
                <P>
                    Section 771(10) of the Act defines the domestic like product as “a product which is like, or in the absence of like, most similar in characteristics and uses with, the article subject to an investigation under this title.”  Thus, the reference point from which the domestic like product analysis begins is “the article subject to an investigation,” 
                    <E T="03">i.e.</E>
                    , the class or kind of merchandise to be investigated, which normally will be the scope as defined in the Petition.
                </P>
                <P>
                    Moreover, the Petitioners do not offer a definition of domestic like product distinct from the scope of the investigation.  The Petition covers certain processed hazelnuts as defined in the Scope of the Investigation section, above, and it constitutes a single class or kind of merchandise.  The Department has no basis on the record to find the Petitioners' definition of the domestic like product to be inaccurate.  The Department, therefore, has adopted the domestic like product definition set forth in the Petition. 
                    <E T="03">See Antidumping Duty Investigation Initiation Checklist</E>
                     (“
                    <E T="03">Initiation Checklist</E>
                    ”).
                </P>
                <P>
                    Based on the Petition data, the share of total estimated U.S. production of the domestic like product from October 2002 to September 2003 represented by Petitioners and the supporting domestic producers equal over 25 percent of total domestic production but less than 50 percent of production of the domestic like product produced by that portion of the industry expressing support for, or opposition to, the Petition. 
                    <E T="03">See Memorandum to the File from Richard O. Weible, Office Director, Group III, Office 8:  Antidumping Duty Petition on Certain Processed Hazelnuts from Turkey:   Extension of Deadline for Determining Industry Support</E>
                    , dated November 10, 2003.  Petitioners did not meet the 50 percent threshold with their Third Petition Amendment for industry support because there are other hazelnut processors in the United States who are not subject to the U.S. Department of Agriculture's federal marketing order for hazelnuts and source some or all of their supply of hazelnuts from imports.  Therefore, in accordance with Section 732(c)(4)(D), we polled the industry.  On November 12, 2003, the Department sent a letter to possible hazelnut processors requesting U.S. production data for the period October 2002 to September 2003.  This letter is on file in the Central Records Unit in room B-099 of the main Department of Commerce building and on the Import Administration website.  For a detailed summary of the Department's efforts to identify relevant companies, See Memorandum to the File regarding Procedures Used to Determine Industry Support, dated December 1, 2003.  Additionally, the Department published a notice in the 
                    <E T="04">Federal Register</E>
                     extending the twenty-day initiation and requesting production information from hazelnut processors in the United States (
                    <E T="03">See Notice of Request for Information and Extension of time for Initiation:  Antidumping Duty Petition on Certain Processed Hazelnuts from Turkey</E>
                    , (68 FR 64589) November 14, 2003.)  The Department has relied upon the responses to this letter and follow-up phone calls to clarify certain responses to determine industry support.  For the analysis of the data, 
                    <E T="03">See Initiation Checklist</E>
                    .  Our analysis of the data indicates that the domestic producers of processed hazelnuts who support the Petition account for more than 50 percent of the production of the domestic like product produced by that portion of the industry expressing support for, or opposition to, the Petition. 
                    <E T="03">See Initiation Checklist</E>
                    .
                </P>
                <P>Therefore, we find that the industry support requirements of section 732(c)(4)(A) of the Act have been met.</P>
                <HD SOURCE="HD1">Period of Investigation</HD>
                <P>The anticipated period of investigation (“POI”) will be October 1, 2002 through September 30, 2003.</P>
                <HD SOURCE="HD1">Export Price and Constructed Value</HD>
                <P>The following are descriptions of the allegations of sales at less than fair value upon which the Department based its decision to initiate this investigation.  The source or sources of data for the deductions and adjustments relating to U.S. and foreign market prices and cost of production (“COP”) and constructed value (“CV”) have been accorded treatment as business proprietary information.  Petitioner's sources and methodology are discussed in greater detail in the business proprietary version of the Petition and in our Initiation Checklist.  Should the need arise to use any of this information as facts available under section 776 of the Act in our preliminary or final determinations, we may re-examine this information and revise the margin calculations, if appropriate.</P>
                <HD SOURCE="HD1">Export Price</HD>
                <P>In calculating the U.S. price, the Petitioner relied upon actual sales during the POI of Turkish processed hazelnuts to the United States.  Petitioners provided sales invoices as support for their U.S. starting price.  To calculate a net price, Petitioners deducted the Turkish export tax on processed hazelnuts and movement expenses, which include ocean freight, marine insurance, and brokerage.  Petitioners calculated the export tax and the movement expenses from publically available data.</P>
                <HD SOURCE="HD1">Constructed Value</HD>
                <P>
                    Petitioners attempted to locate home market and third country prices of processed hazelnuts and outlined their efforts in the Third Petition Amendment.  Petitioners were unable to locate home market prices that occurred within the POI or prices of subject merchandise (
                    <E T="03">i.e.</E>
                    , shelled hazelnuts).  Petitioners located prices of Turkish processed hazelnuts to Germany and provided information demonstrating reasonable grounds to believe or suspect that sales of processed hazelnuts in the German third county market were made at prices below the fully absorbed cost of production (COP), within the meaning of section 773(b) of the Act, and requested that the Department initiate a country-wide sales-below-cost investigation. 
                    <E T="03">See Memorandum to the File from Steve Williams, Import Analyst, Office of Policy:  Telephone call with Pete Koenig regarding antidumping duty petition of Certain Processed Hazelnuts from Turkey</E>
                    , dated December 01, 2003.  Therefore, pursuant to sections 773(a)(4), 773(b) and 773(e) of the Act, the Petitioners based normal value for sales in Turkey on CV.  The Petitioners calculated CV using the cost of manufacturing, depreciation, selling, general and administrative expenses, and interest expense figures.  Consistent with section 773(e)(2) of the Act, the Petitioners included in CV an amount for profit.  For profit, the Petitioners relied upon amounts reported in a publicly available document.
                </P>
                <PRTPAGE P="68034"/>
                <P>
                    Pursuant to section 773(b)(3) of the Act, COP consists of cost of manufacturing, selling, general and administrative expenses, and packing.  The Petitioners calculated COM based on publicly available information and their own production experience, adjusted for known differences between costs incurred to produce processed hazelnuts in the United States and Turkey using publicly available data.  To calculate SG&amp;A and interest expense, the Petitioners were unable to obtain the financial statements of a Turkish hazelnut processor and therefore relied upon publicly available information for marketing and financing costs and their experience during the POI for general and administrative costs.  Based upon a comparison of the price of the foreign like product in the third-country market, Germany, to the calculated COP of the product, we find reasonable grounds to believe or suspect that sales of the foreign like product were made below the COP, within the meaning of section 773(b)(2)(A)(i) of the Act.  Accordingly, the Department is initiating a country-wide cost investigation relating to third-country sales to Germany.  We note, however, that if we determine that the home market (
                    <E T="03">i.e.</E>
                    , Turkey) is viable, our initiation of a country-wide cost investigation with respect to sales to Germany will be rendered moot.
                </P>
                <P>
                    Based upon the comparison of CV to EP, the Petitioners' calculated estimated dumping margin is 31.80 percent (
                    <E T="03">See Initiation Checklist</E>
                    ).
                </P>
                <HD SOURCE="HD1">Fair Value Comparisons</HD>
                <P>Based on the data provided by Petitioners, there is reason to believe imports of certain processed hazelnuts from Turkey are being, or are likely to be, sold at less than fair value.</P>
                <HD SOURCE="HD1">Allegations and Evidence of Material Injury and Causation</HD>
                <P>Petitioners allege that the U.S. industry producing the domestic like product is being materially injured, or threatened with material injury, by reason of the individual and cumulated imports of the subject merchandise sold at less than NV.</P>
                <P>
                    Petitioners contend that the industry's injured condition is evident in examining reduced production, shipments and net income, decreased employment, declining kernel prices, and lost sales and revenue. 
                    <E T="03">See Petition</E>
                     at pages 23-31.  Petitioners assert its share of the market has declined from 2000 to 2002. 
                    <E T="03">See Petition</E>
                     at page 26.  For a full discussion of the allegations and evidence of material injury, 
                    <E T="03">See Initiation Checklist</E>
                     at Attachment II.
                </P>
                <HD SOURCE="HD1">Initiation of Antidumping Investigation</HD>
                <P>Based on our examination of the Petition covering certain processed hazelnuts, we find it meets the requirements of section 732 of the Act.  Therefore, we are initiating an antidumping duty investigation to determine whether imports of certain processed hazelnuts from Turkey are being, or are likely to be, sold in the United States at less than normal value.  Unless this deadline is extended pursuant to section 733(b)(1)(A) of the Act, we will make our preliminary determinations no later than 140 days after the date of this initiation, or April 19, 2004.</P>
                <HD SOURCE="HD1">Distribution of Copies of the Petition</HD>
                <P>In accordance with section 732(b)(3)(A) of the Act, a copy of the public version of the Petition has been provided to representatives of the government of Turkey.</P>
                <HD SOURCE="HD1">International Trade Commission Notification</HD>
                <P>The ITC will preliminarily determine on December 10, 2003, whether there is reasonable indication that imports of certain processed hazelnuts from Turkey are causing, or threatening,  material injury to a U.S. industry.  A negative ITC determination will result in the investigation being terminated; otherwise, this investigation will proceed according to statutory and regulatory time limits.</P>
                <P>This notice is issued and published pursuant to section 777(i) of the Act.</P>
                <SIG>
                    <DATED>Date: December 1, 2003.</DATED>
                    <NAME>James J. Jochum,</NAME>
                    <TITLE>Assistant Secretary for Import Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30261 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>International Trade Administration</SUBAGY>
                <DEPDOC>[C-475-819]</DEPDOC>
                <SUBJECT>Certain Pasta from Italy:  Notice of Rescission of Countervailing Duty New Shipper Review</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Import Administration, International Trade Administration, Department of Commerce.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of Rescission of Countervailing Duty New Shipper Review.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        On March 5, 2003, the Department of Commerce published in the 
                        <E T="04">Federal Register</E>
                         (68 FR 10446) a notice announcing the initiation of a new shipper review of the countervailing duty order on certain pasta from Italy, covering the time period January 1, 2002 through December 31, 2002.  On March 24, 2003, the Department published a corrected notice of initiation in the 
                        <E T="04">Federal Register</E>
                         (68 FR 14198).  We are now rescinding this new shipper review.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>December 5, 2003.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Daniel J. Alexy or John Brinkmann, AD/CVD Enforcement, Group I, Office 1, Import Administration, U.S. Department of Commerce, 14th Street and Constitution Avenue NW., Washington, DC 20230; telephone (202) 482-1540 or 482-4126, respectively.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>On December 17, 2002, the Department of Commerce (the “Department”) received a request from Pastificio Carmine Russo S.p.A. (“Pastificio Russo”), made pursuant to section 751(a)(2)(B) of the Tariff Act of 1930, as amended (the “Act”) and 19 CFR §351.214(b), to conduct a new shipper review of the countervailing duty order on certain pasta from Italy, which was issued on July 24, 1996 (61 FR 38544).  On February 24, 2003, the Department received submissions from Pastificio Russo containing additional information.</P>
                <P>
                    In accordance with section 751(a)(2)(B) of the Act and 19 CFR §351.214, on February 27, 2003,  the Department initiated a countervailing duty new shipper review for certain pasta from Italy, covering calendar year 2002. 
                    <E T="03">See Certain Pasta from Italy:  Notice of Initiation of Countervailing Duty New Shipper Review</E>
                    , 68 FR 10446 (March 5, 2003).  Corrections to the initiation notice were published in the 
                    <E T="04">Federal Register</E>
                     on March 24, 2003 (
                    <E T="03">See</E>
                     68 FR 14198).  On August 29, 2003, the Department extended the time limit for the publication of the preliminary results in the new shipper review. 
                    <E T="03">See Certain Pasta From Italy:  Notice of Extension of Time Limit for Countervailing Duty New Shipper Review</E>
                    , 68 FR 51965 (August 29, 2003).
                </P>
                <P>
                    On August 22, 2003, the Department, after receiving a timely request from Pastificio Russo pursuant to 19 CFR §351.213(b)(2), initiated an administrative review covering calendar year 2002 for that company. 
                    <E T="03">See Notice of Initiation of Antidumping and Countervailing Duty Administrative Reviews and Requests for Revocation in Part</E>
                    , 68 FR 50750 (August 22, 2003).  Accordingly, parallel reviews covering the same period of review were initiated 
                    <PRTPAGE P="68035"/>
                    under 19 CFR §351.214 (new shipper review) and 19 CFR §351.213 (administrative review).
                </P>
                <HD SOURCE="HD1">Rescission of New Shipper Review</HD>
                <P>Section 351.214(j)(1) of the Department's regulations authorizes the Department to rescind a new shipper review where: (1) the producer or exporter's merchandise is also being covered by an administrative review under section 351.213, and; (2) the Department consults with the exporter or producer.</P>
                <P>
                    As noted, concurrent reviews of Pasificio Russo were initiated by the Department.  The Department also consulted with Pastificio Russo concerning the rescission of the new shipper review. The Department typically does not conduct parallel reviews covering the same period of review, and in this case, the Department preferred proceeding under the administrative review. 
                    <E T="03">See</E>
                     Memorandum to File from Senior Office Director Susan Kuhbach, dated November 5, 2003, “Ex Parte Conversation with counsel for Pastificio Carmine Russo, S.p.A.,” which is on file in the Central Records Unit in room B-099 of the main Department building.  Accordingly, we are rescinding the new shipper review and proceeding with the administrative review.
                </P>
                <HD SOURCE="HD1">Notification</HD>
                <P>
                    The Department will notify U.S. Customs and Border Protection (Customs) that bonding is no longer permitted to fulfill security requirements for shipments from Pastificio Russo entered, or withdrawn from warehouse, for consumption in the United States on or after the publication of this rescission notice in the 
                    <E T="04">Federal Register</E>
                    , and that a cash deposit of 3.85 percent 
                    <E T="03">ad valorem</E>
                     should be collected for any entries exported by Pastificio Russo.
                </P>
                <P>We are publishing this notice of rescission in accordance with 19 CFR §351.214(f)(3).</P>
                <SIG>
                    <DATED>Dated: December 1, 2003.</DATED>
                    <NAME>Jeffrey May,</NAME>
                    <TITLE>Deputy Assistant Secretary for Import Administration.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30262 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-DS-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF COMMERCE</AGENCY>
                <SUBAGY>National Oceanic and Atmospheric Administration </SUBAGY>
                <SUBJECT>NOAA Research Draft Report; Request for Public Comment</SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability and request for public comment.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Office of Oceanic and Atmospheric Research (OAR), will post the NOAA Research Draft Report for public comment on December 15, 2003. The complete draft document will be posted on the National Oceanic and Atmospheric Administration (NOAA), Science Advisory Board (SAB) Web site at 
                        <E T="03">http://www.sab.noaa.gov/reports/review-draft.pdf</E>
                        . The panel is seeking public comment from all interested parties. This draft is being issued for comment only and is not intended for interim use. The Review Team will review the public comments received on the draft document. Suggested changes will be incorporated, where appropriate, in the final draft report.
                    </P>
                    <P>The 2003 House and Senate Appropriations Subcommittee Reports have language pertaining to the Office of Oceanic and Atmospheric Research. The report accompanying the House Commerce, Justice State (CJS) Appropriations Subcommittee mark states: “In recognition of current resource limitations the Committee is forced to operate within, the Committee directs NOAA to review the continued requirements for twelve separate laboratories, six of which are located in Boulder, Colorado. The Committee directs NOAA to submit a laboratory consolidation plan to the Committee by March 15, 2004.” The Senate report language states: “NOAA is directed to report to the Committee on Appropriations on the costs and benefits of breaking OAR up into its constituent parts and distributing those parts as desirable to the other line offices. The report should specifically address how the newly configured research sector will directly assist line offices in developing timely solutions to problems confronting NOAA now and in the next 5 years.”</P>
                    <P>
                        In response to the Congressional report language NOAA appointed an “Ad Hoc Review Team” (here called the NOAA Research Review Team), under the auspices of the Science Advisory Board (SAB) consisting of five members. The Review team will be disbanded once the review is completed and a final report issued. This panel is tasked with: (1) Conducting a review of OAR for the purpose of improving the effectiveness and efficiency of its research enterprise, (2) establishing if OAR is adequately linked to NOAA's service organizations (
                        <E T="03">i.e.</E>
                        , National Weather Service (NWS), National Environmental Satellite Data, and Information Service (NESDIS), National Marine Fisheries Service (NMFS), and the National Ocean Service (NOS)), (3) assessing if the research programs are relevant to the needs of these organizations. The team's recommendations will assist NOAA in responding to the language in the 2004 House and Senate CJS appropriation reports.
                    </P>
                    <P>
                        The NOAA Research Review Team will present its findings to the Science Advisory Board in two (2) reports. The draft of the first report will be posted on the Science Advisory Board Web site at: 
                        <E T="03">http://www.sab.noaa.gov/reports/review-draft.pdf</E>
                        , on December 15, 2003, for public comment. Public comments may be submitted from December 15, 2003, to January 14, 2004.
                    </P>
                    <P>NOAA welcomes all comments on the content of the report. We also ask that you comment on any inconsistencies within the report, and omissions of important topics or issues. For any shortcoming that you note in the draft, please propose specific remedies.</P>
                    <P>Please follow these instructions for preparing and submitting your review. Using the format guidance described below will facilitate the processing of reviewer comments and assure that your comments are appropriately considered. Please provide background information about yourself on the first page of your comments: your name(s), organization(s), area(s) of expertise, mailing address(es), telephone and fax numbers, email address(es). Overview comments on the section should follow your background information and should be numbered. Comments that are specific to particular pages, paragraphs or lines of the section should follow your overview comments and should identify the page numbers to which they apply. Please number all your pages (on the upper right hand of each page), and have your identifying information at the top of each page.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments on this draft document must be submitted by January 14, 2004.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The NOAA Research Review Team Report will be available on the SAB Web site at 
                        <E T="03">http://www.sab.noaa.gov/reports/review-draft.pdf</E>
                         on December 15, 2003.
                    </P>
                    <P>
                        All comments should be sent electronically to 
                        <E T="03">research.review@noaa.gov</E>
                        , or to NOAA Research, Science Advisory Board, c/o Ms. M. Whitcomb, Silver Spring Metro 
                        <PRTPAGE P="68036"/>
                        Center, Bldg. 3, Room 11558, 1315 East-West Highway, Silver Spring, Maryland 20910.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Ms. M. Whitcomb, Silver Spring Metro Center, Bldg. 3, Room 11558, 1315 East-West Highway, Silver Spring, Maryland 20910 (phone 301-713-2454 x 173), during normal business hours of 8 a.m. to 5 p.m. eastern time, Monday through Friday, or visit the SAB Web site at: 
                        <E T="03">http://www.sab.noaa.gov/reports/review_draft.pdf</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>None.</P>
                <SIG>
                    <NAME>Louisa Koch,</NAME>
                    <TITLE>Deputy Assistant Administrator, Office of Oceanic and Atmospheric Research.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-29888 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 3510-KD-U</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">CORPORATION FOR NATIONAL AND COMMUNITY SERVICE</AGENCY>
                <SUBJECT>Reinstatement With Change of a Previously Approved Collection for Which Approval Has Expired; Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Corporation for National and Community Service.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Corporation for National and Community Service (hereinafter the “Corporation”), as part of its continuing effort to reduce paperwork and respondent burden, conducts a pre-clearance consultation program to provide the general public and Federal agencies with an opportunity to comment on proposed and/or continuing collections of information in accordance with the Paperwork Reduction Act of 1995 (PRA95) (44 U.S.C. 3506(c)(2)(A)). This program helps to ensure that requested data can be provided in the desired format, reporting burden (time and financial resources) is minimized, collection instruments are clearly understood, and the impact of collection requirement on respondents can be properly assessed. This form is available in alternate formats. Individuals who use a telecommunications device for the deaf (TTY/TDD) may call (202) 606-5256 between the hours of 9 a.m. and 4:30 p.m. eastern time, Monday through Friday.</P>
                    <P>Currently, the Corporation is soliciting comments concerning the proposed revision of its National Senior Service Corps Project Progress Report (OMB Control Number 3045-0033). The previously approved Progress Report expired on August 31, 2003. However, on November 21, 2003, OMB approved a six month emergency extension and assigned a new expiration date of May 31, 2004.</P>
                    <P>This reinstatement with changes reflects the Corporation's intent to modify selected sections of the collection instrument to reflect changes in data considered “ore reporting” information to meet a variety of needs, including:</P>
                    <P>• Removing data elements no longer required after January 2004;</P>
                    <P>• Adding new data elements as needed to ensure information collection captures appropriate data for the Corporation's required performance measurement and other reporting.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Written comments must be submitted to the office listed in the 
                        <E T="02">ADDRESSES</E>
                         section by February 3, 2004.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>You may submit comments, identified by the title of the information collection activity, by any of the following methods:</P>
                    <P>(1) By mail sent to: Corporation for National and Community Service, National Senior Service Corps; Attention Ms. Angela Roberts, Senior Program Officer; Room 9305, 1201 New York Avenue, NW., Washington, DC 20525.</P>
                    <P>(2) By hand delivery or by courier to the Corporation's mailroom at Room 6010 at the mail address given in paragraph (1) above, between 9 a.m. and 4 p.m. Monday through Friday, except Federal holidays.</P>
                    <P>(3) By fax to: (202) 565-2743, Attention Ms. Angela Roberts, Senior Program Officer.</P>
                    <P>
                        (4) Electronically through the Corporation's e-mail address system: 
                        <E T="03">aroberts@cns.gov</E>
                        .
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Angela Roberts, (202) 606-5000, ext. 111.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P> </P>
                <HD SOURCE="HD1">Comment Request</HD>
                <P>The Corporation is particularly interested in comments which:</P>
                <P>• Evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the Corporation, including whether the information will have practical utility;</P>
                <P>• Evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used;</P>
                <P>• Enhance the quality, utility and clarity of the information to be collected; and</P>
                <P>
                    • Minimize the burden of the collection of information on those who are to respond, including the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, 
                    <E T="03">e.g.</E>
                    , permitting electronic submissions of responses.
                </P>
                <HD SOURCE="HD1">Background</HD>
                <P>The Progress Report (PPR) was designed to assure that National Service Corps (NSSC) grantees address and fulfill legislated program purposes, meet agency program management and grant requirements, and assess progress toward work plan objectives agreed upon in the granting of the award.</P>
                <HD SOURCE="HD1">Current Action</HD>
                <P>The Corporation seeks to reinstate the previously used PPR to: (a) Enhance data elements collected via this information collection tool; (b) migrate the paper version of the form to the Corporation's electronic grants management system, eGrants; and (c) establish reporting periods consistent with the Corporation's integrated grants management and reporting policies.</P>
                <P>The Corporation anticipates making available to all NSSC grantees an OMB approved revised PPR by April of 2004.</P>
                <P>The revised PPR will be used by NSSC grantees to report progress toward accomplishing work plan goals and objectives, reporting actual outcomes related to self-nominated performance measures meeting challenges encountered, describing significant activities, and requesting technical assistance. Submission requirements are proposed to be revised as follows:</P>
                <P>• Established multi-year NSSC grantees will submit the complete report semi-annually within 30 days of the end of their annual budget cycle.</P>
                <P>• New projects in their first year, new components of statewide projects, demonstrations, and projects experiencing problems or with substantial project revisions may, upon review and recommendations of project managers, submit the PPR quarterly.</P>
                <P>
                    <E T="03">Type of Review:</E>
                     Reinstatement With Change of a Previously Approved Collection for Which Approval Has Expired.
                </P>
                <P>
                    <E T="03">Agency:</E>
                     Corporation for National and Community Service.
                </P>
                <P>
                    <E T="03">Title:</E>
                     National Senior Services Corps Project Progress Report.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     3045-0033.
                </P>
                <P>
                    <E T="03">Agency Number:</E>
                     CNCS Form 1020.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     Sponsors of National Senior Service Corps grants.
                </P>
                <P>
                    <E T="03">Total Respondents:</E>
                     1,350.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     Semi-annual. It is estimated that 1,350 will respond semi-annually and 50 quarterly.
                </P>
                <P>
                    <E T="03">Average Time Per Response:</E>
                     8.7 hours.
                    <PRTPAGE P="68037"/>
                </P>
                <P>
                    <E T="03">Estimated Total Burden Hours:</E>
                     11, 000 hours.
                </P>
                <P>
                    <E T="03">Total Burden Cost (capital/startup):</E>
                     None.
                </P>
                <P>
                    <E T="03">Total Burden Cost (operating/maintenance):</E>
                     $2,000.
                </P>
                <P>Comments submitted in response to this notice will be summarized and/or included in the request for Office of Management and Budget approval of the information collection request; they will also become a matter of public record.</P>
                <SIG>
                    <DATED>Dated: December 1, 2003.</DATED>
                    <NAME>Tess Scannell,</NAME>
                    <TITLE>Director, National Senior Service Corps.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30228 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6050-$$-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">ENVIRONMENTAL PROTECTION AGENCY </AGENCY>
                <DEPDOC>[ER-FRL-6646-1] </DEPDOC>
                <SUBJECT>Environmental Impact Statements; Notice of Availability </SUBJECT>
                <P>
                    <E T="03">Responsible Agency:</E>
                     Office of Federal Activities, General Information (202) 564-7167 or 
                    <E T="03">http://www.epa.gov/compliance/nepa/.</E>
                </P>
                <FP SOURCE="FP-1">Weekly receipt of Environmental Impact Statements </FP>
                <FP SOURCE="FP-1">Filed November 24, 2003, through November 28, 2003</FP>
                <FP SOURCE="FP-1">Pursuant to 40 CFR 1506.9. </FP>
                <FP SOURCE="FP-1">
                    <E T="03">EIS No. 030542, Final EIS, HHS, MD,</E>
                     Integrated Research Facility (IRF) at Fort Detrick construction and operation, adjacent to existing U.S. Army Medical Research Institute of Infectious Diseases Facilities, City of Frederick, Frederick County, MD, Due: January 5, 2004, Contact: Ronald Wilson (301) 496-5037. 
                </FP>
                <FP SOURCE="FP-1">
                    <E T="03">EIS No. 030543, Final Supplement, BLM, NV,</E>
                     Millennium Expansion Project, new facilities construction and existed gold mining operations expansion, plan-of-operations approval, Winnemucca, Humboldt County, NV, Due: January 5, 2004, Contact: Jeff Johnson (775) 623-1500. 
                </FP>
                <FP SOURCE="FP-1">
                    <E T="03">EIS No. 030544, Draft EIS, AFS, AZ,</E>
                     Bar T Bar Anderson Springs allotment management plans, to authorize permitted livestock grazing for a 10-year period, Coconino National Forest, Mogollon Rim and Mormon Lake Ranger Districts, Coconino County, AZ, Due: January 20, 2004, Contact: Jerry Gonzales (928) 354-2216. 
                </FP>
                <FP SOURCE="FP-1">
                    <E T="03">EIS No. 030545, Final EIS, FRC, FL,</E>
                     Ocean Express Pipeline Project, construction, operation and maintenance of an interstate natural gas pipeline extending from the Exclusive Economic Zone (EEZ) boundary between the United States and the Bahamas, (Docket No. CP02-090-001-1) plan of operations approval, NPDES and U.S. Army COE section 10 and possible 404 permits, Broward County, FL, Due: January 5, 2004, Contact: Thomas Russo (866) 208-3372. 
                </FP>
                <SIG>
                    <DATED>Dated: December 2, 2003. </DATED>
                    <NAME>Joseph C. Montgomery, </NAME>
                    <TITLE>Director, NEPA Compliance Division, Office of Federal Activities. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30273 Filed 12-4-03; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY </AGENCY>
                <DEPDOC>[ER-FRL-6646-2]</DEPDOC>
                <SUBJECT>Environmental Impact Statements and Regulations; Availability of EPA Comments </SUBJECT>
                <P>
                    Availability of EPA comments prepared pursuant to the Environmental Review Process (ERP), under section 309 of the Clean Air Act and section 102(2)(c) of the National Environmental Policy Act as amended. Requests for copies of EPA comments can be directed to the Office of Federal Activities at (202) 564-7167. An explanation of the ratings assigned to draft environmental impact statements (EISs) was published in the 
                    <E T="04">Federal Register</E>
                     dated April 4, 2003 (68 FR 16511). 
                </P>
                <HD SOURCE="HD1">Draft EISs </HD>
                <P>ERP No. D-AFS-F65044-MI Rating EC1, Baltimore Vegetative Management Project, implementation, Ottawa National Forest, Ontonagon Ranger District, Ontonagon County, MI. </P>
                <P>
                    <E T="03">Summary:</E>
                     EPA expressed environmental concerns with potential impacts to riparian areas and to the complexity of forest structure from fragmentation, management of early successional species and the control of invasives. The final EIS should address impacts from dispersed recreation to soil and water resources. EPA offered several suggested modifications the preferred alternative. 
                </P>
                <P>ERP No. D-AFS-J65391-WY Rating EC1, Blackhall-McAnulty Analysis Area, proposal to reduce the spread of Dwarf Mistletoe and Mountain Pine Beetle in Lodgepole Pine stands, Brush Creek/Hayden Ranger District, Medicine Bow-Routt National Forests and Thunder Basin National Grassland, Carbon County, WY. </P>
                <P>
                    <E T="03">Summary:</E>
                     EPA expressed environmental concerns with potential impacts to aquatic systems and resources, terrestrial habitat and soils. 
                </P>
                <P>ERP No. D-AFS-L65434-WA Rating EC1, Crupina Integrated Weed Management Project, control and eradication of Crupina, implementation, Okanogan and Wenatchee National Forests, Chelan Ranger District, Chelan County, WA. </P>
                <P>
                    <E T="03">Summary:</E>
                     EPA has environmental concerns and recommends that the FEIS provide an improved discussion and definition of suitable habitat for Crupina vulgaris, disclosure of Lake Chelan's potential role as a vector, and improve the document's cartographic information. 
                </P>
                <P>ERP No. D-BLM-K08027-NV Rating EC2, Tracy to Silver Lake Transmission Line Project, construction, operation and maintenance of a 120kV transmission line from Tracy Power Plant to new substations in the Spanish Spring Valley and Stead Areas, right-of-way application, Washoe County, NV. </P>
                <P>
                    <E T="03">Summary:</E>
                     EPA expressed environmental concerns with potential impacts to water quality, especially wetlands and aquatic resources, and air quality. The final EIS should adequate assess all jurisdictional waters, discuss minimization of impacts and mitigation if needed, as well as conformity and cumulative impacts to air quality.
                </P>
                <P>ERP No. D-FHW-F40416-00 Rating EC2, US 24 Transportation Improvements Project, I-469 in New Haven, Indiana to OH-15 in Defiance, OH, funding, NPDES permit and U.S. Army COE section 404 permit, Westernmost and Allen Counties, IN and Paulding and Defiance Counties, OH. </P>
                <P>
                    <E T="03">Summary:</E>
                     EPA has environmental concerns with the proposed project related to wetlands impacts and the need for more information on wetlands mitigation, and the impacts of runoff from roadways. 
                </P>
                <P>ERP No. D-IBR-K65259-CA Rating EC2, Pajaro Valley Water Management Agency (PVWMA) Revised Basin Management Plan Project, connection of PVWMA pipeline to the Santa Clara conduit of the Central Valley Project (CVP), Santa Cruz, Monterey and San Berito Counties, CA. </P>
                <P>
                    <E T="03">Summary:</E>
                     EPA expressed environmental concerns regarding the potential cumulative impacts to water quality and supply associated with this project and related projects in Pajaro Valley. EPA requested additional information related to water quality impacts, alternatives analysis, water conservation commitments, and environmental justice impacts. 
                </P>
                <HD SOURCE="HD1">Final EISs </HD>
                <P>
                    ERP No. F-AFS-L65428-ID, Twin Creek Timber Sale Project, proposal to 
                    <PRTPAGE P="68038"/>
                    cut and remove Lodgepole Pine sawtimber and road construction/reconstruction, Montpelier Ranger District, Caribou National Forest, U.S. Army Corps of Engineers permit, Bear Lake County, ID. 
                </P>
                <P>
                    <E T="03">Summary:</E>
                     No formal comment letter was sent to the preparing agency. 
                </P>
                <P>ERP No. F-BLM-J65374-WY, Snake River Resource Management Plan, BLM-administrated public land and resources allocation and management, Snake River, Jackson  Hole, Teton County, WY. </P>
                <P>
                    <E T="03">Summary:</E>
                     EPA supports BLM's decision to select the preferred alternative to transfer ownership of BLM-administered lands to other agencies. While this alternative has potential for minimal impacts to the environment, it contains uncertainties regarding the impacts to riparian areas and achieving management goals under future land-transfer agreements. 
                </P>
                <P>ERP No. F-BLM-K65241-CA, Headwaters Forest Reserve, Implementation  Resource Management Plan, long-term management plan and planning framework, located in the northwestern Coast Ranges near Humboldt Bay in Humboldt County, CA. </P>
                <P>
                    <E T="03">Summary:</E>
                     EPA expressed no objection to the proposed project. 
                </P>
                <P>ERP No. F-COE-E39061-MS,  Royal D'Iberville Hotel and Casino Development  Project, construction and operation, U.S. Army  COE section 10 and 404 and NPDES permits issuance,  City of D'Iberville on the Back Bay, Mississippi  Gulf Coast, Harrison County, MS. </P>
                <P>
                    <E T="03">Summary:</E>
                     EPA has no significant environmental concerns regarding construction of this casino hotel complex if the mitigation is performed as noted. 
                </P>
                <P>ERP No. F-COE-G35022-TX, Gulf Intracoastal Waterway in the Laguna Madre, maintenance dredging from the JFK Causeway to the Old Queen Isabella Causeway, Nueces, Kleberg, Kenedy, Willacy and Cameron County, TX. </P>
                <P>
                    <E T="03">Summary:</E>
                     No formal comment letter was sent to the preparing agency. 
                </P>
                <P>ERP No. F-FAA-C51022-NJ, Atlantic City International Airport, air service improvements, economic development and efficiency and safety enhancements, airport layout plan approval, Atlantic County, NJ. </P>
                <P>
                    <E T="03">Summary:</E>
                     EPA has no concerns with the implementation of the proposed project. 
                </P>
                <P>ERP No. F-NRS-G36165-OK, Cavalry Creek Watershed supplemental plan for Floodwater Retarding Structure No. 6, Washita River Basin, Washita County, OK. </P>
                <P>
                    <E T="03">Summary:</E>
                     No formal comment letter was sent to the preparing agency. 
                </P>
                <SIG>
                    <DATED>Dated: December 2, 2003. </DATED>
                    <NAME>Joseph C. Montgomery, </NAME>
                    <TITLE>Director, NEPA Compliance Division, Office of Federal Activities. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30274 Filed 12-4-03; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <DEPDOC>[FRL-7594-7]</DEPDOC>
                <SUBJECT>Notice of Public Meeting of the National Environmental Education Advisory Council</SUBJECT>
                <P>Notice is hereby given that the National Environmental Education Advisory Council established under section 9 of the National Environmental Education Act of 1990 (the Act), will hold a public meeting on January 22 and 23, 2004. The meeting will take place 1200 Pennsylvania Ave., NW., Washington, DC from 9 a.m. to 5 p.m. on Thursday, January 22 and Friday, January 23. The purpose of this meeting is to provide the Council with an opportunity to advise EPA's Office of Public Affairs (OPA) and the Office of Environmental Education (OEE) on its implementation of the Act. Members of the public are invited to attend and to submit written comments to EPA following the meeting.</P>
                <P>For additional information regarding the Council's upcoming meeting, please contact Ginger Potter, Office of Environmental Education (1704A), Office of Public Affairs, U.S. Environmental Protection Agency, 1200 Pennsylvania Avenue, NW., Washington, DC 20460 or call (202) 564-0453.</P>
                <SIG>
                    <DATED>Dated: December 3, 2003.</DATED>
                    <NAME>Ginger Potter,</NAME>
                    <TITLE>Designated Federal Official, National Environmental Education Advisory Council.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30268  Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <DEPDOC>[FRL-7595-2] </DEPDOC>
                <SUBJECT>Peer-Review Workshop on Time-Dependent Models and Technical Guidance Document Developed for Benchmark Dose Analysis of Neurobehavioral Toxicity Screening Data </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of a peer-review workshop and public meeting. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The U.S. Environmental Protection Agency (EPA) announces an expert peer-review workshop to review two time-dependent dose-response models and draft guidance for the application of these models to the assessment of data generated under EPA neurotoxicity screening test guidelines (63 FR 26926, May 14, 1998). Oak Ridge Institute for Science and Education (ORISE), an EPA contractor, will organize, convene, and conduct the peer-review workshop. </P>
                    <P>
                        The workshop will focus on application of the new statistical and dose-response methods represented by these models to neurotoxicity data, but applications of these methods to other toxicological data will also be discussed. The Splus® model programs and draft guidance document to be reviewed were developed for the EPA's National Center for Environmental Assessment (NCEA) and National Health and Environmental Effects Laboratory (NHEERL) by the University of South Florida. They are both available for download from the workshop's registration Web site, 
                        <E T="03">http://www.orau.gov/modelreview</E>
                        . 
                    </P>
                    <P>Though the primary purpose of the workshop is to receive comments and suggestions from the peer-review panel members, members of the public are invited to attend the workshop as observers and will be allowed to present brief verbal and/or written comments at the end of the workshop. NCEA and NHEERL will consider comments received at the workshop in preparing the software and a revised guidance document for later release to the public. </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The peer-review workshop will be held on Monday December 15, 2003 from 8:30 a.m. to 5 p.m. </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        The peer-review workshop will be held in Classroom C-112 of the U.S. Environmental Protection Agency, 109 T.W. Alexander Drive, Research Triangle Park, North Carolina 27709. Logistics and registration for the workshop are being arranged by ORISE, P.O. Box 117, Oak Ridge, TN 37831-0117. To attend the workshop, register by December 10, 2003, by going to the Web site at 
                        <E T="03">http://www.orau.gov/modelreview.</E>
                         Space is limited, and reservations will be accepted on a first-come, first-serve basis. 
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        The EPA's contractor, Leslie Shaphard of ORISE, should be contacted at telephone: (865) 241-5784 or e-mail: 
                        <E T="03">ShapardL@orau.gov</E>
                         for details pertaining to the workshop, registration, 
                        <PRTPAGE P="68039"/>
                        and logistics. For technical information contact: Jeff Gift, U.S. EPA, NCEA-RTP, B243-01, Research Triangle Park, NC 27711; telephone: 919-541-4828; facsimile: 919-541-0245; or e-mail: 
                        <E T="03">gift.jeff@epa.gov.</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The U.S. Environmental Protection Agency has supported the use of the benchmark dose (BMD) approach over the NOAEL/LOAEL approach for deriving reference doses for use in the risk assessment process. The software that is currently available at the EPA BMDS Web site (
                    <E T="03">http://www.epa.gov/ncea/bmds.htm</E>
                    ) does not allow for the modeling of data that are longitudinal in nature (
                    <E T="03">e.g.</E>
                    , sequential measurements of effects). With this in mind, the EPA has supported the development of this time-dependent modeling software and guidance for a particular application, the derivation of benchmark dose (BMD) and its lower confidence limit (BMDL) for data generated from the battery of neurotoxicity screening tests under guidance developed by EPA NHEERL. 
                </P>
                <P>Copies of the draft technical guidance document and the software will be available to the public at the registration Web site. Interested parties are invited to assist the EPA in further developing and refining this document at this peer-review workshop. </P>
                <SIG>
                    <DATED>Dated: December 1, 2003. </DATED>
                    <NAME>Peter W. Preuss, </NAME>
                    <TITLE>Director, National Center for Environmental Assessment. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30269 Filed 12-4-03; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6560-50-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <DEPDOC>[OPP-2003-0291; FRL-7331-1]</DEPDOC>
                <SUBJECT>Notice of Receipt of Requests to Voluntarily Cancel Certain Pesticide Registrations for Products Containing Tributyltin Methacrylate, and to Amend Certain Pesticide Registrations Containing Bis(tributyltin) Oxide to Terminate a Use</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with section 6(f)(1) of the Federal Insecticide, Fungicide, and Rodenticide Act (FIFRA), as amended, EPA is issuing a notice of receipt of requests by registrants to voluntarily cancel certain pesticide registrations and to amend certain pesticide registrations to terminate a use.  Atofina Chemicals, Inc. and Crompton Corporation have requested that the registrations for all their tributyltin products registered for use in formulating antifouling paints or which are themselves antifouling paints be canceled, or if the products are registered for use in formulating other pesticides in addition to antifouling paints, that those registrations be amended to terminate the antifoulant use.  Both registrants have requested that the voluntary cancellations and use terminations become effective as of November 30, 2003.  Both companies have requested that they be permitted to sell affected products without change to the labels until that date and no later; no separate existing stocks provisions are necessary since the Agency intends to allow them to sell the affected products only until the effective date as requested.  Both companies have waived the 180-day comment period typically allowed after a request for voluntary cancellation, and both companies have stated that their requests are irrevocable.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Unless the Agency receives substantive comments within the 30-day comment period that would merit further review of the requests, the Agency intends to issue orders granting these requests to cancel certain products, and to amend to terminate certain uses. Comments, identified by docket ID number OPP-2003-0291, must be received on or before January 5, 2004.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments may be submitted electronically, by mail, or through hand delivery/courier.  Please follow the detailed instructions for each method as provided in Unit I.C. of the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                        .
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Jill Bloom, Special Review and Reregistration Division (7508C), Office of Pesticide Programs, Environmental Protection Agency, 1200 Pennsylvania Ave., NW., Washington, DC 20460-0001; telephone number: (703) 308-8019; e-mail address: 
                        <E T="03">bloom.jill@epamail.epa.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. General Information</HD>
                <HD SOURCE="HD2">A. Does this Action Apply to Me?</HD>
                <P>
                    This action is directed to the public in general.  Although this action may be of particular interest to persons who produce or use pesticides, the Agency has not attempted to describe all the specific entities that may be affected by this action.  If you have any questions regarding the information in this notice, consult the person listed under 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    .
                </P>
                <HD SOURCE="HD2">B. How Can I Get Copies of this Document and Other Related Information?</HD>
                <P>
                    1. 
                    <E T="03">Docket</E>
                    .  EPA has established an official public docket for this action under docket identification (ID) number OPP-2003-0291.  The official public docket consists of the documents specifically referenced in this action, any public comments received, and other information related to this action.  Although a part of the official docket, the public docket does not include Confidential Business Information (CBI) or other information whose disclosure is restricted by statute.  The official public docket is the collection of materials that is available for public viewing at the Public Information and Records Integrity Branch (PIRIB), Rm. 119, Crystal Mall #2, 1921 Jefferson Davis Hwy., Arlington, VA.  This docket facility is open from 8:30 a.m. to 4 p.m., Monday through Friday, excluding legal holidays.  The docket telephone number is (703) 305-5805.
                </P>
                <P>
                    2. 
                    <E T="03">Electronic access</E>
                    .  You may access this 
                    <E T="04">Federal Register</E>
                     document electronically through the EPA Internet under the “
                    <E T="04">Federal Register</E>
                    ” listings at 
                    <E T="03">http://www.epa.gov/fedrgstr/</E>
                    .
                </P>
                <P>
                    An electronic version of the public docket is available through EPA's electronic public docket and comment system, EPA Dockets.  You may use EPA Dockets at 
                    <E T="03">http://www.epa.gov/edocket/</E>
                     to submit or view public comments, access the index listing of the contents of the official public docket, and to access those documents in the public docket that are available electronically.  Although not all docket materials may be available electronically, you may still access any of the publicly available docket materials through the docket facility identified in Unit I.B.1.  Once in the system, select “search,” then key in the appropriate docket ID number.
                </P>
                <P>
                    Certain types of information will not be placed in the EPA Dockets.  Information claimed as CBI and other information whose disclosure is restricted by statute, which is not included in the official public docket, will not be available for public viewing in EPA's electronic public docket.  EPA's policy is that copyrighted material will not be placed in EPA's electronic public docket but will be available only in printed, paper form in the official public docket.  To the extent feasible, publicly available docket materials will be made available in EPA's electronic public docket.  When a document is selected from the index list in EPA Dockets, the system will identify whether the document is available for viewing in EPA's electronic public docket. 
                    <PRTPAGE P="68040"/>
                    Although not all docket materials may be available electronically, you may still access any of the publicly available docket materials through the docket facility identified in Unit I.B.1.  EPA intends to work towards providing electronic access to all of the publicly available docket materials through EPA's electronic public docket.
                </P>
                <P>For public commenters, it is important to note that EPA's policy is that public comments, whether submitted electronically or in paper, will be made available for public viewing in EPA's electronic public docket as EPA receives them and without change, unless the comment contains copyrighted material, CBI, or other information whose disclosure is restricted by statute.  When EPA identifies a comment containing copyrighted material, EPA will provide a reference to that material in the version of the comment that is placed in EPA's electronic public docket.  The entire printed comment, including the copyrighted material, will be available in the public docket.</P>
                <P>Public comments submitted on computer disks that are mailed or delivered to the docket will be transferred to EPA's electronic public docket.  Public comments that are mailed or delivered to the docket will be scanned and placed in EPA's electronic public docket.  Where practical, physical objects will be photographed, and the photograph will be placed in EPA's electronic public docket along with a brief description written by the docket staff.</P>
                <HD SOURCE="HD2">C.  How and to Whom Do I Submit Comments?</HD>
                <P>You may submit comments electronically, by mail, or through hand delivery/courier.  To ensure proper receipt by EPA, identify the appropriate docket ID number in the subject line on the first page of your comment.  Please ensure that your comments are submitted within the specified comment period.  Comments received after the close of the comment period will be marked “late.”  EPA is not required to consider these late comments. If you wish to submit CBI or information that is otherwise protected by statute, please follow the instructions in Unit I.D.   Do not use EPA Dockets or e-mail to submit CBI or information protected by statute.</P>
                <P>
                    1. 
                    <E T="03">Electronically</E>
                    .  If you submit an electronic comment as prescribed in this unit, EPA recommends that you include your name, mailing address, and an e-mail address or other contact information in the body of your comment.  Also include this contact information on the outside of any disk or CD ROM you submit, and in any cover letter accompanying the disk or CD ROM.  This ensures that you can be identified as the submitter of the comment and allows EPA to contact you in case EPA cannot read your comment due to technical difficulties or needs further information on the substance of your comment.  EPA's policy is that EPA will not edit your comment, and any identifying or contact information provided in the body of a comment will be included as part of the comment that is placed in the official public docket, and made available in EPA's electronic public docket.  If EPA cannot read your comment due to technical difficulties and cannot contact you for  clarification, EPA may not be able to consider your comment.
                </P>
                <P>
                    i. 
                    <E T="03">EPA Dockets</E>
                    .  Your use of EPA's electronic public docket to submit comments to EPA electronically is EPA's preferred method for receiving comments.  Go directly to EPA Dockets at 
                    <E T="03">http://www.epa.gov/edocket/</E>
                    , and follow the online instructions for submitting comments.  Once in the system, select “search,” and then key in docket ID number OPP-2003-0291.  The system is an “anonymous access” system, which means EPA will not know your identity, e-mail address, or other contact information unless you provide it in the body of your comment.
                </P>
                <P>
                    ii. 
                    <E T="03">E-mail</E>
                    .  Comments may be sent by e-mail to 
                    <E T="03">opp-docket@epa.gov</E>
                    , Attention: Docket ID Number OPP-2003-0291.  In contrast to EPA's electronic public docket, EPA's e-mail system is not an “anonymous access” system.  If you send an e-mail comment directly to the docket without going through EPA's electronic public docket, EPA's e-mail system automatically captures your e-mail address.  E-mail addresses that are automatically captured by EPA's e-mail system are included as part of the comment that is placed in the official public docket, and made available in EPA's electronic public docket.
                </P>
                <P>
                    iii. 
                    <E T="03">Disk or CD ROM</E>
                    .  You may submit comments on a disk or CD ROM that you mail to the mailing address identified in Unit I.C.2.  These electronic submissions will be accepted in WordPerfect or ASCII file format.  Avoid the use of special characters and any form of encryption.
                </P>
                <P>
                    2. 
                    <E T="03">By mail</E>
                    .  Send your comments to:  Public Information and Records Integrity Branch (PIRIB) (7502C), Office of Pesticide Programs (OPP), Environmental Protection Agency, 1200 Pennsylvania Ave., NW., Washington, DC 20460-0001, Attention: Docket ID Number OPP-2003-0291.
                </P>
                <P>
                    3. 
                    <E T="03">By hand delivery or courier</E>
                    .  Deliver your comments to: Public Information and Records Integrity Branch (PIRIB), Office of  Pesticide Programs (OPP), Environmental Protection Agency, Rm. 119, Crystal Mall #2, 1921 Jefferson Davis Hwy., Arlington, VA, Attention: Docket ID Number OPP-2003-0291.  Such deliveries are only accepted during the docket's normal hours of operation as identified in Unit I.B.1.
                </P>
                <HD SOURCE="HD2">D.  How Should I Submit CBI to the Agency?</HD>
                <P>Do not submit information that you consider to be CBI electronically through EPA's electronic public docket or by e-mail.  You may claim information that you submit to EPA as CBI by marking any part or all of that information as CBI (if you submit CBI on disk or CD ROM, mark the outside of the disk or CD ROM as CBI and then identify electronically within the disk or CD ROM the specific information that is CBI).  Information so marked will not be disclosed except in accordance with procedures set forth in 40 CFR part 2.</P>
                <P>
                    In addition to one complete version of the comment that includes any information claimed as CBI, a copy of the comment that does not contain the information claimed as CBI must be submitted for inclusion in the public docket and EPA's electronic public docket.  If you submit the copy that does not contain CBI on disk or CD ROM, mark the outside of the disk or CD ROM clearly that it does not contain CBI.  Information not marked as CBI will be included in the public docket and EPA's electronic public docket without prior notice.  If you have any questions about CBI or the procedures for claiming CBI, please consult the person listed under 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    .
                </P>
                <HD SOURCE="HD2">E.  What Should I Consider as I Prepare My Comments for EPA?</HD>
                <P>You may find the following suggestions helpful for preparing your comments:</P>
                <P>1. Explain your views as clearly as possible.</P>
                <P>2. Describe any assumptions that you used.</P>
                <P>3. Provide copies of any technical information and/or data you used that support your views.</P>
                <P>4. If you estimate potential burden or costs, explain how you arrived at the estimate that you provide.</P>
                <P>5. Provide specific examples to illustrate your concerns.</P>
                <P>6. Offer alternative ways to improve the registration activity.</P>
                <P>7. Make sure to submit your comments by the deadline in this notice.</P>
                <PRTPAGE P="68041"/>
                <P>
                    8. To ensure proper receipt by EPA, be sure to identify the docket ID number assigned to this action in the subject line on the first page of your response. You may also provide the name, date, and 
                    <E T="04">Federal Register</E>
                     citation.
                </P>
                <HD SOURCE="HD1">II. What Action is the Agency Taking?</HD>
                <P>This notice announces receipt by the Agency of requests from Atofina to cancel its EPA Registration Numbers shown below.  Atofina submitted a letter dated September 10, 2003 to the Agency requesting the voluntary cancellation of their registrations for these products containing tributyltin methacrylate.  The letter was received by the Agency on September 12, 2003.  The affected registrations are listed in Table 1 of this unit:</P>
                <GPOTABLE COLS="3" OPTS="L4,i1" CDEF="s20,r60,r100">
                    <TTITLE>
                        <E T="04">Table 1.—Requests for Cancellation</E>
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">Registration Number</CHED>
                        <CHED H="1">Product Name</CHED>
                        <CHED H="1">Chemical Name</CHED>
                    </BOXHD>
                    <ROW RUL="s,s">
                        <ENT I="01" O="xl">5204-63</ENT>
                        <ENT O="xl">Biomet 300 Antifouling Agent</ENT>
                        <ENT O="xl">Tributyltin methacrylate</ENT>
                    </ROW>
                    <ROW RUL="s,s">
                        <ENT I="01" O="xl">5204-65</ENT>
                        <ENT O="xl">Biomet 302 Antifouling Agent</ENT>
                        <ENT O="xl">Tributyltin methacrylate</ENT>
                    </ROW>
                    <ROW RUL="s,s">
                        <ENT I="01" O="xl">5204-67</ENT>
                        <ENT O="xl">Biomet 304 Antifouling Agent</ENT>
                        <ENT O="xl">Tributyltin methacrylate</ENT>
                    </ROW>
                    <ROW RUL="s,s">
                        <ENT I="01" O="xl">5204-80</ENT>
                        <ENT O="xl">Biomet 303/60 Antifouling Agent</ENT>
                        <ENT O="xl">Tributyltin methacrylate</ENT>
                    </ROW>
                    <ROW RUL="s,s">
                        <ENT I="01" O="xl">5204-81</ENT>
                        <ENT O="xl">Biomet 304/60 Antifouling Agent</ENT>
                        <ENT O="xl">Tributyltin methacrylate</ENT>
                    </ROW>
                    <ROW RUL="s,s">
                        <ENT I="01" O="xl">5204-83</ENT>
                        <ENT O="xl">Polyflo 4024</ENT>
                        <ENT O="xl">Tributyltin methacrylate</ENT>
                    </ROW>
                    <ROW RUL="s,s">
                        <ENT I="01" O="xl">5204-87</ENT>
                        <ENT O="xl">Biomet 305</ENT>
                        <ENT O="xl">Tributyltin methacrylate</ENT>
                    </ROW>
                    <ROW RUL="s,s">
                        <ENT I="01" O="xl">5204-88</ENT>
                        <ENT O="xl">Biomet 309</ENT>
                        <ENT O="xl">Tributyltin methacrylate</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01" O="xl">5204-90</ENT>
                        <ENT O="xl">Biomet 300/60 Antifouling Agent</ENT>
                        <ENT O="xl">Tributyltin methacrylate</ENT>
                    </ROW>
                </GPOTABLE>
                <P>This notice also announces receipt by the Agency of requests from Atofina and Crompton to amend their EPA Registration Numbers 5204-1 and 8898-17, respectively, to terminate their use for formulation of antifouling paints.  Atofina and Crompton submitted letters dated September 10, 2003 and September 29, 2003 (as subsequently clarified and corrected by Crompton's letter dated October 29, 2003), respectively, to the Agency requesting the amendment of registrations to terminate this use for these products containing bis(tributyltin) oxide.  The letter from Atofina was received by the Agency on September 12, 2003; the letters from Crompton were received by the Agency on September 30, 2003 and October 29, 2003, respectively.  The affected registrations are listed in Table 2 of this unit:</P>
                <GPOTABLE COLS="3" OPTS="L4,i1" CDEF="s20,r60,r100">
                    <TTITLE>
                        <E T="04">Table 2.—Requests for Amendment to Terminate Uses</E>
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">Registration Number</CHED>
                        <CHED H="1">Product Name</CHED>
                        <CHED H="1">Chemical Name</CHED>
                    </BOXHD>
                    <ROW RUL="s,s">
                        <ENT I="01" O="xl">5204-1</ENT>
                        <ENT O="xl">Biomet TBTO</ENT>
                        <ENT O="xl">Bis(tributyltin) oxide</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01" O="xl">8898-17</ENT>
                        <ENT O="xl">Eurotin TBTO</ENT>
                        <ENT O="xl">Bis(tributyltin) oxide</ENT>
                    </ROW>
                </GPOTABLE>
                <P>Under section 6(f)(1)(A) of FIFRA, registrants may request, at any time, that their pesticide registrations be canceled or amended to terminate one or more pesticide uses.  Section 6(f)(1)(B) of FIFRA requires that before acting on a request for voluntary cancellation, EPA must provide a 30-day public comment period on the request for voluntary cancellation or use termination.  In addition, section 6(f)(1)(C) of FIFRA requires that EPA provide a 180-day comment period on a request for voluntary cancellation or use termination of any minor agricultural use before granting the request, unless (1) the registrants request a waiver of the comment period, or (2) the Administrator determines that continued use of the pesticide would pose an unreasonable adverse effect on the environment.  The registrants have requested that EPA waive the 180-day comment period.  EPA will provide a 30-day comment period on the proposed requests.  EPA anticipates granting the cancellation requests and requests for termination of uses shortly after the end of the 30-day comment period for this notice unless the Agency receives substantive comments within the comment period that would merit further review of the request.</P>
                <P>
                    Unless substantive comments are submitted which merit further review,  the Agency intends to issue orders canceling the subject registrations and granting the amendments affecting the use terminations associated with the requests.  Users of these pesticides or anyone else desiring the retention of a registration or particular use should contact the appropriate registrant and the  person listed under 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                     before the lapse of this 30-day period.
                </P>
                <P>Table 3 of this unit includes the name and address of record for the registrants of the products in Table 1 and 2 of this unit:</P>
                <PRTPAGE P="68042"/>
                <GPOTABLE COLS="2" OPTS="L4,i1" CDEF="s20,r80">
                    <TTITLE>
                        <E T="04">Table 3.—Registrants Requesting Voluntary Cancellation and/or Amendment to Terminate Uses</E>
                    </TTITLE>
                    <BOXHD>
                        <CHED H="1">EPA Company Number</CHED>
                        <CHED H="1">Company Name and Address</CHED>
                    </BOXHD>
                    <ROW RUL="s">
                        <ENT I="01" O="xl">5204</ENT>
                        <ENT O="xl">Atofina Chemicals, Inc., 2000 Market Street, Philadelphia, PA  19103-3222</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01" O="xl">8898</ENT>
                        <ENT O="xl">Crompton Corporation, 1 American Way, Greenwich, CT 06831</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">III.  What is the Agency's Authority for Taking this Action?</HD>
                <P>
                    Section 6(f)(1) of FIFRA provides that a registrant of a pesticide product may at any time request that any of its pesticide registrations be canceled or amended to terminate one or more pesticide uses.  FIFRA further provides that, before acting on the request, EPA must publish a notice of receipt of any such request in the 
                    <E T="04">Federal Register</E>
                    .  Thereafter, the Administrator may approve such a request.
                </P>
                <HD SOURCE="HD1">IV. Provisions for Disposition of Existing Stocks</HD>
                <P>
                    The effective date of cancellation will be the date of the cancellation order.  The orders effecting requested cancellations generally permit a registrant to sell or distribute existing stocks for one year after the date the cancellation request was received.  This policy is in accordance with the Agency's statement of policy as prescribed in the 
                    <E T="04">Federal Register</E>
                     of June 26, 1991 (56 FR 29362) (FRL-3846-4).  Exceptions to this general rule will be made if a product poses a risk concern, or is in noncompliance with reregistration requirements, or is subject to a Data Call-In.  In all cases, product-specific disposition dates will be given in the cancellation orders.
                </P>
                <P>In this case, Atofina requested in its letter dated September 10, 2003 that the Agency allow it to sell existing stocks of its affected products for which Atofina requested voluntary cancellation until November 30, 2003, which is the same date that Atofina requested the cancellations to be effective.  In their letters dated September 10, 2003 and September 29, 2003 (as subsequently clarified and corrected by Crompton's letter dated October 29, 2003) respectively, Atofina and Crompton also requested that the Agency allow them to sell stocks of their affected products for which they have requested amendment to terminate uses, bearing labels allowing the use which is the subject of the use termination request, until that same date, November 30, 2003.  The Agency anticipates granting these requests shortly after the end of the 30-day comment period for this notice unless the Agency receives substantive comments within the comment period that would merit further review of the request.  The cancellation and use termination orders which effect the requests of these two registrants for their TBT antifoulant and antifouling paint registrations will effectively serve as the existing stocks orders for the affected registrations.</P>
                <P>Existing stocks are those stocks of registered pesticide products which are currently in the United States and which have been packaged, labeled, and released for shipment prior to the effective date of the cancellation action.  In this instance, and consistent with their own requests, Atofina and  Crompton will not be permitted existing stocks provisions for any sale, distribution, or use of affected products after the effective date of the cancellations and use terminations.  Unless the provisions of an earlier order apply, existing stocks already in the hands of dealers or users can be distributed, sold, or used legally until they are exhausted, provided that such further sale and use comply with EPA-approved label and labeling of the affected product.  Exception to these general rules will be made in specific cases when more stringent restrictions on sale, distribution, or use of the products or their ingredients have already been imposed, as in a Special Review action, or where the Agency has identified significant potential risk concerns associated with a particular chemical.  The Agency does not anticipate any such exception to these general rules in this case.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects</HD>
                    <P>Environmental protection, Pesticides and pests.</P>
                </LSTSUB>
                <SIG>
                    <DATED>Dated: November 21, 2003.</DATED>
                    <NAME>Betty Shackleford,</NAME>
                    <TITLE>Acting Director, Special Review and Reregistration Division, Office of Pesticide Programs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30165 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <DEPDOC>[OPP-2003-0248; FRL-7318-6]</DEPDOC>
                <SUBJECT>Notice of Availability of the Preliminary Risk Assessment for Creosote Reregistration Eligibility Decision</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice announces the availability of documents that were developed as part of EPA's six-phase public participation reregistration process for creosote.  This chemical, a “heavy duty wood preservative,” was first registered in the United States in 1948 as a coal tar creosote active ingredient.  Presently, 16 products are registered for use as industrial wood preservatives for above and below ground wood protection treatments, as well as treating wood in marine environments.  Creosote wood preservatives are used primarily in the pressure treatment of railroad ties/crossties (about 70% of all creosote use) and utility poles/cross-arms (about 15-20% of all creosote use).  Assorted creosote-treated lumber products (e.g., timbers, poles, posts and ground-line support structures) account for the remaining uses of this wood preservative. This notice starts the 60-day public comment period for the preliminary risk assessment for creosote.  EPA will review all comments received and address them accordingly. The Agency will then announce and conduct a public technical briefing on the revised risk assessment to provide an opportunity for the public to learn more about the data, information, and methods used to develop the revised risk assessment.  The revised assessment will then be made available to the public, and the public will be invited to submit risk management ideas and/or proposals.  By allowing access and opportunity for comments on the preliminary risk assessment, the Agency is seeking to strengthen stakeholder involvement and help ensure its decisions under the Food Quality Protection Act are transparent, and based on the best available information.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments, identified by docket ID number OPP-2003-0248, must be received on or before February 3, 2004.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments may be submitted by mail, electronically, or in person.   Please follow the detailed instructions for each method as provided in Unit I. of the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                        .  To ensure proper receipt by EPA, it is imperative 
                        <PRTPAGE P="68043"/>
                        that you identify docket ID number OPP-2003-0248 in the subject line on the first page of your response.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        <E T="03">By mail</E>
                        : Bonaventure Akinlosotu, Antimicrobials Division (7510C), Office of Pesticide Programs, Environmental Protection Agency, 1200 Pennsylvania Avenue, NW., Washington, DC 20460.
                    </P>
                    <P>
                        <E T="03">Office location for commercial courier delivery, telephone number and e-mail address</E>
                        : Rm. 308, Crystal Mall #2, 1921 Jefferson Davis Highway,  Arlington, VA 22202, (703) 605-0653; e-mail: 
                        <E T="03">akinlosotu.bonaventure@epa.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>This announcement consists of two parts.  The first part contains general information. The second part provides information on what actions the Agency intends to take.</P>
                <HD SOURCE="HD1">I. General Information</HD>
                <HD SOURCE="HD2">A. Does this Action Apply to Me?</HD>
                <P>
                    This action is directed to the public in general.   You may be potentially affected by this action if you manufacture, sell, distribute, or use creosote. Since other entities may also be interested, the Agency has not attempted to describe all the specific entities that may be affected by this action.  If you have any questions regarding the applicability of this action to a particular entity, consult the person listed under 
                    <E T="02">FURTHER INFORMATION CONTACT</E>
                    .
                </P>
                <HD SOURCE="HD2">B. How Can I Get Copies of this Document and Other Related Information?</HD>
                <P>
                    1. 
                    <E T="03">Docket</E>
                    .  EPA has established an official public docket for this action under docket identification (ID) number OPP-2003-0248.  The official public docket consists of the documents specifically referenced in this action, any public comments received, and other information related to this action.  Although a part of the official docket, the public docket does not include Confidential Business Information (CBI) or other information whose disclosure is restricted by statute.  The official public docket is the collection of materials that is available for public viewing at the Public Information and Records Integrity Branch (PIRIB), Rm. 119, Crystal Mall #2, 1921 Jefferson Davis Hwy., Arlington, VA.  This docket facility is open from 8:30 a.m. to 4 p.m., Monday through Friday, excluding legal holidays.  The docket telephone number is (703) 305-5805.
                </P>
                <P>
                    2. 
                    <E T="03">Electronic access</E>
                    .  You may access this 
                    <E T="04">Federal Register</E>
                     document electronically through the EPA Internet under the “
                    <E T="04">Federal Register</E>
                    ” listings at
                    <E T="03">http://www.epa.gov/fedrgstr/</E>
                    .
                </P>
                <P>
                    An electronic version of the public docket is available through EPA's electronic public docket and comment system, EPA Dockets.  You may use EPA Dockets at 
                    <E T="03">http://www.epa.gov/edocket/</E>
                     to submit or view public comments, access the index listing of the contents of the official public docket, and to access those documents in the public docket that are available electronically. Although not all docket materials may be available electronically, you may still access any of the publicly available docket materials through the docket facility identified in Unit I.B.1.  Once in the system, select “search,” then key in the appropriate docket ID number.
                </P>
                <P>Certain types of information will not be placed in the EPA Dockets.  Information claimed as CBI and other information whose disclosure is restricted by statute, which is not included in the official public docket, will not be available for public viewing in EPA's electronic public docket.  EPA's policy is that copyrighted material will not be placed in EPA's electronic public docket but will be available only in printed, paper form in the official public docket.  To the extent feasible, publicly available docket materials will be made available in EPA's electronic public docket.  When a document is selected from the index list in EPA Dockets, the system will identify whether the document is available for viewing in EPA's electronic public docket. Although not all docket materials may be available electronically, you may still access any of the publicly available docket materials through the docket facility identified in Unit I.B.  EPA intends to work towards providing electronic access to all of the publicly available docket materials through EPA's electronic public docket.</P>
                <P>For public commenters, it is important to note that EPA's policy is that public comments, whether submitted electronically or in paper, will be made available for public viewing in EPA's electronic public docket as EPA receives them and without change, unless the comment contains copyrighted material, CBI, or other information whose disclosure is restricted by statute.  When EPA identifies a comment containing copyrighted material, EPA will provide a reference to that material in the version of the comment that is placed in EPA's electronic public docket.  The entire printed comment, including the copyrighted material, will be available in the public docket.</P>
                <P>Public comments submitted on computer disks that are mailed or delivered to the docket will be transferred to EPA's electronic public docket.  Public comments that are mailed or delivered to the docket will be scanned and placed in EPA's electronic public docket.  Where practical, physical objects will be photographed, and the photograph will be placed in EPA's electronic public docket along with a brief description written by the docket staff.</P>
                <HD SOURCE="HD2">C.  How and to Whom Do I Submit Comments?</HD>
                <P>You may submit comments electronically, by mail, or through hand delivery/courier.  To ensure proper receipt by EPA, identify the appropriate docket ID number in the subject line on the first page of your comment.  Please ensure that your comments are submitted within the specified comment period.  Comments received after the close of the comment period will be marked “late.”  EPA is not required to consider these late comments. If you wish to submit CBI or information that is otherwise protected by statute, please follow the instructions in Unit I.D.   Do not use EPA Dockets or e-mail to submit CBI or information protected by statute.</P>
                <P>
                    1. 
                    <E T="03">Electronically</E>
                    .  If you submit an electronic comment as prescribed in this unit, EPA recommends that you include your name, mailing address, and an e-mail address or other contact information in the body of your comment.  Also include this contact information on the outside of any disk or CD ROM you submit, and in any cover letter accompanying the disk or CD ROM.  This ensures that you can be identified as the submitter of the comment and allows EPA to contact you in case EPA cannot read your comment due to technical difficulties or needs further information on the substance of your comment.  EPA's policy is that EPA will not edit your comment, and any identifying or contact information provided in the body of a comment will be included as part of the comment that is placed in the official public docket, and made available in EPA's electronic public docket.  If EPA cannot read your comment due to technical difficulties and cannot contact you for clarification, EPA may not be able to consider your comment.
                </P>
                <P>
                    i. 
                    <E T="03">EPA Dockets</E>
                    .  Your use of EPA's electronic public docket to submit comments to EPA electronically is EPA's preferred method for receiving comments.  Go directly to EPA Dockets at
                    <E T="03">http://www.epa.gov/edocket</E>
                    , and follow the online instructions for submitting comments.  Once in the system, select “search,” and then key in docket ID number OPP-2003-0248. The 
                    <PRTPAGE P="68044"/>
                    system is an “anonymous access” system, which means EPA will not know your identity, e-mail address, or other contact information unless you provide it in the body of your comment.
                </P>
                <P>
                    ii. 
                    <E T="03">E-mail</E>
                    .  Comments may be sent by e-mail to
                    <E T="03">opp-docket@epa.gov</E>
                    , Attention: Docket ID Number OPP-2003-0248.  In contrast to EPA's electronic public docket, EPA's e-mail system is not an “anonymous access” system.  If you send an e-mail comment directly to the docket without going through EPA's electronic public docket, EPA's e-mail system automatically captures your e-mail address.  E-mail addresses that are automatically captured by EPA's e-mail system are included as part of the comment that is placed in the official public docket, and made available in EPA's electronic public docket.
                </P>
                <P>
                    iii. 
                    <E T="03">Disk or CD ROM</E>
                    .  You may submit comments on a disk or CD ROM that you mail to the mailing address identified in Unit I.C.2.  These electronic submissions will be accepted in WordPerfect or ASCII file format.  Avoid the use of special characters and any form of encryption.
                </P>
                <P>
                    2. 
                    <E T="03">By mail</E>
                    .  Send your comments to:  Public Information and Records Integrity Branch (PIRIB) (7502C), Office of Pesticide Programs (OPP), Environmental Protection Agency, 1200 Pennsylvania Ave., NW., Washington, DC 20460-0001, Attention: Docket ID Number OPP-2003-0248.
                </P>
                <P>
                    3. 
                    <E T="03">By hand delivery or courier</E>
                    .  Deliver your comments to:  Public Information and Records Integrity Branch (PIRIB), Office of Pesticide Programs (OPP), Environmental Protection Agency, Rm. 119, Crystal Mall #2, 1921 Jefferson Davis Hwy., Arlington, VA, Attention: Docket ID Number OPP-2003-0248.  Such deliveries are only accepted during the docket's normal hours of operation as identified in Unit I.B.1.
                </P>
                <HD SOURCE="HD2">D.  How Should I Submit CBI to the Agency?</HD>
                <P>Do not submit information that you consider to be CBI electronically through EPA's electronic public docket or by e-mail.  You may claim information that you submit to EPA as CBI by marking any part or all of that information as CBI (if you submit CBI on disk or CD ROM, mark the outside of the disk or CD ROM as CBI and then identify electronically within the disk or CD ROM the specific information that is CBI).  Information so marked will not be disclosed except in accordance with procedures set forth in 40 CFR part 2.</P>
                <P>
                    In addition to one complete version of the comment that includes any information claimed as CBI, a copy of the comment that does not contain the information claimed as CBI must be submitted for inclusion in the public docket and EPA's electronic public docket.  If you submit the copy that does not contain CBI on disk or CD ROM, mark the outside of the disk or CD ROM clearly that it does not contain CBI.  Information not marked as CBI will be included in the public docket and EPA's electronic public docket without prior notice.  If you have any questions about CBI or the procedures for claiming CBI, please consult the person listed under 
                    <E T="02">FOR FURTHER INFORMATION CONTACT</E>
                    .
                </P>
                <HD SOURCE="HD2">E. What Should I Consider as I Prepare My Comments for EPA?</HD>
                <P>You may find the following suggestions helpful for preparing your comments:</P>
                <P>1. Explain your views as clearly as possible.</P>
                <P>2. Describe any assumptions that you used.</P>
                <P>3. Provide copies of any technical information and/or data you used that support your views.</P>
                <P>4. If you estimate potential burden or costs, explain how you arrived at the estimate that you provide.</P>
                <P>5. Provide specific examples to illustrate your concerns.</P>
                <P>6. Make sure to submit your comments by the deadline in this notice.</P>
                <P>
                    7. To ensure proper receipt by EPA, be sure to identify the docket ID number assigned to this action in the subject line on the first page of your response. You may also provide the name, date, and 
                    <E T="04">Federal Register</E>
                     citation.
                </P>
                <HD SOURCE="HD1">II. What Action is the Agency Taking?</HD>
                <P>EPA is making available preliminary risk assessments that have been developed as part of EPA's process for making reregistration eligibility decisions for creosote.  The Agency is providing the opportunity, through this notice, for interested parties to provide written comments and input to the Agency on the preliminary risk assessments for the chemical specified in this notice.   Such comments and input could address, for example, the availability of additional data to further refine the risk assessments, or could address the Agency's risk assessment methodologies and assumptions as applied to this specific chemical. Comments should be limited to issues raised within the preliminary risk assessments and associated documents. EPA will provide other opportunities for public comment on other science issues associated with creosote.   Failure to comment on any issues as part of this opportunity will in no way prejudice or limit a commenter's opportunity to participate fully in later notice and comment processes. All comments should be submitted by February 3, 2004.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects</HD>
                    <P>Environmental protection, Chemicals, Creosote, Pesticides and pests.</P>
                </LSTSUB>
                <SIG>
                    <DATED>Dated: November 25, 2003.</DATED>
                    <NAME>Jack E. Housenger,</NAME>
                    <TITLE>Acting Director, Antimicrobials Division, Office of Pesticide Programs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30270 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">ENVIRONMENTAL PROTECTION AGENCY</AGENCY>
                <DEPDOC>[OPP-2003-0276; FRL-7334-6]</DEPDOC>
                <SUBJECT>Pyridalyl; Notice of Filing a Pesticide Petition to Establish a Tolerance for a Certain Pesticide Chemical in or on Food</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Environmental Protection Agency (EPA).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice announces the initial filing of a pesticide petition proposing the establishment of regulations for residues of a certain pesticide chemical in or on various food commodities.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments, identified by docket (ID) number OPP-2003-0276, must be received on or before January 5, 2004.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments may be submitted electronically, by mail, or through hand delivery/courier. Follow the detailed instructions as provided in Unit I. of the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                        .
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Susan Stanton, Registration Division (7505C), Office of Pesticide Programs, Environmental Protection Agency, 1200 Pennsylvania Ave., NW., Washington, DC 20460-0001; telephone number: (703) 305-5218; e-mail address: 
                        <E T="03">stanton.susan@epa.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">I. General Information</HD>
                <HD SOURCE="HD2">A. Does this Action Apply to Me?</HD>
                <P>You may be potentially affected by this action if you are an agricultural producer, food manufacturer or pesticide manufacturer. Potentially affected entities may include, but are not limited to:</P>
                <P>•  Crop production (NAICS 111)</P>
                <P>•  Animal production (NAICS 112)</P>
                <P>•  Food manufacturing (NAICS 311)</P>
                <P>•  Pesticide manufacturing (NAICS 32532)</P>
                <PRTPAGE P="68045"/>
                <P>
                    This listing is not intended to be exhaustive, but rather provides a guide for readers regarding entities likely to be affected by this action. Other types of entities not listed in this unit could also be affected. The North American Industrial Classification System (NAICS) codes have been provided to assist you and others in determining whether this action might apply to certain entities. If you have any questions regarding the applicability of this action to a particular entity, consult the person listed under 
                    <E T="02">FOR FURTHER INFORMATION CONTACT.</E>
                </P>
                <HD SOURCE="HD2">B. How Can I Get Copies of this Document and Other Related Information?</HD>
                <P>
                    1. 
                    <E T="03">Docket</E>
                    . EPA has established an official public docket for this action under docket ID number OPP-2003-0276. The official public docket consists of the documents specifically referenced in this action, any public comments received, and other information related to this action. Although, a part of the official docket, the public docket does not include Confidential Business Information (CBI) or other information whose disclosure is restricted by statute. The official public docket is the collection of materials that is available for public viewing at the Public Information and Records Integrity Branch (PIRIB), Rm. 119, Crystal Mall #2, 1921 Jefferson Davis Hwy., Arlington, VA. This docket facility is open from 8:30 a.m. to 4 p.m., Monday through Friday, excluding legal holidays. The docket telephone number is (703) 305-5805.
                </P>
                <P>
                    2. 
                    <E T="03">Electronic access</E>
                    . You may access this 
                    <E T="04">Federal Register</E>
                     document electronically through the EPA Internet under the “
                    <E T="04">Federal Register</E>
                    ” listings at 
                    <E T="03">http://www.epa.gov/fedrgstr/</E>
                    .
                </P>
                <P>
                    An electronic version of the public docket is available through EPA's electronic public docket and comment system, EPA Dockets. You may use EPA Dockets at 
                    <E T="03">http://www.epa.gov/edocket/</E>
                     to submit or view public comments, access the index listing of the contents of the official public docket, and to access those documents in the public docket that are available electronically. Although, not all docket materials may be available electronically, you may still access any of the publicly available docket materials through the docket facility identified in Unit I.B.1. Once in the system, select “search,” then key in the appropriate docket ID number.
                </P>
                <P>Certain types of information will not be placed in the EPA Dockets. Information claimed as CBI and other information whose disclosure is restricted by statute, which is not included in the official public docket, will not be available for public viewing in EPA's electronic public docket. EPA's policy is that copyrighted material will not be placed in EPA's electronic public docket but will be available only in printed, paper form in the official public docket. To the extent feasible, publicly available docket materials will be made available in EPA's electronic public docket. When a document is selected from the index list in EPA Dockets, the system will identify whether the document is available for viewing in EPA's electronic public docket. Although, not all docket materials may be available electronically, you may still access any of the publicly available docket materials through the docket facility identified in Unit I.B.1. EPA intends to work towards providing electronic access to all of the publicly available docket materials through EPA's electronic public docket.</P>
                <P>For public commenters, it is important to note that EPA's policy is that public comments, whether submitted electronically or on paper, will be made available for public viewing in EPA's electronic public docket as EPA receives them and without change, unless the comment contains copyrighted material, CBI, or other information whose disclosure is restricted by statute. When EPA identifies a comment containing copyrighted material, EPA will provide a reference to that material in the version of the comment that is placed in EPA's electronic public docket. The entire printed comment, including the copyrighted material, will be available in the public docket.</P>
                <P>Public comments submitted on computer disks that are mailed or delivered to the docket will be transferred to EPA's electronic public docket. Public comments that are mailed or delivered to the docket will be scanned and placed in EPA's electronic public docket. Where practical, physical objects will be photographed, and the photograph will be placed in EPA's electronic public docket along with a brief description written by the docket staff.</P>
                <HD SOURCE="HD2">C. How and to Whom Do I Submit Comments?</HD>
                <P>You may submit comments electronically, by mail, or through hand delivery/courier. To ensure proper receipt by EPA, identify the appropriate docket ID number in the subject line on the first page of your comment. Please ensure that your comments are submitted within the specified comment period. Comments received after the close of the comment period will be marked “late.” EPA is not required to consider these late comments. If you wish to submit CBI or information that is otherwise protected by statute, please follow the instructions in Unit I.D. Do not use EPA Dockets or e-mail to submit CBI or information protected by statute.</P>
                <P>
                    1. 
                    <E T="03">Electronically</E>
                    . If you submit an electronic comment as prescribed in this unit, EPA recommends that you include your name, mailing address, and an e-mail address or other contact information in the body of your comment. Also, include this contact information on the outside of any disk or CD ROM you submit, and in any cover letter accompanying the disk or CD ROM. This ensures that you can be identified as the submitter of the comment and allows EPA to contact you in case EPA cannot read your comment due to technical difficulties or needs further information on the substance of your comment. EPA's policy is that EPA will not edit your comment, and any identifying or contact information provided in the body of a comment will be included as part of the comment that is placed in the official public docket, and made available in EPA's electronic public docket. If EPA cannot read your comment due to technical difficulties and cannot contact you for clarification, EPA may not be able to consider your comment.
                </P>
                <P>
                    i. 
                    <E T="03">EPA Dockets</E>
                    . Your use of EPA's electronic public docket to submit comments to EPA electronically is EPA's preferred method for receiving comments. Go directly to EPA Dockets at 
                    <E T="03">http://www.epa.gov/edocket/</E>
                    , and follow the online instructions for submitting comments. Once in the system, select “search,” and then key in docket ID number OPP-2003-0276. The system is an “anonymous access” system, which means EPA will not know your identity, e-mail address, or other contact information unless you provide it in the body of your comment.
                </P>
                <P>
                    ii. 
                    <E T="03">E-mail</E>
                    . Comments may be sent by e-mail to 
                    <E T="03">opp-docket@epa.gov</E>
                    , Attention: Docket ID number OPP-2003-0276. In contrast to EPA's electronic public docket, EPA's e-mail system is not an “anonymous access” system. If you send an e-mail comment directly to the docket without going through EPA's electronic public docket, EPA's e-mail system automatically captures your e-mail address. E-mail addresses that are automatically captured by EPA's e-mail system are included as part of the comment that is placed in the official public docket, and made available in EPA's electronic public docket.
                </P>
                <P>
                    iii. 
                    <E T="03">Disk or CD ROM</E>
                    . You may submit comments on a disk or CD ROM that 
                    <PRTPAGE P="68046"/>
                    you mail to the mailing address identified in Unit I.C.2. These electronic submissions will be accepted in WordPerfect or ASCII file format. Avoid the use of special characters and any form of encryption.
                </P>
                <P>
                    2. 
                    <E T="03">By mail</E>
                    . Send your comments to: Public Information and Records Integrity Branch (PIRIB) (7502C), Office of Pesticide Programs (OPP), Environmental Protection Agency, 1200 Pennsylvania Ave., NW., Washington, DC 20460-0001, Attention: Docket ID number OPP-2003-0276.
                </P>
                <P>
                    3. 
                    <E T="03">By hand delivery or courier</E>
                    . Deliver your comments to: Public Information and Records Integrity Branch (PIRIB), Office of Pesticide Programs (OPP), Environmental Protection Agency, Rm. 119, Crystal Mall #2, 1921 Jefferson Davis Hwy., Arlington, VA, Attention: Docket ID number OPP-2003-0276. Such deliveries are only accepted during the docket's normal hours of operation as identified in Unit I.B.1.
                </P>
                <HD SOURCE="HD2">D. How Should I Submit CBI to the Agency?</HD>
                <P>Do not submit information that you consider to be CBI electronically through EPA's electronic public docket or by e-mail. You may claim information that you submit to EPA as CBI by marking any part or all of that information as CBI (if you submit CBI on disk or CD ROM, mark the outside of the disk or CD ROM as CBI and then identify electronically within the disk or CD ROM the specific information that is CBI). Information so marked will not be disclosed except in accordance with procedures set forth in 40 CFR part 2.</P>
                <P>
                    In addition to one complete version of the comment that includes any information claimed as CBI, a copy of the comment that does not contain the information claimed as CBI must be submitted for inclusion in the public docket and EPA's electronic public docket. If you submit the copy that does not contain CBI on disk or CD ROM, mark the outside of the disk or CD ROM clearly that it does not contain CBI. Information not marked as CBI will be included in the public docket and EPA's electronic public docket without prior notice. If you have any questions about CBI or the procedures for claiming CBI, please consult the person listed under 
                    <E T="02">FOR FURTHER INFORMATION CONTACT.</E>
                </P>
                <HD SOURCE="HD2">E. What Should I Consider as I Prepare My Comments for EPA?</HD>
                <P>You may find the following suggestions helpful for preparing your comments:</P>
                <P>1. Explain your views as clearly as possible.</P>
                <P>2. Describe any assumptions that you used.</P>
                <P>3. Provide copies of any technical information and/or data you used that support your views.</P>
                <P>4. If you estimate potential burden or costs, explain how you arrived at the estimate that you provide.</P>
                <P>5. Provide specific examples to illustrate your concerns.</P>
                <P>6. Make sure to submit your comments by the deadline in this notice.</P>
                <P>
                    7. To ensure proper receipt by EPA, be sure to identify the docket ID number assigned to this action in the subject line on the first page of your response. You may also provide the name, date, and 
                    <E T="04">Federal Register</E>
                     citation.
                </P>
                <HD SOURCE="HD1">II. What Action is the Agency Taking?</HD>
                <P>EPA has received a pesticide petition as follows proposing the establishment and/or amendment of regulations for residues of a certain pesticide chemical in or on various food commodities under section 408 of the Federal Food, Drug, and Cosmetic Act (FFDCA), 21 U.S.C. 346a. EPA has determined that this petition contains data or information regarding the elements set forth in FFDCA section 408(d)(2); however, EPA has not fully evaluated the sufficiency of the submitted data at this time or whether the data support granting of the petition. Additional data may be needed before EPA rules on the petition.</P>
                <LSTSUB>
                    <HD SOURCE="HED">List of Subjects</HD>
                    <P>Environmental protection, Agricultural commodities, Feed additives, Food additives, Pesticides and pests, Reporting and recordkeeping requirements.</P>
                </LSTSUB>
                <SIG>
                    <DATED>Dated: November 20, 2003.</DATED>
                    <NAME>Susan Lewis,</NAME>
                    <TITLE>Acting Director, Registration Division, Office of Pesticide Programs.</TITLE>
                </SIG>
                <HD SOURCE="HD1">Summary of Petition</HD>
                <P>The petitioner's summary of the pesticide petition is printed below as required by FFDCA section 408(d)(3). The summary of the petition was prepared by the Valent U.S.A. Corporation and represents the view of the petitioner. The petition summary announces the availability of a description of the analytical methods available to EPA for the detection and measurement of the pesticide chemical residues or an explanation of why no such method is needed.</P>
                <HD SOURCE="HD1">Valent U.S.A. Corporation</HD>
                <HD SOURCE="HD2">PP 2F6459, and PP 2E6592</HD>
                <P>EPA has received pesticide petitions (PP 2F6459, and PP 2E6592) from Valent U.S.A. Corporation, 1600 Riviera Ave., Suite 200, Walnut Creek, CA 94596-8025, and IR-4, 681 U.S. Highway #1 South, North Brunswick, NJ, 08902-3390, proposing, pursuant to section 408(d) of the Federal Food, Drug, and Cosmetic Act (FFDCA), 21 U.S.C. 346a(d), to amend 40 CFR part 180 by establishing tolerances for residues of the insecticide chemical pyridalyl, pyridine,2-[3-[2,6-dichloro-4-[(3,3-dichloro-2-propenyl)oxy]phenoxy]propoxy]-5-(trifluoromethyl), in or on the raw agricultural commodities: Cottonseed at 0.4 parts per million (ppm); vegetable, fruiting, group 8, at 1.1 ppm; vegetable, leafy, except Brassica, group 4, at 20.0 ppm; Brassica, head and stem, subgroup 5A, at 5.0 ppm; Brassica, leafy greens, subgroup 5B, at 30.0 ppm; turnip greens at 30 ppm; meat at 0.04 ppm; meat by-products at 0.05 ppm; animal fat at 1.0 ppm; and whole milk at 0.1 ppm and to establish tolerances for residues of the insecticide chemical pyridalyl, pyridine,2-[3-[2,6-dichloro-4-[(3,3-dichloro-2-propenyl)oxy]phenoxy]propoxy]-5-(trifluoromethyl) plus the metabolite S-1812-DP, 3,5-dichloro-4-[3-(5-trifluoromethyl-2-pyridyloxy)]propoxy phenol, in or on the raw agricultural commodity cotton gin by-products at 23.0 ppm. EPA has determined that the petitions contain data or information regarding the elements set forth in section 408(d)(2) of the FFDCA; however, EPA has not fully evaluated the sufficiency of the submitted data at this time or whether the data support granting of the petitions. Additional data may be needed before EPA rules on the petition.</P>
                <HD SOURCE="HD2">A. Residue Chemistry</HD>
                <P>
                    1. 
                    <E T="03">Plant metabolism.</E>
                     The metabolism of pyridalyl in plants is well understood, having been investigated in cabbage, tomato, and cotton. The major residue in all crops is pyridalyl. A minor metabolic pathway in plants involves cleavage of the dichloropropenyl group to the phenol, S-1812-DP, which can be conjugated. Other minor metabolic pathways in cotton are oxidation of the dichloropropenyl group to the acid, S-1812-PhCH2COOH, and hydrolysis to give the pyridone, HTFP, which can be further hydroxylated to 3-hydroxy-5-trifluoromethylpyridone (HPDO).
                </P>
                <P>
                    2. 
                    <E T="03">Analytical method</E>
                    . Based on the metabolism of pyridalyl in plant and animals and the toxicology of the parent and metabolite, quantification of the parent pyridalyl and the metabolite S-1812-DP are sufficient to determine toxic residues. Practical analytical 
                    <PRTPAGE P="68047"/>
                    methods for detecting and measuring levels of pyridalyl and its metabolite S-1812-DP have been developed and validated in all appropriate agricultural commodities and respective processing fractions. These analytical methods are suitable for monitoring of food with residues at the levels proposed for the tolerances. Methods have also, been developed and validated for determining pyridalyl and S-1812-DP in animal matrices. The limit of quantitation (LOQ) of pyridalyl in the crop methods are 0.02 ppm in cottonseed, 0.1 ppm in cotton gin trash, and 0.02 ppm in vegetables. The LOQs of pyridalyl in the animal methods are 0.01 ppm in milk, 0.02 ppm in tissues, liver and kidney, and 0.10 ppm in fat.
                </P>
                <P>
                    3. 
                    <E T="03">Magnitude of residues</E>
                    . Magnitude of residues were conducted in fruiting vegetables tomato and peppers (bell and non-bell), leafy vegetables (head and leaf lettuce, celery, and spinach), head and stem brassica vegetables (broccoli and cabbage), mustard greens, and cotton. Trials were conducted in all of the major use area for each of the crops as specified in the OPPTS Harmonized Guidelines OPPTS 860.1500 with applications at the maximum use rate for each crop. As a result of the field trials, the following tolerances for the residues of pyridalyl are proposed for each of the crop groups, crops or matrices: Cottonseed at 0.4 ppm; turnip greens at 30 ppm; vegetables, leafy, except Brassica, group 4 at 20.0 ppm; brassica, head and stem, subgroup 5A at 5.0 ppm; Brassica, leafy greens, subgroup 5B at 30 ppm; and vegetables, fruiting, group 8 at 1.1 ppm. Tolerances for the residues of pyridalyl plus the metabolite S-1812-DP are proposed for cotton gin by-products at 23.0 ppm. Processing studies were conducted with tomato and cottonseed. No tolerances are proposed for cottonseed and tomato processing commodities since no concentration factor was observed. Tolerances for residues of pyridalyl are also proposed for milk at 0.1 ppm; meat at 0.04 ppm; animal fat at 1.0 ppm; and meat by-products at 0.05 ppm.
                </P>
                <HD SOURCE="HD2">B. Toxicological Profile</HD>
                <P>A full battery of toxicology testing including studies of acute, subchronic, chronic, oncogenicity, developmental, reproductive and genotoxicity effects is available for pyridalyl. The acute toxicity of pyridalyl is low by all routes. Subchronic and chronic studies exhibit no observed adverse effect level (NOAEL) values from a low of 3.4 milligrams/kilogram/day (mg/kg/day) (male rat combined toxicity/oncogenicity study) to 1,000 mg/kg/day (28-day dermal toxicity study). Pyridalyl is not oncogenic and the weight-of-evidence indicates it is not genotoxic. There are no developmental concerns or reproductive effects.</P>
                <P>The lowest acute NOAEL of 50 mg/kg/day is derived from both the maternal and reproductive toxicity endpoint of the rabbit developmental toxicity study.</P>
                <P>The lowest chronic NOAEL of 40 ppm (2.8 mg/kg/day in males) is taken from the premating growth period in the 2-generation reproduction study.</P>
                <P>
                    1. 
                    <E T="03">Acute toxicity</E>
                    . The acute toxicity of pyridalyl technical is low by all routes. Pyridalyl was not toxic when administered in limit tests orally, dermally and via inhalation to rats. It is not a skin irritant and is only a mild eye irritant. Pyridalyl was positive in skin sensitization tests. Pyridalyl and its formulated products will be placed into Toxicity Category III.
                </P>
                <P>
                    2. 
                    <E T="03">Genotoxicty</E>
                    . The genotoxic potential of pyridalyl was studied 
                    <E T="03">in vitro</E>
                     in bacteria (ames test), in mammalian cells hypoxanthine-guanine phosphoribosyl transferase (HGPRT) and mouse lymphoma L5178Y TK+/−), in the chromosome aberration assay, and 
                    <E T="03">in vivo</E>
                     in the unscheduled DNA synthesis (UDS) test and the mouse micronucleus test. The test systems assayed did not show any evidence of pyridalyl genotoxicity except the 
                    <E T="03">in vitro</E>
                     mammalian cytogenetics (chromosome aberration) assay. The weight of the evidence indicates that pyridalyl does not raise significant genotoxicity concerns.
                </P>
                <P>
                    3. 
                    <E T="03">Reproductive and developmental toxicity</E>
                    . Developmental effects of pyridalyl were studied in rats and rabbits and multigenerational effects on reproduction were studied in rats.
                </P>
                <P>
                    i. 
                    <E T="03">Rat developmental.</E>
                     In a developmental toxicity study conducted with rats, the maternal NOAEL was 10 mg/kg/day based on the non-acute effects of reduced body weight gain and food consumption. There were no developmental effects, and the developmental NOAEL is 250 mg/kg/day, the highest dose tested (HDT).
                </P>
                <P>
                    ii. 
                    <E T="03">Rabbit developmental.</E>
                     In a rabbit developmental toxicity study, the acute effects of maternal toxicity and decreased fetal weight was observed at 150 mg/kg/day. The maternal and developmental NOAEL is 50 mg/kg/day.
                </P>
                <P>
                    iii. 
                    <E T="03">Reproduction.</E>
                     In a rat reproduction study, there were no adverse effects of pyridalyl on reproductive parameters in the absence of parental toxicity. The reproductive, parental and offspring toxicity NOAEL is 40 ppm.
                </P>
                <P>
                    4. 
                    <E T="03">Subchronic toxicity.</E>
                     Subchronic toxicity studies have been conducted with pyridalyl in the rat, mouse, and dog.
                </P>
                <P>
                    i. 
                    <E T="03">Rats.</E>
                     Pyridalyl technical was tested in rats in a 3-month feeding study. Effects included decreased body weight gain, altered blood biochemistry, increased relative liver weight and histopathological changes in the liver, ovary, adrenal and lung. The NOAEL is 100 ppm (5.56 mg/kg/day in males and 6.45 mg/kg/day in females).
                </P>
                <P>
                    ii. 
                    <E T="03">Mice.</E>
                     A 13-week feeding study in mice was conducted. Effects included decreased body weight gain, hematological and blood biochemical effects,increased liver weight, decreased kidney and ovary weights and histopathological changes in liver, kidney, ovary and adrenal. The NOAEL is 70 ppm in males (8.169 mg/kg/day) and 700 ppm in females (86.78 mg/kg/day).
                </P>
                <P>
                    iii. 
                    <E T="03">Dogs.</E>
                     A 13-week oral (capsule) toxicity study was conducted in dogs. Effects included decreased body weight gain, clinical signs indicative of respiratory distress, hematological and blood biochemistry effects, increased liver, lung and kidney weights and histopathological alterations of the lung, kidney, adrenal and liver. The NOAEL was 10 mg/kg/day.
                </P>
                <P>
                    iv. 
                    <E T="03">Dermal rat.</E>
                     A 28-day dermal toxicity study in rats with pyridalyl did not produce any signs of dermal or systemic toxicity at 1,000 mg/kg/day, the highest dose tested (HDT).
                </P>
                <P>
                    5. 
                    <E T="03">Chronic toxicity.</E>
                     Pyridalyl has been tested in chronic studies with dogs, rats and mice.
                </P>
                <P>
                    i. 
                    <E T="03">Rats.</E>
                     In a 104-week combined chronic/oncogenicity study in rats, effects included decreased body weight gain, increased frequency of rearing (high dose females only), hematological alterations and histopathological alterations of the spleen. No oncogenicity was found. The NOAEL for this study is 100 ppm (3.4 mg/kg/day in males and 4.1 mg/kg/day in females).
                </P>
                <P>
                    ii. 
                    <E T="03">Mice.</E>
                     Pyridalyl was administered in the diet to mice for 78-weeks. Effects included decreased body weight gain and food consumption/efficiency, and increased liver and kidney weights. The NOAEL of the study was 50 ppm (5.04 mg/kg/day in males and 4.78 mg/kg/day in females)
                </P>
                <P>
                    iii. 
                    <E T="03">Dogs.</E>
                     Pyridalyl was administered for 12-months by capsule to dogs. There were alterations in blood biochemistry (alkaline phosphatase and alanine aminotransaminase) and increased liver weights. The NOAEL of the study was 20 mg/kg/day.
                </P>
                <P>
                    iv. 
                    <E T="03">Carcinogenicity.</E>
                     Pyridalyl did not produce carcinogenicity in chronic studies with rats or mice. Valent anticipates that the oncogenicity 
                    <PRTPAGE P="68048"/>
                    classification of pyridalyl will be “E” (no evidence of carcinogenicity for humans).
                </P>
                <P>
                    6. 
                    <E T="03">Animal metabolism.</E>
                     Rats metabolize and rapidly eliminate 
                    <E T="51">14</E>
                    C S-1812. Most of the administered dose was eliminated within 48 hours mainly in the feces. There were no apparent sex-related differences in either the rate of elimination of 
                    <E T="51">14</E>
                    C S-1812 or in the metabolite distribution. There was no apparent enzymatic induction as the metabolic pattern was unchanged by multiple (14-day) administrations of 
                    <E T="51">14</E>
                    C S-1812 at 5 mg/kg/day.
                </P>
                <P>
                    7. 
                    <E T="03">Metabolite toxicology</E>
                    . Two metabolites of pyridalyl, 2-hydroxy-5-trifluoromethylpyridine (HTFP) and HPDO that occur in extremely low levels in plants and animals, were also tested for genetic toxicity. Each metabolite was tested in an 
                    <E T="03">in vitro</E>
                     bacterial (Ames test) and mammalian HGPRT assay mutagenesis assay as well as in an 
                    <E T="03">in vitro</E>
                     chromosome aberration test. Both metabolites were positive in the bacterial assay, but were negative in the mammalian mutagenesis assay. One metabolite, HPDO, was positive in the chromosome aberration test. The biological significance of this finding is uncertain given that only low levels of these compounds are detectible in plants or animals and that pyridalyl does not appear to be carcinogenic at high and chronic doses.
                </P>
                <P>
                    8. 
                    <E T="03">Endocrine disruption.</E>
                     Data from the rat reproduction and subchronic studies indicated that pyridalyl may effect lipid metabolism and, consequently, hormone levels. These 
                    <E T="03">in vivo</E>
                     results suggested that S-1812 may have a modulating activity on steroid biosynthesis at doses generally exceeding MTD.
                </P>
                <P>
                    To further understand these finding, two additional, non-guideline, mechanistic studies were conducted. A detailed analysis of the effect of S-1812 on serum steroid hormone levels was performed in rats exposed for 4 weeks to dose levels equivalent to those used in the rat reproduction study. And an 
                    <E T="03">in vitro</E>
                     study was conducted in rat primary Leydig cell and ovary cell cultures to investigate the effects of S-1812 on the production of hormones and on the activity of enzymes that catalyze sex steroid hormone biosynthesis. These studies support the conclusion that S-1812 is not an endocrine disruptor in 
                    <E T="03">in vivo</E>
                     mammalian systems. Although, very weak inhibition of a single steroid biosynthesis pathway was observed in the 
                    <E T="03">in vitro</E>
                     study, effects possibly related to this conversion in mammalian systems were observed only at dose levels that greatly exceeded the maximum tolerated dose.
                </P>
                <HD SOURCE="HD2">C. Aggregate Exposure</HD>
                <P>
                    1. 
                    <E T="03">Dietary exposure</E>
                    . Acute and chronic dietary analyses were conducted to estimate exposure to potential pyridalyl residues in or on the following crops and crop groups: Cottonseed, turnip greens, vegetables, leafy, except Brassica, group 4, Brassica, group 5 and vegetables, fruiting, group 8. using the Cumulative and Aggregate Risk Evaluation System (CARES) Version 1.3. Exposure estimates to water were made based upon modeling First Index Screening Tool Reservoir (FIRST model).
                </P>
                <P>
                    i. 
                    <E T="03">Food</E>
                    —a. 
                    <E T="03">Acute.</E>
                     The acute dietary exposure estimate of pyridalyl residues in food at the 99.9
                    <E T="51">th</E>
                     percentile was calculated to be 43% of the acute Reference Dose (aRfD) with a margin of exposure of 235. The population subgroup with the highest exposure was non-nursing infants. The aRfD was defined as the NOAEL from a developmental toxicity study in rabbits and includes an uncertainty factor of 100 (NOAEL = 50 mg/kg body weight (bwt)/day, aRfD = 0.5 mg/kg/day).
                </P>
                <P>
                    b. 
                    <E T="03">Chronic.</E>
                     The chronic dietary exposure estimate of pyridalyl residues in food at the 100
                    <E T="51">th</E>
                     percentile was calculated to be 1.4% of the chronic Reference Dose (cRfD) with a margin of exposure of 732. The population subgroup with the highest exposure was children 1-2 years old. The cRfD was defined as the NOAEL from the 2-generation reproduction study in rats including an uncertainty factor of 100 (NOAEL = 2.8 mg/kg bwt/day, cRfD = 0.028 mg/kg/day).
                </P>
                <P>These values are based on proposed tolerance level residues adjusted for percentages of the crop treated. No adjustments were made for common washing, cooking or preparation practices and as such are very conservative values.</P>
                <P>
                    ii. 
                    <E T="03">Drinking water</E>
                    . Since pyridalyl is applied outdoors to growing agricultural crops, the potential exists for the parent or its metabolites to reach groundwater or surface water that may be used for drinking water. Screening Concentration in Groundwater (SCIGROW) simulation predicted zero S-1812 concentration in ground water indicating that S-1812 will not leach. This result is expected due the very high Koc value of pyridalyl. For the surface water FIRST (version 1.0) simulation produced peak day concentration (acute) of 0.15 parts per billion (ppb). The peak FIRST concentration was used for both the acute and chronic exposure assessment. Based on these modeled drinking water concentrations, the worst-case acute/chronic dietary exposure from drinking water is estimated to be negligible (0.02% of the aRfD, and 0.003% of the cRfD for children).
                </P>
                <P>
                    2. 
                    <E T="03">Non-dietary exposure</E>
                    . Pyridalyl is proposed only for agricultural uses and no homeowner or turf uses. Thus, no non-dietary risk assessment is necessary.
                </P>
                <HD SOURCE="HD2">D. Cumulative Effects</HD>
                <P>Section 408(b)(2)(D)(v) requires that the Agency must consider “available information” concerning the cumulative effects of a particular pesticide's residues and “other substances that have a common mechanism of toxicity.” Available information in this context include not only toxicity, chemistry, and exposure data, but also scientific policies and methodologies for understanding common mechanism of toxicity and conducting cumulative risk assessments. For most pesticides, although, the Agency has some information in its files that may turn out to be helpful in eventually determining whether a pesticide shares a common mechanism of toxicity with any other substances, EPA does not at this time have methodologies to resolve the complex scientific issues concerning common mechanism of toxicity in a meaningful way for most registered pesticides.</P>
                <HD SOURCE="HD2">E. Safety Determination</HD>
                <P>
                    1. 
                    <E T="03">U.S. population.</E>
                     Using the conservative assumption described above, based on the completeness and reliability of the toxicity data, it is concluded that aggregate exposure to the proposed uses of pyridalyl will utilize at most 43% of the acute RfD and 2% of the chronic RfD for the U.S. population and is likely to be much less, as more realistic data and models are developed. The Agency has no cause for concern if total acute residue contribution is less than 100% of the aRfD, because the RfD represents the level at or below which daily aggregate exposure over a lifetime will not pose appreciable risk to human health. Therefore, there is a reasonable certainty that no harm will occur to the U.S. population from aggregate exposure to residues of pyridalyl under the proposed use patterns.
                </P>
                <P>
                    2. 
                    <E T="03">Infants and children</E>
                    . The toxicological data base for evaluating prenatal and postnatal toxicity for pyridalyl is complete with respect to current data requirements. There are no special prenatal and postnatal toxicity concerns for infants and children, based on the results of the rat and rabbit developmental toxicity studies or the 2-generation reproductive toxicity study in rats. Using the conservative 
                    <PRTPAGE P="68049"/>
                    assumption described above, based on the completeness and reliability of the toxicity data, it is concluded that, aggregate exposure to the proposed uses of pyridalyl will utilize at most 43% of the aRfD for non-nursing infants (the most highly exposed subgroup) and 2% of the cRfD for children 1-2 (the most highly exposed subgroup). The drinking water contribution to dietary exposure is insignificant. Therefore, there is a reasonable certainty that no harm will occur to infants and children from aggregate exposure to residues of pyridalyl.
                </P>
                <HD SOURCE="HD2">F. International Tolerances</HD>
                <P>There are currently no international tolerances for pyridalyl.</P>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30164 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6560-50-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">EXPORT-IMPORT BANK</AGENCY>
                <DEPDOC>[Public Notice 58]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Proposed Collection; Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Export Import Bank of the United States. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Export-Import Bank, as a part of its continuing effort to reduce paperwork and respondent burden, invites the general public and other Federal agencies to comment on the proposed information collection, as required by the Paperwork Reduction Act of 1995.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments should be received on or before February 3, 2004 to be assured of consideration.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Direct all comments and requests for additional information to Mr. Wayne Gardella, Director Operations, Export-Import Bank of the U.S., 811 Vermont Avenue, NW., Washington, DC 20571, (202) 565-3787.</P>
                </ADD>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD2">Titles and Form Numbers</HD>
                <FP SOURCE="FP-1">Application for Quotation-Export Credit Insurance, Commercial Bank Insureds, EIB 92-34;</FP>
                <FP SOURCE="FP-1">Beneficiary Certificate and Agreement, EIB 92-37;</FP>
                <FP SOURCE="FP-1">Application for a Financial Institution Buyer Credit Policy, EIB 92-41;</FP>
                <FP SOURCE="FP-1">Application for Export Credit Insurance Financing or Operating Lease Coverage, EIB 92-45;</FP>
                <FP SOURCE="FP-1">Short-Term Multi-Buyer Export Credit Insurance Policy Application, EIB 92-50;</FP>
                <FP SOURCE="FP-1">Exporter's Application for Short-Term Single-Buyer Policy, EIB 92-64;</FP>
                <FP SOURCE="FP-1">Broker Registration Form, EIB 92-79.</FP>
                <P>
                    <E T="03">OMB Number:</E>
                     3048-0009.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Revision and extension of expiration date.
                </P>
                <P>
                    <E T="03">Need and Use:</E>
                     The information requested enables the applicant to provide Ex-Im Bank with the information necessary to obtain legislatively required assurance of repayment and fulfills other statutory requirements. The forms encompass a variety of export credit insurance policies.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     They affect all entities involved in the export of U.S. goods and services including exporters, banks, insurance brokers and non-profit or state and local governments acting as facilitators.
                </P>
                <P>
                    <E T="03">Estimated Annual Respondents:</E>
                     1,762.
                </P>
                <P>
                    <E T="03">Estimated Time per Respondent:</E>
                     1 hour.
                </P>
                <P>
                    <E T="03">Estimated Annual Burden:</E>
                     1,762.
                </P>
                <P>
                    <E T="03">Frequency of Reporting or Use:</E>
                     Applications submitted one time, renewals annually.
                </P>
                <SIG>
                    <DATED>Dated: November 22, 2003.</DATED>
                    <NAME>Solomon Bush,</NAME>
                    <TITLE>Agency Clearance Officer.</TITLE>
                </SIG>
                <BILCOD>BILLING CODE 6690-01-M</BILCOD>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68050"/>
                    <GID>EN05de03.005</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68051"/>
                    <GID>EN05de03.006</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68052"/>
                    <GID>EN05de03.007</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68053"/>
                    <GID>EN05de03.008</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68054"/>
                    <GID>EN05de03.009</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68055"/>
                    <GID>EN05de03.010</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68056"/>
                    <GID>EN05de03.011</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68057"/>
                    <GID>EN05de03.012</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68058"/>
                    <GID>EN05de03.013</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68059"/>
                    <GID>EN05de03.014</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68060"/>
                    <GID>EN05de03.015</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68061"/>
                    <GID>EN05de03.016</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68062"/>
                    <GID>EN05de03.017</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68063"/>
                    <GID>EN05de03.018</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68064"/>
                    <GID>EN05de03.019</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68065"/>
                    <GID>EN05de03.020</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68066"/>
                    <GID>EN05de03.021</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68067"/>
                    <GID>EN05de03.022</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68068"/>
                    <GID>EN05de03.023</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68069"/>
                    <GID>EN05de03.024</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68070"/>
                    <GID>EN05de03.025</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68071"/>
                    <GID>EN05de03.026</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68072"/>
                    <GID>EN05de03.027</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68073"/>
                    <GID>EN05de03.028</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68074"/>
                    <GID>EN05de03.029</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68075"/>
                    <GID>EN05de03.030</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68076"/>
                    <GID>EN05de03.031</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68077"/>
                    <GID>EN05de03.032</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68078"/>
                    <GID>EN05de03.033</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68079"/>
                    <GID>EN05de03.034</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68080"/>
                    <GID>EN05de03.035</GID>
                </GPH>
                <GPH SPAN="3" DEEP="640">
                    <PRTPAGE P="68081"/>
                    <GID>EN05de03.036</GID>
                </GPH>
                <PRTPAGE P="68082"/>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30199  Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6690-01-C</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL DEPOSIT INSURANCE CORPORATION </AGENCY>
                <SUBJECT>Notice of Agency Meeting </SUBJECT>
                <P>Pursuant to the provisions of the “Government in the Sunshine Act” (5 U.S.C. 552b), notice is hereby given that at 11:40 a.m. on Tuesday, December 2, 2003, the Board of Directors of the Federal Deposit Insurance Corporation met in closed session to consider matters relating to the Corporation's supervisory, resolution, and corporate activities.</P>
                <P>In calling the meeting, the Board determined, on motion of Vice Chairman John M. Reich, seconded by Director James E. Gilleran (Director, Office of Thrift Supervision), concurred by Director John D. Hawke, Jr. (Comptroller of the Currency), and Chairman Donald E. Powell, that Corporation business required its consideration of the matters on less than seven days' notice to the public; that the public interest did not require consideration of the matters in a meeting open to public observation; and that the matters could be considered in a closed meeting by authority of subsections (c)(2), (c)(4), (c)(6), (c)(8), (c)(9)(A)(ii), and (c)(9)(B) of the “Government in the Sunshine Act” (5 U.S.C. 552b(c)(2), (c)(4), (c)(6), (c)(8), (c)(9)(A)(ii), and (c)(9)(B)).</P>
                <P>The meeting was held in the Board Room of the FDIC Building located at 550-17th Street, NW., Washington, DC.</P>
                <SIG>
                    <DATED>Dated: December 2, 2003. </DATED>
                    <FP>Federal Deposit Insurance Corporation. </FP>
                    <NAME>Robert E. Feldman, </NAME>
                    <TITLE>Executive Secretary. </TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. E3-00460 Filed 12-3-01; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 6714-01-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">FEDERAL RESERVE SYSTEM</AGENCY>
                <SUBJECT>Proposed Agency Information Collection Activities; Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Board of Governors of the Federal Reserve System</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the requirements of the Paperwork Reduction Act of 1995 (44 U.S.C. chapter 35), the Board of Governors of the Federal Reserve System (Board), the Federal Deposit Insurance Corporation (FDIC), and the Office of the Comptroller of the Currency (OCC) (the “agencies”) may not conduct or sponsor, and the respondent is not required to respond to, an information collection unless it displays a currently valid Office of Management and Budget (OMB) control number.  The Federal Financial Institutions Examination Council (FFIEC), of which the agencies are members, has approved the agencies' publication for public comment of proposed revisions to the Report of Assets and Liabilities of U.S. Branches and Agencies of Foreign Banks (FFIEC 002).  The Board is publishing the proposed revisions on behalf of the agencies.  At the end of the comment period, the comments and recommendations received will be analyzed to determine the extent to which the FFIEC should modify the proposed revisions prior to giving its final approval.  The Board will then submit the revisions to OMB for review and approval.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted on or before February 3, 2004.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Interested parties are invited to submit written comments to the agency listed below.  All comments, which should refer to the OMB control number, will be shared among the agencies.</P>
                </ADD>
                <P>
                    Written comments, which should refer to the “Report of Assets and Liabilities of U.S. Branches and Agencies of Foreign Banks, 7100-dquo; should be addressed to Ms. Jennifer J. Johnson, Secretary, Board of Governors of the Federal Reserve System, 20th and C Streets, NW, Washington, DC 20551.  Due to temporary disruptions in the Board's mail service, commenters are encouraged to submit comments by electronic mail to 
                    <E T="03">regs.comments@federalreserve.gov</E>
                    , or fax them to the Office of the Secretary at (202) 452-3819 or (202) 452-3102.  Comments addressed to Ms. Johnson may also be delivered to the Board's mailroom between 8:45 a.m. and 5:15 p.m. weekdays, and to the security control room outside those hours.  Both the mailroom and the security control room are accessible from the Eccles building courtyard entrance on 20th Street between Constitution Avenue and C Street, NW.  Comments may be inspected in room M-P-500 between 9 a.m. and 5 p.m. on weekdays pursuant to sections 261.12 and 261.14 of the Board's Rules Regarding Availability of Information, 12 CFR 261.12 and 261.14.
                </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>A draft copy of the proposed FFIEC 002 reporting form may be obtained at the FFIEC's web site (www.ffiec.gov).  A copy of the proposed revisions to the collection of information may also be requested from Cindy Ayouch, Board Clearance Officer, (202) 452-3829, Division of Research and Statistics, Board of Governors of the Federal Reserve System, 20th and C Streets, NW, Washington, DC 20551.  Telecommunications Device for the Deaf (TDD) users may call (202) 263-4869.</P>
                </FURINF>
                <HD SOURCE="HD1">Proposal to revise the following currently approved collection of information:</HD>
                <P>
                    <E T="03">Report Title:</E>
                     Report of Assets and Liabilities of U.S. Branches and Agencies of Foreign Banks.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     FFIEC 002.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     7100-0032.
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     Quarterly.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     U.S. branches and agencies of foreign banks.
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents:</E>
                     295.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Responses:</E>
                     1,180.
                </P>
                <P>
                    <E T="03">Estimated Time per Response:</E>
                     22.75 burden hours.
                </P>
                <P>
                    <E T="03">Estimated Total Annual Burden:</E>
                     26,845 burden hours.
                </P>
                <P>
                    <E T="03">General Description of Report:</E>
                     This information collection is mandatory: 12 U.S.C. 3105(b)(2), 1817(a)(1) and (3), and 3102(b). Except for select sensitive items, this information collection is not given confidential treatment (5 U.S.C. 552(b)(8)). Small businesses (that is, small U.S. branches and agencies of foreign banks) are affected.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     On a quarterly basis, all U.S. branches and agencies of foreign banks (U.S. branches) are required to file detailed schedules of assets and liabilities in the form of a condition report and a variety of supporting schedules. This information is used to fulfill the supervisory and regulatory requirements of the International Banking Act of 1978. The data are also used to augment the bank credit, loan, and deposit information needed for monetary policy and other public policy purposes. The Federal Reserve System collects and processes this report on behalf of all three agencies.
                </P>
                <P>
                    <E T="03">Current Actions:</E>
                     The agencies propose to implement a small number of revisions to the existing reporting requirements of the Report of Assets and Liabilities of U.S. Branches and Agencies of Foreign Banks (FFIEC 002).  The proposed revisions would help to achieve consistency with the Reports of Condition and Income (Call Report) (forms FFIEC 031 and 041) filed by insured commercial banks and FDIC-supervised savings banks.
                </P>
                <P>The proposed revisions to the FFIEC 002 that would take effect as of the March 31, 2004, reporting date include:</P>
                <P>
                    <E T="04">Schedule L—Derivatives and Off-Balance-Sheet Items</E>
                </P>
                <PRTPAGE P="68083"/>
                <P>Modifying Line Item 12, “Gross fair values of derivative contracts,” by removing the following requirement: “The following items should be completed by those branches or agencies with total assets of $100 million or more.”  The exemption from reporting the fair values of derivative contracts for branches and agencies with less than dollar;100 million in assets originated when derivatives were considered off-balance sheet items and predates FASB Statement No. 133, Accounting for Derivative Instruments and Hedging Activities (FAS 133), which took effect in 2001.   FAS 133 require all derivatives to be measured at fair value and reported on the balance sheet as assets or liabilities.  Because branches and agencies with less than dollar;100 million in assets that have derivatives now have to regularly determine their fair value for reporting purposes, they have the information necessary to disclose the fair value of their derivatives in Schedule L.  Accordingly, the agencies are proposing to eliminate this disclosure exemption.  The fair value data on derivatives will complement the data that branches and agencies with less than $100 million in assets currently report on the notional amount of their derivative contracts.</P>
                <P>
                    <E T="04">Schedule M—Due from/Due to Related Institutions in the U.S. and in Foreign Countries (CONFIDENTIAL)</E>
                </P>
                <P>1. Modifying Line Item 12, “Gross fair values of derivative contracts,” by removing the following requirement: “The following items should be completed by those branches or agencies with total assets of $100 million or more.”  The rationale for the proposed change is similar to the justification above for the comparable change to Schedule L.</P>
                <P>2. Adding Memoranda items 1.a, “Gross positive fair value,” and 1.b, “Gross negative fair value” to Memorandum item 1, “Notional amount of all credit derivatives on which the reporting branch or agency is the guarantor.”  The new items would provide a better measure of credit and market risk for credit derivatives entered into with related depository institutions, particularly for branches and agencies with large positions in such credit derivatives.</P>
                <P>3. Adding Memoranda items 2.a, “Gross positive fair value,” and 2.b, “Gross negative fair value” to Memorandum item 2, “Notional amount of all credit derivatives on which the reporting branch or agency is the beneficiary.”   The rationale for the proposed change is the same as the justification above for adding items to Memorandum item 1.</P>
                <P>
                    <E T="03">Request for Comment:</E>
                     Comments submitted in response to this Notice will be shared among the agencies and will be summarized or included in the Board's request for OMB approval.  All comments will become a matter of public record.  Written comments should address the accuracy of the burden estimates and ways to minimize burden as well as other relevant aspects of the information collection requests.  Comments are invited on:
                </P>
                <P>(a) Whether the proposed collection of information is necessary for the proper performance of the agencies' functions, including whether the information has practical utility;</P>
                <P>(b) The accuracy of the agencies' estimate of the burden of the information collection, including the validity of the methodology and assumptions used;</P>
                <P>(c) Ways to enhance the quality, utility, and clarity of the information to be collected;</P>
                <P>(d) Ways to minimize the burden of the information collection on respondents, including through the use of automated collection techniques or other forms of information technology; and</P>
                <P>(e) Estimates of capital or start up costs and costs of operation, maintenance, and purchase of services to provide information.</P>
                <SIG>
                    <P>Board of Governors of the Federal Reserve System, December 1, 2003.</P>
                    <NAME>Jennifer J. Johnson</NAME>
                    <TITLE>Secretary of the Board.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30212 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6210-01-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL RESERVE SYSTEM</AGENCY>
                <SUBJECT>Agency Information Collection Activities:  Proposed Collection; Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Board of Governors of the Federal Reserve System</P>
                </AGY>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>On June 15, 1984, the Office of Management and Budget (OMB) delegated to the Board of Governors of the Federal Reserve System (Board) its approval authority under the Paperwork Reduction Act, as per 5 CFR 1320.16, to approve of and assign OMB control numbers to collection of information requests and requirements conducted or sponsored by the Board under conditions set forth in 5 CFR 1320 Appendix A.1.  Board-approved collections of information are incorporated into the official OMB inventory of currently approved collections of information.  Copies of the OMB 83-I's and supporting statements and approved collection of information instruments are placed into OMB's public docket files.  The Federal Reserve may not conduct or sponsor, and the respondent is not required to respond to, an information collection that has been extended, revised, or implemented on or after October 1, 1995, unless it displays a currently valid OMB control number.</P>
                    <HD SOURCE="HD1">Request for comment on information collection proposals</HD>
                    <P>The following information collections, which are being handled under this delegated authority, have received initial Board approval and are hereby published for comment.  At the end of the comment period, the proposed information collections, along with an analysis of comments and recommendations received, will be submitted to the Board for final approval under OMB delegated authority.  Comments are invited on the following:</P>
                    <P>a. whether the proposed collection of information is necessary for the proper performance of the Federal Reserve's functions; including whether the information has practical utility;</P>
                    <P>b. the accuracy of the Federal Reserve's estimate of the burden of the proposed information collection, including the validity of the methodology and assumptions used;</P>
                    <P>c. ways to enhance the quality, utility, and clarity of the information to be collected; and</P>
                    <P>d. ways to minimize the burden of information collection on respondents, including through the use of automated collection techniques or other forms of information technology.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments must be submitted on or before February 3, 2004.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments may be mailed to Ms. Jennifer J. Johnson, Secretary, Board of Governors of the Federal Reserve System, 20th Street and Constitution Avenue, N.W., Washington, DC 20551.  However, because paper mail in the Washington area and at the Board of Governors is subject to delay, please consider submitting your comments by e-mail to 
                        <E T="03">regs.comments@federalreserve.gov</E>
                        , or faxing them to the Office of the Secretary at 202-452-3819 or 202-452-3102.  Members of the public may inspect comments in Room MP-500 between 9:00 a.m. and 5:00 p.m. on weekdays pursuant to 261.12, except as provided in 261.14, of the Board's Rules Regarding Availability of Information, 12 CFR 261.12 and 261.14.
                    </P>
                </ADD>
                <P>
                    A copy of the comments may also be submitted to the OMB desk officer for the Board:  Joseph Lackey, Office of 
                    <PRTPAGE P="68084"/>
                    Information and Regulatory Affairs, Office of Management and Budget, New Executive Office Building, Room 3208, Washington, DC 20503.
                </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>A copy of the proposed form and instructions, the Paperwork Reduction Act Submission (OMB 83-I), supporting statement, and other documents that will be placed into OMB's public docket files once approved may be requested from the agency clearance officer, whose name appears below.</P>
                    <P>Cindy Ayouch, Federal Reserve Board Clearance Officer (202-452-3829), Division of Research and Statistics, Board of Governors of the Federal Reserve System, Washington, DC 20551.  Telecommunications Device for the Deaf (TDD) users may contact (202-263-4869), Board of Governors of the Federal Reserve System, Washington, DC 20551.</P>
                </FURINF>
                <HD SOURCE="HD1">Proposal to approve under OMB delegated authority the extension for three years, with revision, of the following reports:</HD>
                <P>
                    <E T="03">1. Report title:</E>
                     Weekly Report of Assets and Liabilities for Large Banks and Weekly Report of Selected Assets
                </P>
                <P>
                    <E T="03">Agency form numbers:</E>
                     FR 2416 and FR 2644
                </P>
                <P>
                    <E T="03">OMB control number:</E>
                     7100-0075
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     Weekly
                </P>
                <P>
                    <E T="03">Reporters:</E>
                     U.S.-chartered commercial banks
                </P>
                <P>
                    <E T="03">Annual reporting hours:</E>
                     FR 2416: 18,850 hours; FR 2644: 73,216 hours
                </P>
                <P>
                    <E T="03">Estimated average hours per response:</E>
                     FR 2416: 7.25 hours; FR 2644: 1.28 hours
                </P>
                <P>
                    <E T="03">Number of respondents:</E>
                     FR 2416: 50; FR 2644: 1,100
                </P>
                <P>
                    <E T="03">General description of reports:</E>
                     These information collections are voluntary (12 U.S.C. §§ 225(a) and 248(a)(2)).  Individual respondent data are regarded as confidential under the Freedom of Information Act (5 U.S.C. § 552(b)(4)).
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The FR 2416, FR 2644, and the Weekly Report of Assets and Liabilities for Large U.S. Branches and Agencies of Foreign Banks (FR 2069; OMB No. 7100-0030) are referred to collectively as the bank credit reports.  The FR 2416 is a detailed balance sheet that covers domestic offices of large U.S.-chartered commercial banks.  The FR 2644 collects less-detailed information on investments, loans, total assets, and several memoranda items, covering domestic offices of small U.S.-chartered commercial banks.  The bank credit reports are collected as of each Wednesday.
                </P>
                <P>These three voluntary reports are mainstays of the Federal Reserve's reporting system from which data for analysis of current banking developments are derived.  The FR 2416 is used on a stand-alone basis as the “large domestic bank series.”  The FR 2644 collects sample data, which are used to estimate universe levels using data from the quarterly commercial bank Consolidated Reports of Condition and Income (FFIEC 031 and 041; OMB No. 7100-0036) (Call Report).  Data from the bank credit reports, together with data from other sources, are used for constructing weekly estimates of bank credit, of sources and uses of bank funds, and of a balance sheet for the banking system as a whole.</P>
                <P>The Federal Reserve publishes the data in aggregate form in the weekly H.8 statistical release, Assets and Liabilities of Commercial Banks in the United States, which is followed closely by other government agencies, the banking industry, the financial press, and other users.  This release provides a balance sheet for the banking industry as a whole and data disaggregated by its large domestic, small domestic, and foreign-related components.</P>
                <P>
                    <E T="03">Current actions:</E>
                     The Federal Reserve proposes to make the following modifications to the FR 2416: 1) split other assets into two items, 2) split other liabilities into two items, and 3) combine three memoranda items breaking out U.S. Treasury securities.  The Federal Reserve proposes to make the following modifications to the FR 2644: 1) split other loans secured by real estate into two items, 2) add an item for net due from own foreign offices, and 3) add an item for net due to own foreign offices.  The respondent burden estimates are currently under review.  The proposed revisions would be implemented as of June 2004.
                </P>
                <P>
                    <E T="03">2. Report title:</E>
                     Weekly Report of Assets and Liabilities for Large U.S. Branches and Agencies of Foreign Banks
                </P>
                <P>
                    <E T="03">Agency form number:</E>
                     FR 2069
                </P>
                <P>
                    <E T="03">OMB control number:</E>
                     7100-0030
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     Weekly
                </P>
                <P>
                    <E T="03">Reporters:</E>
                     U.S. branches and agencies of foreign banks
                </P>
                <P>
                    <E T="03">Annual reporting hours:</E>
                     19,692 hours
                </P>
                <P>
                    <E T="03">Estimated average hours per response:</E>
                     5.41 hours
                </P>
                <P>
                    <E T="03">Number of respondents:</E>
                     70
                </P>
                <P>
                    <E T="03">General description of report:</E>
                     This information collection is voluntary (12 U.S.C. §§ 248(a)(2) and 3105(a)(2)).  Individual respondent data are regarded as confidential under the Freedom of Information Act (5 U.S.C. § 552(b)(4)).
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The FR 2069 is a detailed balance sheet that covers large U.S. branches and agencies of foreign banks.  This report, along with the FR 2416 and FR 2644, is collected as of each Wednesday.
                </P>
                <P>These three voluntary reports are mainstays of the Federal Reserve's reporting system from which data for analysis of current banking developments are derived.  The FR2069 collects sample data, which are used to estimate universe levels using data from the quarterly Report of Assets and Liabilities of U.S. Branches and Agencies of Foreign Banks (FFIEC 002; OMB No. 7100-0032) (Call Report).  Data from the bank credit reports, together with data from other sources, are used for constructing weekly estimates of bank credit, of sources and uses of bank funds, and of a balance sheet for the banking system as a whole.</P>
                <P>The Federal Reserve publishes the data in aggregate form in the weekly H.8 statistical release, Assets and Liabilities of Commercial Banks in the United States, which is followed closely by other government agencies, the banking industry, the financial press, and other users.  This release provides a balance sheet for the banking industry as a whole and data disaggregated by its large domestic, small domestic, and foreign-related components.</P>
                <P>
                    <E T="03">Current actions:</E>
                     The Federal Reserve proposes to make the following modifications to the FR 2069: 1) combine items for federal funds purchased with banks and other borrowed money owed to banks and 2) combine items for federal funds purchased with others and other borrowed money owed to others. The respondent burden estimates are currently under review.  The proposed revisions would be implemented as of June 2004.
                </P>
                <P>
                    <E T="03">3. Report title:</E>
                     Annual Report of Bank Holding Companies
                </P>
                <P>
                    <E T="03">Agency form number:</E>
                     FR Y-6
                </P>
                <P>
                    <E T="03">OMB control number:</E>
                     7100-0124
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     Annual
                </P>
                <P>
                    <E T="03">Reporters:</E>
                     top-tier domestic Bank Holding Companies (BHCs)
                </P>
                <P>
                    <E T="03">Annual reporting hours:</E>
                     21,913 hours
                </P>
                <P>
                    <E T="03">Estimated average hours per response:</E>
                     4.25 hours
                </P>
                <P>
                    <E T="03">Number of respondents:</E>
                     5,156
                </P>
                <P>
                    <E T="03">General description of report:</E>
                     This information collection is mandatory Section 5(c)(1)(A) of the BHC Act (12 U.S.C. § 1844(c)(1)(A));  Section 8(a) of the International Banking Act (12 U.S.C. § 3106(a)); Sections 11(a)(1), 25 and 25A of the Federal Reserve Act (12 U.S.C. §§ 248(a)(1), 602, and 611a); Section 211.13(c) of Regulation K (12 CFR 211.13(c)); and Section  225.5(b) of Regulation Y (12 CFR 225.5(b)).  Individual respondent data are not considered as confidential.  However, a company may request confidential treatment pursuant to sections (b)(4) and 
                    <PRTPAGE P="68085"/>
                    (b)(6) of the Freedom of Information Act (5 U.S.C. §§ 522(b)(4) and (b)(6)).
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The FR Y-6 is an annual report filed by all BHCs containing financial data, an organization chart, and information about shareholders.  The Federal Reserve uses the data to monitor holding company operations and determine holding company compliance with the provisions of the BHC Act and Regulation Y (12 CFR 225).
                </P>
                <P>
                    <E T="03">Current actions:</E>
                     The Federal Reserve proposes to revise the FR Y-\6 by requiring that only top-tier BHCs file the FR Y-6 report, eliminating Report Item 1(a) that requires a BHC to submit a copy of its Securities and Exchange Commission form 10-K, adding three minor items to the cover page, and clarifying several areas in the instructions.  The proposed FR Y-6 revisions would be effective with fiscal years beginning after December 31, 2003.
                </P>
                <P>
                    <E T="03">4. Report titles:</E>
                     Report of Changes in Organizational Structure and Report of Changes in FBO Organizational Structure
                </P>
                <P>
                    <E T="03">Agency form numbers:</E>
                     FR Y-10 and FR Y-10F
                </P>
                <P>
                    <E T="03">OMB control number:</E>
                     7100-0297
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     Event generated
                </P>
                <P>
                    <E T="03">Reporters:</E>
                     FR Y-10: Top-tier domestic BHCs; financial holding companies (FHCs), and unaffiliated state member banks; FR Y-10F: foreign banking organizations (FBOs) and FHCs
                </P>
                <P>
                    <E T="03">Annual reporting hours:</E>
                     FR Y-10: 9,792 hours; FR Y-10F: 1,635 hours
                </P>
                <P>
                    <E T="03">Estimated average hours per response:</E>
                     FR Y-10: 1 hour; FR Y-10F: 1 hour
                </P>
                <P>
                    <E T="03">Number of respondents:</E>
                     FR Y-10: 2,448; FR Y-10F: 327
                </P>
                <P>
                    <E T="03">General description of reports:</E>
                     These information collections are mandatory Sections 4(k) and 5(c)(1)(A) of the BHC Act (12 U.S.C. §§ 1843(k), 1844(c)(1)(A));  Section 8(a) of the International Banking Act (12 U.S.C. § 3106(a)); Sections 11(a)(1), 25(7) and 25A of the Federal Reserve Act (12 U.S.C. §§ 248(a)(1), 602, and 611a); Section 211.13(c) of Regulation K (12 CFR 211.13(c)); and Sections  225.5(b) and 225.87 of Regulation Y (12 CFR 225.5(b) and 225.87).  Individual respondent data are not considered as confidential.  However, a company may request confidential treatment pursuant to sections (b)(4) and (b)(6) of the Freedom of Information Act (5 U.S.C. §§ 522(b)(4) and (b)(6)).
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The FR Y-10 is an event-generated report filed by top-tier domestic BHCs, including FHCs, and state member banks unaffiliated with a BHC or FHC, to capture changes in their regulated investments and activities. The Federal Reserve uses the data to monitor structure information on subsidiaries and regulated investments of these entities engaged in both banking and nonbanking activities.
                </P>
                <P>The FR Y-10F is an event-generated report filed by FBOs, including FHCs, to capture changes in their regulated investments and activities. The Federal Reserve uses the data to ensure compliance with U.S. banking laws and regulations and to determine the risk profile of the FBO structure.</P>
                <P>
                    <E T="03">Current actions:</E>
                     The Federal Reserve proposes to revise the FR Y-10 and FR Y-10F forms and instructions in an effort to reduce respondent burden.  The proposed revisions to the reporting forms consist primarily of reorganizing line items into separate schedules for banking and nonbanking investments.  In addition, the Federal Reserve proposes to replace the Federal Reserve System activity codes with the North American Industrial Classification System codes and to reorganize and clarify the instructions.  The Federal Reserve is considering the usefulness of a conversion table for converting the Federal Reserve Activity Codes to NAICS codes.  The proposed revisions to the FR Y-10 and FR Y-10F would be implemented as of May 31, 2004.
                </P>
                <SIG>
                    <P>Board of Governors of the Federal Reserve System, December 1, 2003.</P>
                    <NAME>Jennifer J. Johnson,</NAME>
                    <TITLE>Secretary of the Board.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30213 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6210-01-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL RESERVE SYSTEM</AGENCY>
                <SUBJECT>Formations of, Acquisitions by, and Mergers of Bank Holding Companies</SUBJECT>
                <P>
                    The companies listed in this notice have applied to the Board for approval, pursuant to the Bank Holding Company Act of 1956 (12 U.S.C. 1841 
                    <E T="03">et seq.</E>
                    ) (BHC Act), Regulation Y (12 CFR Part 225), and all other applicable statutes and regulations to become a bank holding company and/or to acquire the assets or the ownership of, control of, or the power to vote shares of a bank or bank holding company and all of the banks and nonbanking companies owned by the bank holding company, including the companies listed below.
                </P>
                <P>
                    The applications listed below, as well as other related filings required by the Board, are available for immediate inspection at the Federal Reserve Bank indicated.  The application also will be available for inspection at the offices of the Board of Governors.  Interested persons may express their views in writing on the standards enumerated in the BHC Act (12 U.S.C. 1842(c)).  If the proposal also involves the acquisition of a nonbanking company, the review also includes whether the acquisition of the nonbanking company complies with the standards in section 4 of the BHC Act (12 U.S.C. 1843).  Unless otherwise noted, nonbanking activities will be conducted throughout the United States.  Additional information on all bank holding companies may be obtained from the National Information Center website at 
                    <E T="03">www.ffiec.gov/nic/</E>
                    .
                </P>
                <P>Unless otherwise noted, comments regarding each of these applications must be received at the Reserve Bank indicated or the offices of the Board of Governors not later than December 29, 2003.</P>
                <P>
                    <E T="04">A.  Federal Reserve Bank of Boston</E>
                     (Richard Walker, Community Affairs Officer) 600 Atlantic Avenue, Boston, Massachusetts 02106-2204:
                </P>
                <P>
                    <E T="03">1.  Ponkapoag Bancorp. MHC</E>
                    , and Massapoag Bancorp, Inc., both of Canton, Massachusetts; to become bank holding companies by acquiring 100 percent of the voting shares of The Canton Institution for Saving, The Bank of Canton, Canton, Massachusetts.
                </P>
                <P>
                    <E T="04">B.  Federal Reserve Bank of Richmond</E>
                     (A. Linwood Gill, III, Vice President) 701 East Byrd Street, Richmond, Virginia 23261-4528:
                </P>
                <P>
                    <E T="03">1.  Southern Community Financial Corporation</E>
                    , Winston-Salem, North Carolina; to acquire The Community Bank, Pilot Mountain, North Carolina.  Comments on this application must be received by December 19, 2003.
                </P>
                <SIG>
                    <P>Board of Governors of the Federal Reserve System, December 1, 2003.</P>
                    <NAME>Robert deV. Frierson,</NAME>
                    <TITLE>Deputy Secretary of the Board.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30215 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6210-01-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">FEDERAL RESERVE SYSTEM</AGENCY>
                <SUBJECT>Notice of Proposals to Engage in Permissible Nonbanking Activities or to Acquire Companies that are Engaged in Permissible Nonbanking Activities</SUBJECT>
                <P>
                    The companies listed in this notice have given notice under section 4 of the Bank Holding Company Act (12 U.S.C. 1843) (BHC Act) and Regulation Y (12 CFR Part 225) to engage 
                    <E T="03">de novo</E>
                    , or to acquire or control voting securities or assets of a company, including the companies listed below, that engages either directly or through a subsidiary or other company, in a nonbanking activity that is listed in § 225.28 of Regulation Y (12 CFR 225.28) or that the Board has determined by Order to be closely 
                    <PRTPAGE P="68086"/>
                    related to banking and permissible for bank holding companies.  Unless otherwise noted, these activities will be conducted throughout the United States.
                </P>
                <P>
                    Each notice is available for inspection at the Federal Reserve Bank indicated.  The notice also will be available for inspection at the offices of the Board of Governors.  Interested persons may express their views in writing on the question whether the proposal complies with the standards of section 4 of the BHC Act.  Additional information on all bank holding companies may be obtained from the National Information Center website at 
                    <E T="03">www.ffiec.gov/nic/</E>
                    .
                </P>
                <P>Unless otherwise noted, comments regarding the applications must be received at the Reserve Bank indicated or the offices of the Board of Governors not later than December 19, 2003.</P>
                <P>
                    <E T="04">A.  Federal Reserve Bank of Kansas City</E>
                     (James Hunter, Assistant Vice President) 925 Grand Avenue, Kansas City, Missouri 64198-0001:
                </P>
                <P>
                    <E T="03">1.  Exchange Company</E>
                    , Gibbon, Nebraska; to acquire 100 percent of the voting shares of Ace Sales, Inc., Deshler, Nebraska, and thereby engage in lending activities, pursuant to Section 225.28(b)(1) of Regulation Y.
                </P>
                <SIG>
                    <P>Board of Governors of the Federal Reserve System, December 1, 2003.</P>
                    <NAME>Robert deV. Frierson,</NAME>
                    <TITLE>Deputy Secretary of the Board.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc.03-30214 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 6210-01-S</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Centers for Disease Control and Prevention</SUBAGY>
                <DEPDOC>[60Day-04-10]</DEPDOC>
                <SUBJECT>Proposed Data Collections Submitted for Public Comment and Recommendations</SUBJECT>
                <P>In compliance with the requirement of section 3506(c)(2)(A) of the Paperwork Reduction Act of 1995 for opportunity for public comment on proposed data collection projects, the Centers for Disease Control and Prevention (CDC) will publish periodic summaries of proposed projects. To request more information on the proposed projects or to obtain a copy of the data collection plans and instruments, call the CDC Reports Clearance Officer on (404) 498-1210.</P>
                <P>Comments are invited on: (a) Whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information shall have practical utility; (b) the accuracy of the agency's estimate of the burden of the proposed collection of information; (c) ways to enhance the quality, utility, and clarity of the information to be collected; and (d) ways to minimize the burden of the collection of information on respondents, including through the use of automated collection techniques or other forms of information technology. Send comments to Anne O'Connor, CDC Assistant Reports Clearance Officer, 1600 Clifton Road, MS-D24, Atlanta, GA 30333. Written comments should be received within 60 days of this notice.</P>
                <P>
                    <E T="03">Proposed Project:</E>
                     Jail STD Prevalence Monitoring System, OMB No. 0920-0499—Revision—National Center for HIV, STD's and Tuberculosis (NCHSTP), Centers for Disease Control and Prevention (CDC).
                </P>
                <P>CDC is requesting from Office of Management and Budget (OMB) a 3-year approval for the standardized record layout for the Jail STD Prevalence Monitoring System. The Jail STD Prevalence Monitoring System consists of test data compiled for persons entering corrections facilities. The standard data elements were created in response to the need to systematically assess morbidity in persons entering corrections facilities, who are at high risk for STDs or sexually transmitted diseases and who often do not seek medical care in mainstream medical settings. Use of these standard data elements will improve surveillance of STDs by allowing for systematic assessment of a high risk population, taking advantage of already computerized data.</P>
                <P>States that compile data from corrections facilities are encouraged to participate in the system. In most places, STD test results for persons in corrections facilities are computerized by the laboratory or by the health department. The burden of compiling data in the standardized format involves running a computer program to convert the data to the specified format. This involves an initial investment of time by a programmer but afterwards involves only running the program once a quarter (average of 3 hours per quarter). Therefore, the respondent burden is approximately 12 hours per year.</P>
                <P>If a respondent does not have computerized test results for persons in corrections facilities, and must enter the data, the burden of data-entry is approximately 1.5 minute per record. On an average a respondent will enter approximately 1250 records per quarter, which will result in a total burden of 1875 minutes or 31 hours per quarter.</P>
                <P>During the next 3 years, CDC expects approximately 20 project areas per year to participate. Approximately 15 will have already computerized data for a burden of 180 hours (15x12hrs) per year and five respondents will have to enter data into a computerized database which will result in a burden of 620 additional hours (5x124 hrs) per year. The total estimated annualized burden is 880 hours per year.</P>
                <GPOTABLE COLS="5" OPTS="L2" CDEF="tp0,i1,s100,12,12,12,12">
                    <TTITLE>  </TTITLE>
                    <BOXHD>
                        <CHED H="1">Respondents </CHED>
                        <CHED H="1">
                            No. of respondents 
                            <LI>(STD project areas) </LI>
                        </CHED>
                        <CHED H="1">
                            No. of responses/respondent 
                            <LI>(datasets/yr approx 5000 total records) </LI>
                        </CHED>
                        <CHED H="1">
                            Average burden/response 
                            <LI>(in hours) </LI>
                        </CHED>
                        <CHED H="1">
                            Total burden 
                            <LI>(in hours) </LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">State/local health departments with computerized data</ENT>
                        <ENT>15</ENT>
                        <ENT>4</ENT>
                        <ENT>3</ENT>
                        <ENT>180 </ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">State/local health departments without computerized data</ENT>
                        <ENT>5</ENT>
                        <ENT>4</ENT>
                        <ENT>31</ENT>
                        <ENT>620 </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="03">Total</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT/>
                        <ENT>880 </ENT>
                    </ROW>
                </GPOTABLE>
                <SIG>
                    <PRTPAGE P="68087"/>
                    <DATED>Dated: November 25, 2003.</DATED>
                    <NAME>Laura Yerdon Martin,</NAME>
                    <TITLE>Acting Director, Executive Secretariat, Centers for Disease Control and Prevention.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30257 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4163-18-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Centers for Disease Control and Prevention (CDC)</SUBAGY>
                <SUBJECT>National Center on Birth Defects and Developmental Disabilities</SUBJECT>
                <P>
                    <E T="03">Name:</E>
                     Scientific Workshop on Impact of Maternal Thyroid Disease on the Developing Fetus: Implications for Diagnosis, Treatment, and Screening.
                </P>
                <P>
                    <E T="03">Times and Dates:</E>
                     8 a.m.-7:30 p.m., January 12, 2004. 8 a.m.-4 p.m., January 13, 2004.
                </P>
                <P>
                    <E T="03">Place:</E>
                     Renaissance Atlanta Hotel Downtown, 590 West Peachtree Street, NW., Atlanta, Georgia 30308-3586, Telephone (404) 881-6000.
                </P>
                <P>
                    <E T="03">Status:</E>
                     Open to the public, limited only by the space available.
                </P>
                <P>
                    <E T="03">Purpose:</E>
                     The purpose of the workshop is to summarize the body of scientific evidence, describe the gaps in knowledge, provide direction for future research, and offer guidance for appropriate public health action if warranted.
                </P>
                <P>
                    <E T="03">Matters To Be Discussed:</E>
                     The agenda will include an overview of the prevalence of thyroid dysfunction in reproductive-age women and factors associated with abnormal function, outcomes related to thyroid dysfunction during pregnancy, detection and treatment of thyroid dysfunction, and considerations for public health practice.
                </P>
                <P>Agenda items may be subject to change as priority dictates.</P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Micah H. Milton, Health Scientist, National Center on Birth Defects and Developmental Disabilities, CDC, 1600 Clifton Road, NE., m/s E-87, Atlanta, Georgia 30333. Telephone 404/498-3082.</P>
                    <P>
                        The Director, Management Analysis and Services Office, has been delegated the authority to sign 
                        <E T="04">Federal Register</E>
                         notices pertaining to announcements of meetings and other committee management activities for both CDC and the Agency for Toxic Substances and Disease Registry.
                    </P>
                    <SIG>
                        <DATED>Dated: December 1, 2003.</DATED>
                        <NAME>Joseph E. Salter,</NAME>
                        <TITLE>Acting Director, Management Analysis and Services Office, Centers for Disease Control and Prevention.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30216 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4163-18-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Centers for Medicare and Medicaid Services</SUBAGY>
                <DEPDOC>[Document Identifier: CMS-R-53; CMS-10102]</DEPDOC>
                <SUBJECT>Agency Information Collection Activities: Proposed Collection; Comment Request</SUBJECT>
                <P>
                    <E T="03">Agency:</E>
                     Centers for Medicare and Medicaid Services, HHS.
                </P>
                <P>In compliance with the requirement of section 3506(c)(2)(A) of the Paperwork Reduction Act of 1995, the Centers for Medicare and Medicaid Services (CMS) (formerly known as the Health Care Financing Administration (HCFA)), Department of Health and Human Services, is publishing the following summary of proposed collections for public comment. Interested persons are invited to send comments regarding this burden estimate or any other aspect of this collection of information, including any of the following subjects: (1) The necessity and utility of the proposed information collection for the proper performance of the agency's functions; (2) the accuracy of the estimated burden; (3) ways to enhance the quality, utility, and clarity of the information to be collected; and (4) the use of automated collection techniques or other forms of information technology to minimize the information collection burden.</P>
                <P>
                    1. 
                    <E T="03">Type of Information Collection Request:</E>
                     Extension of a currently approved collection; 
                    <E T="03">Title of Information Collection:</E>
                     Imposition of Cost Sharing Charges Under Medicaid and Supporting Regulations contained in 42 CFR 447.53; 
                    <E T="03">Form No.:</E>
                     CMS-R-53 (OMB# 0938-0429); 
                    <E T="03">Use:</E>
                     The information collection requirements contained in 42 CFR 447.53 require the States to include in their Medicaid State Plan their cost sharing provisions for the medically and categorically needy. The State Plan is the method in which States inform staff of State policies, standards, procedures and instructions; 
                    <E T="03">Frequency:</E>
                     Occasionally; 
                    <E T="03">Affected Public:</E>
                     State, local or tribal government; 
                    <E T="03">Number of Respondents:</E>
                     54; 
                    <E T="03">Total Annual Responses:</E>
                     20; 
                    <E T="03">Total Annual Hours:</E>
                     2,700.
                </P>
                <P>
                    2. 
                    <E T="03">Type of Information Collection Request:</E>
                     New collection; 
                    <E T="03">Title of Information Collection:</E>
                     National Implementation of Hospital CAHPS (HCAHPS); 
                    <E T="03">Form No.:</E>
                     CMS-10102 (OMB# 0938-NEW); 
                    <E T="03">Use:</E>
                     The HCAHPS survey instrument, developed under the CAHPS umbrella, is a reliable and valid instrument that any organization can use (at no cost) to obtain patient data about hospital experiences. This tool will be adopted by the Quality Initiative: A Public Resource on Hospital Performance. Though the main purposes of this survey are consumer choice and hospital accountability, we intend and expect that the collection and reporting of these data will stimulate quality improvements. A standardized hospital survey from the patient's perspective will generate both universal measures and comparative data for consumers who need to select a hospital, and a new incentive for hospitals to further improve quality of care and accountability. This standardized instrument will allow consumers to make “apples to apples” comparisons among hospitals, allow hospitals and hospital chains to self compare, and provide state oversight officials with useful data; 
                    <E T="03">Frequency:</E>
                     Annually; 
                    <E T="03">Affected Public:</E>
                     Individuals or households; 
                    <E T="03">Number of Respondents:</E>
                     2,212,000; 
                    <E T="03">Total Annual Responses:</E>
                     2,212,000; 
                    <E T="03">Total Annual Hours:</E>
                     368,367.
                </P>
                <P>
                    To obtain copies of the supporting statement and any related forms for the proposed paperwork collections referenced above, access CMS's Web site address at 
                    <E T="03">http://cms.hhs.gov/regulations/pra/default.asp,</E>
                     or E-mail your request, including your address, phone number, OMB number, and CMS document identifier, to 
                    <E T="03">Paperwork@hcfa.gov,</E>
                     or call the Reports Clearance Office on (410) 786-1326. Written comments and recommendations for the proposed information collections must be mailed within 60 days of this notice directly to the CMS Paperwork Clearance Officer designated at the following address: CMS, Office of Strategic Operations and Regulatory Affairs, Division of Regulations Development and Issuances, Attention: Melissa Musotto, Room C5-14-03, 7500 Security Boulevard, Baltimore, Maryland 21244-1850.
                </P>
                <SIG>
                    <PRTPAGE P="68088"/>
                    <DATED>Dated: November 26, 2003.</DATED>
                    <NAME>Julie Brown,</NAME>
                    <TITLE>Acting, Reports Clearance Officer, Office of Strategic Operations and Strategic Affairs, Division of Regulations Development and Issuances.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30200 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4120-03-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health </SUBAGY>
                <SUBJECT>National Heart, Lung, and Blood Institute (NHLBI): Opportunity for Cooperative Research and Development Agreements (CRADAs) To Develop Novel Mechanical and Biological Treatments in Interventional Cardiovascular Medicine Using X-Ray Fluoroscopy and/or Real-Time Magnetic Resonance Imaging</SUBJECT>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The National Heart, Lung, and Blood Institute (NHLBI) of the National Institutes of Health (NIH) announces the opportunity for Cooperative Research and Development Agreements (CRADAs) to develop novel mechanical and biological treatments in interventional cardiovascular medicine using x-ray fluoroscopy and real-time magnetic resonance imaging. The NHLBI seeks potential Collaborators wishing to provide expertise in (1) novel biological treatments for cardiovascular disease, including agents to facilitate mobilization of bone-marrow-derived stem and progenitor cells, (2) novel agents for therapeutic angiogenesis for myocardial or peripheral artery applications, (3) novel immune-modulating agents to treat to prevent manifestations of atherosclerosis, coronary artery occlusion, or myocardial ischemia/infarction, (4) novel mechanisms of drug, gene, or cell delivery to the myocardium or skeletal muscle to treat manifestations of coronary or peripheral artery atherosclerosis, and (5) intravascular devices for real-time magnetic resonance imaging-guided treatments including but not limited to angioplasty balloons, recanalization systems, percutaneous cardiac valves, stents, endografts, and bypass grafts.</P>
                    <P>The NHLBI seeks capability statements from parties interested in entering into a potential CRADA to manufacture, prototype, and test the above-specified agents or devices leading to early clinical testing and development. The availability of private sector support may increase the feasibility of particular aspects of the final design, but the primary criterion for selecting potential collaborators is the scientific merit of proposals for developing a plan to identify novel putative therapeutic agents and devices.</P>
                    <P>The NHLBI can provide extensive preclinical and clinical support in the development of Collaborator deliverables, including animal experiments, advanced x-ray fluoroscopic and magnetic resonance imaging laboratories, and investigations conducted in the Warren G. Magnuson Clinical Center at the Bethesda campus of the National Institutes of Health.</P>
                    <P>The control of clinical trials shall reside entirely with the Institute and the scientific participants of the trial. In the event that any adverse effects are encountered which, for legal or ethical reasons, may require communication with the U.S. Food and Drug Administration, the relevant collaborating institutions will be notified. Neither the conduct of the trial nor the results should be represented as an NHLBI endorsement of the agent, drug, or device under study.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Only written CRADA capability statements received by the NHLBI within 21 days of publication of this notice will be considered during the initial design phase. Confidential information must be clearly labeled. Potential collaborators may be invited to meet with the Selection Committee at the Collaborators' expense to provide additional information. The Institute may issue an additional notice of CRADA opportunity during the design phase if circumstances change or if the design alters substantially.</P>
                    <P>
                        <E T="03">For Additonal Information and Questions:</E>
                         Capability statements should be submitted to Ms. Peg Koelble, Office of Technology Transfer and Development, National Heart, Lung, and Blood Institute, National Institutes of Health, 6705 Rockledge Drive, Suite 6018, Bethesda, MD 20892-7992; Tel: 301-594-4095; Fax: 301-594-3080; email: 
                        <E T="03">koelblep@nhlbi.nih.gov.</E>
                    </P>
                    <P>
                        <E T="03">Capability Statements:</E>
                         A Selection Committee will use the information provided in the “Collaborator Capability Statements” received in response to this announcement to help in its deliberations. It is the intention of the NHLBI that all qualified Collaborators have the opportunity to provide information to the Selection Committee through their capability statements. The Capability Statement should not exceed 10 pages and should address the following selection criteria:
                    </P>
                    <P>1. The statement should provide specific details of the method to be used in the development of novel candidate biological treatments, delivery systems, or real-time MRI-guided mechanical treatments for cardiovascular disease.</P>
                    <P>2. The statement should include a detailed plan demonstrating the ability to provide sufficient capacity in drug, gene, or stem cell development and manufacturing or in mechanical device prototyping, testing, development, and manufacturing.</P>
                    <P>3. The statement may include outline measures of interest to the Collaborator. The specifics of the proposed outcome measures and the proposed support should include but not be limited to: expertise in the proposed field, specific personnel allocation to the proposed collaboration, specific internal or external funding commitment to support the advancement of scientific research, services, facilities, equipment, or other resources that would contribute to the conduct of the commerical development.</P>
                    <P>
                        4. The statement must address willingness promptly to publish research results and ability to be bound by PHS intellectual property policies (
                        <E T="03">see</E>
                         CRADA: 
                        <E T="03">http://ott.od.nih.gov/newpages/crada.pdf</E>
                        ).
                    </P>
                </DATES>
                <SIG>
                    <DATED>Dated: November 26, 2003.</DATED>
                    <NAME>Carl Roth,</NAME>
                    <TITLE>Associate Director for Scientific Program Operation, National Heart, Lung, and Blood Institute.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30206  Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>Government-Owned Inventions; Availability for Licensing</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Institutes of Health, Public Health Service, DHHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The inventions listed below are owned by an agency of the U.S. Government and are available for licensing in the U.S. in accordance with 35 U.S.C. 207 to achieve expeditious commercialization of results of federally-funded research and development. Foreign patent applications are filed on selected inventions to extend market coverage for companies and may also be available for licensing.</P>
                </SUM>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Licensing information and copies of the U.S. patent applications listed below may be obtained by writing to the indicated licensing contact at the Office of Technology Transfer, National Institutes of Health, 6011 Executive 
                        <PRTPAGE P="68089"/>
                        Boulevard, Suite 325, Rockville, Maryland 20852-3804; telephone: (301) 496-7057; fax: (301) 402-0220. A signed Confidential Disclosure Agreement will be required to receive copies of the patent applications.
                    </P>
                </ADD>
                <HD SOURCE="HD1">Methods of Preparing Lymphocytes That Express Interleukin-2 and Their Use in the Treatment of Cancer</HD>
                <FP SOURCE="FP-1">Ke Liu and Steven Rosenberg (NCI).</FP>
                <FP SOURCE="FP-1">PCT Application No. PCT/US02/33243 filed 15 Oct 2002 (DHHS Reference No. E-297-2002/0-PCT-01).</FP>
                <FP SOURCE="FP-1">
                    <E T="03">Licensing Contact:</E>
                     Jeffrey Walenta; 301/435-4633; 
                    <E T="03">walentaj@mail.nih.gov.</E>
                </FP>
                <P>Adoptive immunotherapy strategies are highly dependent upon a sustained immune response to a tumor specific antigen. An effective adoptive strategy should ideally recruit and integrate into the existing components of a cancer patient's inherent immune system. However, most cancer patient's immune systems are unable to sustain the expansion of introduced tumor specific T-cells and hence cannot sustain a tumor specific response. Interleukin 2 (IL-2) is a natural cytokine that will promote the growth and expansion of introduced tumor specific T cells. Unfortunately, supplementing a patient's immune system with the systemic introduction of IL-2 has severe toxicity effects at a dose sufficient to promote T-cell growth, limiting the effectiveness of many adoptive strategies.</P>
                <P>
                    This invention relates to methods of preparing autologous T-lymphocytes and tumor-infiltrating lymphocytes that express IL-2. This method comprises the following steps: obtaining peripheral blood mononuclear cells (PBMC) or tumor infiltrating lymphocytes (TIL) from a patient immunized with an antigen of cancer; stimulating the PBMC's or TIL with the antigen of the cancer 
                    <E T="03">in vitro</E>
                    ; transducing the PBMC's or TIL with a retroviral vector encoding IL-2; and reintroducing these autologous T-lymphocytes back into the patient. This method overcomes the potential toxicity issues from systemic IL-2 delivery and creates self-sufficient T-cells for an effective adoptive immunotherapy response.
                </P>
                <HD SOURCE="HD1">Catalytic Domains of β(1,4)-galactosyltransferase I Having Altered Donor and Acceptor Specificities, Domains That Promote In Vitro Protein Folding, and Methods for Their Use</HD>
                <FP SOURCE="FP-1">Pradman Qasba (NCI), Boopathy Ramakrishnan (NCI), Elizabeth Boeggeman (NCI).</FP>
                <FP SOURCE="FP-1">U.S. Provisional Application No. 60/439,298 filed 10 Jan 2003 (DHHS Reference No. E-230-2002/0-US-01); U.S. Provisional Application No. 60/450,250 filed 23 Feb 2003 (DHHS Reference No. E-230-2002/1-US-01).</FP>
                <FP SOURCE="FP-1">
                    <E T="03">Licensing Contact:</E>
                     Peter Soukas; 301/435-4646; 
                    <E T="03">soukasp@mail.nih.gov</E>
                    .
                </FP>
                <P>β(1,4)-galactosyltransferase I catalyzes the transfer of galactose from the donor, UDP-galactose, to an acceptor, N-acetylglucosamine, to form a galactose-β(1,4)-N-acetylglucosamine bond. This reaction allows galactose to be linked to an N-acetylglucosamine that may itself be linked to a variety of other molecules. The reaction can be used to make many types of molecules having great biological significance. For example, galactose-β(1,4)-N-acetylglucosamine linkages are very important for cellular recognition and binding events as well as cellular interactions with pathogens, such as viruses. Therefore, methods to synthesize these types of bonds have many applications in research and medicine to develop pharmaceutical agents and improved vaccines that can be used to treat disease.</P>
                <P>The present invention is based on the surprising discovery that the enzymatic activity of β(1,4)-galactosyltransferase can be altered such that the enzyme can make chemical bonds that are very difficult to make by other methods. These alterations involve mutating the enzyme such that the mutated enzyme can transfer many different types of sugars from sugar nucleotide donors to many different types of acceptors. Therefore, the mutated β(1,4)-galactosyltransferases of the invention can be used to synthesize a variety of products that, until now, have been very difficult and expensive to produce.</P>
                <P>The invention also provides amino acid segments that promote the proper folding of a galactosyltransferase catalytic domain. The amino acid segments may be used to properly fold the galactosyltransferase catalytic domains of the invention and thereby increase their activity. The amino acid segments may also be used to increase the activity of galactosyltransferases that are produced recombinantly. Accordingly, use of the amino acid segments according to the invention allows for production of β(1,4)-galactosyltransferases having increased enzymatic activity relative to β(1,4)-galactosyltransferases produced in the absence of the amino acid segments.</P>
                <P>Some of the many uses for this invention are the following: synthesis of polysaccharide antigens for conjugate vaccines, glycosylation of monoclonal antibodies, and as research tools.</P>
                <HD SOURCE="HD1">Targeting of the Hepatitis A Cellular Receptor To Treat Renal Cancer</HD>
                <P>Gerardo Kaplan (FDA).</P>
                <FP SOURCE="FP-1">U.S. Provisional Patent Application No. 60/442,286 filed 24 Jan 24 2003 (DHHS Reference No. E-227-2002/0-US-01).</FP>
                <FP SOURCE="FP-1">
                    <E T="03">Licensing Contact:</E>
                     Brenda Hefti; (301) 435-4632; 
                    <E T="03">heftib@mail.nih.gov</E>
                    .
                </FP>
                <P>Tumor markers—receptors on the cell surface that are expressed preferentially in tumor cells—are extremely useful in the diagnosis and treatment of cancers. The inventors have discovered that hHAVcr-1 is such a tumor marker because it is overexpressed in renal cell carcinomas, and its degree of overexpression is correlated to the stage of the tumor. In addition, overexpression of this receptor appears to affect differentiation.</P>
                <P>The inventors have also demonstrated that they can target this receptor specifically in vitro, using monoclonal antibodies tagged with toxins and hepatitis A virus vectors. This discovery might be useful as a tumor marker or for gene-based therapeutics. Antibodies against the receptor encoded by hHAVcr-1 might be useful in an antibody-based therapeutic for the treatment of renal cancer.</P>
                <HD SOURCE="HD1">Novel 2-Alkoxy Estradiols and Derivatives Thereof</HD>
                <P>Ravi Varma (NCI).</P>
                <FP SOURCE="FP-1">U.S. Patent Application No. 09/041,212 filed on 12 Mar 1998, which issued as U.S. Patent 6,136,992 on 24 October 2000 (DHHS Reference No. E-188-1998/1-US-01); U.S. Provisional Application No. 60/040,540 filed 13 Mar 1997 (DHHS Reference No. E-188-1998/0-US-01).</FP>
                <FP SOURCE="FP-1">
                    <E T="03">Licensing Contact:</E>
                     George Pipia; 301/435-5560; 
                    <E T="03">pipiag@mail.nih.gov</E>
                    .
                </FP>
                <P>The present invention is directed to novel 2-alkoxy estradiols and derivatives of 2-alkoxy estradiols having anticancer activity as claimed in the U.S. Patent 6,136,992. The invention is also directed to methods of preparing these novel compounds. These compounds have improved activity against a wide variety of tumor cell lines, including lung, colon, central nervous system, melanoma, ovarian, renal, prostate and breast cancers, compared with 2-methoxy estradiols. It is expected that these compounds will be very useful in the treatment of a wide variety of cancers. In addition, the present compounds have a low affinity for the estrogen receptor and are, therefore, expected to have fewer side effects than estradiols.</P>
                <SIG>
                    <PRTPAGE P="68090"/>
                    <DATED>Dated: November 25, 2003.</DATED>
                    <NAME>Steven M. Ferguson,</NAME>
                    <TITLE>Director, Division of Technology Development and Transfer, Office of Technology Transfer, National Institutes of Health.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30207 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>National Institute of Diabetes and Digestive and Kidney Disease; Amended Notice of Meeting</SUBJECT>
                <P>Notice is hereby given of a change in the meeting of the National Institute of Diabetes and Digestive and Kidney Diseases Special Emphasis Panel, November 25, 2003, 9 a.m. to November 25, 2003, 11 a.m. National Institutes of Health, Two Democracy Plaza, 6707 Democracy Boulevard, Bethesda, MD, 20892 which was published in the Federal Register on October 31, 2003, 68 FR 62902.</P>
                <P>The meeting will be held on December 18, 2003 from 3 p.m. until 5 p.m. The meeting is closed to the public.</P>
                <SIG>
                    <DATED>Dated: November 28, 2003.</DATED>
                    <NAME>Anna Snouffer,</NAME>
                    <TITLE>Acting Director, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30202 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>National Institute of Diabetes and Digestive and Kidney Diseases; Notice of Closed Meeting</SUBJECT>
                <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. Appendix 2), notice is hereby given of the following meeting.</P>
                <P>The meeting will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal property.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute of Diabetes and Digestive Kidney Diseases Special Emphasis Panel, Chronic Kidney Disease.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         December 12, 2003.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         3 p.m. to 4:30 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, Two Democracy Plaza, 6707 Democracy Boulevard, Bethesda, MD 20892, (Telephone Conference Call).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Lakshmanan Sankaran, PhD, Scientific Review Administrator, Review Branch, DEA, NIDDK, National Institutes of Health, Room 754, 6707 Democracy Boulevard, Bethesda, MD 20892, (301) 594-7799, 
                        <E T="03">ls38z@nih.gov.</E>
                    </P>
                    <P>This notice is being published less than 15 days prior to the meeting due to the timing limitations imposed by the review and funding cycle.</P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.847, Diabetes, Endocrinology and Metabolic Research; 93.848, Digestive Diseases and Nutrition Research; 93.849, Kidney Diseases, Urology and Hermatology Research, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: November 28, 2003.</DATED>
                    <NAME>Anna Snouffer,</NAME>
                    <TITLE>Acting Director, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30203  Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>National Institute of Mental Health; Notice of Closed Meeting</SUBJECT>
                <P>Pursuant to section 10(d) of the Federal Advisory Committee Act, as amended (5 U.S.C. appendix 2), notice is hereby given of the following meeting.</P>
                <P>The meeting will be closed to the public in accordance with the provisions set forth in sections 552b(c)(4) and 552b(c)(6), Title 5 U.S.C., as amended. The grant applications and the discussions could disclose confidential trade secrets or commercial property such as patentable material, and personal information concerning individuals associated with the grant applications, the disclosure of which would constitute a clearly unwarranted invasion of personal privacy.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Institute of Mental Health Special Emphasis Panel.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         December 10, 2003.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         10:30 a.m. to 1:30 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         To review and evaluate grant applications.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         National Institutes of Health, Neuroscience Center, 6001 Executive Boulevard, Rockville, MD 20852, (Telephone Conference Call).
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         David I. Sommers, PhD, Scientific Review Administrator, Division of Extramural Activities, National Institute of Mental Health, NIH, Neuroscience Center, 6001 Executive Blvd., Room 6144, MSC 9606, Bethesda, MD 20892-9606, 301-443-7861, 
                        <E T="03">dsommers@mail.nih.gov.</E>
                    </P>
                    <P>This notice is being published less than 15 days prior to the meeting due to the timing limitations imposed by the review and funding cycle.</P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.242, Mental Health Research Grants; 93.281, Scientist Development Award, Scientist Development Award for Clinicians, and Research Scientist Award; 93.282, Mental Health National Research Service Awards for Research Training, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: November 28, 2003.</DATED>
                    <NAME>Anna P. Snouffer,</NAME>
                    <TITLE>Acting Director, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30204  Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>National Institute of Child Health and Human Development; Notice of Meeting</SUBJECT>
                <P>Pursuant to section 10(a) of the Federal Advisory Committee Act, as amended (5 U.S.C. Appendix 2), notice is hereby given of a meeting of the National Advisory Board on Medical Rehabilitation Research.</P>
                <P>The meeting will be open to the public with attendance limited to space available. Individuals who plan to attend and need special assistance, such as sign language interpretation or other reasonable accommodations, should notify the Contact Person listed below in advance of the meeting.</P>
                <EXTRACT>
                    <P>
                        <E T="03">Name of Committee:</E>
                         National Advisory Board on Medical Rehabilitation Research.
                    </P>
                    <P>
                        <E T="03">Date:</E>
                         December 8-9, 2003.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         December 8, 2003, 8:30 a.m. to 5 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         NICHD Director's Report presentation, Regional Research Networks, and an update on the Rehabilitation Medicine Scientist Training Program.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Holiday Inn—Silver Spring, 8777 Georgia Avenue, Silver Spring, MD 20910.
                    </P>
                    <P>
                        <E T="03">Time:</E>
                         December 9, 2003, 8:30 a.m. to 12 p.m.
                    </P>
                    <P>
                        <E T="03">Agenda:</E>
                         Other business dealing with the NABMRR Board.
                    </P>
                    <P>
                        <E T="03">Place:</E>
                         Holiday Inn—Silver Spring, 8777 Georgia Avenue, Silver Spring, MD 20910.
                    </P>
                    <P>
                        <E T="03">Contact Person:</E>
                         Ralph M. Nitkin, PhD, Director, BSCD, National Center for Medical Rehabilitation Research, National Institute of Child Health and Human Development, NIH, 6100 Building, Room 2A03, Bethesda, MD 20892, (301) 402-4206.
                    </P>
                    <P>
                        This notice is being published less than 15 days prior to the meeting due to the timing 
                        <PRTPAGE P="68091"/>
                        limitations imposed by the review and funding cycle.
                    </P>
                    <P>In the interest of security, NIH has instituted stringent procedures for entrance into the building by non-government employees. Persons without a government I.D. will need to show a photo I.D. and sign-in at the security desk upon entering the building.</P>
                    <P>
                        Information is also available on the Institute's/Center's Home page: 
                        <E T="03">http://www.nichd.nih.gov/about/ncmrr.htm,</E>
                         where an agenda and any additional information for the meeting will be posted when available.
                    </P>
                    <FP>(Catalogue of Federal Domestic Assistance Program Nos. 93.864, Population Research; 93.865, Research for Mothers and Children; 93.929, Center for Medical Rehabilitation Research; 93.209, Contraception and Infertility Loan Repayment Program, National Institutes of Health, HHS)</FP>
                </EXTRACT>
                <SIG>
                    <DATED>Dated: November 28, 2003.</DATED>
                    <NAME>Anna P. Snouffer,</NAME>
                    <TITLE>Acting Director, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30205  Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>National Institutes of Health</SUBAGY>
                <SUBJECT>Center for Scientific Review; Amended Notice of Meeting</SUBJECT>
                <P>
                    Notice is hereby given of a change in the meeting of the Center for Scientific Review Special Emphasis Panel, December 18, 2003, 1 p.m. to December 18, 2003, 3 p.m., National Institutes of Health, 6701 Rockledge Drive, Bethesda, MD 20892 which was published in the 
                    <E T="04">Federal Register</E>
                     on November 26, 2003, 68 FR 66471-66472.
                </P>
                <P>The meeting will be held on December 19, 2003, from 5 p.m. to 7 p.m. The location remains the same. The meeting is closed to the public.</P>
                <SIG>
                    <DATED>Dated: November 28, 2003.</DATED>
                    <NAME>Anna Snouffer,</NAME>
                    <TITLE>Acting Director, Office of Federal Advisory Committee Policy.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30201  Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4140-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HEALTH AND HUMAN SERVICES</AGENCY>
                <SUBAGY>Substance Abuse and Mental Health Services Administration</SUBAGY>
                <SUBJECT>Current List of Laboratories Which Meet Minimum Standards To Engage in Urine Drug Testing for Federal Agencies</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Substance Abuse and Mental Health Services Administration, HHS.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Department of Health and Human Services (HHS) notifies Federal agencies of the laboratories currently certified to meet the standards of subpart C of the Mandatory Guidelines for Federal Workplace Drug Testing Programs (Mandatory Guidelines) published in the 
                        <E T="04">Federal Register</E>
                         on April 11, 1988 (53 FR 11970), and revised in the 
                        <E T="04">Federal Register</E>
                         on June 9, 1994 (59 FR 29908) and on September 30, 1997 (62 FR 51118). A notice listing all currently certified laboratories is published in the 
                        <E T="04">Federal Register</E>
                         during the first week of each month. If any laboratory's certification is suspended or revoked, the laboratory will be omitted from subsequent lists until such time as it is restored to full certification under the Mandatory Guidelines.
                    </P>
                    <P>If any laboratory has withdrawn from HHS’ National Laboratory Certification Program (NLCP) during the past month, it will be listed at the end, and will be omitted from the monthly listing thereafter.</P>
                    <P>
                        This notice is also available on the Internet at 
                        <E T="03">http://workplace.samhsa.gov</E>
                         and 
                        <E T="03">http://www.drugfreeworkplace.gov.</E>
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Mrs. Giselle Hersh or Dr. Walter Vogl, Division of Workplace Programs, 5600 Fishers Lane, Rockwall 2, Room 815, Rockville, Maryland 20857; 301-443-6014 (voice), 301-443-3031 (fax).</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Mandatory Guidelines were developed in accordance with Executive Order 12564 and section 503 of Public Law 100-71. Subpart C of the Guidelines, “Certification of Laboratories Engaged in Urine Drug Testing for Federal Agencies,” sets strict standards that laboratories must meet in order to conduct urine drug testing for Federal agencies. To become certified, an applicant laboratory must undergo three rounds of performance testing plus an on-site inspection.</P>
                <P>To maintain that certification, a laboratory must participate in a quarterly performance testing program plus periodic, on-site inspections.</P>
                <P>Laboratories which claim to be in the applicant stage of certification are not to be considered as meeting the minimum requirements expressed in the HHS Mandatory Guidelines. A laboratory must have its letter of certification from HHS/SAMHSA (formerly: HHS/NIDA) which attests that it has met minimum standards.</P>
                <P>In accordance with Subpart C of the Mandatory Guidelines, the following laboratories meet the minimum standards set forth in the Mandatory Guidelines:</P>
                <FP SOURCE="FP-1">ACL Laboratories, 8901 W. Lincoln Ave., West Allis, WI 53227, 414-328-7840/800-877-7016, (Formerly: Bayshore Clinical Laboratory)</FP>
                <FP SOURCE="FP-1">ACM Medical Laboratory, Inc., 160 Elmgrove Park, Rochester, NY 14624, 585-429-2264</FP>
                <FP SOURCE="FP-1">Advanced Toxicology Network, 3560 Air Center Cove, Suite 101, Memphis, TN 38118, 901-794-5770/888-290-1150</FP>
                <FP SOURCE="FP-1">Aegis Analytical Laboratories, Inc., 345 Hill Ave., Nashville, TN 37210, 615-255-2400,</FP>
                <FP SOURCE="FP-1">Alliance Laboratory Services, 3200 Burnet Ave., Cincinnati, OH 45229, 513-585-6870, (Formerly: Jewish Hospital of Cincinnati, Inc.)</FP>
                <FP SOURCE="FP-1">Baptist Medical Center-Toxicology Laboratory, 9601 I-630, Exit 7, Little Rock, AR 72205-7299, 501-202-2783, (Formerly: Forensic Toxicology Laboratory Baptist Medical Center)</FP>
                <FP SOURCE="FP-1">Clinical Reference Lab, 8433 Quivira Rd., Lenexa, KS 66215-2802, 800-445-6917</FP>
                <FP SOURCE="FP-1">Diagnostic Services Inc., dba DSI, 12700 Westlinks Dr., Fort Myers, FL 33913, 239-561-8200/800-735-5416</FP>
                <FP SOURCE="FP-1">DrugProof, Division of Dynacare/Laboratory of Pathology, LLC 1229 Madison St., Suite 500, Nordstrom Medical Tower, Seattle, WA 98104, 206-386-2661/800-898-0180, (Formerly: Laboratory of Pathology of Seattle, Inc., DrugProof, Division of Laboratory of Pathology of Seattle, Inc.)</FP>
                <FP SOURCE="FP-1">DrugScan, Inc., P.O. Box 2969, 1119 Mearns Rd., Warminster, PA 18974, 215-674-9310</FP>
                <FP SOURCE="FP-1">Dynacare Kasper Medical Laboratories,* 10150-102 St., Suite 200, Edmonton, Alberta, Canada T5J 5E2, 780-451-3702/800-661-9876</FP>
                <FP SOURCE="FP-1">ElSohly Laboratories, Inc., 5 Industrial Park Dr., Oxford, MS 38655, 662-236-2609</FP>
                <FP SOURCE="FP-1">Express Analytical Labs, 3405 7th Ave., Suite 106, Marion, IA 52302, 319-377-0500</FP>
                <FP SOURCE="FP-1">Gamma-Dynacare Medical Laboratories,* A Division of the Gamma-Dynacare Laboratory Partnership, 245 Pall Mall St., London, ON, Canada N6A 1P4, 519-679-1630</FP>
                <FP SOURCE="FP-1">General Medical Laboratories, 36 South Brooks St., Madison, WI 53715, 608-267-6225</FP>
                <FP SOURCE="FP-1">Kroll Laboratory Specialists, Inc., 1111 Newton St., Gretna, LA 70053, 504-361-8989/800-433-3823, (Formerly: Laboratory Specialists, Inc.)</FP>
                <PRTPAGE P="68092"/>
                <FP SOURCE="FP-1">LabOne, Inc., 10101 Renner Blvd., Lenexa, KS 66219, 913-888-3927/800-873-8845, (Formerly: Center for Laboratory Services, a Division of LabOne, Inc.)</FP>
                <FP SOURCE="FP-1">Laboratory Corporation of America Holdings, 7207 N. Gessner Rd., Houston, TX 77040, 713-856-8288/800-800-2387</FP>
                <FP SOURCE="FP-1">Laboratory Corporation of America Holdings, 69 First Ave., Raritan, NJ 08869, 908-526-2400/800-437-4986, (Formerly: Roche Biomedical Laboratories, Inc.)</FP>
                <FP SOURCE="FP-1">Laboratory Corporation of America Holdings, 1904 Alexander Dr., Research Triangle Park, NC 27709, 919-572-6900/800-833-3984, (Formerly: LabCorp Occupational Testing Services, Inc., CompuChem Laboratories, Inc.; CompuChem Laboratories, Inc., A Subsidiary of Roche Biomedical Laboratory; Roche CompuChem Laboratories, Inc., A Member of the Roche Group)</FP>
                <FP SOURCE="FP-1">Laboratory Corporation of America Holdings, 10788 Roselle St., San Diego, CA 92121, 800-882-7272, (Formerly: Poisonlab, Inc.)</FP>
                <FP SOURCE="FP-1">Laboratory Corporation of America Holdings, 1120 Stateline Rd. West, Southaven, MS 38671, 866-827-8042/800-233-6339, (Formerly: LabCorp Occupational Testing Services, Inc.; MedExpress/National Laboratory Center)</FP>
                <FP SOURCE="FP-1">Marshfield Laboratories, Forensic Toxicology Laboratory, 1000 North Oak Ave., Marshfield, WI 54449, 715-389-3734/800-331-3734</FP>
                <FP SOURCE="FP-1">MAXXAM Analytics Inc.,* 5540 McAdam Rd., Mississauga, ON, Canada L4Z 1P1, 905-890-2555, (Formerly: NOVAMANN (Ontario) Inc.)</FP>
                <FP SOURCE="FP-1">MedTox Laboratories, Inc., 402 W. County Rd. D, St. Paul, MN 55112, 651-636-7466/800-832-3244</FP>
                <FP SOURCE="FP-1">MetroLab-Legacy Laboratory Services, 1225 NE 2nd Ave., Portland, OR 97232, 503-413-5295/800-950-5295</FP>
                <FP SOURCE="FP-1">Minneapolis Veterans Affairs Medical Center, Forensic Toxicology Laboratory, 1 Veterans Dr., Minneapolis, MN 55417, 612-725-2088</FP>
                <FP SOURCE="FP-1">National Toxicology Laboratories, Inc., 1100 California Ave., Bakersfield, CA 93304, 661-322-4250/800-350-3515</FP>
                <FP SOURCE="FP-1">Northwest Drug Testing, a division of NWT Inc., 1141 E. 3900 S., Salt Lake City, UT 84124, 801-293-2300/800-322-3361, (Formerly: NWT Drug Testing, NorthWest Toxicology, Inc.)</FP>
                <FP SOURCE="FP-1">One Source Toxicology Laboratory, Inc., 1705 Center St., Deer Park, TX 77536, 713-920-2559, (Formerly: University of Texas Medical Branch, Clinical Chemistry Division; UTMB Pathology-Toxicology Laboratory)</FP>
                <FP SOURCE="FP-1">Oregon Medical Laboratories, P.O. Box 972, 722 East 11th Ave., Eugene, OR 97440-0972, 541-687-2134 </FP>
                <FP SOURCE="FP-1">Pacific Toxicology Laboratories, 9348 DeSoto Ave., Chatsworth, CA 91311, 800-328-6942, (Formerly: Centinela Hospital Airport Toxicology Laboratory)</FP>
                <FP SOURCE="FP-1">Pathology Associates Medical Laboratories, 110 West Cliff Dr., Spokane, WA 99204, 509-755-8991/800-541-7891, x8991</FP>
                <FP SOURCE="FP-1">PharmChem Laboratories, Inc. 4600 N. Beach, Haltom City, TX 76137, 817-605-5300, (Formerly: PharmChem Laboratories, Inc., Texas Division; Harris Medical Laboratory)</FP>
                <FP SOURCE="FP-1">Physicians Reference Laboratory, 7800 West 110th St., Overland Park, KS 66210, 913-339-0372/800-821-3627</FP>
                <FP SOURCE="FP-1">Quest Diagnostics Incorporated, 3175 Presidential Dr., Atlanta, GA 30340, 770-452-1590/800-729-6432, (Formerly: SmithKline Beecham Clinical Laboratories; SmithKline Bio-Science Laboratories) </FP>
                <FP SOURCE="FP-1">Quest Diagnostics Incorporated, 4770 Regent Blvd., Irving, TX 75063, 800-824-6152, (Moved from the Dallas location on 03/31/01; Formerly: SmithKline Beecham Clinical Laboratories; SmithKline Bio-Science Laboratories)</FP>
                <FP SOURCE="FP-1">Quest Diagnostics Incorporated, 4230 South Burnham Ave., Suite 250, Las Vegas, NV 89119-5412, 702-733-7866/800-433-2750, (Formerly: Associated Pathologists Laboratories, Inc.)</FP>
                <FP SOURCE="FP-1">Quest Diagnostics Incorporated, 400 Egypt Rd., Norristown, PA 19403, 610-631-4600/877-642-2216, (Formerly: SmithKline Beecham Clinical Laboratories; SmithKline Bio-Science Laboratories)</FP>
                <FP SOURCE="FP-1">Quest Diagnostics Incorporated, 506 E. State Pkwy., Schaumburg, IL 60173, 800-669-6995/847-885-2010, (Formerly: SmithKline Beecham Clinical Laboratories; International Toxicology Laboratories)</FP>
                <FP SOURCE="FP-1">Quest Diagnostics Incorporated, 7600 Tyrone Ave., Van Nuys, CA 91405, 818-989-2520/800-877-2520, (Formerly: SmithKline Beecham Clinical Laboratories)</FP>
                <FP SOURCE="FP-1">Scientific Testing Laboratories, Inc., 450 Southlake Blvd., Richmond, VA 23236, 804-378-9130</FP>
                <FP SOURCE="FP-1">Sciteck Clinical Laboratories, Inc., 317 Rutledge Rd., Fletcher, NC 28732, 828-650-0409</FP>
                <FP SOURCE="FP-1">S.E.D. Medical Laboratories, 5601 Office Blvd., Albuquerque, NM 87109, 505-727-6300/800-999-5227</FP>
                <FP SOURCE="FP-1">South Bend Medical Foundation, Inc., 530 N. Lafayette Blvd., South Bend, IN 46601, 574-234-4176 x276</FP>
                <FP SOURCE="FP-1">Southwest Laboratories, 2727 W. Baseline Rd., Tempe, AZ 85283, 602-438-8507/800-279-0027</FP>
                <FP SOURCE="FP-1">Sparrow Health System, Toxicology Testing Center, St. Lawrence Campus, 1210 W. Saginaw, Lansing, MI 48915, 517-377-0520, (Formerly: St. Lawrence Hospital &amp; Healthcare System)</FP>
                <FP SOURCE="FP-1">St. Anthony Hospital Toxicology Laboratory, 1000 N. Lee St., Oklahoma City, OK 73101, 405-272-7052</FP>
                <FP SOURCE="FP-1">Sure-Test Laboratories, Inc., 2900 Broad Ave., Memphis, TN 38112, 901-474-6026</FP>
                <FP SOURCE="FP-1">Toxicology &amp; Drug Monitoring Laboratory, University of Missouri Hospital &amp; Clinics, 301 Business Loop 70 West, Suite 208, Columbia, MO 65203, 573-882-1273</FP>
                <FP SOURCE="FP-1">Toxicology Testing Service, Inc., 5426 N.W. 79th Ave., Miami, FL 33166, 305-593-2260</FP>
                <FP SOURCE="FP-1">
                    US Army Forensic
                    <FTREF/>
                     Toxicology Drug Testing Laboratory, 2490 Wilson St., Fort George G. Meade, MD 20755-5235, 301-677-7085
                </FP>
                <FTNT>
                    <P>* The Standards Council of Canada (SCC) voted to end its Laboratory Accreditation Program for Substance Abuse (LAPSA) effective May 12, 1998. Laboratories certified through that program were accredited to conduct forensic urine drug testing as required by U.S. Department of Transportation (DOT) regulations. As of that date, the certification of those accredited Canadian laboratories will continue under DOT authority. The responsibility for conducting quarterly performance testing plus periodic on-site inspections of those LAPSA-accredited laboratories was transferred to the U.S. HHS, with the HHS' NLCP contractor continuing to have an active role in the performance testing and laboratory inspection processes. Other Canadian laboratories wishing to be considered for the NLCP may apply directly to the NLCP contractor just as U.S. laboratories do.</P>
                    <P>
                        Upon finding a Canadian laboratory to be qualified, HHS will recommend that DOT certify the laboratory (
                        <E T="04">Federal Register</E>
                        , July 16, 1996) as meeting the minimum standards of the Mandatory Guidelines published in the 
                        <E T="04">Federal Register</E>
                         on June 9, 1994 (59 FR 29908) and on September 30, 1997 (62 FR 51118). After receiving DOT certification, the laboratory will be included in the monthly list of HHS certified laboratories and participate in the NLCP certification maintenance program.
                    </P>
                </FTNT>
                <SIG>
                    <NAME>Anna Marsh,</NAME>
                    <TITLE>Acting Executive Officer, SAMHSA.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30217 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4160-20-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="68093"/>
                <AGENCY TYPE="N">FEDERAL RETIREMENT THRIFT INVESTMENT BOARD </AGENCY>
                <SUBJECT>Sunshine Act Notice </SUBJECT>
                <PREAMHD>
                    <HD SOURCE="HED">Time and Date:</HD>
                    <P>10 a.m. (EST), December 15, 2003. </P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">PLACE:</HD>
                    <P>4th Floor, Conference Room, 1250 H Street, NW., Washington, DC. </P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">Status:</HD>
                    <P> Open. </P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">Matters to be Considered:</HD>
                    <P SOURCE="NPAR">1. Approval of the minutes of the November 17, 2003, Board member meeting. </P>
                    <P>2. Thrift Savings Plan activity report by the Executive Director.</P>
                </PREAMHD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Thomas J. Trabucco, Director, Office of External Affairs, (202) 942-1640. </P>
                    <SIG>
                        <DATED>Dated: December 3, 2003. </DATED>
                        <NAME>Elizabeth S. Woodruff, </NAME>
                        <TITLE>Secretary to the Board, Federal Retirement Thrift Investment Board. </TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30406 Filed 12-3-03; 3:19 pm] </FRDOC>
            <BILCOD>BILLING CODE 6760-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOMELAND SECURITY </AGENCY>
                <SUBAGY>Federal Emergency Management Agency </SUBAGY>
                <SUBJECT>Agency Information Collection Activities: Submission for OMB Review; Comment Request </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Emergency Management Agency, Emergency Preparedness and Response Directorate, Department of Homeland Security. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Federal Emergency Management Agency has submitted the following proposed information collection to the Office of Management and Budget for review and clearance in accordance with the requirements of the Paperwork Reduction Act of 1995 (44 U.S.C. 3507). </P>
                    <P>
                        <E T="03">Title:</E>
                         Request for Loan Information Verification. 
                    </P>
                    <P>
                        <E T="03">Type of Information Collection:</E>
                         Revision of a currently approved collection. 
                    </P>
                    <P>
                        <E T="03">OMB Number:</E>
                         1660-0012. 
                    </P>
                    <P>
                        <E T="03">Abstract:</E>
                         The Individuals and Households Program (IHP) uses mobile homes, travel trailers, and other forms of prefabricated housing to provide temporary housing assistance to victims of federally declared disasters. Victims who express interest in purchasing a mobile home at an adjusted sales price must complete FEMA Form 90-68. The form is used by FEMA to obtain information from lenders. The information is required to determine a fair and equitable sales price of a mobile home to disaster victims. 
                    </P>
                    <P>
                        <E T="03">Affected Public:</E>
                         Individuals or households, and Business or other for-profit, Not-for-profit institutions. 
                    </P>
                    <P>
                        <E T="03">Number of Respondents:</E>
                         125 Applicants and 250 lenders. 
                    </P>
                    <P>
                        <E T="03">Estimated Time per Respondent:</E>
                         5 minutes for Applicants and 5 minutes for lenders. 
                    </P>
                    <P>
                        <E T="03">Estimated Total Annual Burden Hours:</E>
                         42 hours. 
                    </P>
                    <P>
                        <E T="03">Frequency of Response:</E>
                         On Occasion. 
                    </P>
                    <P>
                        <E T="03">Comments:</E>
                         Interested persons are invited to submit written comments on the proposed information collection to e-mail address 
                        <E T="03">ahunt@omb.eop.gov</E>
                         or facsimile number (202) 395-7285 within 30 days of the date of this notice. 
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Requests for additional information or copies of the information collection should be made to Muriel B. Anderson, Chief, Records Management Branch, Information Resources Management Division, Information Technology Services Directorate, Federal Emergency Management Agency, Emergency Preparedness and Response Directorate, Department of Homeland Security, 500 C Street, SW., Room 316, Washington, DC 20472, facsimile number (202) 646-3347, or e-mail address 
                        <E T="03">InformationCollections@fema.gov</E>
                        . 
                    </P>
                    <SIG>
                        <DATED>Dated: November 28, 2003. </DATED>
                        <NAME>Muriel B. Anderson, </NAME>
                        <TITLE>Acting Division Director, Information Resources Management Division, Information Technology Services Directorate. </TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30290 Filed 12-4-03; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 9110-10-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY </AGENCY>
                <SUBAGY>Federal Emergency Management Agency </SUBAGY>
                <SUBJECT>Agency Information Collection Activities: Submission for OMB Review; Comment Request </SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Emergency Management Agency, Emergency Preparedness and Response Directorate, Department of Homeland Security. </P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Federal Emergency Management Agency has submitted the following proposed information collection to the Office of Management and Budget for review and clearance in accordance with the requirements of the Paperwork Reduction Act of 1995 (44 U.S.C. 3507). </P>
                    <P>
                        <E T="03">Title:</E>
                         Residential Basement Floodproofing Certificate. 
                    </P>
                    <P>
                        <E T="03">Type of Information Collection:</E>
                         Extension of a currently approved collection. 
                    </P>
                    <P>
                        <E T="03">OMB Number:</E>
                         1660-0033. 
                    </P>
                    <P>
                        <E T="03">Abstract:</E>
                         FEMA Form 81-78 is only used in communities that have been granted an exception by FEMA to allow the construction of flood proof residential basements in Special Flood Hazard Areas (SFHAs). Homeowners must have a registered professional engineer or architect complete FEMA Form 81-78 for development or inspection of structural design basements and certify that the basement design and methods of construction are in accordance with floodplain management ordinances. In any case homeowners are responsible for the fees involved with these services. Homeowners also provide FEMA Form 81-78 to their insurance agent to receive discounted flood insurance under the National Flood Insurance Program (NFIP). 
                    </P>
                    <P>
                        <E T="03">Affected Public:</E>
                         Individuals or households. 
                    </P>
                    <P>
                        <E T="03">Number of Respondents:</E>
                         50. 
                    </P>
                    <P>
                        <E T="03">Estimated Time Per Respondent:</E>
                         3.25 hrs. 
                    </P>
                    <P>
                        <E T="03">Estimated Total Annual Burden:</E>
                         163 hrs. 
                    </P>
                    <P>
                        <E T="03">Frequency of Response:</E>
                         On Occasions. 
                    </P>
                    <P>
                        <E T="03">Comments:</E>
                         Interested persons are invited to submit written comments on the proposed information collection to e-mail address 
                        <E T="03">ahunt@omb.eop.gov</E>
                         or facsimile number (202) 395-7285 within 30 days of the date of this notice. 
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Requests for additional information or copies of the information collection should be made to Muriel B. Anderson, Chief, Records Management Branch, Information Resources Management Division, Information Technology Services Directorate, Federal Emergency Management Agency, Emergency Preparedness and Response Directorate, Department of Homeland Security 500 C Street, SW., Room 316, Washington, DC 20472. Facsimile number (202) 646-3347, or email address 
                        <E T="03">InformationCollections@fema.gov</E>
                        . 
                    </P>
                    <SIG>
                        <DATED>Dated: November 28, 2003. </DATED>
                        <NAME>Muriel B. Anderson, </NAME>
                        <TITLE>Acting Division Director, Information Resources Management Division, Information Technology Services Directorate. </TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30291 Filed 12-4-03; 8:45 am] </FRDOC>
            <BILCOD>BILLING CODE 9110-12-P </BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="68094"/>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Federal Emergency Management Agency</SUBAGY>
                <SUBJECT>Agency Information Collection Activities: Submission for OMB Review; Comment Request</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Emergency Management Agency, Emergency Preparedness and Response Directorate, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Federal Emergency Management Agency has submitted the following proposed information collection to the Office of Management and Budget for review and clearance in accordance with the requirements of the Paperwork Reduction Act of 1995 (44 U.S.C. 3507). </P>
                    <P>
                        <E T="03">Title:</E>
                         Flood Mitigation Assistance (eGrants) and Grant Supplemental Information. 
                    </P>
                    <P>
                        <E T="03">Type of Information Collection:</E>
                         Revision of a currently approved collection. 
                    </P>
                    <P>
                        <E T="03">OMB Number:</E>
                         1660-0072. 
                    </P>
                    <P>
                        <E T="03">Abstract:</E>
                         Information sought with this submission will comprise Phase I of the electronic, web-based application for Flood Mitigation Assistance (FMA) program grants through FEMA's eGrants system. The eGrants system is being developed to meet the intent of the eGovernment initiative, authorized by Public Law 106-107 passed on November 20, 1999. This initiative requires that all government agencies both streamline grant application process and provide for the means to electronically create, review, and submit a grant application via the Internet.
                    </P>
                    <P>The FMA eGrants application will not replace the FMA grants program paper-based collection currently under OMB control number 1660-0025. It is provided as an alternative method for grantees and subgrantees to use.</P>
                    <P>The FMA eGrants application includes the information necessary for FEMA to assess the financial needs of the applicants as well as the projected benefits to be obtained from the use of the grant funds. FEMA will also use the information to determine eligibility and whether the proposed use of such funds meets the requirements and intent of the NFIRA. FEMA will use the information to evaluate applications and make award decisions, monitor ongoing performance and manage the flow of Federal funds, and to appropriately closeout the grant award when all work is completed.</P>
                    <P>
                        <E T="03">Affected Public:</E>
                         State, local and Tribal governments.
                    </P>
                    <P>
                        <E T="03">Number of Respondents:</E>
                         280—56 States and Territories × 4 subgrants per  State = 224 + 56 States to review, coordinate and forward FMA grant applications to FEMA for approval.
                    </P>
                    <P>
                        <E T="03">Estimated Time per Respondent:</E>
                         14.6 hrs.
                    </P>
                    <P>
                        <E T="03">Estimated Total Annual Burden Hours:</E>
                         4,088.
                    </P>
                    <P>
                        <E T="03">Frequency of Response:</E>
                         On occasion.
                    </P>
                    <P>
                        <E T="03">Comments:</E>
                         Interested persons are invited to submit written comments within 30 days of this notice on the proposed information collection to the FEMA Desk Officer at the Office of Management and Budget at e-mail address 
                        <E T="03">David_Rostker@omb.oep.gov.</E>
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Requests for additional information or copies of the information collection should be made to Muriel B. Anderson, Chief, Records Management Branch, Information Resources Management Division, Information Technology Services Directorate, Federal Emergency Management Agency at facsimile number (202) 646-3347 or e-mail address 
                        <E T="03">InformationCollections@fema.gov.</E>
                    </P>
                    <SIG>
                        <DATED>Dated: November 13, 2003.</DATED>
                        <NAME>Edward W. Kernan,</NAME>
                        <TITLE>Division Director, Information Resources Management Division, Information Technology Services Directorate. </TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30292 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-13-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Federal Emergency Management Agency</SUBAGY>
                <DEPDOC>[FEMA-1501-DR]</DEPDOC>
                <SUBJECT>Puerto Rico; Major Disaster and Related Determinations</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Emergency Management Agency, Emergency Preparedness and Response Directorate, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This is a notice of the Presidential declaration of a major disaster for the Commonwealth of Puerto Rico(FEMA-1501-DR), dated November 21, 2003, and related determinations.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>November 21, 2003.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Magda Ruiz, Recovery Division, Federal Emergency Management Agency, Washington,DC 20472, (202) 646-2705.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Notice is hereby given that, in a letter dated November 21, 2003, the President declared a major disaster under the authority of the Robert T. Stafford Disaster Relief and Emergency Assistance Act, 42 U.S.C. 5121-5206 (the Stafford Act), as follows:</P>
                <EXTRACT>
                    <P>I have determined that the damage in certain areas of the Commonwealth of Puerto Rico, resulting from severe storms, flooding, mudslides, and landslides on November 10, 2003, and continuing, is of sufficient severity and magnitude to warrant a major disaster declaration under the Robert T. Stafford Disaster Relief and Emergency Assistance Act, 42 U.S.C. 5121-5206 (the Stafford Act). I, therefore, declare that such a major disaster exists in the Commonwealth of Puerto Rico.</P>
                    <P>In order to provide Federal assistance, you are hereby authorized to allocate from funds available for these purposes, such amounts as you find necessary for Federal disaster assistance and administrative expenses.</P>
                    <P>You are authorized to provide Individual Assistance in the designated areas, Hazard Mitigation throughout the Commonwealth, and any other forms of assistance under the Stafford Act you may deem appropriate. Consistent with the requirement that Federal assistance be supplemental, any Federal funds provided under the Stafford Act for Hazard Mitigation and the Other Needs Assistance under Section 408 of the Stafford Act will be limited to 75 percent of the total eligible costs. If Public Assistance is later warranted, Federal funds provided under that program will also be limited to 75 percent of the total eligible costs.</P>
                    <P>Further, you are authorized to make changes to this declaration to the extent allowable under the Stafford Act.</P>
                </EXTRACT>
                <P>The time period prescribed for the implementation of section 310(a), Priority to Certain Applications for Public Facility and Public Housing Assistance, 42 U.S.C. 5153, shall be for a period not to exceed six months after the date of this declaration.</P>
                <P>The Federal Emergency Management Agency (FEMA) hereby gives notice that pursuant to the authority vested in the Under Secretary for Emergency Preparedness and Response, Department of Homeland Security, under Executive Order 12148, as amended, Justo Hernandez, of FEMA is appointed to act as the Federal Coordinating Officer for this declared disaster.</P>
                <P>I do hereby determine the following areas of the Commonwealth of Puerto Rico to have been affected adversely by this declared major disaster:</P>
                <EXTRACT>
                    <P>
                        The municipalities of Gua
                        <AC T="1"/>
                        nica, Guayama, Juana Diaz, Maunabo, Patillas, Ri
                        <AC T="1"/>
                        o Grande, Salinas, Santa Isabel, and Yauco for Individual Assistance.
                    </P>
                </EXTRACT>
                <P>All municipalities within the Commonwealth of Puerto Rico are eligible to apply for assistance under the Hazard Mitigation Grant Program.</P>
                <SIG>
                    <PRTPAGE P="68095"/>
                    <FP>(The following Catalog of Federal Domestic Assistance Numbers (CFDA) are to be used for reporting and drawing funds: 97.030, Community Disaster Loans; 97.031, Cora Brown Fund Program; 97.032, Crisis Counseling; 97.033, Disaster Legal Services Program; 97.034, Disaster Unemployment Assistance (DUA); 97.046, Fire Management Assistance; 97.048, Individual and Household Housing; 97.049, Individual and Household Disaster Housing Operations; 97.050 Individual and Household Program-Other Needs, 97.036, Public Assistance Grants; 97.039, Hazard Mitigation Grant Program.)</FP>
                    <NAME>Michael D. Brown,</NAME>
                    <TITLE>Under Secretary, Emergency Preparedness and Response, Department of Homeland Security.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30297 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-10-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Federal Emergency Management Agency</SUBAGY>
                <DEPDOC>[FEMA-1501-DR]</DEPDOC>
                <SUBJECT>Puerto Rico; Amendment No. 1 to Notice of a Major Disaster Declaration</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Emergency Management Agency, Emergency Preparedness and Response Directorate, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice amends the notice of a major disaster declaration for the Commonwealth of Puerto Rico (FEMA-1501-DR), dated November 21, 2003, and related determinations.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>November 24, 2003.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Magda Ruiz, Recovery Division, Federal Emergency Management Agency, Washington, DC 20472, (202) 646-2705.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The notice of a major disaster declaration for the Commonwealth of Puerto Rico is hereby amended to include the following areas among those areas determined to have been adversely affected by the catastrophe declared a major disaster by the President in his declaration of November 21, 2003:</P>
                <EXTRACT>
                    <P>The municipalities of Arroyo, Canóvanas, Fajardo, Loiza, Naguabo, Toa Baja, and Yabucoa for Individual Assistance.</P>
                </EXTRACT>
                <SIG>
                    <FP>(The following Catalog of Federal Domestic Assistance Numbers (CFDA) are to be used for reporting and drawing funds: 97.030, Community Disaster Loans; 97.031, Cora Brown Fund Program; 97.032, Crisis Counseling; 97.033, Disaster Legal Services Program; 97.034, Disaster Unemployment Assistance (DUA); 97.046, Fire Management Assistance; 97.048, Individual and Household Housing; 97.049, Individual and Household Disaster Housing Operations; 97.050 Individual and Household Program-Other Needs, 97.036, Public Assistance Grants; 97.039, Hazard Mitigation Grant Program.)</FP>
                    <NAME>Michael D. Brown,</NAME>
                    <TITLE>Under Secretary, Emergency Preparedness and Response, Department of Homeland Security.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30298 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-10-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Federal Emergency Management Agency</SUBAGY>
                <DEPDOC>[FEMA-1499-DR]</DEPDOC>
                <SUBJECT>Washington; Amendment No. 1 to Notice of a Major Disaster Declaration</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Emergency Management Agency, Emergency Preparedness and Response Directorate, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice amends the notice of a major disaster declaration for the State of Washington (FEMA-1499-DR), dated  November 7, 2003, and related determinations.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>November 20, 2003.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Magda Ruiz, Recovery Division, Federal Emergency Management Agency, Washington, DC 20472, (202) 646-2705.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The notice of a major disaster declaration for the State of Washington is hereby amended to include the Public Assistance program for the following areas among those areas determined to have been adversely affected by the catastrophe declared a major disaster by the President in his declaration of November 7, 2003: </P>
                <EXTRACT>
                    <P>Clallam, Grays Harbor, Jefferson, Mason, Skagit, Snohomish, and Whatcom Counties for Public Assistance (already designated for Individual Assistance.)</P>
                    <FP>(The following Catalog of Federal Domestic Assistance Numbers (CFDA) are to be used for reporting and drawing funds: 97.030, Community Disaster Loans; 97.031, Cora Brown Fund Program; 97.032, Crisis Counseling; 97.033, Disaster Legal Services Program; 97.034, Disaster Unemployment Assistance (DUA); 97.046, Fire Management Assistance; 97.048, Individual and Household Housing; 97.049, Individual and Household Disaster Housing Operations; 97.050 Individual and Household Program—Other Needs, 97.036, Public Assistance Grants; 97.039, Hazard Mitigation Grant Program.) </FP>
                </EXTRACT>
                <SIG>
                    <NAME>Michael D. Brown,</NAME>
                    <TITLE>Under Secretary, Emergency Preparedness and Response, Department of Homeland Security.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30293 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-10-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Federal Emergency Management Agency</SUBAGY>
                <DEPDOC>[FEMA-1500-DR]</DEPDOC>
                <SUBJECT>West Virginia; Major Disaster and Related Determinations</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Emergency Management Agency, Emergency Preparedness and Response Directorate, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This is a notice of the Presidential declaration of a major disaster for the State of West Virginia (FEMA-1500-DR), dated November 21, 2003, and related determinations.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>November 21, 2003.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Magda Ruiz, Recovery Division, Federal Emergency Management Agency, Washington, DC 20472, (202) 646-2705.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>Notice is hereby given that, in a letter dated November 21, 2003, the President declared a major disaster under the authority of the Robert T. Stafford Disaster Relief and Emergency Assistance Act, 42 U.S.C. 5121-5206 (the Stafford Act), as follows:</P>
                <EXTRACT>
                    <P>I have determined that the damage in certain areas of the State of West Virginia, resulting from severe storms, flooding, and landslides on November 11, 2003, and continuing is of sufficient severity and magnitude to warrant a major disaster declaration under the Robert T. Stafford Disaster Relief and Emergency Assistance Act, 42 U.S.C. 5121-5206 (the Stafford Act). I, therefore, declare that such a major disaster exists in the State of West Virginia.</P>
                    <P>In order to provide Federal assistance, you are hereby authorized to allocate from funds available for these purposes, such amounts as you find necessary for Federal disaster assistance and administrative expenses.</P>
                    <P>
                        You are authorized to provide Individual Assistance in the designated areas, Hazard Mitigation throughout the State, and any other forms of assistance under the Stafford Act you may deem appropriate. Consistent with the requirement that Federal assistance be supplemental, any Federal funds provided under the Stafford Act for Hazard Mitigation and the Other Needs Assistance under Section 408 of the Stafford Act will be 
                        <PRTPAGE P="68096"/>
                        limited to 75 percent of the total eligible costs. If Public Assistance is later requested and warranted, Federal funds provided under that program will also be limited to 75 percent of the total eligible costs.
                    </P>
                    <P>Further, you are authorized to make changes to this declaration to the extent allowable under the Stafford Act.</P>
                    <P>The time period prescribed for the implementation of section 310(a), Priority to Certain Applications for Public Facility and Public Housing Assistance, 42 U.S.C. 5153, shall be for a period not to exceed six months after the date of this declaration.</P>
                    <P>The Federal Emergency Management Agency (FEMA) hereby gives notice that pursuant to the authority vested in the Under Secretary for Emergency Preparedness and Response, Department of Homeland Security, under Executive Order 12148, as amended, Michael Bolch, of FEMA is appointed to act as the Federal Coordinating Officer for this declared disaster.</P>
                    <P>I do hereby determine the following areas of the State of West Virginia to have been affected adversely by this declared major disaster: </P>
                    <P>Cabell, Kanawha, Lincoln, Nicholas, Putnam, and Wayne Counties for Individual Assistance.</P>
                </EXTRACT>
                <P>All counties within the State of West Virginia are eligible to apply for assistance under the Hazard Mitigation Grant Program.</P>
                <SIG>
                    <FP>(The following Catalog of Federal Domestic Assistance Numbers (CFDA) are to be used for reporting and drawing funds: 97.030, Community Disaster Loans; 97.031, Cora Brown Fund Program; 97.032, Crisis Counseling; 97.033, Disaster Legal Services Program; 97.034, Disaster Unemployment Assistance (DUA); 97.046, Fire Management Assistance; 97.048, Individual and Household Housing; 97.049, Individual and Household Disaster Housing Operations; 97.050 Individual and Household Program-Other Needs, 97.036, Public Assistance Grants; 97.039, Hazard Mitigation Grant Program.)</FP>
                    <NAME>Michael D. Brown,</NAME>
                    <TITLE>Under Secretary, Emergency Preparedness and Response, Department of Homeland Security.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30294 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-10-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Federal Emergency Management Agency</SUBAGY>
                <DEPDOC>[FEMA-1500-DR]</DEPDOC>
                <SUBJECT>West Virginia; Amendment No.1 to Notice of a Major Disaster Declaration</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Emergency Management Agency, Emergency Preparedness and Response Directorate, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice amends the notice of a major disaster declaration for the State of West Virginia (FEMA-1500-DR), dated November 21, 2003, and related determinations.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>November 22, 2003.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Magda Ruiz, Recovery Division, Federal Emergency Management Agency, Washington, DC 20472, (202) 646-2705.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The notice of a major disaster declaration for the State of West Virginia is hereby amended to include the following areas among those areas determined to have been adversely affected by the catastrophe declared a major disaster by the President in his declaration of November 21, 2003:</P>
                <EXTRACT>
                    <P>Boone, Calhoun, Clay, Fayette, Gilmer, Greenbrier, Marion, McDowell, Mercer, Monongalia, Monroe, Raleigh, Summers, Webster, Wetzel, and Wyoming Counties for Individual Assistance.</P>
                </EXTRACT>
                <SIG>
                    <FP>(The following Catalog of Federal Domestic Assistance Numbers (CFDA) are to be used for reporting and drawing funds: 97.030, Community Disaster Loans; 97.031, Cora Brown Fund Program; 97.032, Crisis Counseling; 97.033, Disaster Legal Services Program; 97.034, Disaster Unemployment Assistance (DUA); 97.046, Fire Management Assistance; 97.048, Individual and Household Housing; 97.049, Individual and Household Disaster Housing Operations; 97.050 Individual and Household Program-Other Needs, 97.036, Public Assistance Grants; 97.039, Hazard Mitigation Grant Program.)</FP>
                    <NAME>Michael D. Brown,</NAME>
                    <TITLE>Under Secretary, Emergency Preparedness and Response, Department of Homeland Security.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30295 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-10-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Federal Emergency Management Agency</SUBAGY>
                <DEPDOC>[FEMA-1500-DR]</DEPDOC>
                <SUBJECT>West Virginia; Amendment No. 2 to Notice of a Major Disaster Declaration</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Emergency Management Agency, Emergency Preparedness and Response Directorate, Department of Homeland Security.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice amends the notice of a major disaster declaration for the State of West Virginia (FEMA-1500-DR), dated November 21, 2003, and related determinations.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>November 25, 2003.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Magda Ruiz, Recovery Division, Federal Emergency Management Agency, Washington, DC 20472, (202) 646-2705.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The notice of a major disaster declaration for the State of West Virginia is hereby amended to include the Public Assistance program for the following areas among those areas determined to have been adversely affected by the catastrophe declared a major disaster by the President in his declaration of November 21, 2003:</P>
                <EXTRACT>
                    <P>Boone, Clay, Kanawha, Lincoln, and Wayne Counties for Public Assistance (already designated for Individual Assistance.)</P>
                    <P>Logan County for Public Assistance.</P>
                </EXTRACT>
                <SIG>
                    <FP>(The following Catalog of Federal Domestic Assistance Numbers (CFDA) are to be used for reporting and drawing funds: 97.030, Community Disaster Loans; 97.031, Cora Brown Fund Program; 97.032, Crisis Counseling; 97.033, Disaster Legal Services Program; 97.034, Disaster Unemployment Assistance (DUA); 97.046, Fire Management Assistance; 97.048, Individual and Household Housing; 97.049, Individual and Household Disaster Housing Operations; 97.050 Individual and Household Program-Other Needs, 97.036, Public Assistance Grants; 97.039, Hazard Mitigation Grant Program.)</FP>
                    <NAME>Michael D. Brown,</NAME>
                    <TITLE>Under Secretary,Emergency Preparedness and Response,Department of Homeland Security.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30296 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 9110-10-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY</AGENCY>
                <SUBAGY>Transportation Security Administration</SUBAGY>
                <SUBJECT>Maritime Vulnerability Self-Assessment Tool</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Transportation Security Administration (TSA), Department of Homeland Security (DHS).</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability of TSA's maritime vulnerability self-assessment tool.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        TSA announces the availability of the TSA Maritime Self-Assessment Risk Module (TMSARM), developed to support the United States Coast Guard's (USCG) regulatory efforts promulgated pursuant to the Maritime Transportation Security Act (MTSA) of 2002. MTSA regulations mandate that any facility or vessel that might be involved in a transportation security incident conduct a vulnerability assessment and submit a security plan to the USCG by December 31, 2003. The 
                        <PRTPAGE P="68097"/>
                        Coast Guard published a series of final rules implementing portions of the maritime security initiatives mandated by MTSA, including the vulnerability assessment and security plan requirements. The USCG final rules provide a list of tools that may be used to conduct vulnerability self-assessments. This list includes TMSARM, a no-cost, web-based, flexible vulnerability assessment tool designed by TSA specifically to meet the requirements of MTSA.
                    </P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For additional information or questions, contact Nick Lakis, Office of Maritime and Land Security, Transportation Security Administration Headquarters, West Building, Floor 9, TSA-8, 601 South 12th Street, Arlington, VA 22202-4220; e-mail: 
                        <E T="03">nick.lakis@dhs.gov</E>
                        . For issues regarding the DHS/TSA's vulnerability self-assessment tool, contact Lynne Wolstenholme, Office of Threat Assessment and Risk Management, Transportation Security Administration Headquarters, West Tower, Floor 9, TSA-3, 601 South 12th Street, Arlington, VA 22202-4220; e-mail: 
                        <E T="03">tsarisk@dhs.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>
                    On October 22, 2003, the USCG published in the 
                    <E T="04">Federal Register</E>
                     (68 FR 60447) a series of final rules, codified in the new Subchapter H of Title 33 of the Code of Federal Regulations (CFR), which adopted, with changes, the series of temporary interim rules published July 1, 2003 (68 FR 39240). This series of rules addresses security assessments and plans, as well as other security standards, measures, and provisions that are mandated by the Maritime Transportation Security Act (MTSA) of 2002 (Pub. L. 107-295, 116 Stat. 2064, Nov. 25, 2002). One of these MTSA requirements is that any facility or vessel that might be involved in a transportation security incident (TSI) conduct a vulnerability assessment and submit a security plan to the USCG by December 31, 2003. The MTSA defines a TSI as “a security incident that results in a significant loss of life, environmental damage, transportation system disruption, or economic disruption in a particular area.”
                </P>
                <P>
                    TSA, in coordination with other Federal agencies, academia, and industry, developed a vulnerability self-assessment tool, the TSA Maritime Self-Assessment Risk Module (TMSARM), specifically to meet the security assessment requirements mandated by MTSA. This TSA tool is briefly discussed in the preamble of the USCG final rules. The tool supports three basic functions: (1) Capturing a current snapshot of the user's security system baseline; (2) providing users with a vulnerability assessment tool; and (3) assisting users in their development of a comprehensive security plan. TMSARM is available to Company Security Officers (CSO), Vessel Security Officers (VSO), and Facility Security Officers (FSO). This outstanding service is specific to TMSARM and is available to TMSARM users at no cost. The tool is easily accessible on TSA's website at 
                    <E T="03">http://www.tsa.gov/public/interapp/editorial/editorial_0826.xml</E>
                    , and the user determines all ratings. Any information entered into the tool will not become accessible to the Federal government unless and until the party entering the data formally submits this information to the TSA.
                </P>
                <HD SOURCE="HD1">Elements of the Self-Assessment Tool</HD>
                <P>Although the USCG provides examples of security assessment tools in 33 CFR 101.510, the list is not intended to be exhaustive. The USCG does not require owners or operators to conduct security assessments using a specific tool, provided that the assessments meet the requirements of its regulations. TMSARM is merely one means of satisfying the USCG requirements.</P>
                <P>In general, TMSARM focuses on preventing and mitigating a base array of threat scenarios developed for the various categories of vessels and facilities that comprise the maritime transportation sector and are covered by the USCG rules. Users rate their vessel/facility in terms of target attractiveness and several consequence categories that broadly describe health and well-being, economic consequence, and symbolic value. Users will first list the vessel/facility's baseline security countermeasures that apply for each of the threat scenarios and then rate the effectiveness of the countermeasures in detecting and preventing terrorist's actions against each of the provided threat scenarios. The countermeasures are divided into broad countermeasure groupings that represent different security layers that may be implemented against the various threat scenarios. Descriptive guidance for the effectiveness rating is provided for each of the countermeasure categories. The performance-based effectiveness ratings range from very high to very low, and describe the vessel/facility's ability to thwart the threat.</P>
                <P>TSA has also developed guidance documents for the security countermeasure categories. These documents guide users on how to populate the sections of their security plans with the security information developed through use of both the TMSARM security checklist and the TMSARM vulnerability assessment tool. Additionally, the guidance documents identify specific security vulnerabilities from the USCG regulations and map them to the appropriate TMSARM security countermeasure effectiveness descriptions within the tool. Once vulnerabilities are identified, very specific guidance on how to fill out form USCG Form CG-6025 (Vulnerability and Security Measures Summary) is provided.</P>
                <P>After the tool is applied across each of the provided threat scenarios to determine baseline countermeasures, users can re-apply the tool to assess the impact of adding new countermeasures or enhancing existing countermeasures. Additional or enhanced countermeasures are included in the security plan along with estimated resource requirements and a timeframe for implementation. Upon completion, users receive a report that summarizes their inputs. This report can be included in the security plan that is required to be submitted to the USCG. Users' input to the tool becomes part of a vulnerability assessment, which constitutes Sensitive Security Information (SSI) under TSA regulations at 49 CFR part 1520. SSI may be released only to persons with a need to know, except with the written permission of the TSA Administrator. Unauthorized release of SSI may result in civil penalties or other action.</P>
                <SIG>
                    <DATED>Issued in Arlington, Virginia, on December 1, 2003.</DATED>
                    <NAME>James M. Loy,</NAME>
                    <TITLE>Administrator.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30281 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-62-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF HOUSING AND URBAN DEVELOPMENT</AGENCY>
                <DEPDOC>[Docket No. FR-4809-N-49]</DEPDOC>
                <SUBJECT>Federal Property Suitable as Facilities To Assist the Homeless</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Office of the Assistant Secretary for Community Planning and Development, HUD.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This Notice identifies unutilized, underutilized, excess, and surplus Federal property reviewed by HUD for suitability for possible use to assist the homeless.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Mark Johnston, room 7266, Department of Housing and Urban Development, 
                        <PRTPAGE P="68098"/>
                        451 Seventh Street SW., Washington, DC 20410; telephone (202) 708-1234; TTY number for the hearing- and speech-impaired (202) 708-2565 (these telephone numbers are not toll-free), or call the toll-free Title V information line at 1-800-927-7588.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    In accordance with 24 CFR part 581 and section 501 of the Stewart B. McKinney Homeless Assistance Act (42 U.S.C. 11411), as amended, HUD is publishing this Notice to identify Federal buildings and other real property that HUD has reviewed for suitability for use to assist the homeless. The properties were reviewed using information provided to HUD by Federal landholding agencies regarding unutilized and underutilized buildings and real property controlled by such agencies or by GSA regarding its inventory of excess or surplus Federal property. This Notice is also published in order to comply with the December 12, 1988 Court Order in 
                    <E T="03">National Coalition for  the Homeless</E>
                     v. 
                    <E T="03">Veterans Administration</E>
                    , No. 88-2503-OG (D.D.C.).
                </P>
                <P>Properties reviewed are listed in this Notice according to the following categories: Suitable/available, suitable/unavailable, suitable/to be excess, and unsuitable. The properties listed in the three suitable categories have been reviewed by the landholding agencies, and each agency has transmitted to HUD: (1) Its intention to make the property available for use to assist the homeless, (2) its intention to declare the property excess to the agency's needs, or (3) a statement of the reasons that the property cannot be declared excess or made available for use as facilities to assist the homeless.</P>
                <P>Properties listed as suitable/available will be available exclusively for homeless use for a period of 60 days from the date of this Notice. Where property is described as for “off-site use only” recipients of the property will be required to relocate the building to their own site at their own expense. Homeless assistance providers interested in any such property should send a written expression of interest to HHS, addressed to Shirley Kramer, Division of Property Management, Program Support Center, HHS, room 5B-41, 5600 Fishers Lane, Rockville, MD 20857; (301) 443-2265. (This is not a toll-free number.) HHS will mail to the interested provider an application packet, which will include instructions for completing the application. In order to maximize the opportunity to utilize a suitable property, providers should submit their written expressions of interest as soon as possible. For complete details concerning the processing of applications, the reader is encouraged to refer to the interim rule governing this program, 24 CFR part 581.</P>
                <P>For properties listed as suitable/to be excess, that property may, if subsequently accepted as excess by GSA, be made available for use by the homeless in accordance with applicable law, subject to screening for other Federal use. At the appropriate time, HUD will publish the property in a Notice showing it as either suitable/available or suitable/unavailable.</P>
                <P>For properties listed as suitable/unavailable, the landholding agency has decided that the property cannot be declared excess or made available for use to assist the homeless, and the property will not be available.</P>
                <P>
                    Properties listed as unsuitable will not be made available for any other purpose for 20 days from the date of this Notice. Homeless assistance providers interested in a review by HUD of the determination of unsuitability should call the toll-free information line at 1-800-927-7588 for detailed instructions or write a letter to Mark Johnston at the address listed at the beginning of this Notice. Included in the request for review should be the property address (including zip code), the date of publication in the 
                    <E T="04">Federal Register</E>
                    , the landholding agency, and the property number.
                </P>
                <P>
                    For more information regarding particular properties identified in this Notice (
                    <E T="03">i.e.</E>
                    , acreage, floor plan, existing sanitary facilities, exact street address), providers should contact the appropriate landholding agencies at the following addresses: 
                    <E T="04">AIR FORCE:</E>
                     Mr. Albert F. Lowas, Jr., Air Force Real Property Agency, 1700 North Moore St., Suite 2300, Arlington, VA 22209-2802; (703) 696-5501; 
                    <E T="04">COE:</E>
                     Ms. Shirley Middleswarth, Army Corps of Engineers, Civil Division, Directorate of Real Estate, 441 G Street, NW., Washington, DC 20314-1000; (202) 761-7425; 
                    <E T="04">ENERGY:</E>
                     Mr. Tom Knox, Department of Energy, Office of Engineering &amp; Construction Management, CR-80, Washington, DC 20585; (202) 586-8715; 
                    <E T="04">GSA:</E>
                     Mr. Brian K. Polly, Assistant Commissioner, General Services Administration, Office of Property Disposal, 18th and F Streets, NW., Washington, DC 20405; (202) 501-0052; 
                    <E T="04">INTERIOR:</E>
                     Ms. Linda Tribby, Acquisition &amp; Property Management, Department of the Interior, 1849 C Street, NW., MS5512, Washington, DC 20240; (202) 219-0728; 
                    <E T="04">NAVY:</E>
                     Mr. Charles C. Cocks, Director, Department of the Navy, Real Estate Policy Division, Naval Facilities Engineering Command, Washington Navy Yard, 1322 Patterson Ave., SE., Suite 1000, Washington, DC 20374-5065; (202) 685-9200; 
                    <E T="04">VA:</E>
                     Ms. Amelia E. McLellan, Director, Real Property Service (183C), Department of Veterans Affairs, 810 Vermont Avenue, NW., Room 419, Washington, DC 20420; (202) 565-5398; (These are not toll-free numbers).
                </P>
                <SIG>
                    <DATED>Dated: November 25, 2003.</DATED>
                    <NAME>John D. Garrity,</NAME>
                    <TITLE>Director, Office of Special Needs Assistance Programs.</TITLE>
                </SIG>
                <EXTRACT>
                    <HD SOURCE="HD1">Title V, Federal Surplus Property Program Federal Register Report for 12/5/2003</HD>
                    <HD SOURCE="HD1">Suitable/Available Properties</HD>
                    <HD SOURCE="HD2">Buildings (by State)</HD>
                    <HD SOURCE="HD3">California</HD>
                    <FP SOURCE="FP-1">Bldg. 4607</FP>
                    <FP SOURCE="FP-1">Yosemite Natl Park</FP>
                    <FP SOURCE="FP-1">Mariposa Co: CA 95389-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Interior</FP>
                    <FP SOURCE="FP-1">Property Number: 61200340010</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 66 sq. ft. storage facility, mountainous terrain, off-site use only</FP>
                    <HD SOURCE="HD3">Hawaii</HD>
                    <FP SOURCE="FP-1">Bldg. 255</FP>
                    <FP SOURCE="FP-1">Navy Marine Golf Course</FP>
                    <FP SOURCE="FP-1">Pearl Harbor Co: HI 96860-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200340042</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Comment: 1946 sq. ft., possible asbestos/lead paint, most recent use—guest quarters, off-site use only</FP>
                    <HD SOURCE="HD3">Iowa</HD>
                    <FP SOURCE="FP-1">23 Buildings</FP>
                    <FP SOURCE="FP-1">Former Naval Housing</FP>
                    <FP SOURCE="FP-1">Waverly Co: Bremer IA 50677-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: GSA</FP>
                    <FP SOURCE="FP-1">Property Number: 54200340006</FP>
                    <FP SOURCE="FP-1">Comment: 2 to 3 bedroom homes, 864 to 1760 sq. ft., presence of asbestos/lead paint</FP>
                    <FP SOURCE="FP-1">GSA Number: 7-I-IA-0463-5</FP>
                    <HD SOURCE="HD3">New York</HD>
                    <FP SOURCE="FP-1">Bldg. 240</FP>
                    <FP SOURCE="FP-1">Rome Lab</FP>
                    <FP SOURCE="FP-1">Rome Co: Oneida NY 13441-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200340023</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 39108 sq. ft., presence of asbestos, most recent use—Electronic Research Lab</FP>
                    <FP SOURCE="FP-1">Bldg. 247</FP>
                    <FP SOURCE="FP-1">Rome Lab</FP>
                    <FP SOURCE="FP-1">Rome Co: Oneida NY 13441-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200340024</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 13199 sq. ft., presence of asbestos, most recent use—Electronic Research Lab</FP>
                    <FP SOURCE="FP-1">Bldg. 248</FP>
                    <FP SOURCE="FP-1">Rome Lab</FP>
                    <FP SOURCE="FP-1">Rome Co: Oneida NY 13441-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200340025</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 4000 sq. ft., presence of asbestos, most recent use—Electronic Research Lab</FP>
                    <PRTPAGE P="68099"/>
                    <FP SOURCE="FP-1">Bldg. 302</FP>
                    <FP SOURCE="FP-1">Rome Lab</FP>
                    <FP SOURCE="FP-1">Rome Co: Oneida NY 13441-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200340026</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 10288 sq. ft., presence of asbestos, most recent use—communications facility</FP>
                    <HD SOURCE="HD3">Tennessee</HD>
                    <FP SOURCE="FP-1">Tract 01-202</FP>
                    <FP SOURCE="FP-1">Stones River Natl</FP>
                    <FP SOURCE="FP-1">Battlefield</FP>
                    <FP SOURCE="FP-1">Murfreesboro Co: Rutherford TN 37129-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Interior</FP>
                    <FP SOURCE="FP-1">Property Number: 61200340008</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Comment: 1796 sq. ft. residence, off-site use only</FP>
                    <HD SOURCE="HD3">Texas</HD>
                    <FP SOURCE="FP-1">Tract 104-47</FP>
                    <FP SOURCE="FP-1">San Antonio Mission</FP>
                    <FP SOURCE="FP-1">San Antonio Co: Bexar TX 78223-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Interior</FP>
                    <FP SOURCE="FP-1">Property Number: 61200340012</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Comment: 136 sq. ft., Historical District, off-site use only</FP>
                    <HD SOURCE="HD3">Virginia</HD>
                    <FP SOURCE="FP-1">SSA Trust Fund Bldg.</FP>
                    <FP SOURCE="FP-1">2301 Park Ave.</FP>
                    <FP SOURCE="FP-1">Lynchburg Co: VA 24501-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: GSA</FP>
                    <FP SOURCE="FP-1">Property Number: 54200340010</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Comment: 3400 sq. ft., most recent use—Office</FP>
                    <FP SOURCE="FP-1">GSA Number: 4-G-VA-0734</FP>
                    <HD SOURCE="HD3">West Virginia</HD>
                    <FP SOURCE="FP-1">Quarters 77, 78, 79</FP>
                    <FP SOURCE="FP-1">Hartzog Drive</FP>
                    <FP SOURCE="FP-1">Harpers Ferry Co: Jefferson WV 25425-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Interior</FP>
                    <FP SOURCE="FP-1">Property Number: 61200340013</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Comment: 1797 sq. ft., needs repair, presence of asbestos/lead paint, most recent use—housing, off-site use only</FP>
                    <HD SOURCE="HD2">Land (by State)</HD>
                    <HD SOURCE="HD3">Michigan</HD>
                    <FP SOURCE="FP-1">IOM Site</FP>
                    <FP SOURCE="FP-1">Chesterfield Road</FP>
                    <FP SOURCE="FP-1">Chesterfield Co: Macomb MI</FP>
                    <FP SOURCE="FP-1">Landholding Agency: GSA</FP>
                    <FP SOURCE="FP-1">Property Number: 54200340008</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Comment: approx. 17.4 acres w/concrete block bldg. in poor condition, most recent use—radio antenna field, narrow right-of-way</FP>
                    <FP SOURCE="FP-1">GSA Number: 1-D-MI-0603F</FP>
                    <HD SOURCE="HD1">Suitable/Unavailable Properties</HD>
                    <HD SOURCE="HD2">Buildings (by State)</HD>
                    <HD SOURCE="HD3">Colorado</HD>
                    <FP SOURCE="FP-1">Klein Water Treatment Plant</FP>
                    <FP SOURCE="FP-1">Rocky Mountain Arsenal</FP>
                    <FP SOURCE="FP-1">Denver Co: Adams CO 80022-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: GSA</FP>
                    <FP SOURCE="FP-1">Property Number: 54200340012</FP>
                    <FP SOURCE="FP-1">Status: Surplus</FP>
                    <FP SOURCE="FP-1">Comment: water treatment plant</FP>
                    <FP SOURCE="FP-1">GSA Number: 7-D-CO-0442-3</FP>
                    <HD SOURCE="HD1">Unsuitable Properties</HD>
                    <HD SOURCE="HD2">Buildings (by State)</HD>
                    <HD SOURCE="HD3">Alaska</HD>
                    <FP SOURCE="FP-1">Bldg. 4314</FP>
                    <FP SOURCE="FP-1">Elmendorf AFB</FP>
                    <FP SOURCE="FP-1">Elmendorf AFB Co: AK 99506-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200340001</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 6527</FP>
                    <FP SOURCE="FP-1">Elmendorf AFB</FP>
                    <FP SOURCE="FP-1">Elmendorf AFB Co: AK 99506-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200340002</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 7541</FP>
                    <FP SOURCE="FP-1">Elmendorf AFB</FP>
                    <FP SOURCE="FP-1">Elmendorf AFB Co: AK 99506-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200340003</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 8111</FP>
                    <FP SOURCE="FP-1">Elmendorf AFB</FP>
                    <FP SOURCE="FP-1">Elmendorf AFB Co: AK 99506-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200340004</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 9489</FP>
                    <FP SOURCE="FP-1">Elmendorf AFB</FP>
                    <FP SOURCE="FP-1">Elmendorf AFB Co: AK 99506-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200340005</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 10547</FP>
                    <FP SOURCE="FP-1">Elmendorf AFB</FP>
                    <FP SOURCE="FP-1">Elmendorf AFB Co: AK 99506-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200340006</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <HD SOURCE="HD3">California</HD>
                    <FP SOURCE="FP-1">Bldg. 5057</FP>
                    <FP SOURCE="FP-1">Edwards AFB</FP>
                    <FP SOURCE="FP-1">Los Angeles Co: CA 93523-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200340007</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 6909</FP>
                    <FP SOURCE="FP-1">Edwards  AFB</FP>
                    <FP SOURCE="FP-1">Los Angeles Co: CA 93523-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200340008</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Secured Area</FP>
                    <FP SOURCE="FP-1">28 Bldgs. /Area C</FP>
                    <FP SOURCE="FP-1">Edwards AFB</FP>
                    <FP SOURCE="FP-1">Los Angeles Co: CA 93523-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200340009</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Secured Area</FP>
                    <FP SOURCE="FP-1">Mobile Home/T00706</FP>
                    <FP SOURCE="FP-1">Yosemite Natl Park</FP>
                    <FP SOURCE="FP-1">5001 Trailer Court</FP>
                    <FP SOURCE="FP-1">El Portal Co: Mariposa CA 95318-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Interior</FP>
                    <FP SOURCE="FP-1">Property Number: 61200340009</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">133/215 Conlon</FP>
                    <FP SOURCE="FP-1">Golden Gate Natl Rec Area</FP>
                    <FP SOURCE="FP-1">Mill Valley Co: Marin CA 94941-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Interior</FP>
                    <FP SOURCE="FP-1">Property Number: 61200340011</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <HD SOURCE="HD3">Colorado</HD>
                    <FP SOURCE="FP-1">Bldg. 106</FP>
                    <FP SOURCE="FP-1">Peterson AFB</FP>
                    <FP SOURCE="FP-1">Colorado Springs Co: El Paso CO 80914-8090</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200340010</FP>
                    <FP SOURCE="FP-1">Status: Underutilized</FP>
                    <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material; Within airport runway clear zone; Secured Area.</FP>
                    <FP SOURCE="FP-1">Bldg. 107</FP>
                    <FP SOURCE="FP-1">Peterson AFB</FP>
                    <FP SOURCE="FP-1">Colorado Spring Co: El Paso CO 80914-8090</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200340011</FP>
                    <FP SOURCE="FP-1">Status: Underutilized</FP>
                    <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material; Within airport runway clear zone; Secured Area.</FP>
                    <FP SOURCE="FP-1">Bldg. 108</FP>
                    <FP SOURCE="FP-1">Peterson AFB</FP>
                    <FP SOURCE="FP-1">Colorado Spring Co: El Paso CO 80914-8090</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200340012</FP>
                    <FP SOURCE="FP-1">Status: Underutilized</FP>
                    <FP SOURCE="FP-1">Reasons: Within 2000 ft. of flammable or explosive material; Within airport runway clear zone; Secured Area.</FP>
                    <HD SOURCE="HD3">Hawaii</HD>
                    <FP SOURCE="FP-1">Bldgs. 743, 1002, 6100</FP>
                    <FP SOURCE="FP-1">Johnston Atoll Airfield</FP>
                    <FP SOURCE="FP-1">Honolulu Co: HI</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200340013</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Within 2000 ft. of flammable or explosive material; Within airport runway clear zone; Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 23</FP>
                    <FP SOURCE="FP-1">Naval Station</FP>
                    <FP SOURCE="FP-1">Ford Island Co: Honolulu HI 96818-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200340041</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldgs. 730, 766</FP>
                    <FP SOURCE="FP-1">Pearl City Peninsula</FP>
                    <FP SOURCE="FP-1">Pearl City Co: HI 96819-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200340043</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <HD SOURCE="HD3">Illinois</HD>
                    <FP SOURCE="FP-1">Wings N &amp; P</FP>
                    <FP SOURCE="FP-1">Bldg. 202</FP>
                    <FP SOURCE="FP-1">Argonne National Laboratory</FP>
                    <FP SOURCE="FP-1">Argonne Co: DuPage IL 60439-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Energy</FP>
                    <FP SOURCE="FP-1">Property Number: 41200340020</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <HD SOURCE="HD3">Kansas</HD>
                    <FP SOURCE="FP-1">
                        6 Bldgs.
                        <PRTPAGE P="68100"/>
                    </FP>
                    <FP SOURCE="FP-1">Cottonwood Point/Hillsboro Cove</FP>
                    <FP SOURCE="FP-1">Marion Co: Coffey KS 66861-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340001</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">20 Bldgs.</FP>
                    <FP SOURCE="FP-1">Riverside</FP>
                    <FP SOURCE="FP-1">Burlington Co: Coffey KS 66839-8911</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340002</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">2 Bldgs.</FP>
                    <FP SOURCE="FP-1">Canning Creek/Richey Cove</FP>
                    <FP SOURCE="FP-1">Council Grove Co: Morris KS 66846-9322</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340003</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">6 Bldgs.</FP>
                    <FP SOURCE="FP-1">Santa Fe Trail/Outlet Channel</FP>
                    <FP SOURCE="FP-1">Council Grove Co: Morris KS 66846-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340004</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Residence</FP>
                    <FP SOURCE="FP-1">Melvern Lake Project</FP>
                    <FP SOURCE="FP-1">Melvern Co: Osage KS 66510-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340005</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">2 Bldgs.</FP>
                    <FP SOURCE="FP-1">Management Park</FP>
                    <FP SOURCE="FP-1">Vassar Co: KS 66543-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340006</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg.</FP>
                    <FP SOURCE="FP-1">Hickory Campground</FP>
                    <FP SOURCE="FP-1">Lawrence Co: KS 66049-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340007</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg.</FP>
                    <FP SOURCE="FP-1">Rockhaven Park Area</FP>
                    <FP SOURCE="FP-1">Lawrence Co: KS 66049-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340008</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg.</FP>
                    <FP SOURCE="FP-1">Overlook Park Area</FP>
                    <FP SOURCE="FP-1">Lawrence Co: KS 66049-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340009</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg.</FP>
                    <FP SOURCE="FP-1">Walnut Campground</FP>
                    <FP SOURCE="FP-1">Lawrence Co: KS 66049-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340010</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg.</FP>
                    <FP SOURCE="FP-1">Cedar Ridge Campground</FP>
                    <FP SOURCE="FP-1">Lawrence Co: KS 66049-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340011</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg.</FP>
                    <FP SOURCE="FP-1">Woodridge Park Area</FP>
                    <FP SOURCE="FP-1">Lawrence Co: KS 66049-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340012</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <HD SOURCE="HD3">Missouri</HD>
                    <FP SOURCE="FP-1">Bldg. 3</FP>
                    <FP SOURCE="FP-1">VA Medical Center</FP>
                    <FP SOURCE="FP-1">Jefferson Barracks Division</FP>
                    <FP SOURCE="FP-1">St. Louis Co: MO 63125-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: VA</FP>
                    <FP SOURCE="FP-1">Property Number: 972003400013</FP>
                    <FP SOURCE="FP-1">Status: Underutilized</FP>
                    <FP SOURCE="FP-1">Reason: Secured Area</FP>
                    <FP SOURCE="FP-1">Bldg. 4</FP>
                    <FP SOURCE="FP-1">VA Medical Center</FP>
                    <FP SOURCE="FP-1">Jefferson Barracks Division</FP>
                    <FP SOURCE="FP-1">St. Louis Co: MO 63125-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: VA</FP>
                    <FP SOURCE="FP-1">Property Number: 97200340002</FP>
                    <FP SOURCE="FP-1">Status: Underutilized</FP>
                    <FP SOURCE="FP-1">Reason: Secured Area</FP>
                    <FP SOURCE="FP-1">Bldg. 27</FP>
                    <FP SOURCE="FP-1">VA Medical Center</FP>
                    <FP SOURCE="FP-1">Jefferson Barracks Division</FP>
                    <FP SOURCE="FP-1">St. Louis Co: MO 63125-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: VA</FP>
                    <FP SOURCE="FP-1">Property Number: 97200340003</FP>
                    <FP SOURCE="FP-1">Status: Underutilized</FP>
                    <FP SOURCE="FP-1">Reason: Secured Area</FP>
                    <FP SOURCE="FP-1">Bldg. 28</FP>
                    <FP SOURCE="FP-1">VA Medical Center</FP>
                    <FP SOURCE="FP-1">Jefferson Barracks Division</FP>
                    <FP SOURCE="FP-1">St. Louis Co: MO 63125-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: VA</FP>
                    <FP SOURCE="FP-1">Property Number: 97200340004</FP>
                    <FP SOURCE="FP-1">Status: Underutilized</FP>
                    <FP SOURCE="FP-1">Reason: Secured Area</FP>
                    <FP SOURCE="FP-1">Bldg. 29</FP>
                    <FP SOURCE="FP-1">VA Medical Center</FP>
                    <FP SOURCE="FP-1">Jefferson Barracks Division</FP>
                    <FP SOURCE="FP-1">St. Louis Co: MO 63125-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: VA</FP>
                    <FP SOURCE="FP-1">Property Number: 97200340005</FP>
                    <FP SOURCE="FP-1">Status: Underutilized</FP>
                    <FP SOURCE="FP-1">Reason: Secured Area</FP>
                    <FP SOURCE="FP-1">Bldg. 50</FP>
                    <FP SOURCE="FP-1">VA Medical Center</FP>
                    <FP SOURCE="FP-1">Jefferson Barracks Division</FP>
                    <FP SOURCE="FP-1">St. Louis Co: MO 63125-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: VA</FP>
                    <FP SOURCE="FP-1">Property Number: 97200340006</FP>
                    <FP SOURCE="FP-1">Status: Underutilized</FP>
                    <FP SOURCE="FP-1">Reason: Secured Area</FP>
                    <HD SOURCE="HD3">New Mexico</HD>
                    <FP SOURCE="FP-1">Bldg. 615</FP>
                    <FP SOURCE="FP-1">Kirtland AFB</FP>
                    <FP SOURCE="FP-1">Kirtland AFB Co: Bernalillo NM 87117-5663</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200340014</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 736</FP>
                    <FP SOURCE="FP-1">Kirtland AFB</FP>
                    <FP SOURCE="FP-1">Kirtland AFB Co: Bernalillo NM 87117-5663</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200340015</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Secured Area </FP>
                    <FP SOURCE="FP-1">Bldg. 1013</FP>
                    <FP SOURCE="FP-1">Kirtland AFB</FP>
                    <FP SOURCE="FP-1">Kirtland AFB Co: Bernalillo NM 87117-5663</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200340016</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Secured Area </FP>
                    <FP SOURCE="FP-1">Bldg. 20419</FP>
                    <FP SOURCE="FP-1">Kirtland AFB</FP>
                    <FP SOURCE="FP-1">Kirtland AFB Co: Bernalillo NM 87117-5663</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200340017</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Secured Area </FP>
                    <FP SOURCE="FP-1">Bldgs. 29014, 29016, 29017</FP>
                    <FP SOURCE="FP-1">Kirtland AFB</FP>
                    <FP SOURCE="FP-1">Kirtland AFB Co: Bernalillo NM 87117-5663</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200340018</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area Extensive deterioration </FP>
                    <FP SOURCE="FP-1">Bldg. 30102</FP>
                    <FP SOURCE="FP-1">Kirtland AFB</FP>
                    <FP SOURCE="FP-1">Kirtland AFB Co: Bernalillo NM 87117-5663</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200340019</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Secured Area </FP>
                    <FP SOURCE="FP-1">Bldgs. 37532, 37534</FP>
                    <FP SOURCE="FP-1">Kirtland AFB</FP>
                    <FP SOURCE="FP-1">Kirtland AFB Co: Bernalillo NM 87117-5663</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200340020</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area  Extensive deterioration </FP>
                    <FP SOURCE="FP-1">Bldg. 57005</FP>
                    <FP SOURCE="FP-1">Kirtland AFB</FP>
                    <FP SOURCE="FP-1">Kirtland AFB Co: Bernalillo NM 87117-5663</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200340021</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area Extensive deterioration </FP>
                    <FP SOURCE="FP-1">Bldgs. 57006, 57013</FP>
                    <FP SOURCE="FP-1">Kirtland AFB</FP>
                    <FP SOURCE="FP-1">Kirtland AFB Co: Bernalillo NM 87117-5663</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Air Force</FP>
                    <FP SOURCE="FP-1">Property Number: 18200340022</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reasons: Secured Area Extensive deterioration</FP>
                    <HD SOURCE="HD3">Ohio</HD>
                    <FP SOURCE="FP-1">Army Reserve Center</FP>
                    <FP SOURCE="FP-1">Plymouth Road</FP>
                    <FP SOURCE="FP-1">Jamestown Co: Greene OH 45335-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: GSA</FP>
                    <FP SOURCE="FP-1">Property Number: 54200340009</FP>
                    <FP SOURCE="FP-1">Status: Surplus</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">GSA Number: 4-G-VA-0734</FP>
                    <HD SOURCE="HD3">Oklahoma</HD>
                    <FP SOURCE="FP-1">2 Bldgs.</FP>
                    <FP SOURCE="FP-1">Outlet Channel/Walker Creek</FP>
                    <FP SOURCE="FP-1">Waurika Co: OK 73573-0029</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340013</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">2 Bldgs.</FP>
                    <FP SOURCE="FP-1">
                        Damsite South
                        <PRTPAGE P="68101"/>
                    </FP>
                    <FP SOURCE="FP-1">Stigler Co: OK 74462-9440</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340014</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">19 Bldgs.</FP>
                    <FP SOURCE="FP-1">Kaw Lake</FP>
                    <FP SOURCE="FP-1">Ponca City Co: OK 74601-9962</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340015</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">30 Bldgs.</FP>
                    <FP SOURCE="FP-1">Keystone Lake</FP>
                    <FP SOURCE="FP-1">Sand Springs Co: OK 74063-9338</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340016</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">13 Bldgs.</FP>
                    <FP SOURCE="FP-1">Oologah Lake</FP>
                    <FP SOURCE="FP-1">Oologah Co: OK 74053-0700</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340017</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">14 Bldgs.</FP>
                    <FP SOURCE="FP-1">Pine Creek Lake</FP>
                    <FP SOURCE="FP-1">Valliant Co: OK 74764-9801</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340018</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">6 Bldgs.</FP>
                    <FP SOURCE="FP-1">Sardis Lake</FP>
                    <FP SOURCE="FP-1">Clayton Co: OK 74536-9729</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340019</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">24 Bldgs.</FP>
                    <FP SOURCE="FP-1">Skiatook Lake</FP>
                    <FP SOURCE="FP-1">Skiatook Co: OK 74070-9803</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340020</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">40 Bldgs.</FP>
                    <FP SOURCE="FP-1">Eufaula Lake</FP>
                    <FP SOURCE="FP-1">Stigler Co: OK 74462-5135</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340021</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">2 Bldgs.</FP>
                    <FP SOURCE="FP-1">Holiday Cove</FP>
                    <FP SOURCE="FP-1">Stigler Co: OK 74462-5135</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340022</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">18 Bldgs.</FP>
                    <FP SOURCE="FP-1">Fort Gibson</FP>
                    <FP SOURCE="FP-1">Ft. Gibson Co: Wagoner OK 74434-0370</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340023</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">2 Bldgs.</FP>
                    <FP SOURCE="FP-1">Fort Supply</FP>
                    <FP SOURCE="FP-1">Ft. Supply Co: Woodward OK 73841-0248</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340024</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Game Bird House</FP>
                    <FP SOURCE="FP-1">Fort Supply Lake</FP>
                    <FP SOURCE="FP-1">Ft. Supply Co: Woodward OK 73841-0248</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340025</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">11 Bldgs.</FP>
                    <FP SOURCE="FP-1">Hugo Lake</FP>
                    <FP SOURCE="FP-1">Sawyer Co: OK 74756-0099</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340026</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">5 Bldgs.</FP>
                    <FP SOURCE="FP-1">Birch Cove/Twin Cove</FP>
                    <FP SOURCE="FP-1">Skiatook Co: OK 74070-9803</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340027</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">2 Bldgs.</FP>
                    <FP SOURCE="FP-1">Fairview Group Camp</FP>
                    <FP SOURCE="FP-1">Canton Co: OK 73724-0069</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340028</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">2 Bldgs.</FP>
                    <FP SOURCE="FP-1">Chouteau &amp; D Bluff</FP>
                    <FP SOURCE="FP-1">Gore Co: Wagoner OK 74935-9404</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340029</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">2 Bldgs.</FP>
                    <FP SOURCE="FP-1">Newt Graham L&amp;D</FP>
                    <FP SOURCE="FP-1">Gore Co: OK 74935-9404</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340030</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">6 Bldgs.</FP>
                    <FP SOURCE="FP-1">Damsite/Fisherman's Landing</FP>
                    <FP SOURCE="FP-1">Sallisaw Co: OK 74955-9445</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340031</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">10 Bldgs.</FP>
                    <FP SOURCE="FP-1">Webbers Falls Lake</FP>
                    <FP SOURCE="FP-1">Gore Co: OK 74435-5541</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340032</FP>
                    <FP SOURCE="FP-1">Status; Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">14 Bldgs.</FP>
                    <FP SOURCE="FP-1">Copan Lake</FP>
                    <FP SOURCE="FP-1">Copan Co: OK 74022-9762</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340033</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <HD SOURCE="HD3">South Carolina</HD>
                    <FP SOURCE="FP-1">Bldg.</FP>
                    <FP SOURCE="FP-1">Fishing Creek/Deer Run</FP>
                    <FP SOURCE="FP-1">Clarks Hill Co: SC 29821-0010</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340034</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <HD SOURCE="HD3">Texas</HD>
                    <FP SOURCE="FP-1">58 Bldgs.</FP>
                    <FP SOURCE="FP-1">Texoma Lake</FP>
                    <FP SOURCE="FP-1">Denison Co: TX 75020-6425</FP>
                    <FP SOURCE="FP-1">Landholding Agency: COE</FP>
                    <FP SOURCE="FP-1">Property Number: 31200340035</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <HD SOURCE="HD3">Virginia</HD>
                    <FP SOURCE="FP-1">Wharf 2</FP>
                    <FP SOURCE="FP-1">Naval Station</FP>
                    <FP SOURCE="FP-1">St. Juliens Creek Annex</FP>
                    <FP SOURCE="FP-1">Chesapeake Co: VA</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200340044</FP>
                    <FP SOURCE="FP-1">Status: Unutilized</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. M2</FP>
                    <FP SOURCE="FP-1">Naval Station</FP>
                    <FP SOURCE="FP-1">St. Juliens Creek Annex</FP>
                    <FP SOURCE="FP-1">Chesapeake Co: VA</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200340045</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 13</FP>
                    <FP SOURCE="FP-1">Naval Station</FP>
                    <FP SOURCE="FP-1">St. Juliens Creek Annex</FP>
                    <FP SOURCE="FP-1">Chesapeake Co: VA</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200340046</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 20</FP>
                    <FP SOURCE="FP-1">Naval Station</FP>
                    <FP SOURCE="FP-1">St. Juliens Creek Annex</FP>
                    <FP SOURCE="FP-1">Chesapeake Co: VA</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200340047</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 64</FP>
                    <FP SOURCE="FP-1">Naval Station</FP>
                    <FP SOURCE="FP-1">St. Juliens Creek Annex</FP>
                    <FP SOURCE="FP-1">Chesapeake Co: VA</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200340048</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldgs. 65, 66, 67</FP>
                    <FP SOURCE="FP-1">Naval Station</FP>
                    <FP SOURCE="FP-1">St. Juliens Creek Annex</FP>
                    <FP SOURCE="FP-1">Chesapeake Co: VA</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200340049</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldg. 86</FP>
                    <FP SOURCE="FP-1">Naval Station</FP>
                    <FP SOURCE="FP-1">St. Juliens Creek Annex</FP>
                    <FP SOURCE="FP-1">Chesapeake Co: VA</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200340050</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <FP SOURCE="FP-1">Bldgs. 255, 275</FP>
                    <FP SOURCE="FP-1">Naval Station</FP>
                    <FP SOURCE="FP-1">St. Juliens Creek Annex</FP>
                    <FP SOURCE="FP-1">Chesapeake Co: VA</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200340051</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <PRTPAGE P="68102"/>
                    <HD SOURCE="HD3">Washington</HD>
                    <FP SOURCE="FP-1">Bldg. 2633</FP>
                    <FP SOURCE="FP-1">Naval Air Station</FP>
                    <FP SOURCE="FP-1">Oak Harbor Co: Island WA 98278-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: Navy</FP>
                    <FP SOURCE="FP-1">Property Number: 77200340052</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Extensive deterioration</FP>
                    <HD SOURCE="HD3">West Virginia</HD>
                    <FP SOURCE="FP-1">Radio Transmitter Rcv Site</FP>
                    <FP SOURCE="FP-1">Greenbrier Street</FP>
                    <FP SOURCE="FP-1">Charleston Co: WV 25311-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: GSA</FP>
                    <FP SOURCE="FP-1">Property Number: 54200340011</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Within 2,000 ft. of flammable or explosive material</FP>
                    <FP SOURCE="FP-1">GSA Number: 4-U-WV-0547</FP>
                    <HD SOURCE="HD2">Land (by State)</HD>
                    <HD SOURCE="HD3">Kentucky</HD>
                    <FP SOURCE="FP-1">Ferry Access Site</FP>
                    <FP SOURCE="FP-1">Route 130</FP>
                    <FP SOURCE="FP-1">Uniontown Co: KY 42461-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: GSA</FP>
                    <FP SOURCE="FP-1">Property Number: 54200340007</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Floodway</FP>
                    <FP SOURCE="FP-1">GSA Number: 4-D-KY-0612</FP>
                    <HD SOURCE="HD3">Montana</HD>
                    <FP SOURCE="FP-1">Sewage Lagoons/40 acres</FP>
                    <FP SOURCE="FP-1">VA Center</FP>
                    <FP SOURCE="FP-1">Ft. Harrison Co: MT 59639-</FP>
                    <FP SOURCE="FP-1">Landholding Agency: VA</FP>
                    <FP SOURCE="FP-1">Property Number: 97200340007</FP>
                    <FP SOURCE="FP-1">Status: Excess</FP>
                    <FP SOURCE="FP-1">Reason: Floodway</FP>
                </EXTRACT>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-29872  Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 42-29-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Fish and Wildlife Service</SUBAGY>
                <SUBJECT>Notice of Availability of a Draft Revised Recovery Plan for the Chittenango Ovate Amber Snail for Review and Comment</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Fish and Wildlife Service, Department of the Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The U.S. Fish and Wildlife Service (Service) announces availability for public review of a draft revised recovery plan for the Chittenango ovate amber snail (
                        <E T="03">Novisuccinea chittenangoensis</E>
                        ). This species is federally listed as threatened under the Endangered Species Act of 1973, as amended (Act) (16 U.S.C. 1531 
                        <E T="03">et seq.</E>
                        ). The Service solicits review and comment from the public on this draft plan.
                    </P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments on the draft recovery plan received on or before January 5, 2004, will be considered by the Service.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Persons wishing to review the draft recovery plan may obtain a copy through the following means:</P>
                    <FP SOURCE="FP-1">1. Through a written request to the Field Supervisor, U.S. Fish and Wildlife Service, New York Field Office, 3817 Luker Road, Cortland, New York 13045.</FP>
                    <FP SOURCE="FP-1">2. By telephone: 607-753-9334 or fax 607-753-9699.</FP>
                    <FP SOURCE="FP-1">
                        3. By e-mail to 
                        <E T="03">Robyn_Niver@fws.gov.</E>
                    </FP>
                    <FP SOURCE="FP-1">
                        4. By accessing the Field Office Web site: 
                        <E T="03">http://nyfo.fws.gov.</E>
                    </FP>
                    <P>Copies of the draft recovery plan may also be viewed at two public libraries: Moon Library, State University of New York College of Environmental Science and Forestry, 1 Forestry Drive, Syracuse, New York 13210 (Telephone: 315-470-6726).</P>
                    <P>Sullivan Free Library, 519 McDonald Street (Back side of Genesee Street), Chittenango, New York 13037 (Telephone: 615-687-6331).</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Ms. Robyn Niver, U.S. Fish and Wildlife Service, New York Field Office, 3817 Luker Road, Cortland, New York 13045.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <HD SOURCE="HD1">Background</HD>
                <P>Restoring an endangered or threatened animal or plant to the point where it is again a secure, self-sustaining member of its ecosystem is a primary goal of the Service's endangered species program. To help guide the recovery effort, the Service is working to prepare recovery plans for most of the federally listed species native to the United States. Recovery plans describe actions necessary for the conservation of the species, establish criteria which, when met, would result in a determination that the species no longer needs the protection of the Act, and provide estimates of the time and cost for implementing the needed recovery measures.</P>
                <P>The Act requires recovery plans for listed species unless such a plan would not promote the conservation of a particular species. Section 4(f) of the Act, as amended in 1988, requires that public notice and opportunity for public review and comment be provided during recovery plan development. The Service will consider all information received during a public comment period when preparing each new or revised recovery plan for approval. The Service and other Federal agencies will also take these comments into consideration in the course of implementing approved recovery plans.</P>
                <P>
                    The Chittenango ovate amber snail (
                    <E T="03">Novisuccinea chittenangoensis</E>
                    ) was listed as a threatened species in July 1978, and the initial recovery plan for the species was completed in March 1983. Since its discovery in 1905, only one extant 
                    <E T="03">N. chittenangoensis</E>
                     colony has been verified, from a site within the Chittenango Falls State Park in Madison County, New York. The Chittenango ovate amber snail was listed due to its rarity and population decline. Since listing, habitat protection and captive propagation measures have been implemented, but the species' status has become exceedingly precarious. The primary threats to the snail are its small population size and limited distribution as well as an undefined negative interaction with an introduced snail, 
                    <E T="03">Succinea</E>
                     sp. B. Additionally, potential threats persist from habitat changes and inadvertent human disturbance.
                </P>
                <P>The Chittenango ovate amber snail is a terrestrial species that requires the cool, mild-temperature, moist conditions provided by the waterfalls and mist in its environment. Its habitat lies within a ravine at the base of a 167-foot waterfall, and the ledges where it is found comprise an early successional sere that is periodically rejuvenated to a bare substrate by floodwaters. The species requires a substrate rich in calcium carbonate and appears to prefer green vegetation such as the various mosses, liverworts, and other low herbaceous vegetation found within the spray zone adjacent to the falls. Clean water may be necessary to maintain essential habitat, although water quality may have only an indirect effect on the snail.</P>
                <P>
                    The recovery goal for the Chittenango ovate amber snail is to achieve long-term viability of the species in the wild, thereby allowing it to be taken off the Federal List of Endangered and Threatened Wildlife. The first phase of recovery for 
                    <E T="03">N. chittenangoensis</E>
                     will involve stabilizing the extant population at Chittenango Falls. To accomplish this, a habitat management/protection plan for Chittenango Falls is needed, along with research into the species' biological requirements and genetic status as well as possible means of controlling the competing 
                    <E T="03">Succinea</E>
                     sp. B and abating any additional threats to the snail and its habitat. Given the grave uncertainty about the in situ survival prospects of this snail, captive propagation is also viewed as essential for the species' stabilization.
                </P>
                <P>
                    Once the 
                    <E T="03">N. chittenangoensis</E>
                     population at Chittenango Falls is stabilized or increased, the second recovery phase for the species will involve establishing additional Chittenango ovate amber snail subpopulations at the Falls. In conjunction with long-term abatement 
                    <PRTPAGE P="68103"/>
                    of threats to the species, this should safeguard the species from extinction caused by highly localized events. Long-term maintenance of 
                    <E T="03">ex situ</E>
                     populations will also help ensure the species' survival.
                </P>
                <HD SOURCE="HD1">Public Information Solicited</HD>
                <P>
                    The Service solicits public comments on the recovery plan described. All comments received by the date specified will be considered prior to approval of the plan. Written comments and materials regarding the plan should be addressed to the Field Supervisor (see 
                    <E T="02">ADDRESSES</E>
                     section). Comments and materials received will be available, by appointment, for public inspection during normal business hours at the above address.
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>The authority for this action is section 4(f) of the Endangered Species Act, 16 U.S.C. 1533(f).</P>
                </AUTH>
                <SIG>
                    <DATED>Dated: November 7, 2003.</DATED>
                    <NAME>Richard O. Bennett,</NAME>
                    <TITLE>Acting Regional Director, Region 5, Fish and Wildlife Service, Department of the Interior. </TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30254 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4310-55-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Geological Survey</SUBAGY>
                <SUBJECT>Request for Public Comments on Information Collection Submitted to the Office of Management and Budget for Review Under the Paperwork Reduction Act</SUBJECT>
                <P>
                    A request extending the collection of information has been submitted to the Office of Management and Budget for approval under the provisions of the Paperwork Reduction Act (44 U.S.C. Chapter 35). Copies of the proposed collection of information and related forms may be obtained by contacting the USGS Clearance Officer at the phone number listed below. OMB has up to 60 days to approve or disapprove the information collection but may respond after 30 days; therefore, public comments should be submitted to OMB within 30 days in order to assure their maximum consideration. Address your comments and suggestions on the information collection requirement by either fax (202) 395-6566 or e-mail (
                    <E T="03">oira_docket@omb.eop.gov</E>
                    ) to the Office of Information and Regulatory Affairs, Office of Management and Budget, Attention: Desk Officer for the Department of the Interior (OMB Control Number 1028-0060). Send copies of your comments and suggestions to the USGS Clearance Officer, U.S. Geological Survey, 807 National Center, Reston, VA 20192.
                </P>
                <P>As required by OMB regulations at CFR 1320.8(d)(1), the U.S. Geological Survey solicits specific public comments regarding the proposed information collection as to:</P>
                <P>1. Whether the collection of information is necessary for the proper performance of the functions of the USGS, including whether the information will have practical utility;</P>
                <P>2. The accuracy of the USGS estimate of the burden of the collection of information, including the validity of the methodology and assumptions used;</P>
                <P>3. The utility, quality, and clarity of the information to be collected; and,</P>
                <P>4. How to minimize the burden of the collection of information on those who are to respond, including the use of appropriate automated electronic, mechanical, or other forms of information technology.</P>
                <P>
                    <E T="03">Title:</E>
                     Mine, Development, and Mineral Exploration Supplement.
                </P>
                <P>
                    <E T="03">Current OMB approval number:</E>
                     1028-0060.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     Respondents supply the U.S. Geological Survey with domestic production, exploration, and mine development data on nonfuel mineral commodities. This information will be published as an Annual Report for use by Government agencies, industry, and the general public.
                </P>
                <P>
                    <E T="03">Bureau form number:</E>
                     9-4000-A.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     Annual.
                </P>
                <P>
                    <E T="03">Description of respondents:</E>
                     Nonfuel Mineral Producers and Exploration Operations.
                </P>
                <P>
                    <E T="03">Annual Responses:</E>
                     754.
                </P>
                <P>
                    <E T="03">Annual burden hours:</E>
                     566.
                </P>
                <P>
                    <E T="03">Bureau clearance officer:</E>
                     John E. Cordyack, Jr., (703) 648-7313.
                </P>
                <SIG>
                    <NAME>John H. DeYoung, Jr.,</NAME>
                    <TITLE>Chief Scientist, Minerals Information Team.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30196  Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4310-Y7-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Bureau of Indian Affairs</SUBAGY>
                <SUBJECT>Rate Adjustments for Indian Irrigation Facilities</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Indian Affairs, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of rate adjustments.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Bureau of Indian Affairs (BIA) owns or has an interest in irrigation facilities located on various Indian reservations throughout the United States. The BIA establishes irrigation assessment rates to recover its costs to administer, operate, maintain, and rehabilitate certain of those facilities. We are notifying you that we have adjusted the irrigation assessment rates at several of our irrigation facilities where we are required to recover our full costs of operation and maintenance.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>The irrigation assessment rates shown in the tables were effective on January 1, 2003.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        For details about a particular BIA irrigation facility, please use the tables in the 
                        <E T="02">SUPPLEMENTARY INFORMATION</E>
                         section to contact the regional or agency office where the facility is located.
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    A Notice of Proposed Rate Adjustment was published in the 
                    <E T="04">Federal Register</E>
                     on January 9, 2003 (68 FR 1191), to adjust the irrigation rates at several BIA irrigation facilities. The public and interested parties were provided an opportunity to submit written comments during the 60-day period subsequent to January 9, 2003.
                </P>
                <HD SOURCE="HD1">Did the BIA Receive any Comments on the Proposed Irrigation Assessment Rate Adjustments?</HD>
                <P>Written comments were received for: (a) Fort Belknap Irrigation Project, Montana; (b) Wapato Irrigation Project, Washington; and (c) Wind River Irrigation Project, Wyoming.</P>
                <HD SOURCE="HD1">What Issues Were of Concern by the Commentators?</HD>
                <P>The commentors were concerned with one or more of the following three issues: (1) Consultation with stakeholders; (2) how funds collected from stakeholders are expended on operation and maintenance; and (3) the impact of an assessment rate increase on the local agricultural economy.</P>
                <HD SOURCE="HD1">How Does BIA Respond to the Concern of Consultation with Stakeholders?</HD>
                <P>
                    Consultations between stakeholders and any of the BIA irrigation facilities are ongoing through local meetings held periodically at different locations convenient to the stakeholders of the individual irrigation facilities. At these consultation meetings, any issue of concern by a stakeholder can be brought up and discussed such as water operations, facility maintenance, and financial management. Stakeholders also can contact BIA representatives at the specific facility serving them using the tables in the 
                    <E T="02">SUPPLEMENTARY INFORMATION</E>
                     section to discuss issues of concern.
                    <PRTPAGE P="68104"/>
                </P>
                <HD SOURCE="HD1">How Does BIA Respond to the Concern of How Funds Are Expended for Operation and Maintenance?</HD>
                <P>
                    The BIA's records for expenditures on all of its irrigation facilities are public records and available for review by stakeholders or interested parties. These records can be reviewed during normal business hours at the individual agency offices. To review these records, stakeholders and interested parties are directed to contact the BIA representative at the specific facility serving them using the tables in the 
                    <E T="02">SUPPLEMENTARY INFORMATION</E>
                     section.
                </P>
                <HD SOURCE="HD1">How Does BIA Respond to the Concern of an Irrigation Assessment Rate Increase and its Impact on the Local Agricultural Economy?</HD>
                <P>All of the BIA's irrigation projects are important economic contributors to the local communities they serve, contributing millions in crop value annually. Historically, BIA tempered irrigation rate increases to demonstrate sensitivity to the economic impact on water users. This has resulted in a rate deficiency at most of the irrigation projects.</P>
                <P>Over the past several years the BIA's irrigation program has been the subject of several Office of Inspector General (OIG) audits. In the most recent audit, No. 96-I-641, March 1996, the OIG concluded, “Operation and maintenance revenues were insufficient to maintain the projects, and some projects had deteriorated to the extent that their continued capability to deliver water was in doubt. This occurred because operation and maintenance rates were not based on the full cost of delivering water, including the costs of systematically rehabilitating and replacing project facilities and equipment, and because project personnel did not seek regular rate increases to cover the full cost of operation.” This audit recommendation is still outstanding.</P>
                <P>A previous OIG audit, No. 88-42, February 1988, reached the same conclusion. A separate audit performed on the Wapato Irrigation Project, No. 95-I-1402, September 1995, reinforced the general findings of the OIG on the BIA's irrigation program. This pointed out a lack of response by the BIA to the original findings of the OIG in addressing this critical issue over an extended period of time. The BIA must systematically review and evaluate irrigation assessment rates and adjust them when necessary to reflect the full costs to properly operate, and perform all appropriate maintenance on, the irrigation facility infrastructure for safe and reliable operation. If this review and evaluation is not accomplished, a rate deficiency can eventually accumulate. Overcoming rate deficiencies can result in the BIA having to raise irrigation assessment rates in larger increments and over shorter time frames than would have been otherwise necessary.</P>
                <HD SOURCE="HD1">Does the BIA Have Any Proposed Rate Adjustments That Were Not Put Into Effect?</HD>
                <P>The proposed rate adjustment for the 2003 irrigation season at the Wind River Irrigation Project from $12.00 to $13.00 was not put into effect. After further consultation with the stakeholders, the BIA agreed to delay the proposed rate adjustment until the 2004 irrigation season. For the 2004 irrigation season a rate adjustment from $12.00 to $14.00 is proposed to make up the lost revenue for the 2003 irrigation season. The proposed rate adjustment is in a separate notice.</P>
                <HD SOURCE="HD1">Where Can I Get Information on the Regulatory and Legal Citations in This Notice?</HD>
                <P>
                    You can contact the individuals listed in the contact tables below or you can use the Internet site for the Government Printing Office at 
                    <E T="03">http://www.gpo.gov</E>
                    .
                </P>
                <HD SOURCE="HD1">What Authorizes Us To Issue This Notice?</HD>
                <P>Our authority to issue this document is vested in the Secretary of the Interior by 5 U.S.C. 301 and the Act of August 14, 1914 (38 Stat. 583; 25 U.S.C. 385). The Secretary has in turn delegated this authority to the Assistant Secretary—Indian Affairs under part 209, chapter 8.1A, of the Department of the Interior's Departmental Manual.</P>
                <HD SOURCE="HD1">Does This Notice Affect Me?</HD>
                <P>This notice affects you if you own or lease land within the assessable acreage of one of our irrigation facilities, or you have a carriage agreement with one of our irrigation facilities.</P>
                <HD SOURCE="HD1">Who Can I Contact for Further Information?</HD>
                <P>The following tables list the regional and agency contacts for the irrigation facilities where the BIA recovers its costs for local administration, operation, maintenance, and rehabilitation.</P>
                <GPOTABLE COLS="2" OPTS="L2,tp0,p0,8/9,i1" CDEF="s100,r200">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1"> </CHED>
                    </BOXHD>
                    <ROW EXPSTB="01" RUL="s,">
                        <ENT I="21">
                            <E T="02">Northwest Region Contacts</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="22">Stanley Speaks, Regional Director</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Bureau of Indian Affairs, Northwest Regional Office</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">911 N.E. 11th Avenue</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Portland, Oregon 97232-4169</ENT>
                    </ROW>
                    <ROW RUL="s,s">
                        <ENT I="22">Telephone (503) 231-6702</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11">Name: </ENT>
                        <ENT>Contacts:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Flathead Irrigation Project </ENT>
                        <ENT>Ernest T. Moran, Superintendent,Flathead Agency Irrigation Division,PO Box 40,Pablo, Montana 59855-5555,Telephone: (406) 675-2700.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Fort Hall Irrigation Project</ENT>
                        <ENT>Eric J. LaPointe, Superintendent,Fort Hall Agency,PO Box 220,Fort Hall, Idaho 83203-0220,Telephone: (208) 238-2301.</ENT>
                    </ROW>
                    <ROW RUL="s,s">
                        <ENT I="01">Wapato Irrigation Project </ENT>
                        <ENT>Pierce Harrison, Project Administrator,Wapato Irrigation Project,PO Box 220,Wapato, WA 98951-0220,Telephone: (509) 877-3155.</ENT>
                    </ROW>
                    <ROW EXPSTB="01" RUL="s,">
                        <ENT I="21">
                            <E T="02">Rocky Mountain Region Contacts</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="22">Keith Beartusk, Regional Director</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Bureau of Indian Affairs, Rock Mountain Regional Office</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">316 North 26th Street</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Billings, Montana 59101.</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="22">Telephone: (406) 247-7943</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11">Name: </ENT>
                        <ENT>Contacts:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Blackfeet Irrigation Project </ENT>
                        <ENT>
                            Ross Denny, Superintendent,Cliff Hall, Irrigation Manager,Box 880,Browning, MT 59417,Telephones: (406) 338-7544, Superintendent;(406) 338-7519, Irrigation.
                            <PRTPAGE P="68105"/>
                        </ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Crow Irrigation Project</ENT>
                        <ENT>Gordon Jackson, Superintendent,Dan Lowe, Irrigation Manager, PO Box 69,Crow Agency, MT 59022,Telephones: (406) 638-2672, Superintendent;(406) 638-2863, Irrigation.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Fort Belknap Irrigation Project </ENT>
                        <ENT>Cleo Hamilton, Superintendent,Dan Spencer, Irrigation Manager,R.R.1, Box 980,Harlem, MT 59526,Telephones: (406) 353-2901 Superintendent;(406) 353-2905, Irrigation.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Fort Peck Irrigation Project </ENT>
                        <ENT>Spike Bighorn, Superintendent,PO Box 637,Poplar, MT 59255,Rhonda Knutsen, Irrigation Manager, 602 6th Avenue North,Wolf Point, MT 59201, Telephones: (406) 768-5312, Superintendent;(406) 653-1752, Irrigation.</ENT>
                    </ROW>
                    <ROW RUL="s">
                        <ENT I="01">Wind River Irrigation Project </ENT>
                        <ENT>Steven Pollock, (Acting) Superintendent,Hilare Peck, Irrigation Manager,PO Box 158,Fort Washakie, WY 82514,Telephones: (307) 332-7810, Superintendent;(307) 332-2596, Irrigation.</ENT>
                    </ROW>
                    <ROW EXPSTB="01" RUL="s,">
                        <ENT I="21">
                            <E T="02">Southwest Region Contacts</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="22">Rob Baracker, Regional Director</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Bureau of Indian Affairs, Southwest Regional Office</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">615 First Street, NW</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Albuquerque, New Mexico 87102</ENT>
                    </ROW>
                    <ROW RUL="s,">
                        <ENT I="22">Telephone (505) 346-7587</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11">Name: </ENT>
                        <ENT>Contacts:</ENT>
                    </ROW>
                    <ROW RUL="s,">
                        <ENT I="01">Pine River Irrigation Project </ENT>
                        <ENT>Michael Stancampiano, Superintendent, Kenneth Caveney, Irrigation Engineer, PO Box 315, Ignacio, CO 81137-0315, Telephones: (970) 563-4511, Superintendent; (970) 563-1017, Irrigation.</ENT>
                    </ROW>
                    <ROW EXPSTB="01" RUL="s,">
                        <ENT I="21">
                            <E T="02">Western Region Contacts</E>
                        </ENT>
                    </ROW>
                    <ROW EXPSTB="00">
                        <ENT I="22">Wayne Nordwall, Regional Director</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Bureau of Indian Affairs, Western Regional Office</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">PO Box 10</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22">Phoenix, Arizona 85001</ENT>
                    </ROW>
                    <ROW RUL="s,">
                        <ENT I="22">Telephone (602) 379-6600</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11">Name: </ENT>
                        <ENT>Contacts:</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Colorado River Irrigation Project </ENT>
                        <ENT>Allen Anspach, Superintendent, R.R. 1, Box 9-C, Parker, AZ 85344, Telephone: (928) 669-7111.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Duck Valley Irrigation Project </ENT>
                        <ENT>Paul Young, Superintendent, 1555 Shoshone Circle, Elko, Nevada 89801, Telephone: (775) 738-0569, Superintendent.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Fort Yuma Irrigation Project </ENT>
                        <ENT>William Pyott, Land Operations Officer, P.O. Box 11000, Yuma, Arizona, Telephone: (520) 782-1202.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">San Carlos Irrigation Project Joint Works </ENT>
                        <ENT>Carl Christensen, Irrigation Manager, 13805 N. Arizona Boulevard, Coolidge, AZ 85228, Telephone: (520) 723-6216.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">San Carlos Irrigation Project Indian Works </ENT>
                        <ENT>Joe Revak, Pima Agency, Land Operations, Box 8, Sacaton, AZ 85247, Telephone: (520) 562-3372.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Uintah Irrigation Project </ENT>
                        <ENT>Lynn Hansen, Irrigation Manager, PO Box 130, Fort Duchesne, UT 84026, Telephone: (435) 722-4341.</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Walker River Irrigation Project </ENT>
                        <ENT>Robert Hunter, Superintendent, 1677 Hot Springs Road, Carson City, Nevada 89706, Telephone: (775) 887-3500.</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">What Will BIA Charge for the 2003 Irrigation Seasons?</HD>
                <P>The rate tables below show how we billed each of our irrigation facilities for the 2003 irrigation season as indicated. An asterisk immediately following the name of the facilities notes the irrigation facilities where rates were adjusted.</P>
                <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s100,r100,11">
                    <TTITLE>Northwest Region Rate Table</TTITLE>
                    <BOXHD>
                        <CHED H="1">Name</CHED>
                        <CHED H="1">Rate category</CHED>
                        <CHED H="1">
                            2003 
                            <LI>season rate</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Flathead Irrigation Project (See Note #1 below)</ENT>
                        <ENT>Basic per acre</ENT>
                        <ENT>$19.95</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Fort Hall Irrigation Project *</ENT>
                        <ENT>Basic per acre</ENT>
                        <ENT>22.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Fort Hall Irrigation Project—Minor Units</ENT>
                        <ENT>Basic per acre</ENT>
                        <ENT>14.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Fort Hall Irrigation Project—Michaud *</ENT>
                        <ENT>Basic per acre</ENT>
                        <ENT>30.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Pressure per acre</ENT>
                        <ENT>43.50</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Wapato Irrigation Project—Ahtanum Unit *</ENT>
                        <ENT>Billing Charge Per Tract</ENT>
                        <ENT>5.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Farm unit/land tracts up to one acre (minimum charge)</ENT>
                        <ENT>13.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Farm unit/land tracts over one acre—per acre</ENT>
                        <ENT>13.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Wapato Irrigation Project—Toppenish/Simcoe Units *</ENT>
                        <ENT>Billing Charge Per Tract</ENT>
                        <ENT>5.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Farm unit/land tracts up to one acre (minimum charge)</ENT>
                        <ENT>13.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Farm unit/land tract over one acre—per acre</ENT>
                        <ENT>13.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Wapato Irrigation Project—Wapato/Satus Unit *</ENT>
                        <ENT>Billing Charge Per Tract</ENT>
                        <ENT>5.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Farm unit/land tracts up to one acre (minimum charge)</ENT>
                        <ENT>51.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>“A” farm unit/land tracts over one acre—per acre</ENT>
                        <ENT>51.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Additional Works farm unit/land tracts over one acre—per acre</ENT>
                        <ENT>56.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>“B” farm unit/land tracts over one acre—per acre</ENT>
                        <ENT>61.00</ENT>
                    </ROW>
                    <ROW>
                        <PRTPAGE P="68106"/>
                        <ENT I="22"> </ENT>
                        <ENT>Water Rental Agreement Lands—per acre</ENT>
                        <ENT>62.00</ENT>
                    </ROW>
                    <TNOTE>
                        <E T="02">Note #1.</E>
                        —The Flathead Irrigation Project assessment rate for the 2004 season was proposed in 68 FR 1191-1196 at $21.45 per acre. This rate is considered implemented for the 2004 season and will be published in the Federal Register notice for the 2004 irrigation season.
                    </TNOTE>
                </GPOTABLE>
                <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s100,r100,10">
                    <TTITLE>Rocky Mountain Region Rate Table</TTITLE>
                    <BOXHD>
                        <CHED H="1">Name</CHED>
                        <CHED H="1">Rate category</CHED>
                        <CHED H="1">2003 season rate</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Blackfeet Irrigation Project</ENT>
                        <ENT>Basic per acre</ENT>
                        <ENT>$13.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Crow Irrigation Project</ENT>
                        <ENT>Basic per acre </ENT>
                        <ENT>16.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Fort Belknap Irrigation Project</ENT>
                        <ENT>Indian per acre</ENT>
                        <ENT>7.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Non-Indian per acre</ENT>
                        <ENT>14.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Fort Peck Irrigation Project</ENT>
                        <ENT>Basic per acre </ENT>
                        <ENT>14.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Wind River Irrigation Project</ENT>
                        <ENT>Basic per acre </ENT>
                        <ENT>12.00</ENT>
                    </ROW>
                </GPOTABLE>
                <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s100,r100,10">
                    <TTITLE>Western Region Rate Table</TTITLE>
                    <BOXHD>
                        <CHED H="1">Project name</CHED>
                        <CHED H="1">Rate category</CHED>
                        <CHED H="1">2003 season rate</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Colorado River Irrigation Project</ENT>
                        <ENT>Basic per acre up to 5.75 acre-feet</ENT>
                        <ENT>$47.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="11"> </ENT>
                        <ENT>Excess Water per acre foot over 5.75 acre-feet</ENT>
                        <ENT>17.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Duck Valley Irrigation Project</ENT>
                        <ENT>Basic per acre </ENT>
                        <ENT>5.30</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Fort Yuma Irrigation Project (See Note #2 below)</ENT>
                        <ENT>Basic per acre up to 5.0 acre-feet</ENT>
                        <ENT>60.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Excess Water per acre-foot over 5.0 acre-feet</ENT>
                        <ENT>10.50</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">San Carlos Irrigation Project (Joint Works)</ENT>
                        <ENT>Basic per acre</ENT>
                        <ENT>20.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">San Carlos Irrigation Project (Indian Works)</ENT>
                        <ENT>Basic per acre</ENT>
                        <ENT>56.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Uintah Irrigation Project *</ENT>
                        <ENT>Basic per acre</ENT>
                        <ENT>11.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Walker River Irrigation Project</ENT>
                        <ENT>Indian per acre</ENT>
                        <ENT>7.32</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>non-Indian per acre</ENT>
                        <ENT>15.29</ENT>
                    </ROW>
                    <TNOTE>
                        <E T="02">Note #2.</E>
                        —The Fort Yuma Irrigation Project is owned and operated by the Bureau of Reclamation (Reclamation). The irrigation rate assessed for operation and maintenance are established by Reclamation and are provided for informational purposes only. The BIA only collects the irrigation assessments on behalf of Reclamation.
                    </TNOTE>
                </GPOTABLE>
                <GPOTABLE COLS="3" OPTS="L2,i1" CDEF="s100,r100,10">
                    <TTITLE>Southwest Region Rate Table</TTITLE>
                    <BOXHD>
                        <CHED H="1">Name</CHED>
                        <CHED H="1">Rate category</CHED>
                        <CHED H="1">2003 season rate</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Pine River Irrigation Project</ENT>
                        <ENT>Minimum Charge per tract</ENT>
                        <ENT>$25.00</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="22"> </ENT>
                        <ENT>Basic per acre</ENT>
                        <ENT>8.50</ENT>
                    </ROW>
                </GPOTABLE>
                <HD SOURCE="HD1">Consultation and Coordination With Tribal Governments (Executive Order 13175)</HD>
                <P>The BIA irrigation facilities are vital components of the local agriculture economy of the reservations on which they are located. To fulfill its responsibilities to the tribes, tribal organizations, water user organizations, and the individual water users, the BIA communicates, coordinates, and consults on a continuing basis with these entities on issues of water delivery, water availability, costs of administration, operation, maintenance, and rehabilitation. This is accomplished at the individual irrigation facilities by agency and regional representatives, as appropriate, in accordance with local protocol and procedures. This notice is one component of the BIA's overall coordination and consultation process to provide notice and request comments from these entities on adjusting irrigation assessment rates.</P>
                <HD SOURCE="HD1">Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use (Executive Order 13211)</HD>
                <P>The rate adjustments will have no adverse effects on energy supply, distribution, or use (including a shortfall in supply, price increases, and increased use of foreign supplies) should the proposed rate adjustments be implemented. This is a notice for rate adjustments at BIA owned and operated irrigation facilities, except for the Fort Yuma Irrigation Project. The Fort Yuma Irrigation Project is owned and operated by the Bureau of Reclamation with a portion serving the Fort Yuma Reservation.</P>
                <HD SOURCE="HD1">Regulatory Planning and Review (Executive Order 12866)</HD>
                <P>These rate adjustments are not a significant regulatory action and do not need to be reviewed by the Office of Management and Budget under Executive Order 12866.</P>
                <HD SOURCE="HD1">Regulatory Flexibility Act</HD>
                <P>This rate making is not a rule for the purposes of the Regulatory Flexibility Act because it is “a rule of particular applicability relating to rates.” 5 U.S.C. 601(2).</P>
                <HD SOURCE="HD1">Unfunded Mandates Act of 1995</HD>
                <P>
                    These rate adjustments impose no unfunded mandates on any governmental or private entity and are 
                    <PRTPAGE P="68107"/>
                    in compliance with the provisions of the Unfunded Mandates Act of 1995.
                </P>
                <HD SOURCE="HD1">Takings Implications (Executive Order 12630)</HD>
                <P>The Department has determined that these rate adjustments do not have significant “takings” implications. The rate adjustments do not deprive the public, state, or local governments of rights or property.</P>
                <HD SOURCE="HD1">Federalism (Executive Order 13132)</HD>
                <P>The Department has determined that these rate adjustments do not have significant Federalism effects because they pertain solely to Federal-tribal relations and will not interfere with the roles, rights, and responsibilities of states.</P>
                <HD SOURCE="HD1">Civil Justice Reform (Executive Order 12988)</HD>
                <P>In accordance with Executive Order 12988, the Office of the Solicitor has determined that this rule does not unduly burden the judicial system and meets the requirements of sections 3(a) and 3(b)(2) of the Order.</P>
                <HD SOURCE="HD1">Paperwork Reduction Act of 1995</HD>
                <P>These rate adjustments do not affect the collections of information which have been approved by the Office of Information and Regulatory Affairs, Office of Management and Budget, under the Paperwork Reduction Act of 1995. The OMB Control Number is 1076-0141 and expires April 30, 2006.</P>
                <HD SOURCE="HD1">National Environmental Policy Act</HD>
                <P>The Department has determined that these rate adjustments do not constitute a major Federal action significantly affecting the quality of the human environment and that no detailed statement is required under the National Environmental Policy Act of 1969 (42 U.S.C. 4321-4370(d)).</P>
                <SIG>
                    <DATED>Dated: November 21, 2003.</DATED>
                    <NAME>Aurene M. Martin,</NAME>
                    <TITLE>Principal Deputy Assistant Secretary—Indian Affairs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30253 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4310-W7-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Bureau of Indian Affairs</SUBAGY>
                <SUBJECT>Lytton Rancheria of California Ordinance Governing the Sale, Consumption, and Possession of Alcoholic Beverages</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Indian Affairs, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This notice publishes the Lytton Rancheria of California Liquor Ordinance. The ordinance regulates and controls the distribution, sale, consumption, possession, inspection, licensing, enforcement and legal compliance associated with the introduction of alcohol at the Casino San Pablo premises, Contra Costa County, California.</P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">EFFECTIVE DATE:</HD>
                    <P>This Ordinance is effective on December 5, 2003.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Duane T. Bird Bear, Office of Tribal Services, Bureau of Indian Affairs, 1951 Constitution Avenue, NW., MS-320-SIB, Washington, DC 20240, Telephone: (202) 513-7641.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    Pursuant to the Act of August 15, 1953, Public Law 83-277, 67 Stat. 586, 18 U.S.C. 1161, as interpreted by the Supreme Court in 
                    <E T="03">Rice</E>
                     v. 
                    <E T="03">Rehner</E>
                    , 463 U.S. 713 (1983), the Secretary of the Interior shall certify and publish in the 
                    <E T="04">Federal Register</E>
                     notice of adopted liquor ordinances for the purpose of regulating liquor transactions in Indian Country. The Tribal Council of the Lytton Rancheria of California, also known as the Lytton Band of Pomo Indians, adopted a Tribal Liquor Ordinance on April 10, 2001. The purpose of this ordinance is to govern the distribution, sale, consumption, possession, inspection, licensing, enforcement and legal compliance associated with the introduction of alcohol on the Casino San Pablo premises in the County of Contra Costa, California.
                </P>
                <P>
                    This notice is published in accordance with the authority delegated by the Secretary of the Interior to the Principal Deputy Assistant Secretary—Indian Affairs. Amendments to the ordinance are subject to the approval of the Assistant Secretary for Indian Affairs and shall be published in the 
                    <E T="04">Federal Register</E>
                     before the amendments become effective.
                </P>
                <P>I certify that the Tribal Liquor Ordinance was duly adopted by the Tribal Council of the Lytton Band of Pomo Indians on April 10, 2001.</P>
                <SIG>
                    <DATED>Dated: November 21, 2003.</DATED>
                    <NAME>Aurene M. Martin,</NAME>
                    <TITLE>Principal Deputy Assistant Secretary—Indian Affairs.</TITLE>
                </SIG>
                <P>The Lytton Rancheria of California Liquor Ordinance reads as follows:</P>
                <HD SOURCE="HD1">Resolution of the Lytton Rancheria (Lytton Band of Pomo Indians)</HD>
                <HD SOURCE="HD1">Adopting an Ordinance Governing the Sale, Consumption, and Possession of Alcoholic Beverages at Lytton's Casino San Pablo</HD>
                <P>Whereas: The Lytton Band of Pomo Indians (“the Tribe”) plans to own and operate the Casino San Pablo and to offer Class II and Class III gaming there pursuant to federal and tribal law, a tribal-state compact, and its Municipal Services Agreement with the City of San Pablo; and</P>
                <P>Whereas: The Tribe has determined that it is in its best interest for the sale of alcoholic beverages at Casino San Pablo to continue pursuant to state, federal, and tribal law after the Tribe becomes the owner and operator of Casino San Pablo;</P>
                <P>
                    <E T="03">It is therefore resolved that</E>
                     the Tribe hereby adopts the following Ordinance, to become effective as set forth therein:
                </P>
                <HD SOURCE="HD1">Lytton Rancheria (Lytton Band of Pomo Indians) Contra Costa County, California</HD>
                <HD SOURCE="HD1">Sale, Possession, and Consumption of Alcoholic Beverages</HD>
                <P>The Tribal Council (hereinafter “Council”) of the Lytton Rancheria (hereinafter “Tribe”), also known as the Lytton Band of Pomo Indians, hereby enacts this Ordinance to govern the sale and consumption of alcoholic beverages on Rancheria lands in Contra Costa County, California.</P>
                <HD SOURCE="HD2">Preamble</HD>
                <P>
                    A. Title 18, United States Code, Section 1161, provides Indian tribes with authority to enact ordinances governing the consumption and sale of alcoholic beverages on their Reservations, provided such ordinance is certified by the Secretary of the Interior and published in the 
                    <E T="04">Federal Register</E>
                     and such activities are in conformity with state law.
                </P>
                <P>B. Pursuant to Article III of the Tribe's Constitution, the Tribal Council is the governing body of the Tribe. Pursuant to Article XIII of the Constitution, the Tribal Council is empowered to promulgate and enforce tribal laws exercising the Tribe's regulatory authority for the protection of public health and safety (Section 13.1 (f)) and administering all lands and assets and managing all economic affairs, planning and enterprises of the Tribe (Section 13.1(e); and to regulate the conduct of all persons who enter the jurisdiction of the Tribe (Section 13.1(i)).</P>
                <P>
                    C. Pursuant to Article I of the Tribe's Constitution, the territorial jurisdiction of the Tribe includes all lands held in 
                    <PRTPAGE P="68108"/>
                    trust by the United States for and possessed or occupied by the Tribe or its members.
                </P>
                <P>D. Pursuant to Section 819 of the Omnibus Indian Advancement Act of 2000 (“the Act”), the United States is to become the owner in trust for Tribe of that certain Contra Costa County, California property (“the Property”) described in the Act, which is commonly known as Casino San Pablo. Immediately upon acceptance by the United States of the Property in trust of the Tribe, the Tribe will become the owner and operator of Casino San Pablo (the “Facility”) pursuant to the Indian Gaming Regulatory Act. The Facility will be an integral and indispensable part of the Tribe's economy, providing income to the Tribe and training and employment to its members. The Tribal Council has determined that it is in the Tribe's best interest to offer alcoholic beverages for sale and consumption in the Facility.</P>
                <P>E. Pursuant to its Ordinance Restricting Gaming Activities And Areas At Lytton's Casino San Pablo To Persons Of The Age Of Twenty-One Years Old And Older, the Tribe has restricted gaming activities in the Facility to persons over the age of twenty-one years old.</P>
                <P>F. It is the purpose of this Ordinance to set out the terms and conditions under which the sale and consumption of said alcoholic beverages may take place.</P>
                <HD SOURCE="HD2">General Terms</HD>
                <P>1. The sale of alcoholic beverages within the Facility, for on-Premises consumption only, is hereby authorized.</P>
                <P>2. No alcoholic beverages may be sold at any location on the Rancheria other than inside the Facility.</P>
                <P>3. The sale of said alcoholic beverages authorized by this Ordinance shall be in conformity with all applicable laws of the State of California, and the sale of said beverages shall be subject to state sales tax, federal excise tax and any fees required by the Federal Bureau of Alcohol, Tobacco and Firearms. This includes but is not limited to the following examples:</P>
                <P>a. No person under the age of 21 years shall consume, acquire or have in his or her possession at the Premises any alcoholic beverage.</P>
                <P>b. No person shall sell alcohol to any person under the age of 21 at the Premises.</P>
                <P>c. No person shall sell alcohol to a person apparently under the influence of liquor at the Premises.</P>
                <P>4. Where there may be a question of a person's right to purchase liquor by reason of his or her age, such person shall be required to present any one of the following types of identification which shows his or her correct age and bears his or her signature and photograph: (1) Driver's license or identification card issued by any state Department of Motor Vehicles; (2) United States Active Duty Military card; (3) passport.</P>
                <P>5. All liquor sales within the Premises shall be on a cash only basis and no credit shall be extended to any person, organization or entity, except that this provision does not prevent the use of major credit cards.</P>
                <HD SOURCE="HD2">Posting</HD>
                <P>6. This Ordinance shall be conspicuously posted within the Premises at all times it is open to the public.</P>
                <HD SOURCE="HD2">Enforcement</HD>
                <P>7. This Ordinance may be enforced by the Tribal Council and by any additional tribal government agencies to which the Tribal Council may from time to time by resolution delegate such enforcement powers. Enforcement sanctions may include, but are not limited to, the assessment of monetary fines not to exceed $500 and revocation of authorization to sell alcohol at the Facility. Prior to any enforcement action, any alleged violator of this Ordinance shall be provided with at least three (3) days notice in writing of an opportunity to be heard during a hearing at which due process is provided. The decision of the Tribal Council or other agency with delegated authority after such hearing shall be final.</P>
                <HD SOURCE="HD2">Severability</HD>
                <P>8. If any provision or application of this Ordinance is determined by the Tribal Council or other agency with delegated authority to be invalid, such adjudication shall not be held to render ineffectual the remaining portions of this Ordinance or to render such provisions inapplicable to other circumstances.</P>
                <HD SOURCE="HD2">Amendment</HD>
                <P>9. This Ordinance may only be amended by a majority vote of the Tribal Council and such amendment shall be subject to the provisions of Title 18, United States Code, Section 1161.</P>
                <HD SOURCE="HD2">Sovereign Immunity</HD>
                <P>10. Nothing in this Ordinance in any way limits, alters, restricts or waives the Tribe's sovereign immunity from unconsented suit, claim, or action.</P>
                <HD SOURCE="HD2">Effective Date</HD>
                <P>
                    11. This Ordinance shall not be effective until: (1) It is certified by the Secretary of the Interior and published in the 
                    <E T="04">Federal Register</E>
                    , and (2) the Property is accepted by the United States in trust for the Tribe. Its effective date shall be the date of the happening of the later of those actions.
                </P>
                <HD SOURCE="HD1">Certification</HD>
                <P>The foregoing Resolution was adopted by a vote of 7 for, and -0- against and -0- abstentions, at a duly called meeting of the Tribal Council of the Lytton Rancheria (aka the Lytton Band of Pomo Indians) at which a quorum was present, on this 10th day of April, 2001.</P>
                <EXTRACT>
                    <FP>Margie Mejia,</FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Tribal Chair.</E>
                    </FP>
                    <FP>Danny O'Campo,</FP>
                    <FP SOURCE="FP-1">
                        <E T="03">Tribal Secretary.</E>
                    </FP>
                </EXTRACT>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30243 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4310-4J-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Bureau of Land Management</SUBAGY>
                <DEPDOC>[NV-020-1990-EX]</DEPDOC>
                <SUBJECT>Notice of Availability of Final Supplemental Environmental Impact Statement; Glamis Marigold Mining Company/Marigold Mine Millennium Expansion Project, Humboldt Co., NV</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Land Management, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of availability.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>Pursuant to section 102(2)(c) of the National Environmental Policy Act of 1969, notice is given that the Winnemucca Field Office of the Bureau of Land Management (BLM) has prepared, by third party contractor, a Final Supplemental Environmental Impact Statement (SEIS) on the Glamis Marigold Mining Company/Marigold Mine Millennium Expansion Project, located in Humboldt County, Nevada.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">EFFECTIVE DATES:</HD>
                    <P>
                        The period of availability for public review of the Final SEIS ends 30 days after publication of this notice in the 
                        <E T="04">Federal Register</E>
                         by the Environmental Protection Agency. At that time, public comments will be reviewed and considered in the decision making process. The Record of Decision will reflect any changes made to the Draft SEIS.
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>A copy of the Final SEIS can be obtained from: Bureau of Land Management, Winnemucca Field Office, 5100 East Winnemucca Blvd., Winnemucca, Nevada 89445.</P>
                </ADD>
                <FURINF>
                    <PRTPAGE P="68109"/>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Jeffrey D. Johnson, Project Manager, at the above Winnemucca Field Office address or telephone (775) 623-1500.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The Final SEIS analyzes the direct, indirect and cumulative impacts related to expansion of existing mine facilities (pits, overburden dumps &amp; heap leach pads) and development of the Millennium Projects. Development includes construction of five new pits, overburden disposal areas, two additional heap leach facilities, drainage diversions, haul and exploration roads and ancillary facilities. Alternatives analyzed include: (1) Moving the Trout Creek Diversion toward the west, farther from the Red Rock Pit, (2) increasing backfilling along the west high wall of the Red Rock Pit, and (3) taking no action. The agency-preferred alternative is alternative number 2; increasing backfilling along the west high wall of the Red Rock Pit. The Final SEIS contains in its entirety the analysis originally presented in the Draft SEIS (issued April 5, 2003) with all text changes presented in bold type. In addition, letters received during the Draft SEIS comment period and the agency's responses to the comments have been incorporated into the Final SEIS.</P>
                <SIG>
                    <DATED>Dated: June 30, 2003.</DATED>
                    <NAME>Terry Reed,</NAME>
                    <TITLE>Field Manager.</TITLE>
                </SIG>
                <EDNOTE>
                    <HD SOURCE="HED">
                        Editor's 
                        <E T="04">Note:</E>
                          
                    </HD>
                    <P>This document was received at the Office of the Federal Register on December 1, 2003.</P>
                </EDNOTE>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30193 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4310-HC-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>Bureau of Land Management</SUBAGY>
                <DEPDOC>[MT-070-04-1010-PH]</DEPDOC>
                <SUBJECT>Notice of Public Meeting, Western Montana Resource Advisory Council Meeting</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Bureau of Land Management, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of public meeting.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Federal Land Policy and Management Act (FLPMA) and the Federal Advisory Committee Act of 1972 (FACA), the U.S. Department of the Interior, Bureau of Land Management (BLM), Western Montana Resource Advisory Council will meet as indicated below.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>A meeting will be held February 19, 2004 at the BLM Missoula Field Office, 3255 Fort Missoula Road, Missoula, Montana beginning at 9 a.m. The public comment period will begin at 11:30 a.m. and the meeting will adjourn at approximately 3:00 p.m.</P>
                </DATES>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The 15-member Council advises the Secretary of the Interior, through the Bureau of Land Management, on a variety of planning and management issues associated with public land management in western Montana. At the February 19 meeting, possible topics we plan to discuss include: updates on the Dillon, Butte and Limestone Hills planning processes, election of chair and vice-chair, weeds, possible pilot projects, an update on Land and Water Conservation Fund (LWCF) projects, outyear budget planning and initiatives, and an update on the proposed changes to the grazing regulations.</P>
                <P>All meetings are open to the public. The public may present written comments to the Council. Each formal Council meeting will also have time allocated for hearing public comments. Depending on the number of persons wishing to comment and time available, the time for individual oral comments may be limited. Individuals who plan to attend and need special assistance, such as sign language interpretation, or other reasonable accommodations, should contact the BLM as provided below.</P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Marilyn Krause, Resource Advisory Council Coordinator, at the Butte Field Office, 106 North Parkmont, Butte, Montana 59701, telephone 406-533-7617 or Nancy Anderson, Field Manager, Missoula Field Office, telephone 406-329-3914.</P>
                    <SIG>
                        <DATED>Dated: November 24, 2003.</DATED>
                        <NAME>Nancy T. Anderson,</NAME>
                        <TITLE>Field Manager.</TITLE>
                    </SIG>
                </FURINF>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30255 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4310-$$-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>National Park Service</SUBAGY>
                <SUBJECT>Information Collection; Request for Extension</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Park Service.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of request for extension of a currently approved information collection. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In compliance with the Paperwork Reduction Act of 1995, the National Park Service (NPS) is announcing its intention to request an extension of a currently approved collection of information (OMB# 1024-0231) for 36 CFR part 51, § 51.47 regarding the appeal of a preferred offeror determination, §§ 51.54 and 51.55 regarding NPS approval of the construction of capital improvements by concessioners, and section 51.98 concerning recordkeeping requirements with which concessioners must comply.</P>
                    <P>The information is being collected to meet the requirements of section 403(7) and (8) of the NPS Concessions Management Improvement Act of 1998 (the Act), concerning the granting of a preferential right to renew a concession contract, section 405 of the Act regarding the construction of capital improvements by concessioners, and section 414 of the Act regarding recodkeeping requirements of concessioners. The information will be used by the agency in considering appeals concerning preferred offeror determinations, agency review and approval of construction projects and determinations with regard to the leasehold surrender interest value of such projects, and when necessary, agency review of a concessioner's books and records related to its activities under a concession contract.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Comments on this notice must be received no later than February 3, 2004.</P>
                    <P>
                        <E T="03">Additional Information or Comments:</E>
                         Contact Cynthia Orlando, Concession Program Manager, National Park Service, 1849 C Street, NW., (2410), Washington, DC 20240, or 202/513-7144.
                    </P>
                </DATES>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    <E T="03">Title:</E>
                     Concession Contract—36 CFR 51.
                </P>
                <P>
                    <E T="03">OMB Control Number:</E>
                     1024-0231.
                </P>
                <P>
                    <E T="03">Expiration Date of Approval:</E>
                     November 30, 2003.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Extension of a currently approved information collection.
                </P>
                <P>
                    <E T="03">Abstract:</E>
                     The Office of Management and Budget (OMB) regulations as 5 CFR 1320, which implement provisions of the Paperwork Reduction Act of 1995 (Pub. L. 104-13), require that interested members of the public and affected agencies have an opportunity to comment on information collection and recordkeeping activities (
                    <E T="03">see</E>
                     5 CFR 1320.8(d)). This notice identifies information collection activities that NPS will submit to OMB for approval. The OMB control number for this collection of information is 1024-0231, and is identified in 36 CFR Section 51.104.
                </P>
                <P>
                    NPS has identified burden estimates based on its experience with concession contracts and on information previously supplied by concessioners or offerors in response to concession prospectuses. NPS will request a 3-year term of 
                    <PRTPAGE P="68110"/>
                    approval for this information collection activity.
                </P>
                <P>
                    <E T="03">Bureau Form Number:</E>
                     None.
                </P>
                <P>
                    <E T="03">Frequency of Collection:</E>
                     Once.
                </P>
                <P>
                    <E T="03">Description of Respondents:</E>
                     NPS concessioners, and, in the case of appeals of preferred offeror determinations, offerors in response to concession prospectuses.
                </P>
                <P>
                    <E T="03">Total Annual Responses:</E>
                     758.
                </P>
                <P>
                    <E T="03">Total Annual Burden Hours:</E>
                     3,276.
                </P>
                <P>Send comments on (1) the need for the collection of information for the performance of the functions of the agency; (2) the accuracy of the agency's burden estimates; (3) ways to enhance the quality, utility and clarity of the information collection; and (4) ways to minimize the information collection burden on respondents, such as use of automated means of collection of the information. Please refer to OMB control number 1024-0231 in all correspondence. All responses to this notice will be summarized and included in the request for OMB approval. All comments will also become a matter of public record. Copies of the information collection can be obtained from Cynthia L. Orlando, Concession Program Manager, National Park Service, Department of the Interior, 1849 C Street, NW., (2410), Washington, DC 20240.</P>
                <SIG>
                    <DATED>Dated: October 30, 2003.</DATED>
                    <NAME>Leonard E. Stowe,</NAME>
                    <TITLE>Acting NPS Information Collection Clearance Officer, Washington Administrative Program Center.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-29987  Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4312-53-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>National Park Service</SUBAGY>
                <SUBJECT>60-Day Notice of Intention To Request Clearance of Collection of Information; Opportunity for Public Comment</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of the Interior, National Park Service.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>NPS requests comments on extending and modifying two existing NPS information collection instruments that are processed by the existing, Internet-based Research Permit and Reporting System. One information collection instrument, the Application for a Scientific Research and Collecting Permit, is used by applicants to apply to parks for scientific research and collecting permits for natural or social science activities that require permits. The other instrument, the Investigator's Annual Report, is used by permittees to submit their required annual progress reports. NPS will use the information you submit in response to this notice to assist its decision-making regarding whether or not to request extension of, and to make modifications to, the two collections of information administered through the existing Research Permit and Reporting System. Once NPS develops and adopts any modifications that may be appropriate, NPS currently expects to submit a request for an extension of the existing, but slightly modified, collection of information package to OMB with a request that OMB approve the package and assign an OMB clearance number to the two collection of information forms that are part of this system.</P>
                </SUM>
                <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s40,10,10">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1"> </CHED>
                        <CHED H="1">Estimated numbers of</CHED>
                        <CHED H="2">Responses</CHED>
                        <CHED H="2">
                            Burden 
                            <LI>hours</LI>
                        </CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">Research Permit and Reporting System</ENT>
                        <ENT>6,000</ENT>
                        <ENT>4,875</ENT>
                    </ROW>
                </GPOTABLE>
                <P>Under provisions of the Paperwork Reduction Act of 1995 and 5 CFR Part 1320, Reporting and Record Keeping Requirements, the National Park Service is soliciting comments on the need for gathering the information in the two collections of information being considered for modification and extension. The NPS also is asking for comments on the practical utility of the information being gathered; the validity and accuracy of the reporting burden hour estimate; ways to enhance the quality, utility, and clarity of the information to be collected; and ways to minimize the burden to respondents, including use of automated information collection techniques or other forms of information technology.</P>
                <P>
                    You may obtain copies of the existing application form, annual reporting form, and related guidance and explanatory material from the NPS Research Permit and Reporting System Web site at: 
                    <E T="03">http://science.nature.nps.gov/research.</E>
                     You also may obtain copies of the documents and additional information from the source identified below.
                </P>
                <P>If you wish to comment, you may submit your comments by any one of several methods. Although you may mail comments to the postal address given here, due to delays caused by processing of mail you may wish to use a different method. You may send your comments by facsimile to the fax number given below. You may instead comment via the Internet to the e-mail address given here (Please submit e-mail comments as an attached ASCII or MSWord file and avoid the use of special characters and any form of encryption. Please also include “Attn: NPS Research Permit and Reporting System” and your name and return address in your e-mail message. If you would like, but do not receive, a confirmation from the system that we have received your e-mail message, contact us directly at the phone number given here). Finally, you may hand-deliver comments to the address given below.</P>
                <P>Our practice is to make comments, including respondent names and addresses (business or home, whatever we receive), available for public review during regular business hours. Individual respondents may request that we withhold their home address from the record, which we will honor to the extent allowable by law. There also may be circumstances in which we would withhold from the record a respondent's identity, as allowable by law. If you wish us to withhold your name and/or address, you must state this prominently at the beginning of your comment. We will make all submissions from organizations or businesses, and from individuals identifying themselves as representatives or officials of organizations or businesses, available for public inspection in their entirety. We will not consider anonymous comments.</P>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        Public comments will be accepted on or before 60 days from the date this notice is published in the 
                        <E T="04">Federal Register</E>
                        .
                    </P>
                    <P>
                        <E T="03">Send Comments To:</E>
                         Dr. John G. Dennis. By mail: Natural Resources (3127 MIB), National Park Service, 1849 C Street, NW., Washington, DC 20240. By hand delivery: Natural Resources (11th floor), National Park Service, 1201 Eye Street, NW., Washington, DC 20005. By fax: 202-371-2131. By e-mail: 
                        <E T="03">researchcoll@nps.gov</E>
                        .
                    </P>
                </DATES>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                         Dr. John G. Dennis. Voice: 202-513-7174 Fax: 202-371-2131; E-mail: 
                        <E T="03">researchcoll@nps.gov</E>
                        .
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P SOURCE="NPAR">
                    <E T="03">Title:</E>
                     National Park Service Research Permit and Reporting System.
                </P>
                <P>
                    <E T="03">Bureau Form Number:</E>
                     Application for a Scientific Research and Collecting Permit: 10-741; Investigator's Annual Report: 10-226.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1024-0236.
                </P>
                <P>
                    <E T="03">Expiration Date:</E>
                     4/30/2004.
                </P>
                <P>
                    <E T="03">Type of Request:</E>
                     Revision of a previously approved collection.
                </P>
                <P>
                    <E T="03">Description of Need:</E>
                     The currently approved information collection responds to the statutory requirement 
                    <PRTPAGE P="68111"/>
                    that NPS preserve park resources and regulate the use of units of the National Park System. The information currently collected identifies: (1) Names and business contact information for people who seek a permit to conduct natural or social science research and collecting activities in individual units of the National Park System, (2) what activities they wish to conduct, (3) where they wish to conduct the activities, (4) whether or not they wish to collect specimens as part of the activities they propose to conduct, and (5) for applicants who have received a permit, annual summaries of the actual results of their permitted activities. NPS uses the collected information for managing the use  and preservation of park resources and for reporting the status of permitted research and collecting activities. NPS is considering proposing to change both the Application for a Scientific Research and Collecting Permit and the Investigator's Annual Report to improve their usability by respondents and to improve the focus of the information NPS collects to address specific needs that use of the two forms over the last three years has revealed. Examples of such needs associated with managing the permit include additional information about the project scope and status, such as expected total time span of the project, specific identification of project personnel who will be working in the park, status of processing collected specimens, planned schedules for the field work phases of the project, and expected end date for the project.
                </P>
                <P>More specifically, NPS is considering proposing changes to the Application to improve the use of the Application for both scientific research and collecting and scientific education activities. NPS is considering proposing changes to the Application to improve the clarity of information provided to, and obtained from, respondents who request use of a non-NPS repository regarding the duty the respondents have for securing acceptance by the proposed non-NPS repository of becoming the curator for collections authorized in the permit. NPS is considering proposing changes to the Application to better understand the schedule of field work activities. NPS is considering proposing changes to the Investigator's Annual Report to reduce the complexity of the form by assigning responsibility to NPS, not the respondent, for determining the appropriate activity code for each permitted project.</P>
                <P>
                    <E T="03">Automated Data Collection:</E>
                     The information collection and status reporting system for which the renewal of two components of a single collection of information package is being proposed in this notice currently is available to applicants, permittees, and the public through the NPS Research Permit and Reporting System Web site (
                    <E T="03">http://science.nature.nps.gov/research</E>
                    ). In addition to considering the modification of the two information collection forms, NPS is developing modification to the Internet site to increase the effectiveness and efficiency of this automation system to facilitate the permit application and progress reporting process.
                </P>
                <P>
                    <E T="03">Description of Respondents:</E>
                     Representatives of academic and other research institutions, Federal, state, or local agencies, research businesses; other scientific parties seeking an NPS research and collecting permit; permittees who submit the annual report of accomplishment that is one of the permit conditions.
                </P>
                <P>
                    <E T="03">Estimated Average Number of Respondents:</E>
                     3,000 per year.
                </P>
                <P>
                    <E T="03">Estimated Average Number of Responses:</E>
                     6,000 per year. For each permit cycle, each respondent will respond usually once to prepare and submit the application for a permit and respondents who are successful in being awarded a permit will respond a second time to submit the Investigator's Annual Report. Given the most applicants are successful in being awarded a permit and that permit renewal usually occurs annually, the number of responses will approach a total that is two times the number of respondents.
                </P>
                <P>
                    <E T="03">Estimated Average Burden Hours Per Two-Part Response:</E>
                     1,625 hours per year total for responding to both parts of the collection information.
                </P>
                <P>
                    <E T="03">Frequency of Response:</E>
                     2 times per respondent per year—once to submit the application and once to submit the Investigator's Annual Report.
                </P>
                <P>
                    <E T="03">Estimated Annual Reporting Burden:</E>
                     4,875 hours.
                </P>
                <SIG>
                    <DATED>Dated: November 12, 2003.</DATED>
                    <NAME>Leonard E. Stowe,</NAME>
                    <TITLE>Acting National Park Service Information Collection Clearance Officer.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-29988 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 43210-70-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                <SUBAGY>National Park Service</SUBAGY>
                <SUBJECT>60-Day Notice of Intent To Renew Request for Clearance of Information Collection, Backcountry Use Permit, Opportunity for Public Comment</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Park Service, Interior.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice and request for comments. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>In accordance with the Paperwork Reduction Act of 1995 (Pub. L. 104-13, 44 U.S.C. 3507) the National Park Service (NPS) invites public comment on a request for renewal of the information collection requirements of NPS Standard Form 10-4-4, Backcountry Use Permit. The permit was initially authorized under OMB Control No. 1024-0022. The Backcountry Use Permit is the primary form used to provide access into NPS backcountry areas including those areas that require a reservation to enter or where use limits are imposed in accordance with other NPS regulations. Such permitting enhances hazard warnings, search and rescue efforts and resource protection.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Public comments will be accepted until February 3, 2004</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Send comments to Lee Dickinson, National Park Service, 1849 C Street NW., (org. code 2460), Washington, DC 20240 or e-mail at 
                        <E T="03">Lee_Dickinson@nps.gov.</E>
                         All responses to this notice will be summarized and included in the request for Office of Management  and Budget (OMB) approval. All comments will become a matter of public record. Copies of this form may be obtained from the Internet at 
                        <E T="03">http://www.nps.gov/policy/DOrders/BUP.pdf</E>
                         or by contacting Lee Dickinson.
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Lee Dickinson, National Park Service, 1849 C Street NW., (org. code 2460)., Washington, DC 20240 by telephone at 202-513-7092 or by e-mail at 
                        <E T="03">Lee_Dickinson@nps.gov</E>
                    </P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>In 1976, the NPS initiated a backcountry registration system in accordance with the regulations found at 36 CFR 1.5, 1.6 and 2.10. The objective of the backcountry use permit system is to provide campers access to backcountry areas of national parks with continuing opportunities for solitude, while enhancing resource protection and providing a means of disseminating public safety messages regarding backcountry travel.</P>
                <P>
                    NPS backcountry program managers, by designating access routes and overnight camping locations, can redistribute campers in response to user impact, high fire danger, flood or wind hazard, bear activity or other situations that may temporarily close a portion of the backcountry. The NPS may also use the permit system as a means of ensuring that each backcountry user receives up-to-date information on backcountry sanitation procedures, food storage, wildlife activity, trail conditions and weather projections so that concerns for visitor safety are met.
                    <PRTPAGE P="68112"/>
                </P>
                <P>The Backcountry Use Permit is an extension of the NPS statutory authority responsibility to protect the park areas it administers and to manage the public use thereof (16 U.S.C. 1 and 3). NPS regulations codified in 36 CFR Parts 1 through 7, 12 and 13, are designed to implement statutory mandates that provide for resource protection and public enjoyment.</P>
                <P>
                    <E T="03">Estimated annual number of respondents:</E>
                     295,339.
                </P>
                <P>
                    <E T="03">Estimated annual number of responses:</E>
                     295,339.
                </P>
                <P>
                    <E T="03">Estimated average burden hours per response:</E>
                     5 minutes.
                </P>
                <P>
                    <E T="03">Estimated frequency of response:</E>
                     the collection information must be provided each time a visitor or group wants to enter into the park's backcountry overnight. Frequency of response will depend on number of visits to parks annually.
                </P>
                <P>
                    <E T="03">Estimated annual resorting burden:</E>
                     24,612 hours per year.
                </P>
                <P>The NPS especially invites public comments as to:</P>
                <P>a. Whether the collection of information is necessary for the proper performance of the functions of the Service, and whether the information will have practical utility.</P>
                <P>b. The accuracy of the Service's estimate of the burden of the collection of information, including the validity of the methodology and assumptions used;</P>
                <P>c. the quality, utility, and clarity of the information to be collected; and</P>
                <P>d. How to minimize the burden of the collection of information on those who are to respond, including the use of appropriate automated, electronic, mechanical or other forms of information technology.</P>
                <SIG>
                    <DATED>Dated: November 7, 2003.</DATED>
                    <NAME>Leonard E. Stowe,</NAME>
                    <TITLE>Acting, Information Collection Clearance Officer, National Park Service.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-29989  Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4310-70-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">INTERNATIONAL TRADE COMMISSION</AGENCY>
                <DEPDOC>[USITC SE-03-040]</DEPDOC>
                <SUBJECT>Sunshine Act Meeting</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>International Trade Commission.</P>
                </AGY>
                <PREAMHD>
                    <HD SOURCE="HED">Time and Date:</HD>
                    <P>December 10, 2003 at 2 p.m.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">Place:</HD>
                    <P>Room 101, 500 E Street SW., Washington, DC 20436, Telephone: (202) 205-2000.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">Status:</HD>
                    <P>Open to the public.</P>
                </PREAMHD>
                <PREAMHD>
                    <HD SOURCE="HED">Matters To Be Considered:</HD>
                    <P SOURCE="NPAR">1. Agenda for future meetings: none.</P>
                    <P>2. Minutes.</P>
                    <P>3. Ratification List.</P>
                    <P>4. Inv. No. 731-TA-1057 (Preliminary)(Certain Processed Hazelnuts from Turkey)—briefing and vote. (The Commission is currently scheduled to transmit its determination to the Secretary of Commerce on or before December 11, 2003; Commissioners' opinions are currently scheduled to be transmitted to the Secretary of Commerce on or before December 18, 2003.)</P>
                    <P>5. Outstanding action jackets: none.</P>
                    <P>In accordance with Commission policy, subject matter listed above, not disposed of at the scheduled meeting, may be carried over to the agenda of the following meeting.</P>
                </PREAMHD>
                <SIG>
                    <DATED>Issued: December 3, 2003.</DATED>
                    <P>By order of the Commission:</P>
                    <NAME>Marilyn R. Abbott,</NAME>
                    <TITLE>Secretary to the Commission.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30350 Filed 12-3-03; 11:24 am]</FRDOC>
            <BILCOD>BILLING CODE 7020-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF JUSTICE</AGENCY>
                <SUBAGY>Federal Bureau of Investigation</SUBAGY>
                <DEPDOC>[Docket No. FBI 109; RIN 1100-AA14]</DEPDOC>
                <SUBJECT>Implementation of Section 104 of the Communications Assistance for Law Enforcement Act</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Federal Bureau of Investigation, (FBI), Justice.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Final notice of capacity; supplement for the purpose of responding to remand.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        By this notice, the FBI is responding to a court decision to remand for further explanation two issues from the final notice of capacity. The final notice of capacity was published on March 12, 1998, at 63 FR 12218, pursuant to the requirements of the Communications Assistance for Law Enforcement Act (“CALEA”), 47 U.S.C. 1001, 
                        <E T="03">et seq.</E>
                         Because the court did not vacate the final notice of capacity, we are providing further explanation as to the two remanded issues and are not republishing the final notice of capacity. Telecommunications carriers should note that the provisions of 47 U.S.C. 1003(d) do not apply to today's notice and should not file a “carrier statement” in response thereto. Comments on this notice may be submitted in accordance with the instructions below.
                    </P>
                </SUM>
                <EFFDATE>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Written comments must be received at CALEA Implementation Unit, 14800 Conference Center Drive, Chantilly, VA 20153 on or before February 3, 2004.</P>
                </EFFDATE>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Contact the CALEA Implementation Unit, Federal Bureau of Investigation (FBI) at (703) 814-4700, or at CALEA Implementation Unit, 14800 Conference Center Drive, Chantilly, VA 20153.</P>
                    <HD SOURCE="HD1">I. Background</HD>
                    <P>
                        Congress enacted CALEA in 1994 to require telecommunications carriers to ensure that their networks have the capability to enable local police, Federal officers and all other law enforcement agencies to conduct lawfully authorized electronic surveillance. Electronic surveillance is an indispensable tool used in investigating serious crimes, including terrorism, drug trafficking, and kidnaping. Congress has long recognized the importance of this investigative technique, and has authorized and governed its use through several laws, including Title III of the Omnibus Crime Control and Safe Streets Act of 1968, 18 U.S.C. 2510 
                        <E T="03">et seq.</E>
                         (“Title III”), the Electronic Communications Privacy Act of 1986, 18 U.S.C. 2701 
                        <E T="03">et seq.</E>
                         (“ECPA”), and the Pen Registers and Trap and Trace Devices provisions, 18 U.S.C. 3121 
                        <E T="03">et seq.</E>
                        , as those laws were recently modified by the USA PATRIOT Act, Public Law 107-56, 115 Stat. 272, recently.
                    </P>
                    <P>Under these laws, the government can obtain authority to intercept various forms of transmitted communications, including but not limited to, telephone conversations, pager messages, electronic mail, and computer data transmissions. Communications interceptions, commonly referred to as “wiretaps,” are strictly regulated by Title III. With few and limited exceptions, wiretaps are prohibited without prior court authorization. The threshold level of proof to obtain such authorization includes a determination that probable cause exists to believe that the communications to be intercepted will constitute evidence of a crime.</P>
                    <P>
                        The government can also obtain authority from a court to use a “pen register” or “trap and trace device.” This requires a lower amount of proof than that required under Title III. Pen registers and traps and traces may not be used to intercept communications; rather, they are used to acquire “call identifying information.” This information includes the dialing and signaling associated with a communication. 
                        <E T="03">See</E>
                         47 U.S.C. 1001(2) (definition of “call identifying information”). Telephone numbers and the routing information in a packet header are both examples of call 
                        <PRTPAGE P="68113"/>
                        identifying information. Pen registers are devices or processes for acquiring outgoing dialing, routing, addressing and signaling information, and traps and traces are used to record such information as it is incoming. 18 U.S.C. 3127(3), (4).
                    </P>
                    <P>
                        The electronic surveillance laws cited above delineate the government's lawful authority to intercept communications and acquire call-identifying information. CALEA, by contrast, is intended to preserve the government's technical ability to engage in electronic surveillance as allowed by law. It does so by requiring “telecommunications carriers” to design or modify their systems to ensure the government's ability to intercept communications and acquire call-identifying information, pursuant to lawful authorization. 
                        <E T="03">See generally</E>
                         47 U.S.C. 1002.
                    </P>
                    <P>
                        In addition, CALEA contains “capacity requirements.” 
                        <E T="03">See generally id</E>
                         § 1003. The capacity provisions generally require carriers to be capable of supporting a certain number of communications interceptions, pen registers, and traps and traces at the same time. These provisions also require the Attorney General to issue a notice of the maximum and actual capacity requirements setting forth the “maximum” and “actual” number of communications interceptions, pen registers, and traps and traces that all government agencies may, in the future, conduct and use at the same time. The FBI Director is the authorized delegate of the Attorney General with respect to the implementation of CALEA, and therefore has issued such notices of capacity on the Attorney General's behalf.
                        <SU>1</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             
                            <E T="03">See</E>
                             28 CFR 0.85(o).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">A. Notices of Capacity</HD>
                    <P>In 1995, the FBI published an initial notice of capacity which expressed capacity requirements in terms of a “percentage of engineered capacity.” 60 FR 53643 (Oct. 16, 1995). After receiving comments from the public we revised that methodology and published a second notice of capacity. 62 FR 1902 (Jan. 14, 1997). After an additional round of comments, we published the final notice of capacity (referred to herein as the “final notice”) on March 12, 1998. 63 FR at 12218-12310. At all times, we sought and incorporated the comments of the telecommunications industry, which assisted us in understanding the challenges facing the industry and others in applying the capacity requirements. The FBI acted on behalf of all Federal, State and local law enforcement agencies nationwide in establishing these capacity requirements.</P>
                    <P>
                        The capacity requirements contained in the final notice were based on data obtained through a survey of Federal and State court clerks, law enforcement agencies, and telecommunications carriers. These entities were requested to provide records of any past surveillance activity conducted between January 1, 1993, and March 1, 1995. After gathering and organizing this data, we formed “baseline” numbers of surveillances for each region in the country.
                        <SU>2</SU>
                        <FTREF/>
                         The final notice identified capacity requirements for telecommunications carriers offering local exchange services (referred to as “wireline”) and wireless carriers providing certain commercial mobile radio services, specifically cellular service and personal communications service (PCS).
                        <SU>3</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>2</SU>
                             We use the term “surveillances” herein, to refer to multiple instances of any type of surveillance, whether communications interceptions, pen registers, and/or traps and traces.
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>3</SU>
                             
                            <E T="03">See</E>
                             63 FR 12220. In the final notice of capacity, PCS was considered a service operating in the licensed portion of the 2 GHz band of the electromagnetic spectrum, from 1850 MHz to 1990 MHz. 
                            <E T="03">Id.</E>
                        </P>
                    </FTNT>
                    <P>
                        Counties 
                        <SU>4</SU>
                        <FTREF/>
                         were used as the geographic region in identifying capacity requirements for wireline carriers. With respect to wireless services, the Federal Communications Commission (FCC) utilizes 306 Metropolitan Statistical Areas (MSA) and 428 Rural Statistical Areas (RSA) for cellular licensing purposes; and 51 Major Trading Areas (MTA) and 493 Basic Trading Areas (BTA) for PCS licensing. Each of these geographic regions was used in identifying capacity requirements for cellular and PCS services respectively. For purposes of this publicaiton, we will collectively refer to all of these types of wireless service areas as “market service areas.”
                    </P>
                    <FTNT>
                        <P>
                            <SU>4</SU>
                             The term “counties” includes boroughs and parishes as well as the District of Columbia and independent cities. U.S. territories (
                            <E T="03">i.e.</E>
                            , American Samoa, Guam, Mariana Islands, Puerto Rico, and the U.S. Virgin Islands) were considered as single entities.
                        </P>
                    </FTNT>
                    <P>
                        The baseline numbers were derived from analysis of the number of surveillances that were ongoing on particular days during the survey period.
                        <SU>5</SU>
                        <FTREF/>
                         The final notice describes in detail how the baselines were calculated. 
                        <E T="03">See</E>
                         63 FR 12224-26. As the final notice describes, we chose to count multiple surveillances ongoing on the same day as occurring “simultaneously” for the purpose of determining capacity requirements. For example, if the survey data had indicated that on January 2, 1993, in a particular market service area, Title III surveillance had been established on two cellular telephones, and a pen register had been installed on a third, then these would have been counted as three simultaneous surveillances. Having formed baselines, we thereafter generated the capacity requirements by multiplying the baseline by a growth factor. The FBI chose in the final notice to publish capacity requirements in the form of a single “actual” and “maximum” number for each region, rather than as separate numbers for the different types of surveillance (communications interceptions and pen registers/traps and traces).
                    </P>
                    <FTNT>
                        <P>
                            <SU>5</SU>
                             A single surveillance is an interception, pen register or trap and trace established with respect to a single subscriber line. Thus, a single court order might authorize multiple “surveillances” as that term is used herein. 
                            <E T="03">See</E>
                             63 FR 12224.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">B. Court Decision</HD>
                    <P>
                        On January 18, 2002, the District of Columbia Circuit ruled on a number of challenges to the final notice. 
                        <E T="03">See USTA</E>
                         v. 
                        <E T="03">FBI,</E>
                         276 F.3d 620 (D.C. 2002). While the Court's decision largely upheld the final notice, it vacated one issue and remanded two others to the FBI. The Court vacated the statement in the final notice (63 FR 12219) that “law enforcement considers 5 business days from a telecommunications carrier's receipt of a court order to be a reasonable time within which to permit an incremental expansion up to the maximum capacity.” 
                        <E T="03">USTA,</E>
                         276 F.3d at 627. The Court also required the FBI to provide further explanation of: (1) our decision to count any two historical surveillances occurring on the same day as simultaneous and, (2) our decision to set forth only one “actual” and one “maximum” capacity requirement number per region, rather than separate requirements for each type of surveillance.
                    </P>
                    <P>The Court's concern with both of these issues centered on the explanations contained in the final notice. The Court did not vacate these portions of the final notice, but directed the district court to remand them to the FBI for a more adequate explanation.</P>
                    <HD SOURCE="HD1">II. Response to the Remand</HD>
                    <P>
                        This publication responds to the Court's remand by addressing both issues as follows. First, we provide additional explanation, not previously before the Court, for our interpretation of the term “simultaneously.” Second, we are supplying carriers with supplemental guidance with regard to the previously-published numerical capacity requirements by providing a method of breaking those numbers down between communications 
                        <PRTPAGE P="68114"/>
                        interceptions and acquisitions of call-identifying information.
                        <SU>6</SU>
                        <FTREF/>
                         This additional guidance should further assist carriers in their efforts to comply with CALEA's capacity requirements, while at the same time it will address the concerns raised by the remand. Following the end of the comment period, the FBI will review any such comments it receives and publish a finalized notice in the 
                        <E T="04">Federal Register</E>
                        .
                    </P>
                    <FTNT>
                        <P>
                            <SU>6</SU>
                             For the purposes of this publication, we will use the term “pen register/trap and trace” to refer to the acquisition of call-identifying information, whether incoming, outgoing or both.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD2">A. Meaning of “Simultaneously”</HD>
                    <P>
                        The first issue we address herein is the interpretation of the term “simultaneously.” The Court of Appeals noted that the final notice “treated interceptions as   ‘simultaneous’ if they occurred on same day, even though they may each only take moments and do not overlap in the least.” 
                        <E T="03">USTA,</E>
                         276 F.3d at 626. We understand the Court's concern to be that communications, such as telephone calls for example, could be short in duration, and interceptions of two or more of them on the same day might “not overlap” if they occurred at different times. The Court directed us to provide further explanation for our determination of capacity requirements based not on a number of overlapping communications interceptions, but on a number of surveillances ongoing on the same day.
                        <SU>7</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>7</SU>
                             The Court referred only to overlapping communications interceptions, and not to pen registers/traps and traces, in its discussion of “simultaneously.” As set forth below, however, the statute also refers to the simultaneous use of pen register or trap and trace devices, as well as the simultaneous use of such a device along with the conduct of one or more communications interceptions. For purposes of this publication, we will first address the Court's cited concerns with regard to non-overlapping communications interceptions.
                        </P>
                    </FTNT>
                    <P>In response to the Court's direction, the FBI provides the following further explanation of its capacity methodology. First, the FBI examined the statutory language of CALEA. This examination suggested that 47 U.S.C. 1003 permits using same day data. The statute only requires that the government provide estimates of interceptions, pen registers, and trap and traces that law enforcement “may conduct and use simultaneously.” 47 U.S.C. 1003(a)(1)(A), (B). The word “may” indicates that capacity requirements should represent a number of interceptions that might take place. Second, the FBI examined how other courts have interpreted the word simultaneously. These cases suggested that the word simultaneous can be interpreted more broadly than coterminous, giving the FBI additional latitude to use the data available. Third, the FBI offers an explanation of how technology impacts capacity requirements. This explanation shows how using the number of same day ongoing surveillances provides a technology neutral approach allowing carriers to use their expertise to efficiently design their systems. For example, some technical intercept solutions require dedicated hardware for the duration of a court order regardless of whether the target is actually communicating, while an alternative technical intercept solution requires carriers' resources only when communications occur. Finally, we explain how the capacity requirements are based on data and expressed in terms within the FBI's and other law enforcement agencies' expertise. The FBI's particular expertise includes knowledge of the historical patterns of criminal activity within our jurisdiction, and of the investigative resources historically needed to detect and prevent such activity. Our expertise also includes an understanding of the frequency with which we have had to rely on electronic surveillance as a tool, and of the implications of limitations on its use in the future.</P>
                    <HD SOURCE="HD3">1. Statutory Language</HD>
                    <P>
                        As set forth above, CALEA requires the government to estimate the number of interceptions, pen registers, and trap and trace devices, that law enforcement authorities “may conduct and use 
                        <E T="03">simultaneously</E>
                        .” 47 U.S.C. 1003(a)(1)(A), (B) (emphasis added). These terms, including the word “simultaneously,” are not defined in CALEA.
                    </P>
                    <P>
                        First, we believe that CALEA's language supports the FBI's approach to the capacity requirements, even when viewing the term “simultaneously” as referring only to precisely coterminous actions. This is because Congress directed us to estimate the number of interceptions, pen registers, and traps and traces that law enforcement agencies “
                        <E T="03">may</E>
                         conduct and use simultaneously.” (emphasis added). The term “may” indicates that capacity requirements should represent a number of interceptions that might take place, which is precisely what the FBI approach accomplishes. For example, in our experience, criminal suspects may, like anyone else, make and receive phone calls at any time of the day or night. Thus when two or more telephones are under lawful surveillance on the same day, calls may occur at any time and thus “may” result in communications interceptions at the same exact time. Our establishment of capacity requirements based on a number surveillances on the same day is therefore a reasonable basis on which to predict the number of precisely coterminous interceptions that law enforcement agencies “may” conduct.
                    </P>
                    <P>
                        Second, in common usage, the word “simultaneously” could encompass events that are not precisely coterminous but happen on the same day or around the same time. This understanding has been applied in court opinions as well. 
                        <E T="03">See, e.g., Mendes-Silva</E>
                         v. 
                        <E T="03">United States,</E>
                         980 F.2d 1482, 1486 (D.C. Cir. 1993) (“simultaneous administration” of drug defined by party as administration on “the same day”), 
                        <E T="03">cert. denied,</E>
                         479 U.S. 923 (1986); 
                        <E T="03">San Luis Obispo Mothers for Peace</E>
                         v. 
                        <E T="03">NRC,</E>
                         789 F.2d 26, 40 n.11 (D.C. Cir. 1986) (“simultaneous occurrence” of earthquake and nuclear accident defined as occurrence of the two events within “48 hours”). Courts also refer to actions, such as the filing of motions, as “simultaneous” if they occur on the same day. 
                        <E T="03">See generally, Spenkelink</E>
                         v. 
                        <E T="03">Wainwright,</E>
                         442 U.S. 1301, 1303 (1979) (per Rehnquist, J., in chambers) (“[t]he District Court simultaneously entered a second order”); 
                        <E T="03">Dillard</E>
                         v. 
                        <E T="03">Industrial Comm'n of Virginia,</E>
                         416 U.S. 783, 792 (1974) (insurance company “[s]imultaneously” applied for a regulatory hearing and discontinued payments to insured); 
                        <E T="03">City of Orrville</E>
                         v. 
                        <E T="03">FERC,</E>
                         147 F.3d 979, 984 (D.C. Cir. 1998) (on “same day” that one party requested a rehearing another party “simultaneously moved to intervene”). The FBI's treatment of interceptions occurring on the same day as simultaneous, is therefore, a permissible interpretation of this statutory term.
                    </P>
                    <P>
                        We further note that the statute directs us to give notice of a number of simultaneous surveillances of all types, not just interceptions. In pertinent part, it states that the Attorney General should “provide * * * notice of the * * * number of communications interceptions, pen registers, and trap and trace devices * * * that the Attorney General estimates that government agencies authorized to conduct electronic surveillance may 
                        <E T="03">conduct and use simultaneously</E>
                        .” 47 U.S.C. 1003(a)(1)(A) (emphasis added). This provision plainly contemplates, among other things, the “use” of a pen register or trap and trace device, simultaneously with the “conduct” of one or more interceptions. Although, as the Court observed, two communications interceptions might not overlap if they occur at different times of the day, the same cannot be said for either the simultaneous “use” of 
                        <PRTPAGE P="68115"/>
                        two or more pen registers or trap and devices, or the simultaneous use of such device(s) with the conduct of an interception. Since a pen register or trap and trace device may be said to be in “use” for so long as it is installed on a line, and not just when it is actually obtaining information, then its “use” would continue throughout each day over the time period that it is installed. The device's use would then occur “simultaneously” with the conduct of any communication interceptions on the same day, irrespective of the time. It would also be simultaneous with the use of any other pen register or trap and trace devices on the same day. Our approach to the capacity requirements is consistent with this reading of the statutory language, since we counted the numbers of ongoing surveillances of all types on a single day in determining the baselines. For all of the reasons discussed above, we opine that it is appropriate to determine and express the capacity requirements in terms of a number of surveillances ongoing on the same day.
                    </P>
                    <HD SOURCE="HD3">2. Law Enforcement Needs and Capacity Requirements</HD>
                    <P>The FBI's approach to the capacity requirements is based on the premises: (A) that carriers will need to use certain resources to assist with each lawful surveillance, and (B) that more resources might be needed for each additional surveillance initiated while others are ongoing. As the Court is aware, we sought, to determine a number of surveillances that might be ongoing on the same day within particular geographic regions. Having notice of this number, we believed, carriers (as well as law enforcement agencies) would be able to anticipate and plan for the amount of resources they might need to use in order to facilitate the specified number of surveillances. Ultimately, therefore, our approach was intended to ensure the important goals that carriers will have the appropriate notice and will make the appropriate level of resources available in order to meet law enforcement's surveillance needs.</P>
                    <P>We now seek to provide the Court with further explanation of our approach. First, determining the capacity requirements as a number of ongoing surveillances is an approach that is “neutral” as to the system design chosen by the carrier to meet the requirements. By contrast, determining and expressing the requirements in terms of a number of overlapping communications interceptions would assume the carrier's system only utilizes additional resources when the communications interceptions overlap. In fact, some carriers' systems require additional dedicated resources for each additional ongoing surveillance, notwithstanding whether communications interceptions overlap.</P>
                    <P>Second, our approach allows the industry the flexibility to use its expertise to design different systems and allows law enforcement agencies to benefit from such expertise. Under the FBI's approach, a carrier is not precluded from designing and implementing different systems for meeting the requirements, including systems that do not require dedicated resources for each additional surveillance. If the number of overlapping communications were relevant to a carrier's chosen design, the telecommunications industry may rely on its special, if not unique, expertise in determining the extent to which that might occur.</P>
                    <HD SOURCE="HD3">(a) The Final Notice Determined Capacity Requirements in a System-Neutral Manner</HD>
                    <P>
                        Determining capacity requirements in a system-neutral manner is necessary because CALEA did not authorize the FBI to require any specific system design. 
                        <E T="03">See</E>
                         47 U.S.C. 1002(b)(1). In addition, we know that carriers in fact use designs that differ in their capabilities to accommodate multiple surveillances at the same time. To accommodate these realities, we sought to give carriers notice of a number of surveillances that may be conducted at the same time, because they may need to use more resources to support each additional surveillance while others are ongoing. This is in fact the case in systems that are designed to use specific resources for the entire time that a surveillance is ongoing, even when no communication is actually being intercepted.
                    </P>
                    <P>For example, some telecommunications switches are designed to send lawfully intercepted communications and call-identifying information to a law enforcement agency over a high-capacity connection referred to as a “T1.” These systems are designed such that a T1 connection must be dedicated to the surveillance for the entire time that the surveillance is in effect. The number of T1 connections that can be supported at one time by a telecommunications switch is limited. Hence, such a carrier would likely need to be able to support multiple T1 connections in order to facilitate multiple surveillances on the same switch on the same day.</P>
                    <P>
                        CALEA's legislative history indicates that Congress may have contemplated a similar example when enacting CALEA's capacity provisions in the first instance. At the time of CALEA's enactment, Congress was made aware by the FBI of a number of cases where lawfully authorized surveillance had been impeded due to insufficient “cellular port capacity.” 
                        <E T="03">See</E>
                         H.R. Rep. No. 103-827, 103rd Cong., 2nd Sess., at 15 (1994). At this time, cellular telephone surveillance was conducted by accessing a subject's communications at the telecommunications switch through one of a limited number of access ports used for maintenance. Hence, each interception required the use of another access port, and the number of interceptions that could be active at the same time was limited by the number of available ports.
                    </P>
                    <P>In both of the above examples, the ability of the carrier's system to accommodate multiple surveillances at the same time is limited. Importantly, this ability is limited by the number of surveillances ongoing at the same time, not by the number of overlapping communications actually being intercepted at the same time. If we were to adopt an alternative approach by determining capacity requirements based on a number of overlapping communications interceptions, then the capacity requirements based thereon would not provide carriers with systems similar to the examples above with notice of the number of surveillances they could be required to accommodate at the same time. Such carriers might then underestimate the resources necessary to support those surveillances. In order to ensure that all carriers will have the information they need in order to meet law enforcement's needs, the capacity requirements should therefore be based on a number of ongoing surveillances.</P>
                    <P>
                        We are aware, however, that some carriers' systems function differently. For example, some telecommunications switches are capable of sending intercepted communications and call-identifying information over an ordinary phone line, by “dialing-out” such information each time a communication occurs. In these systems, the switch resources are released after the intercepted communications are transmitted and become available for other uses. The carriers' ability to facilitate multiple surveillances in these cases might to some degree be affected by the number of overlapping communications interceptions. Nevertheless, we cannot base the capacity requirements on an assumption that all carriers' systems have this or similar abilities, because, in fact, many do not.
                        <PRTPAGE P="68116"/>
                    </P>
                    <P>Nothing in our approach to the capacity requirements would preclude a carrier from meeting them by using a “dialing-out” capability or any other system design. Having notice of the number of surveillances that law enforcement agencies may conduct at any given time, carriers and their manufacturers and suppliers could engineer methods of facilitating that number of surveillances without reliance on additional resources being dedicated for each additional surveillance maintained. If it were relevant to the system design, members of the telecommunications industry, as discussed below, have special expertise in determining the frequency with which communications (and the interceptions thereof) might overlap.</P>
                    <P>Applying our preceding explanation, we believe that determining capacity requirements based on a number of same-day surveillances is the most appropriate method for ensuring that carriers will be able to meet law enforcement's surveillance needs.</P>
                    <HD SOURCE="HD3">(b) The Final Notice Allows for Different System Designs and Allows Law Enforcement To Benefit From Industry Expertise</HD>
                    <P>Another benefit not previously presented to the Court is that the capacity requirements stated in the final notice allow carriers to design a system that can meet the requirements through different methods. Stating capacity requirements in terms of a number of simultaneous surveillances thus allows law enforcement agencies to benefit from the special expertise of the telecommunications industry. With notice of the number of simultaneous surveillances that they should be able to facilitate, carriers can use their own expertise to decide how to design a system to facilitate that number of surveillances.</P>
                    <P>
                        CALEA recognizes that carriers, manufacturers and suppliers are naturally in a position to assess the capabilities of their own systems, and to design and implement technical changes to their systems to meet different demands. The structure of CALEA reflects a recognition that members of the telecommunications industry possess expertise in engineering technical requirements necessary to facilitate lawful surveillance. For example, CALEA allows carriers to design systems that follow an industry-adopted set of technical standards that meet CALEA's requirements. See 47 U.S.C. 1006(c); 
                        <E T="03">see also USTA</E>
                         v. 
                        <E T="03">FCC,</E>
                         227 F.3d 450, 460 (referencing CALEA's “unique structure” in delegating the establishment of technical standards to both the telecommunications industry and the FCC).
                    </P>
                    <P>In order for law enforcement agencies to obtain the benefit of industry expertise, it is most appropriate that the capacity requirements be determined and expressed in terms of a certain number of ongoing surveillances. The industry is then left free to design an appropriate system to meet these requirements. As discussed below, such designs might involve the dedication of certain resources for the duration of each surveillance, or might rely on shared resources that are invoked only when a communication is actually being intercepted and then released when the communication is over, or some combination of both. The capacity requirements set forth in the Final Notice, as discussed above, are “system neutral” in that they do not assume any particular system design.</P>
                    <P>Carriers, along with their manufacturers and suppliers, possess special expertise in assessing their subscribers's potential use of their telecommunications systems. Carriers routinely in the ordinary course of their business engage in “traffic engineering” to determine the “busy hour,” when the frequency and/or duration of their subscribers” telecommunications activity is highest. In order to guarantee a certain level of service to their subscribers, carriers are necessarily well informed of the level of burden that subscribers are likely to place on the telecommunications system at any given time. Without such knowledge they would not be able to provide the level of service that their subscribers expect. For example, wireline telephone carriers routinely estimate the number of their subscribers who are likely to pick up their telephones at the same time in order to place a call. The same types of assessments are routinely made by carriers with regard to the design and implementation of new “features” that the carrier offers to subscribers, such as call-waiting or conference calling. The carrier's telecommunications system is designed in such a way as to be able to satisfy the subscribers' demands as closely as possible. Such assessments are particularly within the scope of the industry's particular expertise.</P>
                    <P>Carriers and other industry members are therefore specially, if not uniquely, qualified to assess the burdens that a certain number of surveillances could place on their telecommunications systems. In one sense, the carrier's design of a system to meet CALEA's requirements is analogous to the design of any other “feature” that may be associated with a subscriber's service. Carriers and other members of the telecommunications industry are specially qualified to assess the frequency and duration of the communications made by a subscriber under surveillance, and the extent to which a given number of surveillances might involve communications that overlap, in the event that such an assessment is relevant to the particular system design chosen by the carrier. Indeed, a carrier's routine assessment of its subscribers' use of the telecommunications system will necessarily include an assessment of such use by those subscribers who happen to be under lawful surveillance. For example, in a wireline carrier's system, if an assessment of the frequency and duration of the phone calls made or received by subscribers under surveillance is relevant to the carrier's design of a system to meet the capacity requirements, then the carrier can use its expertise to make that determination. Law enforcement agencies, in turn, will benefit from the industry's expertise in this regard.</P>
                    <HD SOURCE="HD3">3. The Capacity Requirements Are Based on Data and Expressed in Terms Within the FBI's and Other Law Enforcement Agencies's Expertise</HD>
                    <P>The FBI chose the aforementioned approach towards determining capacity requirements because the data and the terms in which we stated the capacity requirements were within our expertise, the area of law enforcement. The data we acquired through our survey, as discussed above, included information regarding the number of surveillances ongoing at certain times within a given geographic area. Our particular expertise allowed us to analyze and derive conclusions from this data regarding the number of surveillances likely to be sought by law enforcement agencies in particular geographic regions at the same time. These data did not include information from which we could determine the number of overlapping communications interceptions. In addition, as outlined below, stating the capacity requirements in such terms would have had little meaning or usefulness to other law enforcement agencies. We offer the following explanation to illustrate why it was reasonable for the capacity requirements to be based on, and expressed in terms of, a number of ongoing surveillances.</P>
                    <P>
                        The FBI's particular expertise includes knowledge of the historical patterns of criminal activity within our jurisdiction, and of the investigative resources historically needed to detect and prevent such activity. Our expertise 
                        <PRTPAGE P="68117"/>
                        also includes an understanding of the frequency with which we have had to rely on electronic surveillance as a tool, and of the implications of limitations on its use in the future. Indeed, we are necessarily familiar with the frequency with which we have sought to conduct communications interceptions, in part through our compliance with the requirements of Federal law regarding reports to the Administrative Office of the Courts. 
                        <E T="03">See</E>
                         18 U.S.C. 2519. Therefore, we believe it was reasonable that our survey focus on determining the frequency with which all law enforcement agencies nationwide have relied upon electronic surveillance in their investigations.
                    </P>
                    <P>As already stated, the data acquired through our survey cannot be used to determine the frequency of overlapping communications interceptions. Such data did not include any information regarding the hours, minutes and times of day that particular communications interceptions occurred. Rather, the survey data reflects the days over which surveillances were ongoing.</P>
                    <P>The FBI now offers this further explanation to justify why our reliance on data reflecting numbers of ongoing surveillances was reasonable. First and foremost, an analysis thereof was within the FBI's expertise in assessing the level of investigative resources needed to combat crime. Conversely, a survey and analysis focused on the number of overlapping communications interceptions would not be within our traditional expertise. Such an exercise would be more akin to the “traffic engineering” studies traditionally engaged in by the telecommunications industry. For example, it would require us to make determinations about the extent to which individuals will make or receive phone calls at the same time. As discussed above, if that assessment were relevant to the system design chosen by a carrier, then the carrier is in the most appropriate position to make it.</P>
                    <P>Second, the capacity requirements set forth in the final notice, in addition to satisfying the requirement for notice to carriers, will serve as guidance to law enforcement agencies in understanding potential technical limitations on the use of electronic surveillance. Agencies can readily comprehend, and if necessary, plan for, being able to conduct only a certain limited number of surveillances at a given time. On the other hand, stating the capacity requirements in terms of a number of overlapping communications interceptions would have little or no meaning to law enforcement agencies.</P>
                    <P>
                        We further note that initiating a new study to determine the frequency of overlapping communications interceptions would consume a large amount of time and resources, would be problematic, and, for all of the reasons discussed herein, would ultimately not be beneficial to our goal of ensuring that law enforcement's needs are met. Such a study would require us to gather and analyze numerous evidence files in an attempt to determine the exact times at which communications were intercepted and whether or not they overlapped. Because most surveillances are conducted by agencies other than the FBI, most of these files would need to be obtained from third parties, such as other law enforcement agencies or the courts. Given the number of surveillances determined from our survey, this could involve hundreds of files. Moreover, it is also doubtful that such data could even be used to derive a “typical” frequency of overlap among interceptions on which we could reliably base the capacity requirements. First, not every communication that might be intercepted through an ongoing surveillance actually is intercepted, such that it is recorded and entered into evidence files. In particular, some communications made over the facilities subject to the surveillance are not recorded because they are not pertinent to the investigation. 
                        <E T="03">See</E>
                         18 U.S.C. 2518(5) (this is often referred to as the “minimization” requirement under Title III). An incomplete picture of the potential for overlap might therefore be presented through a review of evidence files. Second, the probability for overlap when conducting surveillances in different types of cases could vary greatly. In our experience, some surveillances, such as those in bookmaking or drug dealing cases, may involve many communications interceptions over a relatively short period of time. In other cases, such as kidnaping, only a few communications may be actually intercepted.
                    </P>
                    <P>Finally, as described above, we believe that estimating the number of overlapping intercepted communications would not be ultimately beneficial to effectively estimating law enforcement's capacity requirements. In particular, as we discuss above, we believe that capacity requirements are most appropriately based on a number of surveillances being conducted on the same day, not on a number of overlapping interceptions.</P>
                    <HD SOURCE="HD2">B. Breakdown of Capacity Requirements by Type of Surveillance</HD>
                    <P>
                        The second issue we address in this publication is the breakdown of capacity requirements by type of surveillance. The statute, as discussed above, directs us to provide “notice of 
                        <E T="03">the</E>
                         actual 
                        <E T="03">number</E>
                         of communications interceptions, pen registers, and trap and trace devices.” 47 U.S.C. 1003(a)(1) (emphasis added). The FBI decided, therefore, in the final notice to provide an “actual” and a “maximum” number representing a total number of surveillances, for each county and market service area. The Court questioned our explanation of the basis for this decision, noting that the FBI's numbers “drew no distinction between different types of interceptions (
                        <E T="03">e.g.</E>
                        , communications content versus mere pen registers).” 
                        <E T="03">USTA,</E>
                         276 F.3d at 626. According to the Court, different types of surveillance may “impose different demands” on the carrier's ability to meet the capacity requirements. 
                        <E T="03">Id.</E>
                         at 627. The Court further noted, as we stated in the final notice, that more delivery channels may be needed in order to facilitate a communications interception as opposed to the operation of a pen register and/or a trap and trace device. 
                        <E T="03">Id.</E>
                         The Court therefore remanded this issue to us for a more adequate explanation.
                    </P>
                    <P>The FBI has considered this issue and continues to find that it is appropriate, given the statutory requirements, to state the capacity requirements for each geographic region as a single actual and single maximum number. Moreover, our approach was consistent with the methodology we used to determine the capacity requirements, which, as described above, focused on the highest number of surveillances of any type that were ongoing on a single day or days during the survey period.</P>
                    <P>
                        Nevertheless, we find that we can further address the court's concerns and at the same time benefit law enforcement agencies and telecommunications carriers, by providing additional guidance on the application of the capacity requirements. We set forth our analysis of the issue and our finding that the method described below achieves this goal by limiting the number of simultaneous communications interceptions that are required to be accommodated in the counties and market service areas with the highest capacity requirements. By so limiting the number of communications interceptions, we are now giving the carriers providing service in these regions guidance that allows them to 
                        <PRTPAGE P="68118"/>
                        draw a distinction between different types of surveillances in meeting the capacity requirements.
                    </P>
                    <HD SOURCE="HD3">1. National Average Ratio Is Not an Appropriate Basis</HD>
                    <P>
                        As we stated in the final notice, the ratio of interceptions to pen registers/traps and traces according to the national average, is not an appropriate basis on which to determine capacity requirements. 63 FR 12235-36. This is because our survey determined that the historical experience of each county and market service area varies greatly. In some regions, all or nearly all historical surveillances consisted of communications interceptions, while in others, all of the surveillances were pen registers or traps and traces. 
                        <E T="03">Id</E>
                        . The national average ratio of communications interceptions to pen registers/traps and traces is not therefore representative of any specific geographic region.
                    </P>
                    <HD SOURCE="HD3">2. Conclusions From Historical Survey Information</HD>
                    <P>
                        Because a national average ratio would not be appropriate to use, we decided to examine the breakdown between different types of surveillance at the county and market service area level. Using the FBI's original survey data, we examined the percentage of communications interceptions that were included within the historical experience of each county and market service area.
                        <SU>8</SU>
                        <FTREF/>
                         Some general conclusions were able to be drawn from this examination, as described below.
                    </P>
                    <FTNT>
                        <P>
                            <SU>8</SU>
                             A “historical experience” figure, representing the baseline number of simultaneous surveillances is published for each county and market service area in the appendices to the final notice.
                        </P>
                    </FTNT>
                    <P>
                        We first examined the data for geographic regions with low historical experience figures, and correspondingly low capacity requirements. Within this group, the portion of total historical experience that consisted of communications interceptions varied widely. For example, for counties with a total historical experience of 10 or less, the percentage amount of communications interceptions from total historical experience ranged from zero to 100. The same variance (zero to 100) was found for wireless services licensed by MSA/RSA, MTA and BTA, but only in market service areas with a total historical experience of 5 or less.
                        <SU>9</SU>
                        <FTREF/>
                    </P>
                    <P>Continuing with this comparison process for regions with successively higher total historical experience amounts, we found that the percentage of communications interceptions tended to decrease as the total historical experience increased. For the county with the highest historical experience, we found that 25 percent of the total experience were communications interceptions. For the market services area with the highest historical experience, 50 percent of the total historical experience consisted of communications interceptions.</P>
                    <FTNT>
                        <P>
                            <SU>9</SU>
                             We used the historical interception activity of cellular carriers to develop projections of future capacity requirements for PCS carriers. 
                            <E T="03">See</E>
                             63 FR 12226.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">3. Establishment of Percentage Groups</HD>
                    <P>Based on the overall relationships described above, we determined that a breakdown of the capacity requirements by surveillance type could be achieved by placing limits on the extent to which the number of surveillances reflected in the capacity requirements could include communications interceptions. The tendency in our data, as described above, was for a decreasing proportion of communications interceptions as the total number of surveillances increased. We concluded therefore that a set of percentages that decrease as historical experience increases, could be used to limit the number of communications interceptions as a proportion of the total capacity requirement.</P>
                    <P>
                        We therefore established decreasing percentages, and assigned groups of particular geographic regions to those percentages (hereinafter “percentage groups”) with respect to all counties and market service areas described in the final notice. For counties, the FBI has established four percentage groups: 100, 75, 50, and 25 percent. For each of the three different types of wireless geographic regions (
                        <E T="03">i.e.</E>
                        , MSA/RSA, MTA, and BTA) the FBI has established three percentage groups: 100, 75, and 50 percent.
                    </P>
                    <P>As explained further below, the applicable percentage indicates the highest proportion of capacity requirements (actual and maximum capacity requirements) that could consist of communications interceptions. Regions with low historical experience, and correspondingly low capacity requirements, fall within the 100 percent group. A carrier operating within such a region must be able to accommodate the number of surveillances indicated by the capacity requirement such that all (100 percent) of the surveillances are communications interceptions, or all are pen registers/traps and traces, or some combination of both types of surveillance equal to the capacity requirement. This is consistent with our findings regarding the variability of the types of surveillances within the historical experience of regions with low levels of such experience.</P>
                    <P>At the other end of the range, regions with high historical experience levels fall within the 25 percent group for counties, or the 50 percent group for market service areas. Carriers operating within these regions must still be able to accommodate the total number of surveillances indicated by their capacity requirement, but the proportion of that number that could be communications interceptions is limited by the applicable percentage. The determination of the percentage groups and the application of the percentage is described in further detail below.</P>
                    <HD SOURCE="HD3">4. Determination of Percentage Groups Applicable to Geographic Regions</HD>
                    <P>Carriers can determine the applicable percentage group by looking at the “historical experience” number associated with their capacity requirements as published in the final notice.</P>
                    <P>We assigned particular regions to the percentage groups based on their total historical experience. We first examined the historical data to locate the region with the highest number of historical surveillances wherein 100 percent of them were communications interceptions. This number was 10 for capacity requirements determined by county and 5 for capacity requirements determined by market service area. This number became the upper limit of the 100 percent group, and all counties with a historical experience of 10 or less, and market service areas with a historical experience of 5 or less, were then deemed within the 100 percent group.</P>
                    <P>
                        The process was continued by examining the historical data for all those counties not already falling within the 100 percent group, in order to determine the appropriate upper limit for the 75 percent group. We examined the data for the remaining regions for the highest number of surveillances wherein 75 percent of the total consisted of communications interceptions. This number was 44 for counties and 10 for market service areas. Again, the process was continued with those geographic regions not already deemed to be within the 100 or 75 percent groups. That is, we examined the data regarding the remaining regions to determine the region with the highest number of historical surveillances wherein 50 percent of the total consisted of communications interceptions. This number was 100 for counties. For wireless market service areas, this number was 106, which was also the highest historical experience figure. Hence, all remaining market 
                        <PRTPAGE P="68119"/>
                        service areas, those with historical experience figures between 11 and 106 (inclusive), were assigned to the 50 percent group. For wireline services, the remaining counties with a historical experience of 101 or more, were determined to be within the 25 percent group.
                    </P>
                    <P>Thus, the percentage group applicable to a particular county or market service area can be determined according to its total historical experience, as summarized below.</P>
                    <HD SOURCE="HD3">a. Counties</HD>
                    <P>Counties with a total historical experience between 0 and 10 (inclusive), are in the 100 percent group; between 11 and 44 (inclusive), are in the 75 percent group; between 45 and 100 (inclusive) are in the 50 percent group; and greater than 100, are in the 25 percent group. The following chart summarizes these determinations:</P>
                    <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s25,8">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1">Historical experience</CHED>
                            <CHED H="1">Percentage group</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">0-10 </ENT>
                            <ENT>100</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">11-44 </ENT>
                            <ENT>75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">45-100 </ENT>
                            <ENT>50</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">101 or more </ENT>
                            <ENT>25</ENT>
                        </ROW>
                    </GPOTABLE>
                    <HD SOURCE="HD3">b. Market Service Areas</HD>
                    <P>The following describes the percentage groups for wireless carriers regardless of the type of geographic region (MSA/RSA, MTA, and BTA). Market service areas with a total historical experience between zero and five (inclusive) are in the 100 percent group; between six and ten (inclusive) are in the 75 percent group; and greater than ten, are in the 50 percent group. The following chart summarizes these determinations:</P>
                    <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s25,8">
                        <TTITLE> </TTITLE>
                        <BOXHD>
                            <CHED H="1">Historical experience</CHED>
                            <CHED H="1">Percentage group</CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">0-5 </ENT>
                            <ENT>100</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">6-10 </ENT>
                            <ENT>75</ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">11 or more </ENT>
                            <ENT>50</ENT>
                        </ROW>
                    </GPOTABLE>
                    <HD SOURCE="HD3">5. Application of Percentage to Actual and Maximum Capacity Requirements</HD>
                    <P>Carriers can use the applicable percentage to determine the number of simultaneous communications interceptions that they should be capable of accommodating within their total capacity requirements.</P>
                    <P>As described above, the actual and maximum capacity requirements specify a total number of surveillances. The applicable percentage is then multiplied by the capacity requirement to determine the highest number of simultaneous surveillances that could be in the form of communications interceptions. If the calculation results in a fraction, then the number of communications interceptions should be rounded up.</P>
                    <P>The percentage does not change the total number of surveillances specified in the actual and maximum capacity requirements, and does not change the total number of surveillances that carriers must be able to accommodate simultaneously in order to meet the capacity requirements. In cases where the carrier's capacity requirements fall within the 75 percent group, or lower, the percentage will clearly limit the number of simultaneous communications interceptions that a carrier is required to be capable of accommodating. Thus, a carrier must at all times be able to accommodate a number of surveillances equal to its capacity requirement, and the total number of surveillances may be all pen registers/traps and traces or a combination of these and communications interceptions. However, the number of communications interceptions will not exceed the limit, if any, indicated by the applicable percentage. The examples below will illustrate this.</P>
                    <HD SOURCE="HD3">Example 1</HD>
                    <P>Montgomery County, Maryland has a historical experience of 66, an actual capacity requirement of 84, and a maximum capacity requirement of 110. The historical experience of 66 places it within the 50 percent group. Multiplying the percentage by the capacity requirements indicates that the actual capacity requirement is limited to 42 communications interceptions and the maximum capacity requirement is limited to 55 communications interceptions. A carrier providing service in this county is required to be capable of accommodating an actual capacity of 84 pen registers/traps and traces, or any combined number of surveillances equal to 84 where the number of communications interceptions is equal to 42 or less. For example, the carrier must be capable of accommodating 42 simultaneous communications interceptions and 42 simultaneous pen registers/traps and traces. For a further example, the carrier must be capable of accommodating 10 simultaneous communications interceptions and 74 simultaneous pen registers/traps and traces. The same form of analysis applies to the maximum capacity requirements.</P>
                    <HD SOURCE="HD3">Example 2</HD>
                    <P>Metropolitan Statistical Area / Rural Statistical Area (MSA/RSA) 234, Athens, Georgia, has a historical experience of 7, an actual capacity requirement of 12, and a maximum capacity requirement of 20. The historical experience of 7 places it within the 75 percent group. Multiplying the percentage by the capacity requirements indicates that the actual capacity requirement is limited to 9 communications interceptions and the maximum capacity requirement is limited to 15 communications interceptions. A carrier providing service in this MSA/RSA is required to be capable of accommodating an actual capacity of 12 pen registers/traps and traces, or any combined number of both types of surveillances equal to 12, where the number of communications interceptions is equal to 9 or less. For example, the carrier must be capable of accommodating 9 simultaneous communications interceptions and 3 simultaneous pen registers/traps and traces. For a further example, the carrier must be capable of accommodating 2 simultaneous communications interceptions and 10 simultaneous pen registers/traps and traces. The same form of analysis applies to the maximum capacity requirements.</P>
                    <HD SOURCE="HD3">Example 3</HD>
                    <P>
                        Harris County, Texas has a historical experience of 294, an actual capacity requirement of 371, and a maximum capacity requirement of 484. The historical experience of 294 places it within the 25 percent group. Twenty-five percent of 371 is 92.75, which is rounded up to 93. The actual capacity requirement is limited to 93 communications interceptions and the maximum capacity requirement is limited to 121 communications interceptions. A carrier providing service in this county is required to be capable of accommodating an actual capacity of 371 pen registers/traps and traces, or any combined number of both types of surveillances equal to 371 where the number of communications interceptions is equal to 93 or less. For example, the carrier must be capable of accommodating 93 simultaneous communications interceptions and 278 simultaneous pen registers/traps and traces. For a further example, the carrier must be capable of accommodating 10 simultaneous communications interceptions and 361 simultaneous pen registers/traps and traces. The same form of analysis applies to the maximum capacity requirements.
                        <PRTPAGE P="68120"/>
                    </P>
                    <HD SOURCE="HD1">III. Applicable Administrative Procedures and Executive Orders</HD>
                    <HD SOURCE="HD2">A. Initial Regulatory Flexibility Analysis</HD>
                    <P>
                        The Regulatory Flexibility Act, 5 U.S.C. 601 
                        <E T="03">et seq.</E>
                         requires the preparation of an initial regulatory flexibility analysis whenever an agency is required by law “to publish general notice of proposed rulemaking for any proposed rule.” 5 U.S.C. 603(a). This publication provides our response to the remand instructions of the Court of Appeals, by providing further explanation and guidance regarding the final notice of capacity issued pursuant to CALEA, 47 U.S.C. 1003. We are not republishing the final notice of capacity, and are therefore not changing the final regulatory flexibility analysis provided with the final notice. Rather, this publication pertains only to the two discrete issues remanded by the Court, those being our interpretation of the term “simultaneously” and our decision to present only one “actual” and one “maximum” capacity requirement per geographic region. Our initial regulatory flexibility analysis is therefore limited to those issues.
                    </P>
                    <P>The reason for this publication is to respond to the Court's remand instructions. Our objective in issuing it, is to provide further explanation for our interpretation of the term “simultaneously” and to provide additional guidance on the application of the capacity requirements with respect to different types of surveillance (interceptions versus pen registers/traps and traces).</P>
                    <P>
                        The Regulatory Flexibility Act requires a description of, and if feasible, an estimate of the number of small entities to which a proposed rule will apply. 5 U.S.C. 603(b)(3). A “small entity” in the wired or wireless telecommunications business includes an entity that is independently owned and operated, not dominant in its field of operation, and has fewer than 1,500 employees. 5 U.S.C. 601(6)(1); 15 U.S.C. 632; 13 CFR 121.201. The Bureau of the Census issued the 1997 Economic Census on October 20, 2000. The Economic Census profiles the U.S. economy every 5 years, from the national to the local level. The 2002 Economic Census is currently being conducted, and thus the 1997 data represents the most current information. The 1997 Economic Census reports that there were 2,797 wired telecommunications communications (NAICS code 513310) firms, of which all but 24 had fewer than 1,000 employees. 
                        <E T="03">See</E>
                         1997 Economic Census, Establishment and Firm Size, Publication EC97S51S-SZ. It further reports that there were 1,238 cellular and other wireless telecommunications (NAICS code 513322) firms, of which all but 12 had fewer than 1,000 employees. Firms engaged as telecommunications resellers (NAICS code 513330) numbered 1,417, of which all but 2 had fewer than 1,000 employees. We are unaware of any source of further information from which we could determine the number of firms that are independently owned and operated and not dominant in their field of operation.
                    </P>
                    <P>This publication imposes no reporting or record-keeping requirements. The final notice imposed certain compliance requirements, the application of which is further guided and clarified by the statements herein. We are not republishing the final notice, nor changing the existing numerical capacity requirements stated therein. We are also providing further guidance as to the application of the capacity requirements in regions with the highest requirements, by setting a maximum number of communications interceptions that is lower than the total capacity requirement. The economic impact of compliance with the capacity requirements for small entities that operate in regions affected by this guidance, therefore, might be lowered if the entity employed a system that could benefit from a requirement for fewer simultaneous communications interceptions. In all other cases the economic impact created by the final notice will remain unchanged by this publication. We therefore find that there will be no significant economic impact on small businesses as a result of this publication. The FBI is unaware of any rules which would overlap, duplicate or conflict with this publication or the statements therein.</P>
                    <HD SOURCE="HD2">B. Executive Order 12866: Regulatory Planning and Review</HD>
                    <P>This publication has been drafted and reviewed in accordance with Executive Order 12866. The FBI does not find that it constitutes a “significant regulatory action” in accordance with that Order. In particular, we had already determined that the final notice of capacity did not meet the criterion for a “significant regulatory action” and that it would not result in an annual impact on the economy in excess of $100,000,000, nor would economically impact State, local or tribal governments. 63 FR 12220. This publicaton does not significantly alter the economic analysis contained in the final notice, except that compliance costs may be reduced in some cases.</P>
                    <P>In this publication, we are neither republishing the final notice, nor changing the existing numerical capacity requirements stated therein. We are providing further guidance as to the application of the capacity requirements in regions with the highest requirements, by setting a maximum number of communications interceptions that is lower than the total capacity requirement. The economic impact of compliance with the capacity requirements for entities that operate in regions affected by this guidance, therefore, might be lowered if the entity employed a system that could benefit from a requirement for fewer simultaneous communications interceptions. In all other cases the economic impact created by the final notice, remains unchanged by this publication. Although not required by Executive Order 12866, this publication has been submitted for review by the Office of Management and Budget.</P>
                    <HD SOURCE="HD2">C. Executive Order 13132: Federalism</HD>
                    <P>This publication will not have a substantial direct effect of the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government. Therefore, in accordance with Executive Order 13132, it is determined that this publication does not have any federalism implications that warrant preparation of a federalism impact statement.</P>
                    <HD SOURCE="HD2">D. Executive Order 12988: Civil Justice Reform</HD>
                    <P>This publication meets the applicable standards set forth in sections 3(a) and 3(b) of Executive Order 12988, Civil Justice Reform.</P>
                    <HD SOURCE="HD2">E. Unfunded Mandates Reform Act of 1995</HD>
                    <P>
                        We determined in the final notice of capacity that it would not result in the expenditure by State, local or tribal governments, in the aggregate, or by the private sector, of $100,000,000 or more in any one year, and it will not significantly or uniquely affect small governments. This publication only provides further explanation and guidance with regard to two matters contained in the final notice of capacity and would neither alter the analysis contained in the final notice, nor would result in any increase in any expenditures. Therefore, no actions deemed necessary under the provisions of the Unfunded Mandates Reform Act of 1995, 2 U.S.C. 1532(a).
                        <PRTPAGE P="68121"/>
                    </P>
                    <HD SOURCE="HD2">F. Small Business Regulatory Enforcement Fairness Act of 1996</HD>
                    <P>This publication is not a major rule as defined by the Small Business Regulatory Enforcement Fairness Act of 1996, 5 U.S.C. 804. We determined in the final notice of capacity that it would not have an annual effect on the economy of $100,000,000 or more; would not cause a major increase in costs or prices; and would not result in a significant adverse effect on competition, employment, investment or productivity, and innovation, or on the ability of the United States-based companies to compete with foreign-based companies in domestic and export markets. This publication only provides further explanation and guidance with regard to two matters contained in the final notice of capacity and would neither alter the analysis contained in the final notice, nor would result in any increase in expenditures. Some reductions in expenditures by small businesses are possible in certain cases.</P>
                    <HD SOURCE="HD2">G. Paperwork Reduction Act</HD>
                    <P>
                        This Supplement contains no information collection or record-keeping requirements under the Paperwork Reduction Act, 44 U.S.C. 3501 
                        <E T="03">et seq.</E>
                    </P>
                    <SIG>
                        <DATED>Dated: November 4, 2003.</DATED>
                        <NAME>Valerie E. Caproni,</NAME>
                        <TITLE>General Counsel, Federal Bureau of Investigation.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30258 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4410-02-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF LABOR</AGENCY>
                <SUBAGY>Office of the Secretary</SUBAGY>
                <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
                <DATE> November 26, 2003.</DATE>
                <P>
                    The Department of Labor (DOL) has submitted the following public information collection request (ICR) to the Office of Management and Budget (OMB) for review and approval in accordance with the Paperwork Reduction Act of 1995 (Pub. L. 104-13, 44 U.S.C. Chapter 35). A copy of this ICR, with applicable supporting documentation, may be obtained by contacting the Department of Labor. To obtain documentation, contact Darrin King on 202-693-4129 (this is not a toll-free number) or E-Mail: 
                    <E T="03">reeves.vanessa2@dol.gov</E>
                    .
                </P>
                <P>
                    Comments should be sent to Office of Information and Regulatory Affairs, Attn: OMB Desk Officer for the Employment and Training Administration (ETA), Office of Management and Budget, Room 10235, Washington, DC 20503 (202-395-7316 / this is not a toll-free number), within 30 days from the date of this publication in the 
                    <E T="04">Federal Register</E>
                    .
                </P>
                <P>The OMB is particularly interested in comments which:</P>
                <P>• Evaluate whether the proposed collection of information is necessary for the proper performance of the functions of the agency, including whether the information will have practical utility;</P>
                <P>• Evaluate the accuracy of the agency's estimate of the burden of the proposed collection of information, including the validity of the methodology and assumptions used;</P>
                <P>• Enhance the quality, utility, and clarity of the information to be collected; and</P>
                <P>
                    • Minimize the burden of the collection of information on those who are to respond, including through the use of appropriate automated, electronic, mechanical, or other technological collection techniques or other forms of information technology, 
                    <E T="03">e.g.</E>
                    , permitting electronic submission of responses.
                </P>
                <P>
                    <E T="03">Agency:</E>
                     Employment and Training Administration.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Revision of a currently approved collection.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Workforce Investment Act: National Emergency Grant (NEG) Assistance-Application and Reporting Procedures.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1205-0439.
                </P>
                <P>
                    <E T="03">Affected Public:</E>
                     State, local, or tribal government.
                </P>
                <P>
                    <E T="03">Type of Response:</E>
                     Reporting.
                </P>
                <P>
                    <E T="03">Frequency:</E>
                     On occasion and quarterly.
                </P>
                <P>
                    <E T="03">Number of Respondents:</E>
                     150.
                </P>
                <GPOTABLE COLS="6" OPTS="L2,tp0,i1" CDEF="s100,10,xs66,10,7.2,10">
                    <TTITLE> </TTITLE>
                    <BOXHD>
                        <CHED H="1">Information collection</CHED>
                        <CHED H="1">Estimated number of respondents</CHED>
                        <CHED H="1">Frequency</CHED>
                        <CHED H="1">Estimated annual responses</CHED>
                        <CHED H="1">Average response time (hours)</CHED>
                        <CHED H="1">Estimated annual burden hours</CHED>
                    </BOXHD>
                    <ROW>
                        <ENT I="01">SF-434 (OMB No. 0348-0043)</ENT>
                        <ENT>150</ENT>
                        <ENT>1 time</ENT>
                        <ENT>150</ENT>
                        <ENT>0.75</ENT>
                        <ENT>113</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">Narrative Summary</ENT>
                        <ENT>150</ENT>
                        <ENT>1 time</ENT>
                        <ENT>150</ENT>
                        <ENT>1</ENT>
                        <ENT>150</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">TAA Certification Report</ENT>
                        <ENT>50</ENT>
                        <ENT>1 time</ENT>
                        <ENT>50</ENT>
                        <ENT>0.5</ENT>
                        <ENT>25</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ETA-9103</ENT>
                        <ENT>150</ENT>
                        <ENT>1 time</ENT>
                        <ENT>150</ENT>
                        <ENT>1.5</ENT>
                        <ENT>225</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ETA-9105</ENT>
                        <ENT>75</ENT>
                        <ENT>1 time</ENT>
                        <ENT>75</ENT>
                        <ENT>0.5</ENT>
                        <ENT>38</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ETA-9106</ENT>
                        <ENT>150</ENT>
                        <ENT>1 time</ENT>
                        <ENT>150</ENT>
                        <ENT>1</ENT>
                        <ENT>150</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ETA-9107</ENT>
                        <ENT>100</ENT>
                        <ENT>1 time</ENT>
                        <ENT>100</ENT>
                        <ENT>0.25</ENT>
                        <ENT>25</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="01">ETA-9104</ENT>
                        <ENT>150</ENT>
                        <ENT>Quarterly</ENT>
                        <ENT>600</ENT>
                        <ENT>0.5</ENT>
                        <ENT>300</ENT>
                    </ROW>
                    <ROW RUL="n,s">
                        <ENT I="01">Grant Modifications</ENT>
                        <ENT>140</ENT>
                        <ENT>1 time</ENT>
                        <ENT>140</ENT>
                        <ENT>0.5</ENT>
                        <ENT>70</ENT>
                    </ROW>
                    <ROW>
                        <ENT I="04">Total</ENT>
                        <ENT/>
                        <ENT/>
                        <ENT>1,565</ENT>
                        <ENT/>
                        <ENT>1,096</ENT>
                    </ROW>
                </GPOTABLE>
                <P>
                    <E T="03">Total Annualized Capital/Startup Costs:</E>
                     $0.
                </P>
                <P>
                    <E T="03">Total Annual Costs (operating/maintaining systems or purchasing services):</E>
                     $0.
                </P>
                <P>
                    <E T="03">Description:</E>
                     The Department of Labor/Employment and Training Administration announces policies and application and reporting procedures for states and local entities to enable them to access funds for National Emergency Grant (NEG) programs. NEGs are discretionary grants intended to complement the resources and service capacity at the State and local area levels by providing supplemental funding for workforce development and employment services and other adjustment assistance for dislocated workers and other eligible individuals as defined in sections 101, 134 and 173 of the Workforce Investment Act; sections 113, 114 and 203 of the Trade Act of 2002; and 20 CFR 671.140.
                </P>
                <SIG>
                    <NAME>Ira L. Mills,</NAME>
                    <TITLE>Departmental Clearance Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30248 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4510-30-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="68122"/>
                <AGENCY TYPE="S">DEPARTMENT OF LABOR</AGENCY>
                <SUBAGY>Employment and Training Administration</SUBAGY>
                <SUBJECT>Workforce Security Programs: Training and Employment Guidance Letter Interpreting Federal Law</SUBJECT>
                <P>
                    The Employment and Training Administration interprets federal law requirements pertaining to unemployment compensation (UC) and public employment services (ES). These interpretations are issued in Training and Guidance Letters (TEGLs) to the State Workforce Agencies. The TEGL described below is published in the 
                    <E T="04">Federal Register</E>
                     in order to inform the public.
                </P>
                <HD SOURCE="HD1">TEGL 18-01, Change 1</HD>
                <P>TEGL 18-01, Change 1, using a Q &amp; A format, answers additional questions related to the appropriate uses of the Reed Act distribution made on March 13, 2002.</P>
                <SIG>
                    <DATED>Dated: December 1, 2003.</DATED>
                    <NAME>Emily Stover DeRocco,</NAME>
                    <TITLE>Assistant Secretary of Labor.</TITLE>
                </SIG>
                <EXTRACT>
                    <HD SOURCE="HD1">Employment and Training Administration Advisory System, U.S. Department of Labor, Washington, DC 20210</HD>
                    <FP SOURCE="FP-1">CLASSIFICATION: Reed Act</FP>
                    <FP SOURCE="FP-1">CORRESPONDENCE SYMBOL: DL</FP>
                    <FP SOURCE="FP-1">DATE: March 19, 2003</FP>
                    <HD SOURCE="HD3">Training and Employment Guidance Letter No. 18-01 Change 1</HD>
                    <FP SOURCE="FP-2">To: All State Workforce Liaisons,Allstate Workforce Agencies,Allstate Worker Adjustment Liaisons,Allone-Stop Center System Leads</FP>
                    <FP SOURCE="FP-2">From: Emily Stover DeRocco, Assistant Secretary</FP>
                    <FP SOURCE="FP-2">Subject: Reed Act—Questions and Answers</FP>
                    <P>
                        1. 
                        <E T="03">Purpose.</E>
                         To answer questions related to the use of Reed Act funds that have arisen since the issuance of Training and Employment Guidance Letter (TEGL) 18-01.
                    </P>
                    <P>
                        2. 
                        <E T="03">References.</E>
                         Section 209 of the Temporary Extended Unemployment Compensation Act of 2002 (TEUCA), which is Title II of the Job Creation and Worker Assistance Act of 2002, P.L. No. 107-147, signed by the President on March 9, 2002; Title IX of the Social Security Act (SSA); the Federal Unemployment Tax Act (FUTA); the Wagner-Peyser Act; TEGL 18-01 (67 FR 34730 (May 15, 2002)); TEGL 24-01; and Unemployment Insurance Program Letter (UIPL) 39-97 (62 FR 63960 (December 3, 1997)), UIPL 39-97, Change 1 (January 16, 2002) and UIPL 20-02 (April 4, 2002).
                    </P>
                    <P>
                        3. 
                        <E T="03">Background.</E>
                         TEGL 18-01 described the permissible uses of the $8 billion Reed Act distribution that was made to the states' accounts in the Unemployment Trust Fund on March 13, 2002. In general, this distribution is available for the payment of unemployment compensation (UC) and the administration of state UC laws and public employment offices.
                    </P>
                    <FP SOURCE="FP-1">RESCISSIONS: None</FP>
                    <FP SOURCE="FP-1">EXPIRATION DATE: Continuing</FP>
                    <P>Since the issuance of TEGL 18-01, the Department has received questions concerning permissible uses of Reed Act funds. In addition, the Department has reviewed state legislative proposals appropriating the Reed Act funds, some of which raised issues of consistency with federal law. The following Questions and Answers address these matters.</P>
                    <P>
                        4. 
                        <E T="03">Action.</E>
                         State administrators should distribute this advisory to appropriate staff. States must adhere to the requirements of Federal law that are contained in this advisory.
                    </P>
                    <P>
                        5. 
                        <E T="03">Inquiries.</E>
                         Questions should be addressed to your Regional Office.
                    </P>
                    <P>
                        6. 
                        <E T="03">Attachment.</E>
                    </P>
                    <HD SOURCE="HD3">Reed Act Distributions Under the Temporary Extended Unemployment Compensation Act of 2002—Questions and Answers</HD>
                    <HD SOURCE="HD1">Attachment—Reed Act Distributions Under the Temporary Extended Unemployment Compensation Act of 2002—Questions and Answers</HD>
                    <P>
                        1. 
                        <E T="03">Question:</E>
                         Since my state's legislature meets in session only for short periods each year, my state's law delegates certain legislative functions, including certain appropriation functions, to the Governor. May the Governor “appropriate” Reed Act funds under this delegation?
                    </P>
                    <P>
                        <E T="03">Answer:</E>
                         No. Question and Answer 9 in Attachment I to TEGL 18-01 explains that Section 903(c)(2), SSA, provides that a state may use Reed Act funds for administrative purposes only “pursuant to a specific appropriation made by the legislative body of the State.” (Emphasis added.) That section of the SSA goes on to provide that a withdrawal may be made for the payment of administrative expenses “if and only if” the appropriation law meets certain requirements. Among these requirements is that “the purposes and the amounts” must be “specified in the law making the appropriation.” Senate Report No. 1621 elaborated on the appropriation requirement. It states that a state may use Reed Act funds for administrative expenses only “through a special appropriation act of its legislature” and that such use of Reed Act funds is “subject to rigid control by the state legislature (which control is specified in the bill in detail).” (Emphasis added. 1954 U.S.C.C.A.N. 2909, 2910, 2914.)
                    </P>
                    <P>
                        2. 
                        <E T="03">Question:</E>
                         May Reed Act funds be used for administrative expenses incurred before the date of enactment of the state appropriations?
                    </P>
                    <P>
                        <E T="03">Answer:</E>
                         No. Under Section 903(c)(2)(C), SSA, a state's Reed Act appropriation law must provide that “the expenses are incurred after” the date of the enactment of the appropriation.
                    </P>
                    <P>
                        3. 
                        <E T="03">Question:</E>
                         May my state use Reed Act funds to deliver employment services outside its One-Stop system?
                    </P>
                    <P>
                        <E T="03">Answer:</E>
                         In general, no. Reed Act funds may be used for expenses incurred by a state “for the administration of its unemployment compensation law and public employment offices.” As noted in TEGL 18-01, “administration of * * * public employment offices” means “any function fundable under the Wagner-Peyser Act.” Section 7(e), Wagner-Peyser, provides that “all job search, placement, recruitment, labor employment statistics, and other labor exchange services authorized under subsection (a) shall be provided, consistent with the other requirements of this Act, as part of the one-stop delivery system established by the state.”
                    </P>
                    <P>Section 7(b)(2), Wagner-Peyser, does authorize provisions of services outside the One-Stop. However, these services may be provided only to “groups with special needs, carried out pursuant to joint agreements between the employment service and the appropriate local workforce investment board and chief elected official or officials or other public agencies or private nonprofit organization.” (Emphasis added.) Thus, for Reed Act purposes, moneys may be expended outside the one-stop system on these groups with special needs only if there is an agreement with the state's ES agency.</P>
                    <P>Note that the state's share of the $100 million Reed Act distributions made in each of fiscal years 2000 through 2002 may be used only for UC administration. (See Question and Answer 20 in Attachment I to TEGL 18-01.)</P>
                    <P>
                        4. 
                        <E T="03">Question:</E>
                         May my state legislature appropriate Reed Act funds to an agency other than the state agency (or agencies) administering the UC program and the employment service (ES) program?
                    </P>
                    <P>
                        <E T="03">Answer:</E>
                         No. While nothing prohibits the UC or ES agencies from providing Reed Act funds to other agencies to perform permissible Reed Act activities (
                        <E T="03">e.g.</E>
                        , information technology services supporting the UC and ES agencies), the appropriation must be made to the UC and/or ES agency.
                    </P>
                    <P>The intent behind the Reed Act was to allow states to supplement their federal UC and ES grants. (See, for example, H. Rep. 21 (1954 U.S.C.C.A.N. 2909-2911); H. Rep. 251, 107th Cong. 1st Sess. 58-59.) Therefore, just as the state agency administering the state's UC law receives the federal UC administrative grant, the same agency is to receive Reed Act funds for administering the UC law. Similarly, just as the state agency administering the state's ES program receives the Wagner-Peyser grant, the same agency is to receive Reed Act funds for administering its public employment offices.</P>
                    <P>Appropriating Reed Act funds only to the state UC and/or ES agencies, which have expertise in determining what are permissible UI and Wagner-Peyser Act functions, helps assure that Reed Act funds are used only for permissible purposes. This in turn will help avoid federal questions regarding use.</P>
                    <P>If the state legislature appropriated Reed Act funds to an agency other than the state agency administering the state UC or ES programs prior to the effective date of this TEGL, the Department will not raise any issues with respect to the appropriation to such other agency. However, the state UC and/or ES agencies, as appropriate, should work with such other state agency to assure that Reed Act funds are used consistently with federal law requirements.</P>
                    <P>
                        5. 
                        <E T="03">Question:</E>
                         May Reed Act funds be used to pay travel expenses incurred by trainees?
                        <PRTPAGE P="68123"/>
                    </P>
                    <P>
                        <E T="03">Answer.</E>
                         Only to the same extent Wagner-Peyser Act funds may be used for this purpose. Generally, Wagner-Peyser Act funds may not pay for transportation costs, but there are two exceptions:
                    </P>
                    <P>• Section (7)(b)(2) of the Wagner-Peyser Act discusses “services for groups with special needs, carried out pursuant to joint agreements between the employment service and the appropriate workforce investment board and chief elected official or officials or other public agencies or private nonprofits organization.” Costs of transporting members of such groups may be funded from Reed Act funds.</P>
                    <P>• Section 7(b)(3), Wagner-Peyser, identifies “the extra costs of exemplary models for delivering” Wagner-Peyser services as an allowable use of Wagner-Peyser funds. If transportation were part of an exemplary service delivery model for such services, it may be funded from Reed Act.</P>
                    <P>In both cases, transportation costs would be allowable only if the transportation involves transporting customers to enable them to access and receive employment services funded under the Wagner-Peyser Act or the Reed Act.</P>
                </EXTRACT>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30249 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4510-30-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF LABOR</AGENCY>
                <SUBAGY>Employment Standards Administration; Wage and Hour Division</SUBAGY>
                <SUBJECT>Minimum Wages for Federal and Federally Assisted Construction; General Wage Determination Decisions</SUBJECT>
                <P>General wage determination decisions of the Secretary of Labor are issued in accordance with applicable law and are based on the information obtained by the Department of Labor from its study of local wage conditions and data made available from other sources. They specify the basic hourly wage rates and fringe benefits which are determined to be prevailing for the described classes of laborers and mechanics employed on construction projects of a similar character and in the localities specified therein.</P>
                <P>The determinations in these decisions of prevailing rates and fringe benefits have been made in accordance with 29 CFR Part 1, by authority of the Secretary of Labor pursuant to the provisions of the Davis-Bacon Act of March 3, 1931, as amended (46 Stat. 1494, as amended, 40 U.S.C. 276a) and of other Federal statutes referred to in 29 CFR Part 1, Appendix, as well as such additional statutes as may from time to time be enacted containing provisions for the payment of wages determined to be prevailing by the Secretary of Labor in accordance with the Davis-Bacon Act. The prevailing rates and fringe benefits determined in these decisions shall, in accordance with the provisions of the foregoing statutes, constitute the minimum wages payable on Federal and federally assisted construction projects to laborers and mechanics of the specified classes engaged on contract work of the character and in the localities described therein.</P>
                <P>Good cause is hereby found for not utilizing notice and public comment procedure thereon prior to the issuance of these determinations as prescribed in 5 U.S.C. 553 and not providing for delay in the effective date as prescribed in that section, because the necessity to issue current construction industry wage determinations frequently and in large volume causes procedures to be impractical and contrary to the public interest.</P>
                <P>
                    General wage determination decisions, and modifications and supersedeas decisions thereto, contain no expiration dates and are effective from their date on notice in the 
                    <E T="04">Federal Register</E>
                    , or on the date written notice is received by the agency, whichever is earlier. These decisions are to be used in accordance with the provisions of 29 CFR Parts 1 and 5. Accordingly, the applicable decision, together with any modifications issued, must be made a part of every contract for performance of the described work within the geographic area indicated as required by an applicable Federal prevailing wage law and 29 CFR Part 5. The wage rates and fringe benefits, notice of which is published herein, and which are contained in the Government Printing Office (GPO) document entitled “General Wage Determinations Issued Under The Davis-Bacon And Related Acts,” shall be the minimum paid by contractors and subcontractors to laborers and mechanics.
                </P>
                <P>Any person, organization, or governmental agency having an interest in the rates determined as prevailing is encouraged to submit wage rate and fringe benefit information for consideration by the Department.</P>
                <P>Further information and self-explanatory forms for the purpose of submitting this data may be obtained by writing to the U.S. Department of Labor, Employment Standards Administration, Wage and Hour Division, Division of Wage Determinations, 200 Constitution Avenue, NW., Room S-3014, Washington, DC 20210.</P>
                <HD SOURCE="HD1">Modification to General Wage Determination Decisions</HD>
                <P>
                    The number of the decisions listed to the Government Printing Office document entitled “General Wage Determinations Issued Under the Davis-Bacon and Related Acts” being modified are listed by Volume and State. Dates of publication in the 
                    <E T="04">Federal Register</E>
                     are in parentheses following the decisions being modified.
                </P>
                <EXTRACT>
                    <HD SOURCE="HD2">Volume I</HD>
                    <FP SOURCE="FP-2">Rhode Island</FP>
                    <FP SOURCE="FP1-2">RI030001 (Jun. 13, 2003)</FP>
                    <HD SOURCE="HD2">Volume II</HD>
                    <FP SOURCE="FP-2">Pennsylvania</FP>
                    <FP SOURCE="FP1-2">PA030001 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">PA030002 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">PA030003 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">PA030004 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">PA030005 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">PA030006 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">PA030007 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">PA030008 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">PA030009 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">PA0300010 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">PA0300013 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">PA0300014 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">PA0300016 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">PA0300018 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">PA0300019 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">PA0300021 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">PA0300023 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">PA0300024 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">PA0300025 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">PA0300026 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">PA0300030 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">PA0300031 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">PA0300032 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">PA0300033 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">PA0300040 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">PA0300042 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">PA0300052 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">PA0300059 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">PA0300060 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">PA0300061 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">PA0300065 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP-2">West Virginia</FP>
                    <FP SOURCE="FP1-2">WV030001 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">WV030002 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">WV030003 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">WV030006 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">WV030010 (Jun. 13, 2003)</FP>
                    <HD SOURCE="HD2">Volume III</HD>
                    <FP SOURCE="FP-2">Kentucky</FP>
                    <FP SOURCE="FP1-2">KY030003 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">KY030025 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">KY030027 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">KY030029 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">KY030035 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP-2">Mississippi</FP>
                    <FP SOURCE="FP1-2">MS030003 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">MS030050 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">MS030055 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">MS030056 (Jun. 13, 2003)</FP>
                    <HD SOURCE="HD2">Volume IV</HD>
                    <FP SOURCE="FP-2">None</FP>
                    <HD SOURCE="HD2">Volume V</HD>
                    <FP SOURCE="FP-2">Louisiana</FP>
                    <FP SOURCE="FP1-2">LA030053 (Jun. 13, 2003)</FP>
                    <HD SOURCE="HD2">Volume VI</HD>
                    <FP SOURCE="FP-2">Colorado</FP>
                    <FP SOURCE="FP1-2">CO030001 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">CO030002 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">CO030003 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">
                        CO030004 (Jun. 13, 2003)
                        <PRTPAGE P="68124"/>
                    </FP>
                    <FP SOURCE="FP1-2">CO030005 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">CO030006 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">CO030007 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">CO030009 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">CO030011 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">CO030012 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">CO030016 (Jun. 13, 2003)</FP>
                    <HD SOURCE="HD2">Volume VII</HD>
                    <FP SOURCE="FP-2">Nevada</FP>
                    <FP SOURCE="FP1-2">NV030002 (Jun. 13, 2003)</FP>
                    <FP SOURCE="FP1-2">NV030009 (Jun. 13, 2003)</FP>
                </EXTRACT>
                <HD SOURCE="HD1">General Wage Determination Publication</HD>
                <P>General wage determination issued under the Davis-Bacon and related Acts, including those noted above, may be found in the Government Printing Office (GPO) document entitled “General Wage determinations Issued Under the Davis-Bacon And Related Acts”. This publication is available at each of the 50 Regional Government Depository Libraries and many of the 1,400 Government Depository Libraries across the country.</P>
                <P>
                    General wage determinations issued under the Davis-Bacon and related Acts are available electronically at no cost on the Government Printing Office site at 
                    <E T="03">http://www.access.gpo.gov/davisbacon.</E>
                     They are also available electronically by subscription to the Davis-Bacon Online Service (
                    <E T="03">http://davisbacon.fedworld.gov)</E>
                     of the National Technical Information Service (NTIS) of the U.S. Department of Commerce at 1-800-363-2068. This subscription offers value-added features such as electronic delivery of modified wage decisions directly to the user's desktop, the ability to access prior wage decisions issued during the year, extensive Help desk Support, etc.
                </P>
                <P>Hard-copy subscriptions may be purchased from: Superintendent of Documents, U.S. Government Printing Office, Washington, DC 20402, (202) 512-1800.</P>
                <P>When ordering hard-copy subscription(s), be sure to specify the State(s) of interest, since subscriptions may be ordered for any or all of the six separate Volumes, arranged by State. Subscriptions include an annual edition (issued in January or February) which includes all current general wage determinations for the States covered by each volume. Throughout the remainder of the year, regular weekly updates will be distributed to subscribers.</P>
                <SIG>
                    <DATED>Signed at Washington, DC, this 26th day of November, 2003.</DATED>
                    <NAME>John Frank,</NAME>
                    <TITLE>Acting Chief, Branch of Construction Wage Determinations.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 03-29998  Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4510-27-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">NATIONAL SCIENCE FOUNDATION</AGENCY>
                <SUBJECT>Notice of Permit Applications Received Under the Antarctic Conservation Act of 1978 (Public Law 95-541)</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Science Foundation.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of permit applications received under the Antarctic Conservation Act of 1978, Public Law 95-541. </P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The National Science Foundation (NSF) is required to publish notice of permit applications received to conduct activities regulated under the Antarctic Conservation Act of 1978. NSF has published regulations under the Antarctic Conservation Act at title 45 part 670 of the Code of Federal Regulations. This is the required notice of permit applications received.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>Interested parties are invited to submit written data, comments, or views with respect to this permit application by January 5, 2003. This application may be inspected by interested parties at the Permit Office, address below.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>Comments should be addressed to Permit Office, Room 755, Office of Polar Programs, National Science Foundation, 4201 Wilson Boulevard, Arlington, Virginia 22230.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Nadene G. Kennedy at the above address or (703) 292-7405.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>The National Science Foundation, as directed by the Antarctic Conservation Act of 1978 (Pub. L. 95-541), as amended by the Antarctic Science, Tourism and Conservation Act of 1996, has developed regulations for the establishment of a permit system for various activities in Antarctica and designation of certain animals and certain geographic areas a requiring special protection. The regulations establish such a permit system to designate Antarctic Specially Protected Areas.</P>
                <P>The applications received are as follows:</P>
                <HD SOURCE="HD1">1. Applicant</HD>
                <P>Robert A. Blanchette, Department of Plant Pathology; 1991 Upper Buford Circle; 495 Borlaug Hall, University of Minnesota, St. Paul, MN 55108-6030.</P>
                <HD SOURCE="HD2">Activity for Which Permit is Requested</HD>
                <P>Take and Enter Antarctic Specially Protected Areas. The applicant proposes enter the historic huts in the Ross Sea Region (Cape Evans—ASPA #154, Cape Royds—ASPA #156, and Discovery Hut—ASPA #157) to collect samples of deterioration in and around the huts, evaluate damage from historic chemical and fuel spills, assess microbial populations at the sites and set up environmental monitoring of humidity and temperature within the huts. This work is being done in cooperation with the conservators from the New Zealand Antarctic Heritage Trust and researchers from the University of Waikato, New Zealand.</P>
                <HD SOURCE="HD2">Location</HD>
                <P>Cape Evans Historic Site (ASPA #154), Cape Royds (ASPA #156), and Discovery Hut, Ross Island (ASPA #157):</P>
                <HD SOURCE="HD2">Dates</HD>
                <P>January 1, 2004 to December 31, 2007.</P>
                <SIG>
                    <NAME>Nadene G. Kennedy,</NAME>
                    <TITLE>Permit Officer, Office of Polar Programs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30197  Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7555-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">NATIONAL SCIENCE FOUNDATION</AGENCY>
                <SUBJECT>National Science Board; Committee on Education and Human Resources</SUBJECT>
                <P>
                    <E T="03">Date and Time:</E>
                     December 4, 2003, 12 noon-1 p.m., Open Session.
                </P>
                <P>
                    <E T="03">Place:</E>
                     The National Science Foundation, Stafford One Building, 4201 Wilson Boulevard, Room 220,Arlington, VA 22230.
                </P>
                <P>
                    <E T="03">Status:</E>
                     This meeting will be open to the public.
                </P>
                <P>
                    <E T="03">Matters To Be Considered:</E>
                </P>
                <HD SOURCE="HD1">Thursday December 4, 2003</HD>
                <P>
                    <E T="03">Open Session 12 noon to 1 p.m.</E>
                </P>
                <P>Approval of the Board's response to Section 22 of the NSF Authorization Act, December, 2002.</P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>
                        Cathy Hines, Operations Officer, NSB, (703) 292-7000, 
                        <E T="03">http://www.nsf.gov/nsb.</E>
                    </P>
                    <SIG>
                        <NAME>Cathy Hines,</NAME>
                        <TITLE>Operations Officer.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30328 Filed 12-2-03; 4:22 pm]</FRDOC>
            <BILCOD>BILLING CODE 7555-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">NATIONAL SCIENCE FOUNDATION</AGENCY>
                <SUBJECT>National Science Board and Its Subdivisions</SUBJECT>
                <P>
                    <E T="03">Federal Register Citation of Previous Announcement:</E>
                     Volume 68, Number 220, 
                    <E T="04">Federal Register,</E>
                     pages 64661-64662, November 14, 2003.
                </P>
                <P>
                    <E T="03">Previously Announced Date and Time:</E>
                     Wednesday, November 19, 2003.
                    <PRTPAGE P="68125"/>
                </P>
                <HD SOURCE="HD1">Additional Concurrent Session</HD>
                <HD SOURCE="HD2">Open</HD>
                <P>National Science Board, Ad Hoc Task Group on Long-Lived Data Collections, (2:30-3:30 p.m.), Room 1295.</P>
                <P>
                    Place: The National Science Foundation, 4201 Wilson Boulevard, Arlington, VA 22230, 
                    <E T="03">http://www.nsf.gov/nsb</E>
                    .
                </P>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>National Science Board Office (703) 202-7000.</P>
                    <P>
                        <E T="03">Status:</E>
                         Open.
                    </P>
                    <P>
                        <E T="03">Changes in the Meeting:</E>
                         A one-hour open meeting was added to the agenda after the schedule was published on the Web and in the 
                        <E T="04">Federal Register.</E>
                         Public announcement of this additional session was made on the NSF Web site ahead of the meeting; no earlier notice was possible. The following topic was discussed.
                    </P>
                    <P>
                        <E T="03">Discussion:</E>
                         Possible Workshop on Users of Long-Lived Data Collections.
                    </P>
                    <SIG>
                        <NAME>Michael P. Crosby,</NAME>
                        <TITLE>Executive Officer, NSB.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30329  Filed 12-2-03; 4:22 pm]</FRDOC>
            <BILCOD>BILLING CODE 7555-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">NUCLEAR REGULATORY COMMISSION</AGENCY>
                <DEPDOC>[Docket Nos. 50-348 and 50-364]</DEPDOC>
                <SUBJECT>Southern Nuclear Operating Company, Joseph M. Farley Nuclear Plant; Notice of Intent to Prepare an Environmental Impact Statement and Conduct Scoping Process</SUBJECT>
                <P>
                    Southern Nuclear Operating Company (SNC) has submitted an application for renewal of Facility Operating Licenses, NPF-2 and NPF-8 for an additional 20 years of operation at the Joseph M. Farley Nuclear Plant, Units 1 and 2. The Farley Nuclear Plant (FNP) is located in Houston County, Alabama about 16.5 miles east of the City of Dothan, Alabama. The operating licenses for Farley Nuclear Plant, Units 1 and 2, expire on June 25, 2017, and March 31, 2021, respectively. The application for renewal was received on September 15, 2003, pursuant to 10 CFR part 54. A notice of receipt and availability of the application, which included the environmental report (ER), was published in the 
                    <E T="04">Federal Register</E>
                     on October 6, 2003, (68 FR 57715). A notice of acceptance for docketing of the application for renewal of the facility operating license was published in the 
                    <E T="04">Federal Register</E>
                     on October 30, 2003, (68 FR 68135). A notice of an opportunity for a hearing regarding the application was published in the 
                    <E T="04">Federal Register</E>
                     on November 5, 2003, (68 FR 62640). The purpose of this notice is to inform the public that the U.S. Nuclear Regulatory Commission (NRC) will be preparing an environmental impact statement (EIS) in support of the review of the license renewal application and to provide the public an opportunity to participate in the environmental scoping process, as defined in 10 CFR 51.29. In addition, as outlined in 36 CFR 800.8, “Coordination with the National Environmental Policy Act,” the NRC plans to coordinate compliance with section 106 of the National Historic Preservation Act in meeting the requirements of the National Environmental Policy Act (NEPA).
                </P>
                <P>
                    In accordance with 10 CFR 51.53(c) and 10 CFR 54.23, SNC submitted the ER as part of the application. The ER was prepared pursuant to 10 CFR part 51 and is available for public inspection at the NRC Public Document Room (PDR), located at One White Flint North, 11555 Rockville Pike (first floor), Rockville, Maryland, or from the Publicly Available Records component of NRC's Agencywide Documents Access and Management System (ADAMS). ADAMS is accessible at 
                    <E T="03">http://www.nrc.gov/reading-rm/adams.html,</E>
                     which provides access through the NRC's Electronic Reading Room link. Persons who do not have access to ADAMS, or who encounter problems in accessing the documents located in ADAMS, should contact the NRC's PDR Reference staff at 1-800-397-4209, or 301-415-4737, or by e-mail to 
                    <E T="03">pdr@nrc.gov.</E>
                     The application may also be viewed on the Internet at 
                    <E T="03">http://www.nrc.gov/reactors/operating/licensing/renewal/applications/farley.html.</E>
                     In addition, the Houston Love Memorial Library, 212 West Burdeshaw Street, Dothan, Alabama and the Lucy Maddox Memorial Library, 11880 Columbia Street, Blakely, Georgia have agreed to make the ER available for public inspection.
                </P>
                <P>This notice advises the public that the NRC intends to gather the information necessary to prepare a plant-specific supplement to the Commission's “Generic Environmental Impact Statement (GEIS) for License Renewal of Nuclear Plants,” (NUREG-1437) in support of the review of the application for renewal of the FNP operating licenses for an additional 20 years. Possible alternatives to the proposed action (license renewal) include no action and reasonable alternative energy sources. The NRC is required by 10 CFR 51.95 to prepare a supplement to the GEIS in connection with the renewal of an operating license. This notice is being published in accordance with the National Environmental Policy Act (NEPA) and the NRC's regulations found in 10 CFR part 51.</P>
                <P>The NRC will first conduct a scoping process for the supplement to the GEIS and, as soon as practicable thereafter, will prepare a draft supplement to the GEIS for public comment. Participation in the scoping process by members of the public and local, State, Tribal, and Federal government agencies is encouraged. The scoping process for the supplement to the GEIS will be used to accomplish the following:</P>
                <P>a. Define the proposed action which is to be the subject of the supplement to the GEIS.</P>
                <P>b. Determine the scope of the supplement to the GEIS and identify the significant issues to be analyzed in depth.</P>
                <P>c. Identify and eliminate from detailed study those issues that are peripheral or that are not significant.</P>
                <P>d. Identify any environmental assessments and other EISs that are being or will be prepared that are related to, but are not part of the scope of the supplement to the GEIS being considered.</P>
                <P>e. Identify other environmental review and consultation requirements related to the proposed action.</P>
                <P>f. Indicate the relationship between the timing of the preparation of the environmental analyses and the Commission's tentative planning and decision-making schedule.</P>
                <P>g. Identify any cooperating agencies and, as appropriate, allocate assignments for preparation and schedules for completing the supplement to the GEIS to the NRC and any cooperating agencies.</P>
                <P>h. Describe how the supplement to the GEIS will be prepared, and include any contractor assistance to be used.</P>
                <P>The NRC invites the following entities to participate in the scoping:</P>
                <P>a. The applicant, Southern Nuclear Operating Company.</P>
                <P>b. Any Federal agency that has jurisdiction by law or special expertise with respect to any environmental impact involved, or that is authorized to develop and enforce relevant environmental standards.</P>
                <P>c. Affected State and local government agencies, including those authorized to develop and enforce relevant environmental standards.</P>
                <P>d. Any affected Indian tribe.</P>
                <P>e. Any person who requests or has requested an opportunity to participate in the scoping process.</P>
                <P>f. Any person who intends to petition for leave to intervene.</P>
                <P>
                    In accordance with 10 CFR 51.26, the scoping process for an EIS may include 
                    <PRTPAGE P="68126"/>
                    a public scoping meeting to help identify significant issues related to a proposed activity and to determine the scope of issues to be addressed in an EIS. The NRC has decided to hold public meetings for the FNP license renewal supplement to the GEIS. The scoping meetings will be held at the Quality Inn, 3053 Ross Clark Circle, Dothan, Alabama, on Thursday, January 8, 2004. There will be two sessions to accommodate interested parties. The first session will convene at 1:30 p.m. and will continue until 4:30 p.m., as necessary. The second session will convene at 7 p.m. with a repeat of the overview portions of the meeting and will continue until 10 p.m., as necessary. Both meetings will be transcribed and will include: (1) An overview by the NRC staff of the NEPA environmental review process, the proposed scope of the supplement to the GEIS, and the proposed review schedule; and (2) the opportunity for interested government agencies, organizations, and individuals to submit comments or suggestions on the environmental issues or the proposed scope of the supplement to the GEIS. Additionally, the NRC staff will host informal discussions one hour before the start of each session at the Quality Inn. No formal comments on the proposed scope of the supplement to the GEIS will be accepted during the informal discussions. To be considered, comments must be provided either at the transcribed public meetings or in writing, as discussed below. Persons may register to attend or present oral comments at the meetings on the scope of the NEPA review by contacting Mr. Cushing, by telephone at 1-800-368-5642, extension 1424, or by Internet to the NRC at 
                    <E T="03">FarleyEIS@nrc.gov</E>
                     no later than January 2, 2004. Members of the public may also register to speak at the meeting within 15 minutes of the start of each session. Individual oral comments may be limited by the time available, depending on the number of persons who register. Members of the public who have not registered may also have an opportunity to speak, if time permits. Public comments will be considered in the scoping process for the supplement to the GEIS. Mr. Cushing will need to be contacted no later than December 17, 2003, if special equipment or accommodations are needed to attend or present information at the public meeting, so that the NRC staff can determine whether the request can be accommodated.
                </P>
                <P>
                    Members of the public may send written comments on the environmental scope of the FNP license renewal review to the Chief, Rules and Directives Branch, Division of Administrative Services, Office of Administration, Mailstop T-6D59, U.S. Nuclear Regulatory Commission, Washington, DC 20555-0001, and should cite the publication date and page number of this 
                    <E T="04">Federal Register</E>
                     notice. Comments may also be delivered to the NRC, Room T-6D59, Two White Flint North, 11545 Rockville Pike, Rockville, Maryland, from 7:30 a.m. to 4:15 p.m. during Federal workdays. To be considered in the scoping process, written comments should be postmarked by February 6, 2004. Electronic comments may be sent by the Internet to the NRC at 
                    <E T="03">FarleyEIS@nrc.gov</E>
                     and should be sent no later than February 6, 2004, to be considered in the scoping process. Comments will be available electronically and accessible through ADAMS at 
                    <E T="03">http://www.nrc.gov/reading-rm/adams.html.</E>
                </P>
                <P>
                    Participation in the scoping process for the supplement to the GEIS does not entitle participants to become parties to the proceeding to which the supplement to the GEIS relates. Notice of opportunity for a hearing regarding the renewal application was the subject of the aforementioned 
                    <E T="04">Federal Register</E>
                     notice (68 FR 62640). Matters related to participation in any hearing are outside the scope of matters to be discussed at this public meeting.
                </P>
                <P>
                    At the conclusion of the scoping process, the NRC will prepare a concise summary of the determination and conclusions reached, including the significant issues identified, and will send a copy of the summary to each participant in the scoping process. The summary will also be available for inspection in ADAMS at 
                    <E T="03">http://www.nrc.gov/reading-rm/adams.html.</E>
                     The staff will then prepare and issue for comment the draft supplement to the GEIS, which will be the subject of separate notices and separate public meetings. Copies will be available for public inspection at the above-mentioned addresses, and one copy per request will be provided free of charge. After receipt and consideration of the comments, the NRC will prepare a final supplement to the GEIS, which will also be available for public inspection.
                </P>
                <P>Information about the proposed action, the supplement to the GEIS, and the scoping process may be obtained from Mr. Cushing at the aforementioned telephone number or e-mail address.</P>
                <SIG>
                    <DATED>Dated at Rockville, Maryland, this 26th day of November, 2003.</DATED>
                    <P>For the Nuclear Regulatory Commission.</P>
                    <NAME>Pao-Tsin Kuo,</NAME>
                    <TITLE>Program Director, License Renewal and Environmental Impacts Program, Division of Regulatory Improvement Programs, Office of Nuclear Reactor Regulation.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30247 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 7590-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <SUBJECT>Sunshine Act Meeting</SUBJECT>
                <P>Notice is hereby given, pursuant to the provisions of the Government in the Sunshine Act, Public Law 94-409, that the Securities and Exchange Commission will hold the following meeting during the week of December 8, 2003:</P>
                <EXTRACT>
                    <P>A closed meeting will be held on Tuesday, December 9, 2003 at 2 p.m.</P>
                </EXTRACT>
                <P>Commissioners, Counsel to the Commissioners, the Secretary to the Commission, and recording secretaries will attend the Closed Meeting. Certain staff members who have an interest in the matters may also be present.</P>
                <P>The General Counsel of the Commission, or his designee, has certified that, in his opinion, one or more of the exemptions set forth in 5 U.S.C. 552b(c) (5), (7), 9(B) and (10) and 17 CFR 200.402(a) (5), (7), (9)(ii) and (10), permit consideration of the scheduled matters at the Closed Meeting.</P>
                <P>Commissioner Atkins, as duty officer, voted to consider the items listed for the closed meeting in closed session.</P>
                <P>The subject matter of the Closed Meeting scheduled for Tuesday, December 9, 2003 will be:</P>
                <FP SOURCE="FP-1">Formal orders of investigation;</FP>
                <FP SOURCE="FP-1">Institution and settlement of administrative proceedings of an enforcement nature;</FP>
                <FP SOURCE="FP-1">Institution and settlement of injunctive actions;</FP>
                <FP SOURCE="FP-1">Litigation matters; and</FP>
                <FP SOURCE="FP-1">Adjudicatory matters.</FP>
                <P>At times, changes in Commission priorities require alterations in the scheduling of meeting items. For further information and to ascertain what, if any, matters have been added, deleted or postponed, please contact:</P>
                <P>The Office of the Secretary at (202) 942-7070.</P>
                <SIG>
                    <DATED>Dated: December 2, 2003.</DATED>
                    <NAME>Jonathan G. Katz,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30325 Filed 12-2-03; 4:18 pm]</FRDOC>
            <BILCOD>BILLING CODE 8010-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <PRTPAGE P="68127"/>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release No. 34-48855; File No. SR-BSE-2003-07]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; Order Granting Approval of Proposed Rule Change and Notice of Filing and Order Granting Accelerated Approval of Amendment No. 1 Thereto by the Boston Stock Exchange, Inc. To Amend Its Listed Securities Requirements Relating to the Mandatory Establishment of Independent Audit Committees for All Listed Issuers</SUBJECT>
                <DATE>December 1, 2003.</DATE>
                <HD SOURCE="HD1">I. Introduction</HD>
                <P>
                    On July 16, 2003, the Boston Stock Exchange, Inc. (“BSE” or “Exchange”) filed with the Securities and Exchange Commission (“Commission”), pursuant to section 19(b)(1) of the Securities Exchange Act of 1934 (“Act”) 
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     a proposed rule change to add new requirements concerning audit committees to its Listed Securities Requirements in Section 10 of Chapter XXVII of the Rules of the Board of Governors of the BSE (“BSE Rules”). The proposed rule change would require each issuer listed on the BSE to establish an independent audit committee and to comply with other specified standards relating to audit committees, as mandated by section 10A(m) of the Act 
                    <SU>3</SU>
                    <FTREF/>
                     and Rule 10A-3 thereunder.
                    <SU>4</SU>
                    <FTREF/>
                     The proposed rule change also includes certification, enforcement, and other compliance requirements, as well as a provision that sets forth the operative dates for the new requirements. The Exchange also committed to adopt additional listing policies and requirements pertaining to issuer corporate governance.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         15 U.S.C. 78j-1(m).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         17 CFR 240.10A-3.
                    </P>
                </FTNT>
                <P>
                    The proposed rule change was published for comment in the 
                    <E T="04">Federal Register</E>
                     on October 28, 2003.
                    <SU>5</SU>
                    <FTREF/>
                     The Commission received no comments on the proposal. On November 19, 2003, the BSE submitted an amendment to the proposed rule change.
                    <SU>6</SU>
                    <FTREF/>
                     This order approves the proposal, publishes notice of Amendment No. 1, and approves Amendment No. 1 on an accelerated basis.
                    <SU>7</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 48668 (October 21, 2003), 68 FR 61494 (“Notice”).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         
                        <E T="03">See</E>
                         letter from John Boese, Vice President, Legal and Compliance, BSE, to Nancy Sanow, Assistant Director, Division of Market Regulation, Commission, dated November 18, 2003 (“Amendment No. 1”). In Amendment No. 1, the BSE made minor, non-substantive changes to the text of the proposed rule and, with respect to investment companies, expanded the scope of the requirement that audit committees establish procedures for the confidential, anonymous submission of concerns regarding questionable accounting or auditing matters.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         Rule 10A-3 requires each national securities exchange and national securities association to have rules that comply with its requirements approved by the Commission no later than December 1, 2003. By the Commission approving the proposed rule change, the Exchange can comply with this deadline.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">II. Discussion</HD>
                <P>
                    After careful review, the Commission finds that the proposed rule change is consistent with the requirements of the Act and the rules and regulations thereunder applicable to a national securities exchange.
                    <SU>8</SU>
                    <FTREF/>
                     Specifically, the Commission finds that the proposal relating to independent audit committees for listed companies is consistent with section 6(b)(5) of the Act,
                    <SU>9</SU>
                    <FTREF/>
                     which requires, among other things, that the BSE's rules be designed to prevent fraudulent and manipulative acts and practices, and, in general, to protect investors and the public interest. Moreover, the Commission believes that the BSE's proposal to add the new requirements concerning audit committees is appropriate and consonant with section 10A(m) of the Act 
                    <SU>10</SU>
                    <FTREF/>
                     and Rule 10A-3 thereunder relating to audit committee standards for listed issuers. The Commission notes that the BSE intends to file an additional rule proposal relating to other corporate governance listing standards.
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         In approving this proposal, the Commission has considered the proposed rule's impact on efficiency, competition, and capital formation. 15 U.S.C. 78c(f).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         15 U.S.C. 78j-1(m).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         
                        <E T="03">See</E>
                         Notice at note .
                    </P>
                </FTNT>
                <P>
                    Furthermore, the Commission finds good cause, consistent with section 19(b)(2) of the Act,
                    <SU>12</SU>
                    <FTREF/>
                     to approve Amendment No. 1 to the proposed rule change prior to the thirtieth day after the date of publication of notice of filing thereof in the 
                    <E T="04">Federal Register</E>
                    . In Amendment No. 1, the BSE expanded, with respect to investment companies, the scope of the proposed provision regarding complaint procedures. Rule 10A-3 requires audit committees to establish procedures for “the confidential, anonymous submission by employees of the listed issuer of concerns regarding questionable accounting or auditing matters.”
                    <SU>13</SU>
                    <FTREF/>
                     The amended BSE proposal would require that audit committees of investment companies also establish procedures for the confidential, anonymous submission of such concerns by employees of the investment adviser, administrator, principal underwriter, or any other provider of accounting related services for the investment company, as well as employees of the investment company. This revision responds to a recommendation by the Commission that self-regulatory organizations take into account, in adopting rules to comply with Rule 10A-3, the fact that most services are rendered to an investment company by employees of third parties, such as the investment adviser, rather than by employees of the investment company.
                    <SU>14</SU>
                    <FTREF/>
                     In Amendment No. 1, the Exchange also made several technical revisions to the rule text. The Commission believes that it is appropriate to accelerate approval of this amendment, because it conforms the rule text to similar rules of the New York Stock Exchange, Inc. and the National Association of Securities Dealers, Inc. that were approved by the Commission,
                    <SU>15</SU>
                    <FTREF/>
                     and the amendment raises no new substantive issues.
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         15 U.S.C. 78s(b)(2).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>13</SU>
                         17 CFR 240.10A-3(b)(3)(ii).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>14</SU>
                         
                        <E T="03">See</E>
                         Securities Act Release No. 8220, Securities Exchange Act Release No. 47654, and Investment Company Act Release No. 26001 (April 9, 2003), 68 FR 18788 (April 16, 2003) (release adopting Rule 10A-3).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>15</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release Nos. 48745 (November 4, 2003), 68 FR 64154 (November 12, 2003) (approval of, among other proposals, File Nos. SR-NYSE-2002-33 and SR-NASD-2002-141).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">III. Solicitation of Comments</HD>
                <P>
                    Interested persons are invited to submit written data, views, and arguments concerning Amendment No. 1, including whether Amendment No. 1 is consistent with the Act. Persons making written submissions should file six copies thereof with the Secretary, Securities and Exchange Commission, 450 Fifth Street, NW., Washington, DC 20549-0609. Copies of the submission, all subsequent amendments, all written statements with respect to the proposed rule change that are filed with the Commission, and all written communications relating to the proposed rule change between the Commission and any person, other than those that may be withheld from the public in accordance with the provisions of 5 U.S.C. 552, will be available for inspection and copying in the Commission's Public Reference Room. Copies of such filings will also be available for inspection and copying at the principal office of the Exchange. All submissions should refer to File No. SR-BSE-2003-07 and should be submitted by December 26, 2003.
                    <PRTPAGE P="68128"/>
                </P>
                <HD SOURCE="HD1">IV. Conclusion</HD>
                <P>
                    <E T="03">It is therefore ordered,</E>
                     pursuant to section 19(b)(2) of the Act,
                    <SU>16</SU>
                    <FTREF/>
                     that Amendment No. 1 is approved on an accelerated basis, and that the proposed rule change (File No. SR-BSE-2003-07) be, and it hereby is, approved.
                </P>
                <FTNT>
                    <P>
                        <SU>16</SU>
                         15 U.S.C. 78s(b)(2).
                    </P>
                </FTNT>
                <SIG>
                    <P>
                        For the Commission, by the Division of Market Regulation, pursuant to delegated authority.
                        <SU>17</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>17</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Margaret H. McFarland,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30252 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8010-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[Release No. 34-48858; File No. SR-CBOE-2003-07]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; Order Approving Proposed Rule Change and Amendment No. 1 by the Chicago Board Options Exchange, Inc., Relating to the Trading of Ratio Orders</SUBJECT>
                <DATE>December 1, 2003.</DATE>
                <HD SOURCE="HD1">I. Introduction</HD>
                <P>
                    On February 24, 2003, the Chicago Board Options Exchange, Inc. (“CBOE” or “Exchange”) filed with the Securities and Exchange Commission (“Commission” or “SEC”), pursuant to section 19(b)(1) of the Securities Exchange Act of 1934 (“Act”) 
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     a proposed rule change to allow ratio orders to be executed through the CBOE. The CBOE filed Amendment No. 1 to the proposal on October 8, 2003.
                    <SU>3</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         letter from James M. Flynn, Attorney II, Legal Division, CBOE, to Yvonne Fraticelli, Division of Market Regulation, Commission, dated October 6, 2003 (“Amendment No. 1”). Amendment No. 1 revises the proposal to provide that the permissible ratio for a ratio order is any ratio that is equal to or greater than one-to-three (.333) and less than or equal to three-to-one (3.0).
                    </P>
                </FTNT>
                <P>
                    The proposed rule change and Amendment No. 1 were published for comment in the 
                    <E T="04">Federal Register</E>
                     on October 28, 2003.
                    <SU>4</SU>
                    <FTREF/>
                     The Commission received no comments regarding the proposal. This order approves the proposed rule change, as amended.
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 48672 (October 21, 2003), 68 FR 61499.
                    </P>
                </FTNT>
                <HD SOURCE="HD1">II. Description of the Proposal</HD>
                <P>
                    The CBOE proposes to amend CBOE Rule 6.53, “Certain Types of Orders Defined,” to allow ratio orders with certain permissible ratio limits, as defined below, to be executed through the CBOE. In addition, the CBOE proposes to revise paragraph (e) of CBOE Rule 6.45, “Priority of Bids and Offers—Allocation of Trades,” to include these types of permissible ratio orders in CBOE Rule 6.45(e), thereby providing such ratio orders with the exception to the priority rules that CBOE Rule 6.45(e) provides currently for spread, straddle, and combination orders.
                    <SU>5</SU>
                    <FTREF/>
                     The CBOE believes that because ratio orders are slight variations on the types of complex orders currently permitted on the CBOE, it is appropriate to treat ratio orders like spread, straddle, and combination orders for purposes of CBOE Rule 6.45(e).
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         CBOE Rule 6.45(e), “Complex Order Priority Exception,” currently states that: “A member holding a spread, straddle, or combination order (or a stock-option order as defined in Rule 1.1(ii)(b)) and bidding (offering) on a net debit or credit basis (in a multiple of the minimum increment) may execute the order with another member without giving priority to equivalent bids (offers) in the trading crowd or in the book provided at least one leg of the order betters the corresponding bid (offer) in the book. Stock-option orders, as defined in Rule 1.1(ii)(a), have priority over bids (offers) of the trading crowd but not over bids (offers) of public customers in the limit order book.”
                    </P>
                </FTNT>
                <P>CBOE Rule 6.53 lists and defines several types of orders that are executed through the CBOE including, among others, three types of complex orders: spread orders, combination orders, and straddle orders. The CBOE proposes to add certain ratio orders within permissible established limits to the list of orders included in CBOE Rule 6.53. CBOE Rule 6.53(n) would define a ratio order as either a spread, straddle, or combination order in which the stated number of option contracts to buy (sell) is not equal to the stated number of option contracts to sell (buy), provided that the number of contracts differs by a permissible ratio. Under CBOE Rule 6.53(n), a permissible ratio would be any ratio that is equal to or greater than one-to-three (.333) or less than or equal to three-to-one (3.0). For example, a one-to-two (.5) ratio, a two-to-three (.667) ratio, or a two-to-one (2.0) ratio is permissible, whereas a one-to-four (.25) ratio or a four-to-one (4.0) ratio is not.</P>
                <HD SOURCE="HD1">III. Discussion</HD>
                <P>
                    The Commission finds that the proposed rule change is consistent with the requirements of the Act and the rules and regulations thereunder applicable to a national securities exchange 
                    <SU>6</SU>
                    <FTREF/>
                     and, in particular, with the requirements of section 6(b)(5) of the Act,
                    <SU>7</SU>
                    <FTREF/>
                     which requires, among other things, that the rules of a national securities exchange be designed to promote just and equitable principles of trade, to remove impediments to and perfect the mechanism of a free and open market and a national market system, and to protect investors and the public interest.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         In approving this proposal, the Commission has considered the proposed rule's impact on efficiency, competition, and capital formation. 15 U.S.C. 78c(f).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         15 U.S.C. 78f(b)(5).
                    </P>
                </FTNT>
                <P>
                    The proposal will allow certain ratio orders to be executed through the CBOE. As described above, a ratio order is a spread, straddle, or combination order in which the stated number of option contracts to buy (sell) is not equal to the stated number of option contracts to sell (buy), provided that the number of contracts differs by a permissible ratio.
                    <SU>8</SU>
                    <FTREF/>
                     The Commission believes that ratio orders within certain permissible ratios may provide market participants with greater flexibility and precision in effectuating trading and hedging strategies. In addition, the Commission believes that including such ratio orders in the exception to the priority rules provided in CBOE Rule 6.45(e) will facilitate the execution of ratio orders. In this regard, the Commission believes that the procedures governing the execution of complex orders, such as ratio orders, serve to reduce the risk of incomplete or inadequate executions while increasing efficiency and competitive pricing by requiring price improvement before the order can receive priority over other orders.
                    <SU>9</SU>
                    <FTREF/>
                     The Commission also notes that the rules of other options exchanges treat certain ratio orders like other complex orders for purposes of their priority rules.
                    <SU>10</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         Under the proposal, a permissible ratio is any ratio that is equal to or greater than one-to-three (.333) or less than or equal to three-to-one (3.0).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>9</SU>
                         
                        <E T="03">See, e.g.</E>
                        , CBOE Rule 6.45(e). 
                        <E T="03">See also</E>
                         Securities Exchange Act Release No. 44955 (October 18, 2001), 66 FR 53819 (October 24, 2001) (order approving File No. SR-ISE-2001-18).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>10</SU>
                         
                        <E T="03">See, e.g.</E>
                        , ISE rule 722(b)(2), “Complex Order Priority,” and PHLX Rule 1033(g), “Ratio Spread Type Priority.”
                    </P>
                </FTNT>
                <P>The CBOE's rule also provides specific examples of permissible ratio orders. Specifically, the rule provides that a permissible ratio is any ratio that is equal to or greater than one-to-three and less than or equal to three-to-one. For example, as indicated in the rule, a one-to-two ratio, a two-to-three ratio, or a two-to-one ratio is permissible, whereas a one-to-four ratio or a four-to-one ratio is not. This should help to provide guidance to CBOE members of the permissible ratios allowed under CBOE rules for such ratio orders.</P>
                <P>
                    The Commission believes that permitting ratio orders to have ratios equal to or greater than one-to-three or 
                    <PRTPAGE P="68129"/>
                    less than or equal to three-to-one will help market participants to tailor their positions more precisely to implement their trading and hedging strategies. Because of concerns that a higher ratio could provide market participants with a means to enter a ratio order that was designed primarily to gain priority over orders on the limit order book or in the trading crowd, rather than to effectuate a bona fide trading or hedging strategy, the Commission would need to examine closely any proposal to provide a higher ratio for ratio orders and would be concerned about whether such a proposal would be consistent with investor protection and the public interest under the Act.
                    <SU>11</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>11</SU>
                         In this regard, the Commission notes that one exchange stated that a proposed three-to-one cap on the ratio for foreign currency option orders “would prevent a trader seeking priority over an order on the book or in the crowd from restating an order as a ratio order. For example, such a cap would prevent a trader from recasting an order to buy 100 calls and sell one out-of-the-money put.” 
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 25503 (March 23, 1988), 53 FR 10323 (March 30, 1988) (order approving File No. SR-PHLX-87-33).
                    </P>
                </FTNT>
                <HD SOURCE="HD1">IV. Conclusion</HD>
                <P>
                    <E T="03">It is therefore ordered,</E>
                     pursuant to section 19(b)(2) of the Act,
                    <SU>12</SU>
                    <FTREF/>
                     that the proposed rule change (SR-CBOE-2003-07), as amended, is approved.
                </P>
                <FTNT>
                    <P>
                        <SU>12</SU>
                         15 U.S.C. 78s(b)(2).
                    </P>
                </FTNT>
                <SIG>
                    <P>
                        For the Commission, by the Division of Market Regulation, pursuant to delegated authority.
                        <SU>13</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>13</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Margaret H. McFarland,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30250 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8010-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                <DEPDOC>[(Release No. 34-48854; File No. SR-NASD-2003-135)]</DEPDOC>
                <SUBJECT>Self-Regulatory Organizations; Order Approving Proposed Rule Change and Amendment No. 1 Thereto by the National Association of Securities Dealers, Inc. To Aggregate Odd-Lot Amounts for Display in SuperMontage Under Certain Circumstances</SUBJECT>
                <DATE>November 28, 2003.</DATE>
                <P>
                    On August 28, 2003, the National Association of Securities Dealers, Inc. (“NASD”), through its subsidiary, The Nasdaq Stock Market, Inc. (“Nasdaq”) submitted to the Securities and Exchange Commission (“Commission”), pursuant to section 19(b)(1) of the Securities Exchange Act of 1934 (“Act”),
                    <SU>1</SU>
                    <FTREF/>
                     and Rule 19b-4 thereunder,
                    <SU>2</SU>
                    <FTREF/>
                     a proposed rule change to aggregate odd-lot share amounts inside the inside spread for display purposes via the SIZE MMID. On October 20, 2003, Nasdaq filed Amendment No. 1 to the proposed rule change.
                    <SU>3</SU>
                    <FTREF/>
                     The 
                    <E T="04">Federal Register</E>
                     published the proposed rule change, as amended, for comment on October 28, 2003.
                    <SU>4</SU>
                    <FTREF/>
                     The Commission received no comments on the proposal.
                </P>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         15 U.S.C. 78s(b)(1).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>2</SU>
                         17 CFR 240.19b-4.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>3</SU>
                         
                        <E T="03">See</E>
                         letter from Mary M. Dunbar, Vice President and Deputy General Counsel, Nasdaq, to Katherine A. England, Assistant Director, Division of Market Regulation, Commission, dated October 17, 2003 (“Amendment No. 1”). Amendment No. 1 replaced and superseded the original proposed rule change in its entirety.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See</E>
                         Securities Exchange Act Release No. 48671 (October 21, 2003), 68 FR 61531.
                    </P>
                </FTNT>
                <P>
                    The Commission finds that the proposed rule change, as amended, is consistent with the requirements of the Act and the rules and regulations thereunder applicable to a national securities association 
                    <SU>5</SU>
                    <FTREF/>
                     and, in particular, the requirements of section 15A of the Act 
                    <SU>6</SU>
                    <FTREF/>
                     and the rules and regulations thereunder. The Commission notes that the proposed rule change, as amended, permits Nasdaq to aggregate odd-lots for display purposes that better the Nasdaq inside market and that combined equal or are larger than one round lot, thus increasing transparency and providing investors with greater price information. Therefore, the Commission finds the proposed rule change is designed to promote just and equitable principles of trade, to remove impediments to and perfect the mechanism of a free and open market and a national market system, and, in general, to protect investors and the public interest, consistent with section 15A(b)(6) of the Act.
                    <SU>7</SU>
                    <FTREF/>
                     As proposed by Nasdaq, the proposed rule change will be effective on December 8, 2003.
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         In approving this proposed rule change, the Commission notes that it has considered the proposed rule's impact on efficiency, competition, and capital formation. 15 U.S.C. 78c(f).
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         15 U.S.C. 78
                        <E T="03">o</E>
                        -3.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         15 U.S.C. 78
                        <E T="03">o</E>
                        -3(b)(6).
                    </P>
                </FTNT>
                <P>
                    <E T="03">It is therefore ordered,</E>
                     pursuant to section 19(b)(2) of the Act,
                    <SU>8</SU>
                    <FTREF/>
                     that the proposed rule change, as amended, (SR-NASD-2003-135) be, and it hereby is, approved.
                </P>
                <FTNT>
                    <P>
                        <SU>8</SU>
                         15 U.S.C. 78s(b)(2).
                    </P>
                </FTNT>
                <SIG>
                    <P>
                        For the Commission, by the Division of Market Regulation, pursuant to delegated authority.
                        <SU>9</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>9</SU>
                             17 CFR 200.30-3(a)(12).
                        </P>
                    </FTNT>
                    <NAME>Margaret H. McFarland,</NAME>
                    <TITLE>Deputy Secretary.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30251 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8010-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">SMALL BUSINESS ADMINISTRATION</AGENCY>
                <SUBJECT>Region IX Regulatory Fairness Board; Public Federal Regulatory Enforcement Fairness Roundtable</SUBJECT>
                <P>The Small Business Administration Region IX Regulatory Fairness Board and the SBA Office of the National Ombudsman will hold a Public Roundtable on Thursday, December 4, 2003 at 1 p.m. at the SETA Headquarters, Board Room, 925 Del Paso Boulevard, Sacramento, CA 95815, to provide small business owners and representatives of trade associations with an opportunity to share information concerning the federal regulatory enforcement and compliance environment.</P>
                <P>
                    Anyone wishing to attend or to make a presentation must contact Robert Stitt in writing or by fax, in order to be put on the agenda. Robert Stitt, SBA Sacramento District Office, 650 Capital Mall, Suite 7-500, Sacramento, CA 95814, phone (916) 930-3722, fax (916) 930-3736 or (202) 481-5298, e-mail: 
                    <E T="03">Robert.Stitt@sba.gov.</E>
                </P>
                <SIG>
                    <P>
                        For more information, see our Web site at 
                        <E T="03">http://www.sba.gov/ombudsman.</E>
                    </P>
                    <DATED>Dated: December 1, 2003.</DATED>
                    <NAME>Peter Sorum,</NAME>
                    <TITLE>National Ombudsman (Acting).</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30209 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8025-01-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF STATE</AGENCY>
                <DEPDOC>[Public Notice 4549]</DEPDOC>
                <SUBJECT>60-Day Notice of Proposed Information Collection: DS-2028 Overseas Schools—Grant Status Report; OMB Control Number 1405-0033</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of State.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Department of State is seeking Office of Management and Budget (OMB) approval for the information collection described below. The purpose of this notice is to allow 60 days for public comment in the 
                        <E T="04">Federal Register</E>
                         preceding submission to OMB. This process is conducted in accordance 
                        <PRTPAGE P="68130"/>
                        with the Paperwork Reduction Act of 1995.
                    </P>
                    <P>The following summarizes the information collection proposal to be submitted to OMB:</P>
                    <P>
                        <E T="03">Type of Request:</E>
                         An extension of a currently approved collection.
                    </P>
                    <P>
                        <E T="03">Originating Office:</E>
                         A/OPR/OS.
                    </P>
                    <P>
                        <E T="03">Title of Information Collection:</E>
                         Overseas Schools “ Grant Status Report.
                    </P>
                    <P>
                        <E T="03">Frequency:</E>
                         Annually.
                    </P>
                    <P>
                        <E T="03">Form Number:</E>
                         DS-2028.
                    </P>
                    <P>
                        <E T="03">Respondents:</E>
                         Overseas school grantees.
                    </P>
                    <P>
                        <E T="03">Estimated Number of Respondents:</E>
                         185.
                    </P>
                    <P>
                        <E T="03">Average Hours Per Response:</E>
                         15 minutes.
                    </P>
                    <P>
                        <E T="03">Total Estimated Burden:</E>
                         46.25.
                    </P>
                    <P>Public comments are being solicited to permit the agency to:</P>
                    <P>• Evaluate whether the proposed information collection is necessary for the proper performance of the functions of the agency.</P>
                    <P>• Evaluate the accuracy of the agency's estimate of the burden of the proposed collection, including the validity of the methodology and assumptions used.</P>
                    <P>• Enhance the quality, utility, and clarity of the information to be collected.</P>
                    <P>• Minimize the reporting burden on those who are to respond, including through the use of automated collection techniques or other forms of technology.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Public comments, or requests for additional information, regarding the collection listed in this notice should be directed to Keith D. Miller, Department of State, Office of Overseas Schools, Room H328 SA-1, Washington, DC 20522-0132 who may be reached on 202-261-8200.</P>
                    <SIG>
                        <DATED>Dated: December 1, 2003.</DATED>
                        <NAME>Peggy M. Philbin,</NAME>
                        <TITLE>Executive Director, Bureau of Administration, Department of State.</TITLE>
                    </SIG>
                </FURINF>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30275 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4710-24-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>National Highway Traffic Safety Administration</SUBAGY>
                <DEPDOC>[Docket No. NHTSA-2003-16356]</DEPDOC>
                <SUBJECT>Extension of Comment Period on Whether Nonconforming 2002 and 2003 Ferrari 575 Passenger Cars Are Eligible for Importation</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>National Highway Traffic Safety Administration (NHTSA), DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Extension of comment period.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>This document announces the extension of the comment period on a petition for NHTSA to decide that 2002 and 2003 Ferrari 575 passenger cars that were not originally manufactured to comply with all applicable Federal motor vehicle safety standards are eligible for importation into the United States.</P>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>The closing date for comments on the petition is December 12, 2003.</P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Comments are to be submitted to: Docket Management, Room PL-401, 400 Seventh Street SW., Washington, DC 20590. Docket hours are from 9 am to 5 pm. Anyone is able to search the electronic form of all comments received into any of our dockets by the name of the individual submitting the document (or signing the comment, if submitted on behalf of an association, business, labor union, etc.). You may review DOT's complete Privacy Act Statement in the 
                        <E T="04">Federal Register</E>
                         published on April 11, 2000 (Volume 65, Number 70; Pages 19477-787) or you may visit 
                        <E T="03">http://dms.dot.gov</E>
                        .
                    </P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Coleman Sachs, Office of Vehicle Safety Compliance, NHTSA (202) 366-3151.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>On October 28, 2003, NHTSA published a notice (at 68 FR 61549) that it had received a petition to decide that nonconforming 2002 and 2003 Ferrari 575 passenger cars are eligible for importation into the United States. The notice solicited public comments on the petition and stated that the closing date for comments is November 28, 2003.</P>
                <P>This is to notify the public that NHTSA is extending the comment period until December 12, 2003. This extension is based on a request from Ferrari North America, Inc. (FNA), the U.S. representative of the vehicle's manufacturer, Ferrari, SpA. In requesting the extension, FNA that “the employee of Ferrari SpA who has, among other duties, principal responsibility for technical analysis of importation eligibility petitions has been traveling on company business and therefore has not yet provided FNA with the information needed by FNA to prepare comments in the proceeding.” FNA contended that the requested 2-week extension of the comment period “will not prejudice the parties or unduly delay the proceeding.”</P>
                <P>
                    NHTSA has granted FNA's request. All comments received before the close of business on the closing date indicated above will be considered, and will be available for examination in the docket at the above address both before and after that date. To the extent possible, comments filed after the closing date will also be considered. Notice of final action on the petition will be published in the 
                    <E T="04">Federal Register</E>
                     pursuant to the authority indicated below.
                </P>
                <AUTH>
                    <HD SOURCE="HED">Authority:</HD>
                    <P>49 U.S.C. 30141(a)(1)(A) and (b)(1); 49 CFR 593.8; delegations of authority at 49 CFR 1.50 and 501.8.</P>
                </AUTH>
                <SIG>
                    <DATED>Issued on: December 2, 2003.</DATED>
                    <NAME>Kenneth N. Weinstein,</NAME>
                    <TITLE>Associate Administrator for Enforcement.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30279 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4910-59-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF TRANSPORTATION</AGENCY>
                <SUBAGY>Surface Transportation Board</SUBAGY>
                <DEPDOC>[STB Finance Docket No. 34424]</DEPDOC>
                <SUBJECT>Canadian National Railway Company and Grand Trunk Corporation—Control—Duluth, Missabe and Iron Range Railway Company, Bessemer and Lake Erie Railroad Company, and The Pittsburgh &amp; Conneaut Dock Company</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Surface Transportation Board, DOT.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>
                        Decision No. 2 in STB Finance Docket No. 34424; Notice of Acceptance of Primary Application and Related Filings; Issuance of Procedural Schedule.
                        <SU>1</SU>
                        <FTREF/>
                    </P>
                </ACT>
                <FTNT>
                    <P>
                        <SU>1</SU>
                         This decision covers: the railroad control application filed in STB Finance Docket No. 34424, 
                        <E T="03">Canadian National Railway Company and Grand Trunk Corporation—Control—Duluth, Missabe and Iron Range Railway Company, Bessemer and Lake Erie Railroad Company, and The Pittsburgh &amp; Conneaut Dock Company;</E>
                         the trackage rights exemption notice filed in STB Finance Docket No. 34424 (Sub-No. 1), 
                        <E T="03">Duluth, Winnipeg and Pacific Railway Company—Trackage Rights—Duluth, Missabe and Iron Range Railway Company;</E>
                         and the trackage rights exemption notice filed in STB Finance Docket No. 34424 (Sub-No. 2), 
                        <E T="03">Duluth, Missabe and Iron Range Railway Company—Trackage Rights—Duluth, Winnipeg and Pacific Railway Company.</E>
                         The railroad control application filed in STB Finance Docket No. 34424 is referred to as the “primary application.” The trackage rights exemption notices filed in STB Finance Docket No. 34424 (Sub-Nos. 1 and 2) are referred to collectively as the “related filings.”
                    </P>
                </FTNT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>
                        The Surface Transportation Board (Board) is accepting for consideration the primary application and related filings filed November 5, 2003, by Canadian National Railway Company (CNR, a rail carrier that controls several rail carrier subsidiaries) and Grand Trunk Corporation (GTC, a noncarrier holding company through which CNR controls its U.S. rail carrier subsidiaries). CNR and GTC are referred to collectively as CN or as applicants. The primary application seeks Board approval and authorization under 49 
                        <PRTPAGE P="68131"/>
                        U.S.C. 11321-26 for the acquisition by CN of control of three U.S. railroads: Duluth, Missabe and Iron Range Railway Company (DMIR), Bessemer and Lake Erie Railroad Company (B&amp;LE), and the Pittsburgh &amp; Conneaut Dock Company (P&amp;C Dock). Because DMIR, B&amp;LE, and P&amp;C Dock are now controlled by Great Lakes Transportation LLC (GLT), the primary application is referred to as the “CN/GLT Application,” the transaction proposed in the primary application is referred to as the “CN/GLT Transaction” or the Transaction, and DMIR, B&amp;LE, and P&amp;C Dock are referred to collectively as the “GLT Railroads.” The related filings seek related trackage rights contingent upon approval of the primary application. The Board finds that the transaction proposed in the primary application is a “minor transaction” under 49 CFR 1180.2(c).
                    </P>
                    <P>
                        The Board has considered CN's petition suggesting a 146-day procedural schedule, also filed November 5, 2003. The Board is adopting a 156-day procedural schedule patterned upon the 156-day procedural schedule that was adopted earlier this year in the “KCS/Tex Mex” proceeding.
                        <SU>2</SU>
                        <FTREF/>
                         The 156-day procedural schedule adopted by the Board is essentially the same as the 146-day procedural schedule suggested by CN, except that the Board's schedule adds five days to the “evidentiary proceeding” stage and another five days to the “final decision” stage. The 156-day procedural schedule will allow the Board to issue a decision 45 days after the close of the record and 24 days prior to the statutory deadline, assuming that no unanticipated environmental review is required.
                    </P>
                    <FTNT>
                        <P>
                            <SU>2</SU>
                             
                            <E T="03">See Kansas City Southern—Control—The Kansas City Southern Railway Company, Gateway Eastern Railway Company, and The Texas Mexican Railway Company,</E>
                             STB Finance Docket No. 34342, Decision No. 2 (STB served June 9, 2003, and published at 68 FR 35474 on June 13, 2003).
                        </P>
                    </FTNT>
                </SUM>
                <DATES>
                    <HD SOURCE="HED">DATES:</HD>
                    <P>
                        The effective date of this decision is December 5, 2003. Comments on CN's Environmental Appendix (submitted November 5, 2003, and supplemented November 10, 2003) are due by December 10, 2003. CN must submit its Safety Integration Plan (SIP) by December 15, 2003. Any person who wishes to participate in this proceeding as a party of record (POR) must file, no later than December 19, 2003, a notice of intent to participate. Comments on CN's SIP must be filed by January 22, 2004. All comments, protests, requests for conditions, and any other evidence and argument in opposition to the primary application and/or either or both of the related filings, including filings by the U.S. Department of Justice (DOJ) and the U.S. Department of Transportation (DOT), must be filed by January 26, 2004. Responses to comments, protests, requests for conditions, and other opposition, responses to comments of DOJ and DOT, and rebuttal in support of the primary application and/or either or both of the related filings must be filed by February 24, 2004. A public hearing/oral argument will be held the week of March 1, 2004 (the precise date and the location will be announced later). For further information respecting dates, 
                        <E T="03">see</E>
                         Appendix A (Procedural Schedule).
                    </P>
                </DATES>
                <ADD>
                    <HD SOURCE="HED">ADDRESSES:</HD>
                    <P>
                        Send an original and 20 copies of all pleadings (except for environmental submissions, as discussed below) referring to STB Finance Docket No. 34424 to: Surface Transportation Board, 1925 K Street, NW., Washington, DC 20423-0001.
                        <SU>3</SU>
                        <FTREF/>
                         In addition, one copy of all documents in this proceeding must be sent to each of the following: (1) Secretary of the United States Department of Transportation, 400 Seventh Street, SW., Washington, DC 20590; (2) Attorney General of the United States, c/o Assistant Attorney General, Antitrust Division, Room 3645, Department of Justice, Washington, DC 20530; and (3) Paul A. Cunningham, Esq., Harkins Cunningham LLP, 801 Pennsylvania Avenue, NW., Suite 600, Washington, DC 20004-2664.
                    </P>
                    <FTNT>
                        <P>
                            <SU>3</SU>
                             For a document to be considered a formal filing, the Board must receive an original and 20 copies of the document, which must show that it has been properly served upon all Parties of Record. Documents transmitted by facsimile (Fax) will not be considered formal filings and are not encouraged because they would result in unnecessarily burdensome, duplicative processing. In addition, each formal filing must be accompanied by an electronic submission per the Board's requirements as discussed in detail in this decision.
                        </P>
                    </FTNT>
                    <P>In addition to submitting an original and 20 copies of all paper documents filed with the Board, parties must also submit, on 3.5-inch IBM-compatible floppy diskettes (disks) or compact discs (CDs), copies of all textual materials, electronic workpapers, data bases, and spreadsheets used to develop quantitative evidence. Textual materials must be in, or compatible with, WordPerfect 10.0. Electronic spreadsheets must be in, or compatible with, Lotus 1-2-3 Release 9 or Microsoft Excel 2002. A copy of each disk or CD submitted to the Board should be provided to any other party upon request. Further details are discussed below.</P>
                    <P>Comments (an original and 10 copies) on the Environmental Appendix and SIP should be submitted in writing to: Attn: Phillis Johnson-Ball, STB Finance Docket No. 34424, Surface Transportation Board, 1925 K Street, NW., Washington, DC 20423-0001.</P>
                </ADD>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Julia M. Farr, (202) 565-1655. (Assistance for the hearing impaired is available through the Federal Information Relay Service (FIRS) at 1-800-877-8339.)</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    The CN/GLT Transaction proposed in the primary application contemplates the acquisition, by CN, of control of four carriers—the three GLT Railroads (DMIR, B&amp;LE, and P&amp;C Dock) and an affiliated water carrier (Great Lakes Fleet, Inc., referred to as GLF)—which now operate an integrated iron ore delivery chain that extends from ore mines in Minnesota to steel plants in Pennsylvania. The three GLT Railroads (DMIR, B&amp;LE, and P&amp;C Dock) and the affiliated GLT water carrier (GLF) are referred to collectively as the “GLT Carriers.” The proposed acquisition, by CN, of control of DMIR, B&amp;LE, and P&amp;C Dock is subject to the jurisdiction of the Board; the related acquisition, by CN, of control of GLF is not subject to the jurisdiction of the Board. 
                    <E T="03">See</E>
                     49 U.S.C. 11323 (the Board's “control jurisdiction” extends only to transactions involving rail carriers). The related acquisition, by CN, of control of GLF is, however, subject to review by the U.S. Maritime Administration and the Coast Guard, and is also subject to review under the Hart-Scott-Rodino Antitrust Improvements Act of 1976.
                </P>
                <P>
                    <E T="03">Canadian National.</E>
                     As of September 30, 2003, CN's rail network, which crosses North America from east to west and from north to south, serving major ports on three coasts, consisting of 17,539 route miles in 15 American states and eight Canadian provinces. CN's principal routes run: (1) Between Vancouver and Prince Rupert, BC, in the west, and Halifax, NS, in the east, serving every major metropolitan area in Canada; (2) between Chicago, IL, and Buffalo, NY, serving three major metropolitan areas (Chicago, IL, Detroit, MI, and Buffalo, NY) in the U.S.; (3) between Winnipeg, MB, and Chicago, IL; (4) between Chicago and the Gulf of Mexico, reaching every major metropolitan area on the Mississippi River (including St. Louis, MO, Memphis, TN, and New Orleans, LA); and (5) between Nebraska/Iowa and Chicago, extending from Sioux City and Council Bluffs, IA, in the west, to Chicago in the east. CN's U.S. operations are conducted by CNR and, through CNR's GTC subsidiary, by 10 U.S. railroads that are part of the CN system: Duluth, Winnipeg and Pacific 
                    <PRTPAGE P="68132"/>
                    Railway Company (DWP), Grand Trunk Western Railroad Incorporated (GTW), St. Clair Tunnel Company (SCTC), Illinois Central Railroad Company (IC), Chicago, Central &amp; Pacific Railroad Company (CCP), Cedar River Railroad Company (CRRC), Waterloo Railway Company (WRC), Wisconsin Central Ltd. (WCL), Sault Ste. Marie Bridge Company (SSMB), and Wisconsin Chicago Link Ltd. (WCLL).
                </P>
                <P>In 1999, CN acquired IC to position itself to better serve north-south “NAFTA” traffic by extending its system from Chicago to the Gulf Coast. As a result of the 1999 CN/IC transaction and CN's 1998 marketing alliance with The Kansas City Southern Railway Company (KCS), CN is today part of a NAFTA rail network offering shippers access to TFM, S.A. de C.V. (TFM), Mexico's largest rail system. In 2001, CN acquired WCL and its affiliates, thus providing CN with a connection between Chicago and the CN lines west of the Great Lakes. This connection is completely under CN ownership, with the exception of the 17-mile segment between Nopeming Junction, MN, and South Itasca, WI, over which CN's DWP subsidiary operates by means of trackage rights granted by DMIR.</P>
                <P>
                    <E T="03">The GLT Carriers.</E>
                     DMIR, a Class II railroad that owns 212 miles of rail line in Minnesota and Wisconsin, carries primarily: (1) Taconite pellets (a form of processed iron ore) from taconite plants in the Mesabi Range (a) to DMIR-owned docks on Lake Superior at Duluth, MN, and Two Harbors, MN (for loading onto vessels for movement to steel plants), and (b) to interchange points with other railroads; and (2) limestone from the dock at Duluth to Mesabi Range taconite plants. DMIR's Missabe Main Line runs 74 miles in a generally north-south direction between Mountain Iron, MN, and Duluth, MN. Its Iron Range Main Line runs 74 miles in a generally east-west direction between Iron Junction, MN (where the Missabe Main Line and the Iron Range Main Line intersect) and Two Harbors, MN. DMIR also operates 64 miles of branch lines. Among these branch lines are the Shaw Cut Off/Superior Branch, which runs 16 miles eastward from Emmert, MN, to Keenan, MN, where it meets the Missabe Main Line; the Taconite District, which runs 4.5 miles to the west of Calumet, MN (the Taconite District is not contiguous with any other DMIR line); and the Interstate Branch/Spirit Lake Branch, which runs from Adolph, MN (on the Missabe Main Line), 23 miles in a generally southward and eastward direction through Nopeming Junction, MN, to South Itasca, WI (near Superior, WI), where DMIR's property ends. DMIR's lines between Virginia, MN (in the north), and Duluth, MN, and South Itasca, WI (in the south), are generally parallel to CN's lines between Virginia and South Itasca, and, for the southernmost 17 miles of that corridor (
                    <E T="03">i.e.</E>
                    , the 17-mile segment from Nopeming Junction, MN, to South Itasca, WI), CN and DMIR operate over the same track, pursuant to trackage rights granted by DMIR to CN's DWP subsidiary. DMIR itself operates via trackage rights over 10 miles of CN track between Shelton, MN, and Minorca Junction, MN, and over 19 miles of track of the Burlington Northern and Santa Fe Railway Company (BNSF) between Calumet, MN, and Emmert, MN (the Calumet-Emmert trackage rights enable DMIR to access its Taconite District).
                </P>
                <P>B&amp;LE, a Class II railroad operating between North Bessemer, PA (near Pittsburgh, PA), and the port at Conneaut, OH (on Lake Erie), carries principally coal, iron ore, and limestone. B&amp;LE's main line runs between North Bessemer and Albion, PA, and its two northernmost branch lines run between Albion, PA, on the one hand, and, on the other hand, Conneaut, OH, and Wallace Junction, PA.</P>
                <P>P&amp;C Dock, a Class III railroad, does not own or operate any rail routes, but performs switching operations and ship-to-rail and rail-to-ship bulk transfer operations for B&amp;LE at three docks at Conneaut, OH.</P>
                <P>GLF is a water carrier (not a rail carrier) that owns a fleet of vessels that carry ore and other bulk commodities on the Great Lakes.</P>
                <P>DMIR, B&amp;LE, P&amp;C Dock, and GLF are wholly owned subsidiaries of DMIR Holdings Corp. (DMIR Holdings), B&amp;LE Holdings Corp. (B&amp;LE Holdings), P&amp;CD Holdings Corp. (P&amp;CD Holdings), and GLF Holdings Corp. (GLF Holdings), respectively. DMIR Holdings, B&amp;LE Holdings, P&amp;CD Holdings, and GLF Holdings are noncarriers, and each is a wholly owned subsidiary of Great Lakes Transportation LLC (GLT). GLT is owned by Great Lakes Transportation Holdings, L.P., which is an affiliate of The Blackstone Group.</P>
                <P>
                    <E T="03">The CN/GLT Transaction.</E>
                     GTC and GLT have entered into a Stock Purchase Agreement (the CN/GLT Agreement), dated October 19, 2003, that provides that, subject to a number of conditions, GTC will purchase from GLT all of the issued and outstanding shares of DMIR Holdings, B&amp;LE Holdings, P&amp;CD Holdings, and GLF Holdings for an overall purchase price of $380 million, subject to certain adjustments provided for in the CN/GLT Agreement. CN advises that, if the CN/GLT Transaction is approved, it intends to pay the purchase price in cash on the closing date under the CN/GLT Agreement (CN expects to meet the cash requirements for consummation of the Transaction by borrowing under its existing revolving credit facility, combined with long-term debt), and it intends to consummate control of the GLT Railroads as soon as possible after a final order of the Board approving the primary application and authorizing the Transaction has become effective. CN further advises that, because it plans few operational changes in connection with the CN/GLT Transaction, it expects to fully implement that Transaction shortly after consummation of CN control of the GLT Railroads. CN adds that, although it does not anticipate any increases in total traffic and revenue handled by CN and the GLT Railroads as a result of the CN/GLT Transaction, it does anticipate that the Transaction would lead to more efficient operations and permit efficiency-related cost reductions. CN advises that it has no present plans to merge DMIR Holdings, B&amp;LE Holdings, or P&amp;CD Holdings into any other entity in the CN system, or to merge any of the GLT Railroads with any of CN's other subsidiaries.
                </P>
                <P>
                    <E T="03">Related Filings.</E>
                     DWP and DMIR operate two separate rail lines that run between Shelton Junction, MN (near Virginia, MN), and Nopeming Junction, MN (near Superior, WI). The related filings, which were made pursuant to 49 CFR 1180.2(d)(7), involve reciprocal grants of trackage rights that would allow each of DWP and DMIR to operate its trains, locomotives, cars, and equipment, with its own crews, over the other's essentially parallel line between Shelton Junction and Nopeming Junction. In STB Finance Docket No. 34424 (Sub-No. 1), DWP has filed a notice of exemption relating to trackage rights to be granted to DWP over DMIR's lines between Shelton Junction (Mileage B 2.71 on DMIR's Virginia Branch) and Nopeming Junction (Mileage R 5.77 on DMIR's Spirit Lake Branch), a distance of approximately 64 miles. In STB Finance Docket No. 34424 (Sub-No. 2), DMIR has filed a notice of exemption relating to trackage rights to be granted to DMIR over DWP's lines between Shelton Junction (MP 70.7 on DWP's Rainy Subdivision) and Nopeming Junction (MP 10.7 on DWP's Rainy Subdivision), a distance of approximately 60 miles. The reciprocal trackage rights provided for in the notices of exemption filed in STB Finance Docket No. 34424 (Sub-Nos. 1 and 2) are intended to be effective upon 
                    <PRTPAGE P="68133"/>
                    acquisition by CN of control of DMIR, and, therefore, are contingent upon approval of the primary application.
                </P>
                <P>
                    <E T="03">CN/GLT Common Control: Purposes Served.</E>
                     CN contends that its acquisition of control of the GLT Railroads would serve three primary purposes.
                </P>
                <P>First, acquisition of control of DMIR would give CN full ownership of the route over which all CN traffic between Winnipeg and Chicago now moves. CN notes that, at present, it must operate by means of trackage rights granted by DMIR over the 17-mile segment between Nopeming Junction and South Itasca.</P>
                <P>Second, CN contends that acquisition of control of DMIR would increase CN's operational flexibility by allowing CN to institute “directional running” on the two parallel Shelton Junction-Nopeming Junction lines, which would reduce transit time and increase service reliability over CN's entire Winnipeg-Chicago corridor. CN adds that, because DMIR's Shelton Junction-Nopeming Junction line has newer ties and newer and heavier rail than DWP's Shelton Junction-Nopeming Junction line, the transfer to the DMIR line of some traffic that now uses the DWP line would allow CN to avoid the capital expenditures that would otherwise be required for centralized traffic control (CTC) and extensions of sidings on the DWP line.</P>
                <P>Third, CN contends that acquisition of control of the four GLT Carriers (DMIR, B&amp;LE, P&amp;C Dock, and GLF), which provide an important supply line for the North American steel industry, would enable CN to develop closer and more extensive relationships with companies in and serving that industry.</P>
                <P>
                    <E T="03">CN/GLT Common Control: Public Interest Considerations.</E>
                     CN contends that the CN/GLT Transaction would benefit the public interest by connecting two transportation systems that do not compete with each other but, rather, complement each other. The CN/GLT Transaction, CN argues, would strengthen the GLT Railroads by making them part of the rail system operated by CN, a successful rail carrier that would have the commitment and ability to make long-term investments in plant, equipment, and systems as they become needed. CN contends that the CN/GLT Transaction would enable CN to lower its maintenance costs and to improve transit times and reliability for shippers by using the parallel DWP and DMIR lines between Shelton Junction and Nopeming Junction for freight moving between western Canada and Chicago. And, CN adds, the CN/GLT Transaction would eliminate the need for interchange between CN and DMIR, thus permitting some single-line rail operations to and from shippers on CN and on DMIR, which should result in reduced handling and shortened car transit times.
                </P>
                <P>CN contends that, in view of the limited scope of the CN/GLT Transaction, the record of CN and its constituent railroads over the past decade in successfully implementing rail consolidations, the good operating condition of both systems, and the absence of any need for a sweeping “Day One” change in systems, the CN/GLT Transaction would present a low risk of implementation-related service difficulties.</P>
                <P>CN contends that the CN/GLT Transaction would have no anticompetitive effects.</P>
                <P>
                    (1) 
                    <E T="03">Horizontal Effects.</E>
                     CN contends that the CN/GLT Transaction would not have adverse “horizontal” effects on competition. CN explains that, except for Virginia, MN, and Duluth, MN/Superior, WI, which each receive rail service from three or more rail carriers, the CN and GLT lines serve no common metropolitan areas or cities. CN further explains that there would be no 2-to-1 shippers (
                    <E T="03">i.e.</E>
                    , there is no shipper now capable of receiving rail service from more than one independent railroad who would be reduced to having only one independent railroad available to it), and that, although there would arguably be one 3-to-2 shipper (
                    <E T="03">i.e.</E>
                    , a shipper now capable of receiving rail service from three independent railroads that, as a result of the Transaction, would only have two independent railroads available), that shipper (Koppers, Inc., at Ambridge, MN) would not be adversely affected by the nominal reduction in horizontal competition.
                    <SU>4</SU>
                    <FTREF/>
                </P>
                <FTNT>
                    <P>
                        <SU>4</SU>
                         
                        <E T="03">See</E>
                         CN-2 at 53. 
                        <E T="03">See also</E>
                         CN-2 at 68 &amp; n.3.
                    </P>
                </FTNT>
                <P>
                    (2) 
                    <E T="03">Vertical Effects.</E>
                     CN contends that the CN/GLT Transaction would not have adverse “vertical” effects on competition. CN explains that there would be no harm to shippers from a reduction in source or geographic competition, because CN and the GLT Railroads do not serve competing origins or destinations. CN further explains that, although vertical effects might conceivably arise when a railroad with market power in one geographic market merges with a connecting railroad and, as a result of the merger, extends its market power to the connecting railroad's territory, closing gateways and thus foreclosing other connecting railroads from participating in movements to or from the first railroad's service area, vertical effects of this nature are unlikely as a matter of economic theory. CN adds that, in any event, applicants would not engage in such foreclosure by closing efficient gateways; rather, applicants would keep all existing active gateways affected by the CN/GLT Transaction open on commercially reasonable terms, and applicants would waive any defenses they might otherwise have as a result of the CN/GLT Transaction, under the Board's general policy that it does not separately regulate bottleneck rates, in circumstances where a shipper prior to the CN/GLT Transaction would have been entitled to regulation of a bottleneck rate under the Board's “contract exception” to the general rule.
                </P>
                <P>
                    <E T="03">Special Case: Eveleth Mines, LLC, d/b/a EVTAC Mining.</E>
                     CN advises: that, until May 2003, Eveleth Mines, LLC, d/b/a EVTAC Mining (EVTAC), operated a facility at Fairlane, MN (11 miles south of Virginia, MN), that processed raw iron ore into taconite pellets; that, although only DMIR was physically capable of carrying iron ore to, or processed taconite pellets from, the loading and unloading tracks at EVTAC's Fairlane facility, both CN and DMIR were capable of carrying general freight (
                    <E T="03">i.e.</E>
                    , commodities other than iron ore and taconite) to and from other tracks at that facility; and that, therefore, if EVTAC had not closed the Fairlane facility in May 2003, that facility would have been regarded, as respects the CN/GLT Transaction, as a “1-to-1” facility for iron ore and taconite and a “2-to-1” facility for general freight. CN also advises, however, that it might be argued that CN could have built in to the Fairlane facility to handle its iron ore and taconite freight, or that EVTAC could have built out to CN to obtain competitive service from CN as respects EVTAC's iron ore and taconite movements. CN further advises: That, if the EVTAC facility should reopen and require rail service, CN would be prepared to offer competitive access to another railroad for general freight, so as to restore two-railroad competition for that traffic; that, to this end, CN intends, should EVTAC reopen, to grant trackage rights access to EVTAC to another railroad, or, if traffic volumes are too low to justify trackage rights operations, to provide haulage service or switching at a rate that would not disadvantage the other railroad; and that, to replicate any build-in or build-out opportunity that now exists as respects iron ore and taconite traffic, CN would also be prepared to provide another railroad access to the build-in or build-out point via trackage rights over the DWP line. CN adds that, although it would expect to negotiate the terms of such access (either as respects general freight or as 
                    <PRTPAGE P="68134"/>
                    respects access to the build-in/build-out point) through voluntary agreement with a competing railroad, it is, of course, possible that the parties might be unable to agree on such terms. CN therefore contends that, if the Board approves the primary application, the Board should retain jurisdiction over the CN/GLT Transaction for a reasonable period for the purpose of reopening this proceeding if the EVTAC facility should resume operations and require rail service, if necessary to prescribe terms of access for a second rail carrier to handle general freight (
                    <E T="03">i.e.</E>
                    , commodities other than iron ore and taconite) to and/or from the EVTAC facility, or to prescribe terms of access to a build-in or build-out point on the existing DWP line that would permit a second rail carrier to handle iron ore and taconite to/from that facility. CN adds that, because its trackage rights agreement with DMIR prohibits CN from transporting iron ore (including taconite pellets) over the DMIR line between Nopeming Junction and South Itasca, CN should not be required to permit use of that DMIR line for transportation of iron ore, except on commercial terms. CN also adds that, because CN does not have access to an ore dock of its own in the Duluth/Superior area, the railroad receiving trackage rights to a build-in/build-out point should not be one that presently owns such a dock.
                </P>
                <P>
                    <E T="03">Labor Protection.</E>
                     CN projects that the CN/GLT Transaction would result in the elimination of 122 positions and the transfer of 18 positions. CN also projects that the reciprocal grants of Shelton Junction-Nopeming Junction trackage rights provided for in the related filings would have no adverse effect on train and engine service employees. CN notes, however, that, whereas these projections represent CN's best estimate, based on information presently available, of the changes necessary to effect the public transportation benefits and the efficiencies of the CN/GLT Transaction, additional changes might be required as circumstances change, opportunities open elsewhere on the CN system, traffic and shipping patterns evolve, and CN acquires experience in operating the combined system. CN acknowledges that the applicable level of labor protection for the CN/GLT Transaction would be that set forth in 
                    <E T="03">New York Dock Ry.—Control—Brooklyn Eastern Dist.,</E>
                     360 I.C.C. 60, 84-90 (1979), 
                    <E T="03">aff'd sub nom. New York Dock Ry.</E>
                     v. 
                    <E T="03">United States,</E>
                     609 F.2d 83 (2d Cir. 1979), and that the applicable level of labor protection for the Shelton Junction-Nopeming Junction trackage rights would be that set forth in 
                    <E T="03">Norfolk and Western Ry. Co.—Trackage Rights—BN,</E>
                     354 I.C.C. 605, 610-15 (1978), as modified in 
                    <E T="03">Mendocino Coast Ry., Inc.—Lease and Operate,</E>
                     360 I.C.C. 653, 664 (1980), 
                    <E T="03">aff'd sub nom. Railway Labor Exec. Ass'n</E>
                     v. 
                    <E T="03">United States,</E>
                     675 F.2d 1248 (D.C. Cir. 1982). CN adds that management employees whose positions would be eliminated as a result of the Transaction, and who would not be offered a job opportunity elsewhere in the CN system, would be offered severance packages, and that, if relocation to another job is offered, CN would also offer to relocate the management employee in accordance with the then-current CN management relocation plan.
                </P>
                <HD SOURCE="HD1">Primary Application and Related Filings Accepted</HD>
                <P>
                    The Board agrees with CN that the CN/GLT Transaction proposed in the primary application would be a “minor transaction” under 49 CFR 1180.2(c), and the Board is accepting the primary application for consideration because it is in substantial compliance with the applicable regulations governing minor transactions. 
                    <E T="03">See</E>
                     49 U.S.C. 11321-26; 49 CFR part 1180. The Board is also accepting for consideration the two related filings, which are also in compliance with the applicable regulations. The Board reserves the right to require the filing of supplemental information from CN or any other party or individual, if necessary to complete the record in this matter.
                </P>
                <HD SOURCE="HD1">Public Inspection</HD>
                <P>The primary application and the related filings are available for inspection in the Docket File Reading Room (Room 755) at the offices of the Surface Transportation Board, 1925 K Street, NW., in Washington, DC. In addition, they may be obtained from CN's representative (Mr. Cunningham) at the address indicated above.</P>
                <HD SOURCE="HD1">Procedural Schedule</HD>
                <P>CN contends that, in view of the asserted public benefits of the CN/GLT Transaction, the asserted lack of competitive harm, and the asserted absence of complicating environmental factors or related applications, a shorter procedural schedule than the 180-day maximum procedural schedule allowed by statute would be appropriate. CN has therefore proposed a 146-day procedural schedule that provides for issuance of a decision by the Board on March 30, 2004.</P>
                <P>The Board is adopting a 156-day procedural schedule patterned upon the 156-day procedural schedule that was adopted earlier this year in the “KCS/Tex Mex” proceeding. The Board's 156-day procedural schedule, although 10 days longer than the schedule suggested by CN, still provides for less total time than the 180-day procedural schedule (30 days + 105 days + 45 days) established by the deadlines set forth at 49 U.S.C. 11325(a), (d)(2). Comments on CN's Environmental Appendix (submitted November 5, 2003, and supplemented November 10, 2003) are due by December 10, 2003. CN must submit its Safety Integration Plan (SIP) by December 15, 2003. Any person who wishes to participate in this proceeding as a party of record (POR) must file, no later than December 19, 2003, a notice of intent to participate. Comments on CN's SIP must be filed by January 22, 2004. All comments, protests, requests for conditions, and any other evidence and argument in opposition to the primary application and/or either or both of the related filings, including filings by the U.S. Department of Justice (DOJ) and the U.S. Department of Transportation (DOT), must be filed by January 26, 2004. As in past proceedings, DOT will be allowed to file, on the reply due date (here, February 24, 2004), its comments in response to the comments of other parties, and CN will be allowed to late-file (as quickly as possible) a reply to DOT's responsive comments. Responses to comments, protests, requests for conditions, and other opposition, responses to comments of DOJ and DOT, and rebuttal in support of the primary application and/or either or both of the related filings must be filed by February 24, 2004. A public hearing/oral argument will be held the week of March 1, 2004 (the precise date and the location will be announced later). The Board's decision will be issued on April 9, 2004 (the 156th day after the date on which the primary application and the related filings were filed, and the 45th day after the close of the record). If, however, it is determined that an Environmental Impact Statement or Environmental Assessment is required, the procedural schedule will be adjusted as necessary.</P>
                <HD SOURCE="HD1">Notice of Intent To Participate</HD>
                <P>
                    Any person who wishes to participate in this proceeding as a POR must file with the Board, no later than December 19, 2003, an original and 20 copies of a notice of intent to participate, accompanied by a certificate of service indicating that the notice has been properly served on the Secretary of the United States Department of Transportation, the Attorney General of the United States, and CN's representative (Mr. Cunningham). In 
                    <PRTPAGE P="68135"/>
                    addition, as previously noted, parties must submit one electronic copy of each document filed with the Board. Further details respecting such electronic submissions are provided below.
                </P>
                <P>The Board will serve, as soon as practicable, a notice containing the official service list (the service list notice). Each POR will be required to serve upon all other PORs, within 10 days of the service date of the service list notice, copies of all filings previously submitted by that party (to the extent such filings have not previously been served upon such other parties). Each POR also will be required to file with the Board, within 10 days of the service date of the service list notice, an original plus 10 copies of a certificate of service, along with an electronic copy, indicating that the service required by the preceding sentence has been accomplished. Every filing made by a POR after the service date of the service list notice must have its own certificate of service indicating that all PORs on the service list have been served with a copy of the filing. Members of the United States Congress (MOCs) and Governors (GOVs) are not parties of record, and therefore, need not be served with copies of filings, unless any such Member or Governor has requested to be, and is designated as, a POR.</P>
                <P>
                    The Board will serve copies of its decisions, orders, and notices only on those persons who are designated on the official service list as either POR, MOC, or GOV. All other interested persons are encouraged to make advance arrangements with the Board's copy contractor, ASAP Document Solutions,
                    <SU>5</SU>
                    <FTREF/>
                     to receive copies of Board decisions, orders, and notices served in this proceeding. ASAP Document Solutions will handle the collection of charges and the mailing and/or faxing of decisions, orders, and notices to persons who request this service.
                </P>
                <FTNT>
                    <P>
                        <SU>5</SU>
                         The mailing address is: ASAP Document Solutions, Suite 405, 1925 K Street, NW., Washington, DC 20006. The telephone number is: (202) 293-7878. The e-mail address is: 
                        <E T="03">asapdoc.@verizon.net.</E>
                    </P>
                </FTNT>
                <P>
                    An interested person does not need to be on the service list to obtain a copy of the primary application or any other filing made in this proceeding. The Board's Railroad Consolidation Procedures provide: “Any document filed with the Board (including applications, pleadings, 
                    <E T="03">etc.</E>
                    ) shall be promptly furnished to interested persons on request, unless subject to a protective order.” 49 CFR 1180.4(a)(3). The primary application and other filings in this proceeding will also be available on the Board's Web site at 
                    <E T="03">www.stb.dot.gov</E>
                     under “Filings.” Furthermore, ASAP Document Solutions will provide, for a charge, copies of the primary application or any other filing made in this proceeding, except to the extent any such filing is subject to the protective order previously entered in this proceeding.
                </P>
                <HD SOURCE="HD1">Comments, Protests, Requests for Conditions, and Other Opposition Evidence and Argument, Including Filings by DOJ and DOT</HD>
                <P>All comments, protests, requests for conditions, and any other evidence and argument in opposition to the primary application and/or either or both of the related filings, including filings by DOJ and DOT, must be filed by January 26, 2004.</P>
                <P>
                    Parties (including DOJ and DOT) filing such comments, 
                    <E T="03">etc.</E>
                    , must submit an original and 20 copies thereof. Each such submission: must be filed with the Surface Transportation Board, 1925 K Street, NW., Washington, DC 20423-0001; must refer to STB Finance Docket No. 34424; and must be clearly labeled with an identification acronym and number (
                    <E T="03">e.g.</E>
                    , the primary application was labeled “CN-2”), 
                    <E T="03">see</E>
                     49 CFR 1180.4(a)(2). In addition, as previously noted, parties must submit one electronic copy of each document filed with the Board. Further details respecting such electronic submissions are provided below.
                </P>
                <P>
                    Comments, 
                    <E T="03">etc.</E>
                    , must be concurrently served by first class mail on the U.S. Attorney General and the Secretary of the United States Department of Transportation, CN's representative, and all other PORs, and should include the docket number and title of the proceeding, and the name, address, and telephone number of the commenting party and its representative upon whom service shall be made.
                </P>
                <P>Because the CN/GLT Transaction proposed in the primary application has been determined to be a minor transaction, no responsive applications will be permitted. See 49 CFR 1180.4(d)(1).</P>
                <P>
                    Protesting parties are advised that, if they seek either the denial of the primary application or the imposition of conditions upon any approval thereof, on the theory that approval (or approval without imposition of conditions) would harm competition and/or their ability to provide essential services, they must present substantial evidence in support of their positions. 
                    <E T="03">See Lamoille Valley R.R. Co.</E>
                     v. 
                    <E T="03">ICC,</E>
                     711 F.2d 295 (D.C. Cir. 1983).
                </P>
                <HD SOURCE="HD1">Responses to Comments, Protests, Requests for Conditions, and Other Opposition, Including DOJ and DOT; Rebuttal in Support of Primary Application</HD>
                <P>Responses to comments, protests, requests for conditions, and other opposition submissions, responses to comments of DOJ and DOT, and rebuttal in support of the primary application and/or either or both of the related filings must be filed by February 24, 2004.</P>
                <HD SOURCE="HD1">Environmental Matters</HD>
                <P>Under the regulations of the President's Council on Environmental Quality implementing the National Environmental Policy Act of 1969 (NEPA) and under the Board's environmental regulations as well, actions are separated into three classes that prescribe the level of documentation required in the NEPA process. Actions that may significantly affect the environment generally require the Board to prepare an Environmental Impact Statement (EIS). 40 CFR 1501.4(a)(1); 49 CFR 1105.4(f), 1105.6(a). Actions that may or may not have a significant environmental impact ordinarily require the Board to prepare a more limited Environmental Assessment (EA) (an EA is a document containing environmental analysis sufficient for the Board to determine whether it should prepare an EIS or may make a finding that the transaction will have no significant environmental impact). 40 CFR 1501.4(c); 49 CFR 1105.4(d), 1105.6(b). Actions that ordinarily have insignificant environmental effects may normally be categorically excluded from NEPA review, without a case-by-case review. 40 CFR 1500.4(p), 1501.4(a)(2), 1508.4; 49 CFR 1105.6(c). And, even when the Board's presumptive tonnage thresholds for environmental analysis are met, the Board may reclassify a particular transaction or modify the requirement that an EIS or EA be prepared, if the railroad applicant demonstrates that the proposed transaction has no potential for significant environmental effects. 49 CFR 1105.6(d).</P>
                <P>
                    Prior to filing the CN/GLT Application with the Board on November 5, 2003, CN discussed the CN/GLT Transaction with the Board's Section of Environmental Analysis (SEA) and explained that, in its view, the CN/GLT Transaction would have no significant environmental impacts, and that, therefore, preparation by the Board of an EIS or EA is not required to discharge the Board's obligations under NEPA. Pursuant to CN's discussions 
                    <PRTPAGE P="68136"/>
                    with SEA, CN prepared an Environmental Appendix that describes what CN regards as the reasonably foreseeable impacts of the CN/GLT Transaction, and that explains why CN believes that there is no need to prepare either an EIS or an EA. CN argues, in essence: that the only reasonably foreseeable Transaction-related operational change involves coordinated use of the DWP/DMIR lines in the 64-mile Shelton Junction-Nopeming Junction corridor (which, CN advises, lies in a relatively sparsely populated area of northeastern Minnesota); that, if foreseeable increases in tonnage on the DMIR line are compared to traffic volumes now moving on the DMIR line, the Board's presumptive tonnage thresholds for environmental analysis would be exceeded on a total of 61.5 miles of the DMIR line; but that, if foreseeable increases in tonnage on the DMIR line are compared to the traffic volumes generated before the recent closing of EVTAC's Fairlane facility, the Board's presumptive tonnage thresholds would not be exceeded at all, except on the 6.0-mile segment running through the rural territory between Adolph and Nopeming Junction. CN contends, in essence, that whether potential traffic shifts are measured against a base that includes or excludes EVTAC traffic, the reality of the situation is that the environmental consequences of the CN/GLT Transaction would be insignificant and thus do not warrant environmental review beyond that entailed in the preparation and review of CN's Environmental Appendix.
                </P>
                <P>CN offers the following points in support of this contention: (1) The Transaction should have no impact on land use, biological resources, or natural resources because there would be no construction or abandonment of rail lines, and no construction or operational changes in connection with rail yards or intermodal facilities; (2) there are no plans to dispose of or alter any properties that are 50 years old or older; (3) the only operational change contemplated by CN is the coordination of operations on the parallel DWP and DMIR lines between Shelton Junction and Nopeming Junction; (4) any traffic increases resulting from such coordination would reflect shifts of existing traffic, not new traffic or diversions from trucks or other railroads; (5) the DMIR line between Shelton Junction and Nopeming Junction runs through a lightly populated area; (6) the estimated increase in rail traffic on that line would be below the applicable tonnage threshold on nearly the entire length of that line, if the increase were measured against pre-May 2003 traffic volumes; (7) the potential environmental impacts from increased traffic on DMIR's Shelton Junction-Nopeming Junction line would be minimal (because there would be no increase in energy consumption, air quality would be unchanged or better, noise impacts would be insignificant, roadway at-grade crossings would remain safe, there would be little impact on rail safety, the quantities of hazardous materials shifted to the DMIR line would be modest, directional running should allow rail traffic to move more smoothly, and there would be no high and adverse impacts on any “environmental justice” populations); and (8) even the potential environmental impacts from increased traffic on the Adolph-Nopeming Junction segment of DMIR's Shelton Junction-Nopeming Junction line should be insignificant (CN claims that only 66 structures of any kind lie within 1,000 feet of the Adolph-Nopeming Junction right-of-way).</P>
                <P>To facilitate public review of all aspects of the Environmental Appendix, and to provide an opportunity for comments to SEA on the CN/GLT Transaction, and, in particular, on CN's conclusion that the Transaction would have no significant environmental impacts, CN mailed copies of the Environmental Appendix to appropriate local, state, and federal environmental agencies and other interested parties, and placed notices in major newspapers delivered to potentially affected communities. December 10, 2003, is the date by which interested parties may submit comments on the Environmental Appendix directly to SEA.</P>
                <P>
                    CN has advised that, pursuant to the joint regulations adopted by the Board and the Federal Railroad Administration (FRA) to ensure adequate and coordinated consideration of safety integration issues by both the Board and FRA, 
                    <E T="03">see</E>
                     49 CFR Parts 244 and 1106, CN will submit a Safety Integration Plan (SIP) to the Board and FRA by December 15, 2003. CN has further advised that it will distribute the SIP to appropriate government agencies and other interested parties, and will place notices in major newspapers delivered to potentially affected communities, to announce the availability of the SIP. Interested parties will have until January 22, 2004, to submit comments on the SIP to SEA. In accordance with past practice, the Board will include in any decision approving the CN/GLT Transaction a condition requiring CN to comply with the SIP. 
                    <E T="03">See</E>
                     49 CFR 1106.4(b)(4).
                </P>
                <P>Based on its consideration of all timely comments on the Environmental Appendix and the SIP and its own independent review of all available environmental information, SEA will recommend to the Board whether there is a need for formal environmental review of the CN/GLT Transaction, and the Board will then determine whether formal environmental review is required and, if so, whether an EIS or an EA should be prepared. If an EIS or an EA is required to meet the Board's obligations under NEPA, the procedural schedule set forth in this decision will be adjusted accordingly.</P>
                <HD SOURCE="HD1">Public Hearing/Oral Argument</HD>
                <P>To afford interested parties an opportunity to address the Board respecting any issues arising out of the CN/GLT Transaction, a public hearing/oral argument will be held the week of March 1, 2004. The precise date and the location will be announced later.</P>
                <HD SOURCE="HD1">Discovery</HD>
                <P>Discovery may begin immediately. The parties are encouraged to resolve all discovery matters expeditiously and amicably.</P>
                <HD SOURCE="HD1">Electronic Submissions: In General</HD>
                <P>
                    As already mentioned, in addition to submitting an original and 20 paper copies of each document filed with the Board, parties must submit, on 3.5-inch IBM-compatible floppy diskettes (disks) or on compact discs (CDs), copies of all textual materials, electronic workpapers, data bases, and spreadsheets used to develop quantitative evidence. Parties unable to comply with the electronic submission requirement can seek a waiver from the Board. Textual materials must be in, or compatible with, WordPerfect 10.0. Electronic spreadsheets must be in, or compatible with, Lotus 1-2-3 Release 9 or Microsoft Excel 2002. Each disk or CD should be clearly labeled with the identification acronym and number of the corresponding paper document, 
                    <E T="03">see</E>
                     49 CFR 1180.4(a)(2), and a copy of such disk or CD should be provided to any other party upon request. Also, each disk or CD should be clearly labeled as containing confidential or redacted materials. The data contained on the disks and CDs submitted to the Board will be subject to the protective order granted in Decision No. 1 (served October 29, 2003), and will be for the exclusive use of Board employees reviewing substantive and/or procedural matters in this proceeding. The flexibility provided by computer data will facilitate timely review by the Board and its staff. The electronic 
                    <PRTPAGE P="68137"/>
                    submission requirements set forth in this decision supersede, for the purposes of this proceeding, the otherwise applicable electronic submission requirements set forth in the Board's regulations. 
                    <E T="03">See</E>
                     49 CFR 1104.3(b).
                </P>
                <HD SOURCE="HD1">Electronic Submissions: Workpapers, Data Bases, and Spreadsheets</HD>
                <P>
                    In the past, the Board has encountered problems with the “links” in spreadsheets functioning properly when the spreadsheets are installed on desktop computers or network servers. To avoid such problems, parties submitting electronic workpapers, data bases, and/or spreadsheets should use naming and linking conventions that will permit the spreadsheets to operate on the Board's computers.
                    <SU>6</SU>
                    <FTREF/>
                     Electronic data bases should be compatible with the Microsoft Open Database Connectivity (ODBC) standard.
                    <SU>7</SU>
                    <FTREF/>
                     The Board currently uses Microsoft Access 2000, and data bases submitted should be either in this format or another ODBC-compatible format. Otherwise, submitters should explain why it is not possible to submit the data base in this format and seek a determination as to whether it is feasible for the Board to accept the data base in another format.
                </P>
                <FTNT>
                    <P>
                        <SU>6</SU>
                         The Board will not specify a particular naming and linking convention. It is incumbent upon the submitter to use generic naming and linking conventions that will permit the spreadsheets to operate on desktop computers or from a network server. Questions concerning naming and linking matters and/or compatibility with the Board's computers can be addressed to William H. Washburn, Office of Economics, Environmental Analysis, and Administration, at (202) 565-1550.
                    </P>
                </FTNT>
                <FTNT>
                    <P>
                        <SU>7</SU>
                         ODBC is a Windows technology that allows a database software package, such as Microsoft Access, to import data from a database created using a different software package. All databases must be supported with adequate documentation on data attributes, SQL queries, programmed reports, 
                        <E T="03">etc.</E>
                    </P>
                </FTNT>
                <P>This action will not significantly affect either the quality of the human environment or the conservation of energy resources.</P>
                <P>
                    <E T="03">It is ordered:</E>
                </P>
                <P>1. The primary application in STB Finance Docket No. 34424 and the related filings in STB Finance Docket No. 34424 (Sub-Nos. 1 and 2) are accepted for consideration.</P>
                <P>2. The parties to this proceeding must comply with the Procedural Schedule adopted by the Board in this proceeding as shown in Appendix A.</P>
                <P>3. The parties to this proceeding must comply with the procedural requirements described in this decision.</P>
                <P>4. This decision is effective on December 5, 2003.</P>
                <SIG>
                    <DATED>Decided: November 25, 2003.</DATED>
                    <P>By the Board, Chairman Nober.</P>
                    <NAME>Vernon A. Williams,</NAME>
                    <TITLE>Secretary.</TITLE>
                </SIG>
                <APPENDIX>
                    <HD SOURCE="HED">Appendix A: Procedural Schedule</HD>
                    <FP SOURCE="FP-1">November 5, 2003—Primary application, related filings, Environmental Appendix, and petition for establishment of procedural schedule filed.</FP>
                    <FP SOURCE="FP-1">November 10, 2003—Supplemented Environmental Appendix submitted.</FP>
                    <FP SOURCE="FP-1">
                        December 5, 2003—Board notice of acceptance of primary application and related filings published in the 
                        <E T="04">Federal Register</E>
                        .
                    </FP>
                    <FP SOURCE="FP-1">December 10, 2003—Comments on the Environmental Appendix due.</FP>
                    <FP SOURCE="FP-1">December 15, 2003—Safety Integration Plan (SIP) due.</FP>
                    <FP SOURCE="FP-1">December 19, 2003—Notices of intent to participate due.</FP>
                    <FP SOURCE="FP-1">January 22, 2004—Comments on the SIP due.</FP>
                    <FP SOURCE="FP-1">January 26, 2004—All comments, protests, requests for conditions, and any other evidence and argument in opposition to the primary application and/or either or both of the related filings, including filings of the U.S. Department of Justice (DOJ) and the U.S. Department of Transportation (DOT), due.</FP>
                    <FP SOURCE="FP-1">February 24, 2004—Responses to comments, protests, requests for conditions, and other opposition due. Responses to comments of DOJ and DOT due. Rebuttal in support of the primary application and/or either or both of the related filings due.</FP>
                    <FP SOURCE="FP-1">Week of March 1, 2004—A public hearing/oral argument will be held the week of March 1, 2004 (the precise date and the location will be announced later).</FP>
                    <FP SOURCE="FP-1">April 9, 2004—Date of service of final decision (if no unanticipated environmental review is required).</FP>
                </APPENDIX>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30090 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4915-00-P</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF THE TREASURY</AGENCY>
                <SUBJECT>Submission for OMB Review; Comment Request</SUBJECT>
                <DATE>November 27, 2003.</DATE>
                <P>The Department of Treasury has submitted the following public information collection requirement(s) to OMB for review and clearance under the Paperwork Reduction Act of 1995, Pub. L. 104-13. Copies of the submission(s) may be obtained by calling the Treasury Bureau Clearance Officer listed. Comments regarding this information collection should be addressed to the OMB reviewer listed and to the Treasury Department Clearance Officer, Department of the Treasury, Room 11000, 1750 Pennsylvania Avenue, NW., Washington, DC 20220.</P>
                <P>
                    <E T="03">Dates:</E>
                     Written comments should be received on or before January 5, 2004 to be assured of consideration.
                </P>
                <HD SOURCE="HD1">Internal Revenue Service (IRS)</HD>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-0043.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     IRS Form 972.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Extension.
                </P>
                <P>
                    <E T="03">Title:</E>
                     Consent of Shareholder to Include Specific Amount in Gross Income.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Form 972 is filed by shareholders of corporations to elect to include an amount in gross income as a dividend. The IRS uses Form 972 as a check to see if an amended return is filed to include the amount income and to determine if the corporation claimed the correct amount.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Individuals or households, business or other for-profit.
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents/Recordkeeping:</E>
                     400.
                </P>
                <P>
                    <E T="03">Estimated Burden Hours Respondent/Recordkeeper:</E>
                </P>
                <FP SOURCE="FP-1">Recordkeeping—13 min.</FP>
                <FP SOURCE="FP-1">Learning about the law or the form—4 min.</FP>
                <FP SOURCE="FP-1">Preparing the form—16 min.</FP>
                <FP SOURCE="FP-1">Copying, assembling, and sending the form to the IRS—20 min.</FP>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion.
                </P>
                <P>
                    <E T="03">Estimated Total Reporting/Recordkeeping Burden:</E>
                     368 hours.
                </P>
                <P>
                    <E T="03">OMB Number:</E>
                     1545-0138.
                </P>
                <P>
                    <E T="03">Form Number:</E>
                     IRS Form 2063.
                </P>
                <P>
                    <E T="03">Type of Review:</E>
                     Revision.
                </P>
                <P>
                    <E T="03">Title:</E>
                     U.S. Departing Alien Income Tax Statement.
                </P>
                <P>
                    <E T="03">Description:</E>
                     Form 2063 is used by a departing resident alien against whom a termination assessment has not been made, or a departing nonresident alien who has no taxable income from United States sources, to certify that they have satisfied all U.S. income tax obligations. The data is used by the IRS to certify that departing aliens have complied with U.S. income tax laws.
                </P>
                <P>
                    <E T="03">Respondents:</E>
                     Individuals or households.
                </P>
                <P>
                    <E T="03">Estimated Number of Respondents/Recordkeepers:</E>
                     20,540.
                </P>
                <P>
                    <E T="03">Estimated Burden Hours Respondent/Recordkeeper:</E>
                </P>
                <FP SOURCE="FP-1">Recordkeeping—6 min.</FP>
                <FP SOURCE="FP-1">Learning about the law or the form—3 min.</FP>
                <FP SOURCE="FP-1">Preparing the form—26 min.</FP>
                <FP SOURCE="FP-1">Copying, assembling, and sending the form to the IRS—13 min.</FP>
                <P>
                    <E T="03">Frequency of Response:</E>
                     On occasion.
                </P>
                <P>
                    <E T="03">Estimated Total Reporting/Recordkeeping Burden:</E>
                     17,049 hours.
                </P>
                <P>Clearance Officer: R. Joseph Durbala, (202) 622-3634, Internal Revenue Service, Room 6411, 1111 Constitution Avenue, NW., Washington, DC 20224.</P>
                <P>
                    OMB Reviewer: Joseph F. Lackey, Jr., (202) 395-7316, Office of Management and Budget, Room 10235, New 
                    <PRTPAGE P="68138"/>
                    Executive Office Building, Washington, DC 20503.
                </P>
                <SIG>
                    <NAME>Lois K. Holland,</NAME>
                    <TITLE>Treasury PRA Clearance Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30242 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 4830-01-U</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="N">DEPARTMENT OF VETERANS AFFAIRS</AGENCY>
                <SUBJECT>Capital Asset Realignment for Enhanced Services (CARES) Commission; Notice of Meeting</SUBJECT>
                <P>The Department of Veterans Affairs (VA) gives notice under Public Law 92-463 (Federal Advisory Committee Act) that the Capital Asset Realignment for Enhanced Services (CARES) Commission will hold a meeting on December 18, 2003, at the Hotel Washington, Pennsylvania Avenue at 15th Street, NW., Washington, DC 20004. The meeting will begin at 10 a.m. and will end at 4 p.m. and is open to the public.</P>
                <P>The purpose of the Commission is to conduct an external assessment of VA's capital asset needs and to assure that stakeholder and beneficiary concerns are fully addressed. The Commission is reviewing and reaching decisions on recommendations in the Draft National CARES Plan. The Commission also takes into consideration recommendations submitted by veterans service organizations, individual veterans, Congress, medical and nursing school affiliates, VA employees, local governments, community groups and others. Following its assessment, the Commission will make specific recommendations to the Secretary of Veterans Affairs on the realignment and allocation of VA capital assets to meet the demand for, and to enhance, veterans health care services over the next 20 years.</P>
                <P>At the December 18 meeting, the Commission will conclude its review of the information received from nationwide site visits, public hearings, and various requests for data as well as information discussed in its regular public meetings. The Commission will engage in final deliberations regarding the Draft National CARES Plan and its impact in the various markets, and make decisions regarding its report to the Secretary.</P>
                <P>No time will be allocated at these meetings for receiving oral presentations from the public. Any member of the public wishing additional information should contact Mr. Richard E. Larson, Executive Director, CARES Commission, at (202) 501-2000.</P>
                <SIG>
                    <DATED>Dated: November 28, 2003.</DATED>
                    <P>By Direction of the Secretary.</P>
                    <NAME>E. Philip Riggin,</NAME>
                    <TITLE>Committee Management Officer.</TITLE>
                </SIG>
            </PREAMB>
            <FRDOC>[FR Doc. 03-30227  Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8320-01-M</BILCOD>
        </NOTICE>
        <NOTICE>
            <PREAMB>
                <AGENCY TYPE="S">DEPARTMENT OF VETERANS AFFAIRS</AGENCY>
                <SUBJECT>Enhanced-Use Lease Development of Property at the Department of Veterans Affairs Medical Center, Dayton, OH</SUBJECT>
                <AGY>
                    <HD SOURCE="HED">AGENCY:</HD>
                    <P>Department of Veterans Affairs.</P>
                </AGY>
                <ACT>
                    <HD SOURCE="HED">ACTION:</HD>
                    <P>Notice of intent to designate.</P>
                </ACT>
                <SUM>
                    <HD SOURCE="HED">SUMMARY:</HD>
                    <P>The Secretary of the Department of Veterans Affairs (VA) intends to designate Building 401 (23,600 square feet), with an abutting playground (11,500 square feet) at the Department of Veterans Affairs Medical Center, Dayton, Ohio, for an enhanced-use lease. The Department intends to enter into a 35-year lease of real property with a selected lessee/developer who would be responsible for all costs and risks associated with the design, development, renovation, expansion, operation, maintenance, and provision of services at an existing non-profit child care center.</P>
                </SUM>
                <FURINF>
                    <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                    <P>Vanessa Chambers, Capital Asset Management and Planning Service (182C), Department of Veterans Affairs, 810 Vermont Avenue, NW., Washington, DC 20420, (202) 565-6554.</P>
                </FURINF>
            </PREAMB>
            <SUPLINF>
                <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                <P>
                    38 U.S.C. 8161, 
                    <E T="03">et seq.</E>
                     specifically provides that the Secretary may enter into an enhanced-use lease if he determines that at least part of the use of the property under the lease will be to provide appropriate space for an activity contributing to the mission of the Department; the lease will not be inconsistent with and will not adversely affect the mission of the Department; and the lease will enhance the property or result in improved services to veterans. This project meets these requirements.
                </P>
                <SIG>
                    <APPR>Approved: November 26, 2003.</APPR>
                    <NAME>Anthony J. Principi,</NAME>
                    <TITLE>Secretary of Veterans Affairs.</TITLE>
                </SIG>
            </SUPLINF>
            <FRDOC>[FR Doc. 03-30226 Filed 12-4-03; 8:45 am]</FRDOC>
            <BILCOD>BILLING CODE 8320-01-P</BILCOD>
        </NOTICE>
    </NOTICES>
    <VOL>68 </VOL>
    <NO>234 </NO>
    <DATE>Friday, December 5, 2003 </DATE>
    <UNITNAME>Rules and Regulations </UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="68139"/>
            <PARTNO>Part II </PARTNO>
            <AGENCY TYPE="P">Department of Homeland Security </AGENCY>
            <SUBAGY>Bureau of Customs and Border Protection </SUBAGY>
            <HRULE/>
            <CFR>19 CFR Parts 4, 103, et al. </CFR>
            <TITLE>Required Advance Electronic Presentation of Cargo Information; Final Rule </TITLE>
        </PTITLE>
        <RULES>
            <RULE>
                <PREAMB>
                    <PRTPAGE P="68140"/>
                    <AGENCY TYPE="S">DEPARTMENT OF HOMELAND SECURITY </AGENCY>
                    <SUBAGY>Bureau of Customs and Border Protection </SUBAGY>
                    <CFR>19 CFR Parts 4, 103, 113, 122, 123, 178 and 192 </CFR>
                    <DEPDOC>[CBP Dec. 03-32] </DEPDOC>
                    <RIN>RIN 1651-AA49 </RIN>
                    <SUBJECT>Required Advance Electronic Presentation of Cargo Information </SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Customs and Border Protection, Homeland Security. </P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Final rule. </P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>This document amends the Customs Regulations to provide that the Bureau of Customs and Border Protection (CBP) must receive, by way of a CBP-approved electronic data interchange system, information pertaining to cargo before the cargo is either brought into or sent from the United States by any mode of commercial transportation (sea, air, rail or truck). The cargo information required is that which is reasonably necessary to enable high-risk shipments to be identified for purposes of ensuring cargo safety and security and preventing smuggling pursuant to the laws enforced and administered by CBP. These regulations are specifically intended to effectuate the provisions of section 343(a) of the Trade Act of 2002, as amended by the Maritime Transportation Security Act of 2002. </P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>Effective Date: This rule is effective January 5, 2004. </P>
                        <P>Compliance Dates: The various compliance dates for these regulations are set forth, as applicable, in §§ 4.7(b)(5), 122.48a(e), 123.91(e), 123.92(e), and 192.14(e). </P>
                    </EFFDATE>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>Legal matters: Glen E. Vereb, Office of Regulations and Rulings, 202-572-8724; Trade compliance issues:</P>
                        <FP SOURCE="FP-1">Inbound vessel cargo: Kimberly Nott, Field Operations, 202-927-0042; </FP>
                        <FP SOURCE="FP-1">Inbound air cargo: David M. King, Field Operations, 202-927-1133; </FP>
                        <FP SOURCE="FP-1">Inbound truck cargo: Enrique Tamayo, Field Operations, 202-927-3112; </FP>
                        <FP SOURCE="FP-1">Inbound rail cargo: Juan Cancio-Bello, Field Operations, 202-927-3459; </FP>
                        <FP SOURCE="FP-1">Outbound cargo, all modes: Robert Rawls, Field Operations, 202-927-5301. </FP>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <HD SOURCE="HD1">Background </HD>
                    <P>Section 343(a) of the Trade Act of 2002 (Pub. L. 107-210, 116 Stat. 933, enacted on August 6, 2002), as amended by section 108 of the Maritime Transportation Security Act of 2002 (Pub. L. 107-295, 116 Stat. 2064, enacted on November 25, 2002), required that the Secretary endeavor to promulgate final regulations not later than October 1, 2003, providing for the mandatory collection of electronic cargo information by the Customs Service (now the Bureau of Customs and Border Protection (CBP)), either prior to the arrival of the cargo in the United States or its departure from the United States by any mode of commercial transportation (sea, air, rail or truck). Under section 343(a), as amended (codified at 19 U.S.C. 2071 note), the information required must consist of that information about the cargo which is determined to be reasonably necessary to enable CBP to identify high-risk shipments so as to ensure cargo safety and security and prevent smuggling pursuant to the laws that are enforced and administered by CBP. </P>
                    <HD SOURCE="HD1">Proposed Rulemaking </HD>
                    <P>
                        Consequently, in accordance with the parameters set forth in section 343(a), as amended, a document was published in the 
                        <E T="04">Federal Register</E>
                         (68 FR 43574) on July 23, 2003, proposing to amend the Customs Regulations in order to require the advance electronic transmission of information pertaining to cargo prior to its being brought into, or sent from, the United States by sea, air, rail or truck. 
                    </P>
                    <P>In part, section 343(a), as amended, required that a broad range of parties likely to be affected by the regulations be consulted and their comments be taken into consideration in developing these regulations. For this reason, separate public meetings were held in January 2003 to address specific issues, and to obtain public input, related to the advance electronic presentation of information, respectively, for sea, air, rail or truck cargo. The CBP also received numerous public comments via e-mail. In addition, extensive meetings were held with workgroups of the subcommittee on advance cargo information requirements of the Treasury Advisory Committee on the Commercial Operations of the U.S. Customs Service (COAC). For a detailed discussion of the development of the proposed rule, and the evaluation of the comments received as the result of the consultation process, see 68 FR 43574-43592. </P>
                    <HD SOURCE="HD1">Discussion of Comments </HD>
                    <P>
                        A total of 128 commenters responded in timely manner to the July 23, 2003, notice of proposed rulemaking. What follows is a review of, and CBP's response to, the issues and questions that were presented by these commenters concerning the proposed regulations. The CBP also received comments pertaining to the preliminary regulatory impact analysis which was published as an appendix to the proposed rule. Those comments, and the corresponding CBP response, have been addressed separately immediately following this section under the heading, “Comments on Economic Analysis”. In addition, a summary of the findings contained in the regulatory impact analysis for this rule can be found in the “REGULATORY ANALYSES” section of this document. For more detailed information, the complete regulatory impact analysis is available on the following Web site, 
                        <E T="03">http://www.cbp.gov</E>
                    </P>
                    <HD SOURCE="HD1">General; Issues Affecting Multiple Modes; Issuance of Separate House Bills of Lading</HD>
                    <P>
                        <E T="03">Comment:</E>
                         The requirement that a separate house bill of lading be issued for each shipper/consignee relationship imposed significant costs upon commerce. Carriers would now have to issue multiple bills of lading for each container of consolidated cargo, and they would charge a fee for each additional bill of lading, where the consolidated goods were tendered for shipment by a single freight forwarder and were destined to a single consignee in the United States. It was stated that CBP should modify AMS (the Automated Manifest System) so that it could receive vendor information for consolidated shipments without requiring the entry of entirely separate bills of lading.
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP reasonably needs detailed shipper information on the house bill of lading because this information is critical for targeting purposes under section 343(a)(2) of the Trade Act of 2002, as amended (19 U.S.C. 2071 note, section (a)(2)). Thus, where a freight forwarder or other consolidator receives goods from several foreign vendors (shippers) for consolidation and shipment to a single consignee in the United States, listing the freight forwarder or other consolidator, instead of the foreign vendor, as the shipper on the house bill of lading would be at odds with the intent of section 343(a). It is, of course, a business decision as to whether a forwarder or consolidator would choose to charge for any additional bill(s) of lading issued.
                    </P>
                    <P>
                        However, at the present time, the AMS system generally lacks the capability to process data for multiple shippers/consignees from a single house 
                        <PRTPAGE P="68141"/>
                        bill of lading. The AMS systems were built with a one-to-one relationship—one shipper to one consignee. To alter this would require a complete redesign of the system for all modes of transportation. In addition, it would also force the entire bill of lading to be placed on hold rather than one specific shipment. This is not a programming process that CBP can undertake at this time and, more specifically, detailed communication with the trade community would be required.
                    </P>
                    <HD SOURCE="HD1">Confidentiality </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Proposed § 103.31a should be revised to indicate that advance cargo information which contained classified or sensitive unclassified information would be released only in accordance with applicable regulations, statutes, and orders. Also, it was believed that the vessel cargo declaration information required to be reported in advance could be different from the manifest information envisioned in 19 U.S.C. 1431. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Section 103.31a, as proposed pursuant to section 343(a)(3)(G), as amended (19 U.S.C. 2071 note, section (a)(3)(G)), exempts from disclosure advance cargo data for all inbound and outbound air, rail, or truck cargo unless the owner of the information expressly agrees in writing to its release. In addition, as far as vessel cargo data collected under 19 U.S.C. 1431 is concerned, section 1431 already adequately addresses the conditions under which such information may not be disclosed, including where the information is authorized to be kept secret in the interest of national defense, as provided in 5 U.S.C. 552(b)(1); or where disclosure of the information would pose a threat of personal injury or property damage (see 19 U.S.C. 1431(c)(2)(A) &amp; (B)). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter discussed the matter of public disclosure of outbound cargo information which would be required to be submitted to CBP electronically. It was stated that since cargo information on outbound ocean shipments would rely upon Automated Export System (AES) submissions and not upon vessel cargo manifests, such information should not be subject to the public disclosure provisions of 19 U.S.C. 1431. Another commenter, however, fully supported the release of cargo data from outward vessel cargo manifests pursuant to the disclosure provisions of section 1431. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The underlying cargo manifest statute in question, 19 U.S.C. 1431, applies to both inbound and outbound cargoes. Although manifests are actually comprised of numerous documents, including the Shipper's Export Declaration (SED), the SED document itself is exempt from public disclosure pursuant to 13 U.S.C. 301(g) unless the Secretary of Commerce determines that such exemption would be contrary to the national interest. 
                    </P>
                    <P>Also appearing in existing Customs Regulations (19 CFR 103.31) is a provision making available for copying and publication certain information and data appearing on outward manifests. The scope of that information is described and limited in § 103.31. As in the case of inward vessel cargo manifest information, § 103.31 also provides that certain parties may file certifications with CBP to request confidentiality for outward vessel cargo manifest information (19 CFR 103.31(d)(2)). </P>
                    <HD SOURCE="HD1">Automated Manifest System (AMS) </HD>
                    <P>
                        <E T="03">Comment:</E>
                         The CBP did not provide an updated response to the question of what carriers should do when the Automated Manifest System (AMS) was not functioning. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP currently has procedures in place for the processing of cargo when automated systems have experienced a level of failure. The CBP offices routinely accept voluntary submissions of paper documents during this time from trade members looking for immediate release. The CBP's automated systems are designed to queue transmissions sent from the trade during downtime, and the system automatically begins to issue status and release messages when service is restored.
                    </P>
                    <P>For the purposes of the 24-Hour rule, the trade has been instructed to present paper manifests to CBP in either the appropriate Container Security Initiative (CSI) port of departure, or at the Domestic port of arrival in order to allow for advance targeting. The CBP anticipates instructing the trade the same for the purposes of section 343(a) of the Trade Act of 2002. It will admittedly be difficult and not all submissions will be made promptly. The CBP will then use informed, considered judgement in the issuance of penalties, the mitigation of penalties and other possible action against particular shipments.</P>
                    <P>If downtime is identified as severe and anticipated to last a significant period, the trade is notified and instructed to present papers entries, in-bond transportation documents and other release paperwork to the CBP offices. Carriers are instructed to present paper manifests for their arriving conveyances. As CBP manually processes the release and other paperwork, determining risk and satisfaction of all requirements to the best of the inspector's ability, copies of those documents are presented to the carriers to gain release of the cargo, or to demonstrate authorization for it to move in-bond or within the port.</P>
                    <P>When the automated system resumes service, CBP policy is to enter the information about paper processing into the system to generate corresponding electronic release messages and to also ensure that historical records are updated, and the clocks for duties, taxes and fees are correctly started. </P>
                    <P>Over the last years, the Automated Commercial System (ACS) has been very reliable in its processing and suffered very little unscheduled downtime. The CBP has made downtime requirements available on its Web site for the enforcement of the 24-Hour rule and will also do the same for the purposes of section 343(a) of the Trade Act of 2002.</P>
                    <P>
                        <E T="03">Comment:</E>
                         For ABI (Automated Broker Interface) filers (importer or brokers) that transmitted advance air or truck cargo data, it was asked whether their ABI Filer Codes would qualify as their unique identification code, or whether CBP would require that they obtain another code, such as an IATA (International Air Transport Association) code or a SCAC code (Standard Carrier Alpha Code).
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The ABI filer that transmits advance cargo data would be identified by its 3-digit ABI Filer Code. However, in the air environment, since the Air Automated Manifest System (Air AMS) requires a 7-character code to identify parties transmitting house air waybill level information, ABI filers electing to transmit such advance cargo data will be assigned codes in the format “BCBPXXX”, where, in place of the “XXX”, the ABI filer would insert its own unique 3-digit ABI filer code. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Under the 24-hour rule for incoming vessel cargo, Non Vessel Operating Common Carriers (NVOCCs) had to apply for approval to become a Vessel AMS filer. The question was raised, in the context of other modes of inbound transportation (air and truck), as to whether an ABI filer of information would have to go through the same approval process, including some form of application and qualification testing, before being allowed to file advance cargo data with CBP for incoming shipments.
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         ABI transmission capabilities are available to all entry filers who handle truck entries and that have been authorized to participate in ABI under the procedures prescribed in part 143, subpart A, Customs Regulations (19 CFR part 143, subpart 
                        <PRTPAGE P="68142"/>
                        A). In this context, it is the carrier's responsibility to ensure that the ABI transmitter of cargo data (broker or importer) receives the appropriate corresponding transportation information via fax or other means.
                    </P>
                    <P>However, each new participant in the Air Automated Manifest System (Air AMS) will be required to undergo certification testing prior to full participation. Certification/authorization to participate in ABI will not, by itself, be sufficient to satisfy this requirement. The CBP will provide updated lists of approved Air AMS participants. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Under the 24-hour rule, where an NVOCC filed the advance vessel cargo data, the NVOCC then had to perform other duties otherwise undertaken by the incoming ocean carrier for the arriving cargo, such as handling the arrival of the cargo, obtaining permits for its transfer, and coordinating any in-bond movements. However, as to incoming air cargo, provided that accurate links existed between the house and master bills of lading, the issue arose as to whether the incoming air carrier would be responsible for all of the documentary transactions related to the arrival and movement of the air freight once it had landed at the port of arrival. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         With consolidated shipments, given that an air carrier would transmit information for the incoming cargo at the master air waybill level, the carrier would be responsible for handling those transactions related to the arrival and movement of such cargo following its landing at the port of arrival. Coincident with this, any other eligible party transmitting (house bill) information for the incoming cargo would need to associate the house bill number with the master air waybill pertaining to such cargo (see § 122.48a(d)(2)(i) in this final rule). 
                    </P>
                    <P>Furthermore, CBP is currently working on additional programming changes to the Vessel Automated Manifest System (Vessel AMS) which would allow the incoming ocean carrier, after the cargo is landed at the port of arrival, to handle the movement of the cargo, and its clearance, etc., on the master bill of lading. </P>
                    <P>
                        <E T="03">Comment:</E>
                         It was remarked that all CBP automated systems in place had to be able to accommodate the required manifest reporting sufficiently for legitimate trade to continue to flow smoothly. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The requirement that cargo information be electronically presented in advance allows CBP to effectively target any cargo that may need to be held for further examination prior to the arrival of the vessel or other conveyance, which thereby enables legitimate cargo to move smoothly through the chain of commerce.
                    </P>
                    <HD SOURCE="HD1">C-TPAT Exemption</HD>
                    <P>
                        <E T="03">Comment:</E>
                         It was proposed that “low-risk” companies and those who were engaged in supply-chain security programs, such as the Customs-Trade Partnership Against Terrorism (C-TPAT), should be given a preference that would let such parties file their cargo declarations after, rather than prior to, the arrival of the cargo, or be subject to various relaxed restrictions in cargo information reporting. It was also suggested that CBP allow C-TPAT participants to use “Buyers Consolidation” (where multiple shippers/consignees were listed on a single bill of lading, instead of each shipper/consignee having to be included on a separate bill of lading). Otherwise, CBP was asked to explain what benefits accrued to C-TPAT members. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP will not allow exemption from, or alteration of, the requirement that C-TPAT partners submit cargo information in advance of arrival under these regulations, which includes the requirement that each shipper/consignee relationship be documented by a separate house bill of lading; and, moreover, CBP believes that compliance with these regulations complements supply chain security and efficiency procedures being implemented by C-TPAT partners.
                    </P>
                    <P>Furthermore, it is again emphasized that C-TPAT membership will continue to be viewed in a positive light for targeting purposes. It is more likely that shipments made by C-TPAT members will be readily and expeditiously cleared, and not be delayed for greater CBP scrutiny. Other related perquisites of C-TPAT partnership may include essential security benefits for suppliers, employees, and customers, such as a reduction in the number and extent of border inspections, an opportunity for self-policing rather than Customs verifications, and eligibility for account-based processes. </P>
                    <P>Account-based processing is only offered to importers at this time. Account-based processing provides advantages to importers such as web-based views into their importing history with CBP, the important elements of their bond sufficiency records, and the future ability to make periodic payments of the their duty statements. Each transaction is still reviewed as part of the manifest processing; while there may be a reduced number of trade compliance examinations, no account is exempt from enforcement or security screening. </P>
                    <P>
                        <E T="03">Comment:</E>
                         It was asked whether CBP would take into consideration low-risk status and participation in programs, such as C-TPAT, when minor reporting discrepancies occurred.
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         While participants in programs such as C-TPAT will not be exempt from electronically filing their cargo information in advance, as noted above, such participation will also be taken into account in connection with the occurrence of minor discrepancies in the advance reporting of cargo data. 
                    </P>
                    <HD SOURCE="HD1">Exemption; U.S. Department of Defense (DoD) </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Concern was expressed about the movement of military cargo on U.S. Department of Defense (DoD)-chartered aircraft, vessels, or trucks where DoD had exclusive use and control of the conveyance. The revised advance reporting time standards could adversely affect transit time for DoD cargo in the commercial transportation system. Exemptions were requested from advance cargo information reporting for DoD-chartered vessels, aircraft, and trucks. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         In the proposed rule, CBP agreed that an exemption from the requirement of entry would be extended to certain DoD-chartered vessels or aircraft (see 68 FR at 43577 and 43579, respectively). To accomplish this, §§ 4.5 and 122.41, Customs Regulations (19 CFR 4.5 and 122.41), are amended in this final rule document to exempt from entry requirements (but not from clearance requirements) any vessel or aircraft that is chartered by and exclusively carrying cargo, the property of the U.S. Department of Defense (DoD), where the DoD-chartered vessel or aircraft is manned entirely by the civilian crew of the vessel or air carrier under contract to DoD. Any vessel or aircraft exempt from entry would, of course, also be exempt from advance cargo information filing under this final rule. 
                    </P>
                    <P>
                        However, concerning trucks chartered by DoD, CBP has at least provisionally concluded that, balancing the potential risks posed against the costs at issue, an exemption from advance filing is not needed in this case. The advance filing time frame is sufficiently abbreviated that it should not have a negative effect on the transit time for military cargo moving in the commercial transportation chain (
                        <E T="03">e.g.</E>
                        , a mere 30 minutes advance notice in the case of Free And Secure Trade (FAST) trade participants) (see the discussion for incoming truck cargo, 
                        <E T="03">infra</E>
                        ). 
                        <PRTPAGE P="68143"/>
                    </P>
                    <HD SOURCE="HD1">Other Government Agencies; Single Portal for Collecting Data </HD>
                    <P>
                        <E T="03">Comment:</E>
                         It was advocated that CBP and the U.S. Food and Drug Administration (FDA) should harmonize the data elements and time frames for advance information that both agencies would now require. A single integrated computer system should be developed for the submission of advance information. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP is working diligently with the FDA towards integrated filing and risk management mechanisms. In fact, an agreement was reached in May 2003 between CBP and FDA to modify CBP's Automated Commercial System (ACS) to enable importers, in most cases, to use this system to satisfy the advance informational requirements of the Public Health Security and Bioterrorism Preparedness and Response Act of 2002 (Public Law 107-188) (the Bioterrorism Act) and implementing regulations. In the 
                        <E T="04">Federal Register</E>
                         of October 10, 2003 (68 FR 58974), FDA, in conjunction with CBP, issued an interim final rule requiring prior notice of food imported into the United States, beginning on December 12, 2003. The interim final rule requires that the prior notice be submitted to FDA electronically via either the CBP's Automated Broker Interface (ABI)/ACS Interface or the FDA's Prior Notice System Interface. The interim final rule on prior notice of imported food shipments is available at 
                        <E T="03">http://www.cfsan.fda.gov/~lrd/fr03o10b.html.</E>
                         The CBP is also making modifications to ACS to allow ACS to be used to satisfy the prior notice requirements of the Bioterrorism Act. 
                    </P>
                    <P>The CBP's Automated Commercial Environment (ACE) is intended to operate as a single window for the submission of import information to the Government, once it is developed and implemented as part of the International Trade Data System (ITDS). Nevertheless, in light of the urgent need, in particular, to implement both section 343(a), as amended, and the Bioterrorism Act, the Government cannot delay such implementation until a fully-interfaced, multi-agency electronic data interchange system is in place, either within ACS or ACE. </P>
                    <HD SOURCE="HD1">The Automated Commercial Environment (ACE) </HD>
                    <P>By way of additional perspective on the Automated Commercial Environment (ACE), CBP Modernization began in 2001, with the ACE focusing on import and export cargo operations. The ACE, as just noted, along with other entities will ultimately form one system providing a “single screen” for the international business community to interact with CBP and other government agencies on import/export requirements. The ACE will power an expedited release process for carriers and shippers that have prefiled, been pre-approved, and have been subject to enforcement prescreening and targeting. An integrated risk management and targeting system will implement all types of enforcement and selectivity screening for commercial shipments. The ACE will provide both CBP and the business community with the tools and technology to ensure secure supply-chain management. The program will include tools that will provide for: advanced manifesting system for all modes of transportation; tracking of intermodal shipment movements and cargo moving in-bound; enhanced conveyance and transit cargo tracking for shipments from origin to destination. Finally, when exports are processed in ACE, CBP will have a complete end-to-end record of cross-border processing and international supply chain information. </P>
                    <P>To date, ACE has provided the infrastructure to support the establishment of 41 Importer Accounts. These accounts have access to a quick view of their importing and compliance history as well as the functionality to print numerous reports. This functionality also provides for interaction between the Accounts and CBP in the form of an Action Plan and a Significant Activity Log. Both the Trade Community and CBP now have access to an electronic automated Harmonized Tariff Schedule. Near term functionality for ACE will include the establishment of 1100 Accounts to include brokers, importers and truck carriers. The establishment of these accounts will allow the account holders to pay duties and fees on a Monthly Periodic Statement (April 2004) and provide for the capability of truck carriers to file an advanced electronic Truck Manifest (October 2004), which will support the legislative requirements of the Trade Act of 2002. </P>
                    <HD SOURCE="HD1">Time Period for Implementing Advance Cargo Data Reporting </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Consideration should be given to making the advance reporting provisions operational on a region-by-region “roll out.” There should also be a liberal “grace period” permitted prior to enforcement of the new regulations so that both Government and the trade would have sufficient time to adjust to the new security requirements without disorganization or disruption. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         It is stressed that the differing effective dates of these regulations may be further delayed for the several modes, both inbound and outbound, as already provided variously in §§ 122.48a(e) (for inbound air cargo), 123.91(e) (for inbound rail cargo), 123.92(e) (for inbound truck cargo), and 192.14(e) (for outbound cargo, all modes). Only as to incoming vessel cargo is there a firm effective date of March 4, 2004, by which time all participating advance cargo data filers must be operational on the Vessel Automated Manifest System (Vessel AMS). 
                    </P>
                    <P>However, no matter when the various regulations in this final rule go into effect, CBP will adopt a phased-in enforcement process for these Trade Act Regulations similar to that which was utilized when the 24-Hour Rule was implemented. Depending on the circumstances, CBP may take an “informed compliance” approach during a short period following the effective date of the rule. In appropriate circumstances, this approach would consist of performing audits of the carriers' and NVOCCs' (Non Vessel Operating Common Carriers’) submissions and advising their owners or operators of problem areas that could have been subject to enforcement action. </P>
                    <P>Following an initial 2-month period after issuance of the 24-Hour rule, CBP created an enforcement approach that focused first on egregious violations. The CBP experienced an enormous decrease in the instances of such problem submissions immediately before, and after, expiration of the initial period when the “informed compliance” approach was implemented. </P>
                    <P>Therefore, in implementing these Trade Act Regulations, CBP has demonstrated experience in implementing a phased-in enforcement strategy and expects to develop similar plans with respect to these new advance cargo reporting requirements. </P>
                    <P>Furthermore, as with the 24-hour rule, CBP intends to continue to work with the trade to achieve compliance with the requirements of these regulations. However, CBP does not believe that a region-by-region implementation of the regulations would be either advantageous or advisable under the circumstances. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Two commenters wanted a uniform advance notification enforcement date for all modes to include both outbound and inbound shipments. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The implementation dates for all modes will vary, due to the readiness and availability of the 
                        <PRTPAGE P="68144"/>
                        automated systems that support each mode and the degree to which the necessary technology is available to particular modes of transportation. This fully comports with the mandate of section 343(a)(3)(D) and (E), as amended. 
                    </P>
                    <HD SOURCE="HD1">Bond Issues </HD>
                    <P>
                        <E T="03">Comment:</E>
                         A question was presented as to whether electronic filers of advance cargo data through the Automated Manifest System (AMS) would need to possess an international carrier bond. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Other than Automated Broker Interface (ABI) filers in the air environment (consisting of importers and brokers) (see § 122.48a(c)(2) in this final rule), electronic filers through AMS (whether Vessel, Air or Rail AMS) must possess an international carrier bond under 19 CFR 113.64. By contrast, an ABI filer of advance cargo data, that is an importer, would need to possess an amended basic importation and entry bond, as described in § 113.62(j)(2) in this final rule; and an ABI broker who files advance cargo data would be obligated under 19 U.S.C. 1641 and 19 CFR part 111 to do so in the manner and in the time period prescribed in § 122.48a in this final rule. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A Customs bond could be written as a single transaction bond or as a continuous bond. It was recommended that CBP provide in the regulations that any bond needed for reporting cargo information prior to arrival be a continuous bond. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP does not agree with the commenter. The commenter suggests that the rule be amended to state that all bonds required in support of presentation of advanced manifest information must be continuous bonds. Continuous bonds are bonds taken out by principals that are in effect for a period of time (usually 1 year, with automatic renewal unless terminated) and insure all relevant transactions occurring in that period of time. In contrast, single transaction bonds are bonds that are taken out one at a time and are presented to insure only a single transaction or arrival. The rule only requires that a bond be posted. It does not matter whether that bond is continuous or single transaction and there is no need to provide for a bond type restriction. 
                    </P>
                    <HD SOURCE="HD1">Liability Concerns </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Where the party presenting information to CBP had acquired this information from another, and the information was determined to be false, clarification was requested as to how this would play a role in the penalty/liquidated damage process. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Mindful of the requirements of section 343(a)(3)(B), as amended (19 U.S.C. 2071 note, section (a)(3)(B)), CBP will take the facts and circumstances of any such situation into account in determining whether a penalty/liquidated damages claim should be initiated and whether and/or to what extent such a claim should be mitigated. The CBP intends to issue mitigation guidelines in this matter. 
                    </P>
                    <HD SOURCE="HD1">Submission of Cargo Data in Advance of Arrival or Departure </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Having to present cargo information in advance for both exports and imports would add severely to port congestion in the U.S., and thus raise the costs and burdens of both types of trade. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP disagrees. The receipt of advance electronic information will reduce port congestion because CBP can make enforcement decisions before conveyances arrive in the United States. This has been true in the vessel environment for some time, and has been improved upon under the 24-hour rule because CBP can perform examinations overseas via the Container Security Initiative (CSI). Furthermore, CBP will use in implementing this final rule a phased-in compliance program, similar to that described above for the 24-Hour Rule, in order to make sure that technical violations do not unnecessarily disrupt the flow of goods across the U.S. border. Therefore, there is no compelling reason to conclude that congestion at U.S. ports will result. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Further explanation was sought as to the basis for the differences among the time-frame reporting requirements for inbound and outbound shipments in all modes of transportation. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Generally speaking, and as further discussed for each individual mode, 
                        <E T="03">infra,</E>
                         in determining the timing for transmittal of advance cargo data, CBP, as directed by the statute, took into account the differences existing among the different modes of transportation, both inbound and outbound, including differences in commercial practices, operational characteristics, and the technological capacity to collect and transmit information electronically; and, as the law also directed for each mode, CBP undertook to balance the likely impact on the flow of commerce with the impact on cargo safety and security. 
                    </P>
                    <HD SOURCE="HD1">Miscellaneous Issues </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Concern was expressed about information security requirements associated with advance notifications for shipments of radioactive material. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Advance cargo information is transmitted to and received by CBP on a secure and encrypted data line. As for cargo arriving by vessel, manifest information for such cargo is not available for public disclosure until after the vessel has arrived; and, as previously indicated, in accordance with 19 U.S.C. 1431(c)(2)(A) &amp; (B), such information may be exempted from disclosure in the interest of national defense pursuant to 5 U.S.C. 552(b)(1), or where the disclosure would pose a threat of personal injury or property damage. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         In the future, CBP should allow the electronic submission of comments. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Requiring written comments in response to a notice of proposed rulemaking is a matter of agency policy that is beyond the scope of this particular rulemaking. However, it is observed that comments via e-mail were invited and accepted regarding the development of the proposed rulemaking in this case (68 FR at 43575). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A format for Frequently Asked Questions (FAQs) should be established for each mode of transportation on the CBP Web site, which should be regularly updated with new or revised questions. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         CBP intends to post FAQs for each mode of transportation on the CBP Web site (
                        <E T="03">http://www.cbp.gov</E>
                        ), which will be updated as necessary. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter offered to provide, at no cost to the Government, cargo inspections at the point of origin and then transmit the results of the inspections by way of a CBP-approved electronic data interchange system. The commenter requested only that CBP accept such inspected shipments as “low risk” and thus eligible for expedited clearance upon arrival. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         In effect, CBP believes that the same results would be achievable by joining the C-TPAT program (The Customs-Trade Partnership Against Terrorism). As already explained, participation in C-TPAT is considered as a positive factor in targeting shipments to determine whether cargo needs to be held at the port of arrival for examination or receipt of further information. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Additional instruction was sought as to what terms would satisfy the requirement for a precise description for incoming cargo (§ 4.7a(c)(4)(vii); and proposed §§ 122.48a(d)(1)(ix) and (d)(2)(iii), 123.91(d)(5), and 123.92(d)(9)). In 
                        <PRTPAGE P="68145"/>
                        particular, for automotive producers, it was stated that obtaining a complete and correct list of the Harmonized Tariff Schedule (HTS) numbers for all exports of automotive parts and components could be a daunting task. One shipment could contain many types of original equipment manufacturer (OEM) or replacement parts; it was instead urged that CBP accept a generic cargo description such as “New Autoparts” regardless of the mode of transportation involved. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         CBP will issue an Acceptable and Non-Acceptable cargo description list as was done with the 24-Hour Rule for incoming vessel cargo. This list will be the same for all modes of transportation. 
                    </P>
                    <P>Generally speaking, CBP has defined a precise cargo description as a description precise enough for CBP to be able to identify the shapes, physical characteristics, and likely packaging of the manifested cargo so that CBP can discern any anomalies in the cargo when a container is run through imaging equipment. Also, the description must be precise enough to identify any goods which may emit radiation. </P>
                    <P>The requirement that a carrier/filer use cargo descriptions that would not be considered vague should not be overly burdensome. The CBP has undertaken continuous efforts prior to and since the promulgation of the 24-hour Advance Manifest Rule in the sea environment to educate all filers on cargo descriptions that would be considered vague as well as on issues raised by trade representatives. The cargo descriptions that are considered vague have been posted on the CBP Web site (Frequently Asked Questions) since March 2003. The descriptions were not designed to force carriers/filers to achieve entry level descriptions. In most cases, the descriptions require only one or two further qualification descriptors. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Participation in such an electronic data interchange as the Automated Manifest System (AMS) should be covered by regulations pursuant to the Administrative Procedure Act that provide uniform requirements for enrollment and acceptance into these electronic filing programs, and that govern the suspension, revocation or modification of participation in these programs. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Participation in the electronic systems described in this rulemaking was formerly voluntary as part of the National Customs Automation Program (NCAP) described in 19 U.S.C. 1411(a). As part of the Trade Act of 2002, Congress amended section 1411 to permit CBP to mandate use of the electronic systems of NCAP. To effectuate the requirement in section 343 of the Trade Act of 2002 for the electronic transmission of section 343 cargo information in compliance with Congress's timetable, CBP is mandating use of several of these existing NCAP electronic systems. 
                    </P>
                    <P>
                        The criteria for establishing connection with these systems were set forth in the notices of the tests of these systems (
                        <E T="03">e.g.</E>
                        , for the Vessel Automated Manifest System (Vessel AMS) program, see 61 FR 47782 (September 10, 1996), and 67 FR 77318 (December 17, 2002)); the eligibility criteria for these programs also appear on the CBP Web site: 
                        <E T="03">http://www.cbp.gov/xp/cgov/import/operations_support/automated_systems/ams/</E>
                        . 
                    </P>
                    <P>
                        Because electronic filing is now mandatory, CBP will not prohibit or restrict use of the required systems by filers as it might under a voluntary test program. The CBP does reserve the right to take necessary technical steps to deny connections in the event of electronic attacks (
                        <E T="03">e.g.</E>
                        , denial of service attacks), but otherwise access will be available. Therefore, no procedures regarding suspension or revocation of access to these systems are required. Instead, CBP will ensure compliance with mandatory electronic filing requirements through monitoring by account managers, penalty assessments or claims for liquidated damages, as appropriate to the circumstances. 
                    </P>
                    <HD SOURCE="HD1">Vessel Cargo Destined to the United States </HD>
                    <HD SOURCE="HD2">Submission Time Frames </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Seven commenters advocated that the pre-arrival and post-loading data submissions acceptable for the other modes should also be acceptable for maritime cargo. There should be no significant differences in risk between air and maritime cargoes. The 24-hour pre-loading requirement could disrupt “Just In Time” (JIT) delivery systems. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         As explained in the 24-hour rule (67 FR at 66319) and as reiterated in the proposed rule in this case (68 FR at 43577), the 24-hour pre-lading requirement for vessel cargo, especially containerized vessel cargo, is tied inextricably to the Container Security Initiative (CSI), a core element of which is to pre-screen vessel cargo containers at the foreign port of departure before they are loaded onto the vessel for shipment to the United States. To enable such pre-screening to be done fully and successfully, it is essential that the related cargo data be transmitted to CBP at least 24 hours prior to lading the cargo aboard the vessel. 
                    </P>
                    <P>In relation to JIT deliveries, CBP requires the electronic transmission of cargo declaration information 24 hours in advance; CBP is not requiring that the cargo be ready for inspection or that the cargo be at the dock. However, CBP recognizes the 24-hour pre-lading reporting may occasion some changes in the practice of sometimes adding last minute loads to vessels, but only if such loads were not manifested 24 hours prior to their lading. </P>
                    <HD SOURCE="HD1">Exemption From Advance Filing </HD>
                    <HD SOURCE="HD2">Bulk/Break Bulk Cargo </HD>
                    <P>
                        <E T="03">Comment:</E>
                         It was requested that consideration be given to exempting bulk cargoes from the requirement of electronically having to submit cargo declarations. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         CBP has given bulk, and some break-bulk shipments, exemptions from the requirement to file 24-hours prior to loading, but these entities will still be required to file their cargo declarations electronically. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Section 4.7(b)(2), Customs Regulations (19 CFR 4.7(b)(2)), implied, erroneously, that only vessels exclusively carrying bulk or break bulk cargo could be exempted from having to report such cargo 24 hours prior to loading the cargo aboard the vessel in the foreign port. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP agrees. Section 4.7(b)(2) will be revised to make it clear, in agreement with § 4.7(b)(4), that for vessels that carry both non-exempt cargo and exempt bulk/break bulk cargo, only the non-exempt cargo must be reported on the electronic cargo declaration 24 hours prior to loading such cargo in a foreign port. 
                    </P>
                    <HD SOURCE="HD1">Data Elements </HD>
                    <HD SOURCE="HD2">Precise Cargo Description; 6-Digit HTS Number </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Section 4.7a(c)(4)(vii) stated that either a precise cargo description or the 6-digit Harmonized Tariff Schedule (HTS) number for the cargo had to be provided. However, the Vessel AMS system in fact required a narrative cargo description and (if desired) an HTSUS 6-digit number for the cargo, or the transmitted bill of lading would be rejected. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Currently, AMS does require text in the description field of the electronic transmission, or AMS will reject the transmission, even though a 6-digit HTSUS number is also provided in the appropriate field of the transmission. The CBP intends shortly to effect programming changes to allow for either a precise cargo description or 
                        <PRTPAGE P="68146"/>
                        the 6-digit HTSUS number; but until such time as these programming changes are adopted, AMS participants which provide the HTSUS number will also have to enter a cargo description in the description field of the electronic transmission. However, as an alternative to providing a precise cargo description in the description field of the transmission, the applicable 6-digit HTSUS number may instead be included in the description field to satisfy the current programming requirement that some text appear in this field. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         In light of the recent final rule regarding corporate compliance activity (CBP Dec. 03-15, 68 FR 47455; August 11, 2003), the question arose as to whether the submission by the electronic filer of the 6-digit HTSUS number via AMS would fall within the purview of “Customs business” under 19 CFR part 111. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         “Customs business” does not involve the mere electronic transmission of data received for transmission to CBP (19 CFR 111.1). Moreover, the 6-digit HTSUS number is intended exclusively for ensuring cargo safety and security, and not for determining merchandise entry or for any other commercial admissibility or enforcement purposes which fall within the scope of Customs business. An 8-digit HTSUS number is needed and is used for merchandise entry purposes. 
                    </P>
                    <P>The “corporate compliance activity” rule dealt with the conduct of “Customs Business” as established by statute (19 U.S.C. 1641). The activities covered under that rule all relate to the entry of merchandise, not its manifesting. Reporting commodity identification by use of 6-digit HTSUS numbers, rather than the more specific 8- or 10-digit designations, was included because there is international agreement and uniformity at the 6-digit level. Use of HTSUS designations is merely offered by CBP as an option to be used in place of a precise narrative description of cargo content. </P>
                    <HD SOURCE="HD2">Definition of Shipper; Consignee </HD>
                    <P>
                        <E T="03">Comment:</E>
                         A number of questions were raised with respect to the provision in proposed § 4.7a(c)(4)(viii) that, for consolidated shipments, the shipper listed on the house bill of lading be the owner and exporter of the goods from the foreign country. In sum, it was basically asserted that this would be inconsistent with the commercial practice of the transportation trade which essentially identified the shipper as the party with whom the carrier had a contractual relationship, and that it was improper for the U.S. Government to unilaterally change this practice. It was also said to be at odds with the prevailing requirement that the foreign vendor or manufacturer be listed as the shipper on a house bill. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         In light of the above comments, CBP has closely reviewed what shipper information must be listed on a house bill of lading for a consolidated shipment. Cargo information collected under this rule is not intended for commercial purposes, but rather for purposes of ensuring cargo safety and security as part of an antiterrorism national security initiative (see 19 U.S.C. 2071 note, section (a)(3)(F)). Otherwise stated, it is essential that CBP receive house level information on the identity of the shipper that will enable an accurate national-security risk assessment concerning the related cargo. To this specific end, CBP will thus accept as the shipper on a house bill of lading the identity of the foreign vendor, supplier, manufacturer, or other similar party. Also, the shipper's address must be a foreign address. By contrast, CBP will not accept the carrier, NVOCC, freight forwarder or consolidator as valid house level information on the identity of the shipper. 
                    </P>
                    <P>Accordingly, proposed § 4.7a(c)(4)(viii), as well as proposed §§ 122.48a(d)(1)(x), 122.48a(d)(2)(vi), 123.91(d)(6) and 123.92(d)(11), are thus revised in this final rule. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Greater guidance was requested as to what would be acceptable in the Notify Party field of the electronic transmission (proposed § 4.7a(c)(4)(ix)). It was thought that if there was any other commercial party listed in the bill of lading, such party would be included in the Notify Party field; otherwise, this field would be left blank. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP requires that if the cargo has not yet been sold or is shipped “to order”, and there is no consignee information, then the Notify Party field must include the identity of a responsible party in the United States. Such a responsible party could include any other commercial party that is listed in the bill of lading for delivery or contact purposes. 
                    </P>
                    <HD SOURCE="HD2">Date and Time of Departure of Vessel From Foreign Port </HD>
                    <P>
                        <E T="03">Comment:</E>
                         With respect to proposed § 4.7a(c)(4)(xv) and (xvi), it was asserted that the information concerning the date and time that the vessel departed for the United States as reflected in the vessel log could not be provided 24 hours prior to foreign lading of the cargo aboard the vessel. 
                    </P>
                    <P>Also, a question arose concerning whether these data elements referred to the date and time of departure from the foreign port of loading with respect to which the 24-hour declaration was made, or the date and time of departure from the last foreign port before sailing to the United States. </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The date and time of departure should capture the date and time that the vessel departs from the foreign port of loading with respect to which the 24-hour cargo declaration is made (see § 4.7(b)(2) in this final rule). However, CBP will not require the information as to the date and time of vessel departure to be transmitted 24 hours prior to the lading of the cargo at the foreign port. Instead, the time frame for reporting these two data elements will be either: (1) No later than 24 hours after departure from the foreign port of lading, for those vessels that will arrive in the United States more than 24 hours after sailing from that foreign port; or (2) no later than the time of presentation of a permit to unlade (Customs Form (CF) 3171, or electronic equivalent), for those vessels that will arrive less than 24 hours after sailing from the foreign port of lading. Proposed § 4.7a(c)(4)(xv) and (xvi) are revised in this final rule to include these additional provisions. 
                    </P>
                    <P>Also, the transmission of these date and time data elements may be handled as an amendment to the vessel header, which will eliminate the need for each bill of lading to be amended. </P>
                    <HD SOURCE="HD1">Vessel AMS Issues </HD>
                    <HD SOURCE="HD2">Importer Participation in Vessel AMS </HD>
                    <P>
                        <E T="03">Comment:</E>
                         It was stated that the party most likely to have the information needed for targeting was the U.S. importer, while the incoming carrier would only be able to provide information which was received from the charterer of the vessel. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         CBP finds that allowing importers to participate in advance electronic filing through Vessel AMS would at this time be neither advisable nor practicable, given the current design and functionality of the Vessel AMS system and the lack of consensus in the trade community as to whether importers should furnish sea cargo data to CBP. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A shipper should be allowed to file advance cargo data through AMS. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Again, given the prevailing operation of the Vessel AMS, CBP finds that allowing freight forwarders who are not NVOCCs, and other parties identified as “consolidators,” even though they may be NVOCCs (see 68 FR at 43577) to 
                        <PRTPAGE P="68147"/>
                        participate in the Vessel AMS electronic data interchange system would at this time be neither advisable nor practicable. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         It was stated that the Shipper field in Vessel AMS could not accommodate more than 3 or 4 lines of information. This could prove inadequate in the case of consolidated shipments where there could be multiple shippers. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         This inability of the Shipper field in Vessel AMS to capture multiple shipper data is academic inasmuch as CBP requires that for each shipper/consignee relationship a separate bill of lading be issued. This mandate for a separate house bill of lading for each shipper/consignee relationship constitutes a critical component for automated targeting purposes in identifying high-risk shipments. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         With respect to proposed § 4.7(b)(5), which provided that carriers, and participating NVOCCs, would need to become automated at all ports of entry where their cargo would initially arrive, it was asked whether it would be the Vessel AMS computer mainframe's problem to forward the carrier's transmission to the appropriate Customs port of entry. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Ocean carriers and NVOCCs currently operational on Vessel AMS, although not at all ports of entry, will now be required to become operational at all such ports. Any carrier or NVOCC that hereafter becomes automated on Vessel AMS will thereby be automated at all ports. Since the automation of electronic filers through Vessel AMS will per se encompass all ports of entry, proposed § 4.7(b)(5) is revised in this final rule by removing the phrase, “where their cargo will initially arrive”. However, carriers must indicate in their respective electronic transmissions each port of arrival where their incoming cargo will be discharged. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Non Vessel Operating Common Carriers (NVOCCs) should be required to electronically present advance cargo information directly to CBP. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP disagrees. As discussed in the proposed rule (68 FR at 43576-43577), certain segments of the trade in fact urged that advance cargo information filing by NVOCCs be eliminated due to operational problems with Vessel AMS, that resulted when NVOCCs, as opposed to the incoming carriers, filed cargo data directly with CBP. Nevertheless, in consideration of the competitive relationships that exist in the international freight forwarding field, CBP continues to believe that NVOCCs who wish to do so may become automated on Vessel AMS, but that they should not be compelled to do so. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         It was observed that a large number of NVOCCs operational on Vessel AMS seemed to opt out of the system at various ports, for apparently no authorized reason. Vessel carriers were said to be unable to audit or police this. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Those NVOCCs who choose to become automated on Vessel AMS must be automated in all ports. While NVOCCs do have the ability to decertify in AMS, they would then be required to submit detailed information to carriers for transmission to CBP for all ports of discharge. If a question should arise as to whether or not an NVOCC is automated, the vessel carrier may contact its CBP client representative for verification. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         It was asked whether there was a maximum reporting window for transmitting cargo data in advance through Vessel AMS. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Vessel AMS has the capacity to retain electronic transmission information up to a maximum of nine months prior to the cargo's Estimated Date of Arrival (EDA). 
                    </P>
                    <HD SOURCE="HD1">Confidentiality </HD>
                    <P>
                        <E T="03">Comment:</E>
                         It was unclear whether the shipper specific information would be publicly disclosed, and whether such information from both master and house bills of lading would be involved. It was remarked that disclosing this information would defeat the purpose of direct filing by NVOCCs. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Information collected pursuant to 19 U.S.C. 1431, including information from both master and house bills, is available for public disclosure in accordance with section 1431(c). However, under the authority of section 1431(c)(1)(A), information relating to the identity of a foreign shipper to an importer or consignee in the United States will not be disclosed if a claim for confidential treatment for such information is made by using the procedure prescribed in 19 CFR 103.31(d)(1). 
                    </P>
                    <HD SOURCE="HD1">Implementation Period for Rule </HD>
                    <P>
                        <E T="03">Comment:</E>
                         It was thought that 90 days was too short a period from the date of publication of the final rule within which a non-automated carrier would need to develop software and programming in Vessel AMS. A period of 120 days was requested. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP believes that 90 days is an adequate and reasonable time frame within which to permit a non-automated vessel carrier to become automated on Vessel AMS. The CBP will continue to work with the trade to achieve compliance with these advance cargo reporting provisions. 
                    </P>
                    <P>In selecting 90 days following publication as an implementation period for mandatory vessel AMS participation, CBP sought to strike a proper balance between the needs of the affected public in adjusting to the new requirements, and meeting the needs of the United States in implementing anti-terrorism measures without undue delay. Ninety days strikes that balance. </P>
                    <HD SOURCE="HD1">Procedure for Amending Cargo Declarations </HD>
                    <P>
                        <E T="03">Comment:</E>
                         The proposed rule did not mention the procedures for amending electronic cargo declarations following their transmission. This would also apply for goods that were sold while in transit. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Complete and accurate information would need to be presented to CBP for cargo to be laden aboard the vessel no later than 24 hours prior to lading the cargo aboard the vessel at the foreign port. As for any changes in the cargo information already transmitted, the procedures for amending the cargo declaration including discrepancy reporting regarding vessels as well as all other modes will be the subject of a separate rulemaking. Prior to the promulgation of new rules concerning discrepancy reporting, the procedures for phased-in compliance as explained above will be employed to address changes that must be made to the transmitted cargo declaration. It should be recognized that each time a bill of lading is amended, it may be subject to increased targeting and at risk for examination. 
                    </P>
                    <HD SOURCE="HD1">Enforcement </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Procedures should be outlined for cargo that arrived without pre-notification or with incomplete information. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         In all modes of transportation discussed in this rulemaking, the carrier must notify CBP immediately upon arrival or as soon as it realizes that it did not submit the proper information. The carrier should then present or transmit the cargo declaration information. Upon arrival in the U.S. port, the cargo declaration will be placed on hold until CBP has had the opportunity to review the documentation, and conduct any necessary examinations. Appropriate penalties may also be issued. If CBP determines that this has become a common occurrence for a carrier, this could eventually lead to denial of a permit to unlade. Additionally, CBP will notify the United States Coast 
                        <PRTPAGE P="68148"/>
                        Guard of a vessel with unmanifested cargo that is scheduled to arrive. If the arriving cargo is food, CBP and FDA are working closely together to ensure they coordinate policies and procedures for dealing with movement of the cargo. 
                    </P>
                    <HD SOURCE="HD1">Miscellaneous Matters </HD>
                    <P>
                        <E T="03">Comment:</E>
                         The view was expressed that the ocean carrier would be reluctant to accept an NVOCC's shipment due to liability concerns, and/or would react, to protect itself from CBP enforcement, by imposing extraordinary and erroneous evidentiary or indemnity obligations on the NVOCC. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP is currently programming Vessel AMS to accept additional bill of lading types that will allow NVOCCs to submit commodity information to CBP that will protect proprietary information from the carrier, and that will enable the vessel carrier to submit master bills of lading to CBP pertaining to the transportation information for the cargo. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         In proposed § 4.7(b)(1), it was stated that the original and one copy of the manifest must be ready for production on demand. It was asserted that the only original manifest carried on board the vessel upon arrival would be the dangerous goods manifest. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Under § 4.7(b)(1), there is no requirement that the original vessel cargo declaration be carried aboard the vessel in those cases where the cargo declaration has already been filed in advance electronically. The CBP decided not to enforce the paper cargo declaration (Customs Form (CF) 1302) rule for formal entrance if a carrier or NVOCC has successfully automated. However, where the cargo declaration has been filed in advance electronically, and a paper copy is not aboard the vessel, the carrier will be afforded a reasonable time within which to generate a paper cargo declaration, should a paper copy be requested by CBP. The CBP will periodically assess this policy to ensure that it is not having an adverse effect on operations. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The proposed rules, especially those related to ocean imports, did not address the status of shippers' associations as shippers and transportation intermediaries and apparently did not give them the right to file the required manifest information directly to CBP. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP has determined that shippers associations are not licensed or registered with the Federal Maritime Commission (FMC). Moreover, such associations cannot be construed to be carriers of cargo in the same sense as ocean carriers or NVOCCS. Therefore, shippers associations will not be permitted to participate in Vessel AMS. 
                    </P>
                    <HD SOURCE="HD1">Air Cargo Destined to the United States </HD>
                    <HD SOURCE="HD2">Time Frame Requirements for Transmitting Advance Cargo Data </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters requested that the time frames in proposed § 122.48a(b) in which the electronic cargo information was transmitted be reduced and that exceptions for certain points of origin be included. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP recognizes the business practices of the air cargo industry and the necessity of adequate time to properly analyze the electronic cargo information and to deploy inspectional resources when required. These issues were carefully considered when establishing the time frames specified in these regulations. 
                    </P>
                    <P>Specifically, CBP weighed the question of an appropriate time frame for air from many angles. To better gauge industry requirements, CBP conducted public meetings (one for each modality), and set up an email address to facilitate the submission of comments by carriers, importers, exporters, freight forwarders, customs brokers, other U.S. Government agencies, foreign governments, as well as local, national and international trade organizations, and private citizens, etc. It should be noted that this elective comment period was in addition to the formal comment period required for the Notice of Proposed Rule Making. The CBP also met intensively with the Treasury Advisory Committee on the Commercial Operations of the U.S. Customs Service (COAC), which resulted in additional unified recommendations for each modality. The CBP assessed internal operational considerations such as the speed at which the various electronic data interchanges are able to process information, the time required for CBP personnel to review the output and determine the appropriate action, and the time needed to deploy personnel to respond. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Further explanation was requested on whether the time frames for flights from nearby foreign areas in proposed § 122.48a(b)(1) included such flights to the territories of the United States, such as Guam and Puerto Rico. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The time frame for nearby flights would include such flights to Puerto Rico because it is part of the Customs territory of the United States. However, flights to Guam are not included in the advance cargo reporting requirements, as Guam is not part of the Customs territory. The CBP finds that a distinction in the time frames for advance filing based upon geographical considerations, as opposed to the duration of the flight, is more administratively feasible. 
                    </P>
                    <HD SOURCE="HD1">Air Freight Forwarder Issues </HD>
                    <P>
                        <E T="03">Comment:</E>
                         It was asked whether CBP would permit foreign indirect air carriers (non-U.S.-based freight forwarders that issue their house bills of lading for air freight shipments) to qualify as one of the authorized filers of information through the Air Automated Manifest System (Air AMS). 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Other than the incoming air carrier, parties eligible to transmit inbound electronic air cargo information are enumerated in § 122.48a(c)(1) in this final rule. Any foreign indirect air carrier that is not one of the parties specified in § 122.48a(c)(1) would have to fully disclose and present the required data for the inbound air cargo to the incoming air carrier or other eligible electronic filer, as applicable, which would then present such data to CBP. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         It was advocated that CBP require freight forwarders, Customs brokers and consolidators to participate in Air AMS. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP disagrees. Such parties may elect to provide the data directly to CBP if they are one of the parties specified in § 122.48a(c)(1), or they may provide the data to the incoming air carrier which will transmit such data directly to CBP. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Two commenters wanted to know whether it was CBP's intention that freight forwarders filing advance cargo data obtain two bonds—an international carrier bond and a custodial bond. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         A freight forwarder filing advance air cargo data would be required to have an international carrier's bond under § 122.48a(c)(2). In addition, if the freight forwarder or any other eligible party were responsible for supplying in-bond information and for transporting cargo in-bond under the provisions of part 18 of the Customs Regulations (19 CFR part 18), such party would also need a Customs custodial bond. 
                    </P>
                    <P>
                        The international carrier bond is required of carriers arriving from foreign locations. That bond exists to guarantee performance with regard to (among other things) conveyance arrival, entry and clearance, cargo manifesting and disposition, and passenger and crew control. The conditions of the international carrier bond appear at 19 CFR 113.64. A custodial bond is required of any party that transports merchandise domestically, either between ports of entry or within a single 
                        <PRTPAGE P="68149"/>
                        port of entry, before that merchandise has been entered for consumption with duties paid thereon and its admissibility into the commerce determined. The custodial bond conditions appear at 19 CFR 113.63. The custodian of the merchandise guarantees compliance with all regulations governing the receipt, carriage, safekeeping and disposition of merchandise transported or held. 
                    </P>
                    <HD SOURCE="HD1">Diversion/Fuel Stop Issues </HD>
                    <P>
                        <E T="03">Comment:</E>
                         It was asked whether the rule allowed for aircraft to stop for fueling at a U.S. location prior to arriving at its final destination. Four commenters requested that fuel stops be exempt from reporting requirements from the U.S. port of arrival to the port of destination. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Section 122.48a does not prohibit an aircraft from including a fuel stop in its itinerary; however, that stop may be the port of arrival in the United States for purposes of § 122.48a(b). Fuel stops will not be excluded from the advance reporting requirement because it is vital to security to target at the first port of arrival and, if necessary, to examine cargo at that location. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         If an aircraft were diverted for reasons such as weather or equipment problems, it was requested that this not be considered part of the manifest reporting requirement if passengers and cargo were not to be discharged there. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP understands that aircraft may be diverted due to weather and/or equipment problems. When this situation occurs, the airline must notify CBP at the designated first port of arrival (the diverted port) as soon as it realizes it is not going to initially reach the original port of arrival. The carrier would then need to re-transmit the electronic cargo information with corrections to reflect the new (diverted) arrival port. 
                    </P>
                    <HD SOURCE="HD1">Air AMS Testing/Problems </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Outstanding operational programming issues should be completed prior to the implementation of the final rule. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP is diligently working on an outstanding list of operational issues and will continue to correct these issues. Under § 122.48a(e)(2), the implementation date for advance air cargo reporting may be delayed if necessary modifications to the CBP-approved electronic data interchange system are not yet in place. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Qualified air freight forwarders electing to participate in advance electronic cargo reporting should be tested on the approved data interchange system prior to the implementation of the final rule. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Appropriate testing will be given to all parties who develop Air AMS communications with CBP. Those parties who elect to use a service provider will be tested via the service provider. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Programming should be provided between the Automated Broker Interface (ABI) and the Air AMS system so that data information could be shared (alternate filers could be brokers and forwarders). 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Cargo selectivity information provided through ABI is distinct from the electronic cargo information required through Air AMS under § 122.48a. The data elements to satisfy compliance with this regulation must be provided through Air AMS; Air AMS is accessible to ABI filers. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The Air AMS system should be changed to preclude an inward air carrier from refusing to authorize (nominate) another eligible party as an agent who had elected to transmit consolidated cargo data directly to CBP; and the system should be programmed to notify such other party of its authorization (nomination) by the inward carrier. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The Air AMS system will independently accept information from each of the parties that supply data to satisfy the advance cargo reporting requirements of § 122.48a. In other words, the inward carrier will no longer need to authorize or nominate another eligible party in order to enable that party to supply house air waybill information to CBP. The identification of another eligible filer in the agent (“AGT”) line will be merely for the purpose of notifying CBP that this party will transmit the house air waybill information, which may be effected either prior to or after the carrier's transmission of the master air waybill record to CBP. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The Air AMS system should be changed to allow for the transmission of a notification that air cargo data had been received or that the air cargo manifest had been accepted with the date and time specified. This feature was said to be currently available in Vessel AMS. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The Air AMS transmits a Freight Error Report message if an air waybill record does not pass certain data acceptance edits. In addition, the Air AMS also provides a Freight Status Query feature that allows an Air AMS participant to query the status of an air waybill record. This feature is available to the Air AMS participant that transmitted the original message and to Air AMS participants that have been properly nominated by the carrier that transmits the master air waybill data. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter was of the opinion that airlines did not want to be obligated to input house air waybill information on behalf of an air freight forwarder. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Under § 122.48a, unless another qualified party elects to participate in the Air AMS system, the relevant house air waybill information must be furnished to the incoming air carrier for presentation to CBP. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         It was asked how a carrier would provide any required cargo data if the records were in the possession of a third party that was not one of the parties identified in proposed § 122.48a(c)(1). 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Under § 122.48a(c)(4), any third party entity in possession of required data for inbound air cargo must fully disclose and present such data to the carrier for presentation to CBP. 
                    </P>
                    <HD SOURCE="HD1">In-Bond Issues </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Participants in Air AMS should be permitted to create subsequent in-bond transactions to close out air manifests at both the master air waybill and house air waybill levels. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         This is included in the regulation (see § 122.48a(a)(1) in this final rule). In-bond information may of course be included at both the master and house air waybill levels (see § 122.48a(d)(1)(xvi) and (d)(2)(viii) in this final rule). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         It was thought that Air AMS could not handle in-bonds for one consolidated express shipment. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The Air AMS system is capable of processing in-bond information for all house air waybills under a consolidated master air waybill. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The Air AMS programming should be altered to allow for more than one in-bond warehouse per location. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Cargo covered by each master air waybill may be transferred to any warehouse location with a unique FIRMS (Facilities Information and Resources Management System) code within the limits of a port of entry. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The scope and timing of the carrier's transmission of any in-bond information should be clarified. Specifically, it was asked whether it would be necessary to allow transmission of this information after arrival of the cargo in the United States, and whether such information would be used for the movement of the subject cargo from the first port of arrival to the master bill destination location. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The data elements specified in § 122.48a(d)(1), including 
                        <PRTPAGE P="68150"/>
                        any in-bond information in § 122.48a(d)(1)(xvi), if applicable, will be analyzed by CBP for the purposes of identifying high-risk cargo. Such data elements must be supplied within the respective advance time frames prescribed in § 122.48a(b). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         In-bond information (from a party other than the incoming carrier) might not be known by origin or prior to its arrival in the United States. It was asked whether information related to the subsequent in-bond movement of the cargo could thereafter be transmitted to CBP prior to the in-bond movement being authorized. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP recognizes that the in-bond destination for cargo covered by house air waybills may not be known prior to the arrival of the aircraft in the United States. If such information is provided outside of the required time frame prescribed in § 122.48a(b), it will be treated as a change to the original information. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         It was asked whether CAFES (Customs Automated Forms Entry System) was compatible with Air AMS for use on in-bonds. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         CAFES is not yet compatible with Air AMS for merchandise arriving via air. 
                    </P>
                    <HD SOURCE="HD1">Truck/Air Issues </HD>
                    <P>
                        <E T="03">Comment:</E>
                         The use of Air AMS should be allowed for goods transiting the border by truck in lieu of a truck manifest. It was advocated that Customs brokers at the border should be required to transmit data through Air AMS for cargo that originated as an air shipment and arrived in a contiguous foreign country, notwithstanding that the cargo would be crossing the border into the United States by truck. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The Air AMS system is the electronic cargo reporting data interchange for merchandise arriving via an aircraft. Merchandise arriving via another mode of transportation, including by truck, must be reported in the manner specified for such mode. Thus, if the merchandise crosses the U.S. border on a truck, such merchandise is not considered to be an air shipment, notwithstanding that such cargo may have arrived in the contiguous foreign country by air. As such, in the event that merchandise, which was previously reported to arrive via an aircraft, should change its mode of transportation prior to arrival in the United States, the previously transmitted information must be cancelled and then reported in the manner appropriate to the actual mode of transportation employed in bringing the merchandise into the United States. 
                    </P>
                    <HD SOURCE="HD1">Shipments by U.S. Postal Service; Letters and Documents Otherwise Shipped </HD>
                    <P>
                        <E T="03">Comment:</E>
                         A number of commenters believed that the advance cargo reporting rules should be applied to shipments through the United States Postal Service (USPS). 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Paragraph K of section 343(a)(3) of the Trade Act of 2002 (19 U.S.C. 2071 note, section (a)(3)(K)), compels consultation with the Postmaster General in considering what type of electronic cargo information requirements should be imposed upon carriers of mail shipments through the USPS. The CBP still has this issue under consideration. Should a determination be made to extend the advance electronic cargo information mandate to USPS shipments, such postal shipments would be the subject of a separate rulemaking procedure. Current procedures regarding the processing of shipments for the USPS will remain in effect. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Shipments of letters and documents, including the material described in General Note 19(c), Harmonized Tariff Schedule of the United States (HTSUS), that were transported by air otherwise than through the USPS, should also be exempted from full advance cargo reporting requirements. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP has decided to make the requirements for advance cargo information for letters and documents the subject of a separate publication in the 
                        <E T="04">Federal Register</E>
                        . Proposed § 122.48a(d)(3) concerning advance cargo information requirements for letters and documents is thus removed from this final rule. 
                    </P>
                    <HD SOURCE="HD1">Liability Issues </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Should the shipper provide inaccurate information in the description, shipper or consignee fields, it was urged that the incoming carrier or other electronic filer presenting such information to CBP not be held liable. )024
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Whether or not liability would be imposed on a carrier in such circumstances would be governed by section 343(a)(3)(B), as amended, and § 122.48a(c)(5) in this final rule. Section 122.48a(c)(5) provides that CBP will take into consideration how, in accord with ordinary commercial practices, the presenting party acquired the information submitted and whether and how that party is able to verify such information. Where the information is not reasonably verifiable, the party will be permitted to present such information based upon a reasonable belief as to its accuracy. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Three commenters wanted to know whether the carrier would be liable for the submission of house air waybill information where another party that elected to furnish this information to CBP did not do so. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The carrier will indicate in the master air waybill record if another party will be transmitting the house air waybill data. If such other party fails to comply with the advance cargo reporting provisions, this party, and not the incoming carrier, will be held liable. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter inquired as to who would be responsible for submitting advance cargo data in the case of a chartered aircraft. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         In the case of a time or voyage charter, the aircraft owner/operator is the party required to transmit the information. In the case of a bareboat charter, where the charterer in effect becomes the owner of the aircraft (the owner 
                        <E T="03">pro hac vice</E>
                        ), the bareboat charterer would be responsible for reporting the cargo information to CBP. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         A question was presented as to what kind of penalty would be imposed on airlines that failed to meet the advance time frame submission. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         An incoming air carrier failing to meet the advance reporting time frame may be liable under 19 U.S.C. 1584 as well as under other pertinent penalty provisions (see § 122.161, Customs Regulations; 19 CFR 122.161). Should another party electing to file advance cargo information fail to do so, such party may be liable for liquidated damages pursuant to its Customs bond. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         It was asked who would be responsible for transmitting cargo data to CBP where a number of freight forwarders co-loaded cargo. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Either the incoming carrier or one of the parties qualified to do so under § 122.48a(c)(1) will be responsible for supplying the information for all house air waybills under a single consolidated master air waybill. 
                    </P>
                    <HD SOURCE="HD1">Data Elements </HD>
                    <P>
                        <E T="03">Comment:</E>
                         A couple of commenters took exception to the requirement that the flight number for the incoming aircraft be reported 4 hours prior to arrival. The flight number could change. Also, it was unclear how the indirect air carrier would know the exact flight number. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Only the incoming carrier is responsible for the transmission of the flight number. The carrier should be aware of its flight 
                        <PRTPAGE P="68151"/>
                        number at the time of its required transmission. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         It was stated that the proposed data elements designated as conditional (“C”) were not currently captured and would require significant modifications to the freight reservations, reporting and tracking systems and that this would be at significant cost to the carrier. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         These data elements are essential to effective cargo targeting. It is also observed that these data elements have previously been received from other air carriers through Air AMS. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Three commenters inquired as to whether the carrier would still have to provide house air waybill numbers, pieces, weight and description on its paper air cargo manifest. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Under proposed § 122.48(a), except as otherwise provided, a paper air cargo manifest need not be filed for any aircraft required to enter under § 122.41. In addition, proposed § 122.48(a) is further changed in this final rule to eliminate the requirement that a cargo manifest be retained aboard any aircraft required to enter under § 122.41; however, a copy of the air cargo manifest (Customs Form (CF) 7509) must otherwise be made available to CBP upon demand. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         It was asked how a company would obtain a unique identifier (which would be transmitted by the carrier to indicate its separate transmission of a portion of the required data elements). 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         A Container Freight Station (CFS) and an Express Consignment Carrier Facility (ECCF) would be identified by its FIRMS (Facilities Information and Resources Management System) code. An air carrier would be identified by its IATA (International Air Transport Association) code. All other parties would be assigned a unique identifier by the Client Representative Branch of CBP's Office of Information and Technology (OIT) upon commencement of certification testing in Air AMS. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         More information was requested as to the description that would be required on the master air waybill in the case of shipments of dangerous goods. It was noted that IATA requirements did not permit a characterization of “consolidation” to be indicated as a description on the master bill. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         For the purposes of satisfying § 122.48a only, a cargo description of “consolidation” is sufficient at the master air waybill level. However, carriers may elect to provide additional information in the description field at the master bill level if they choose to do so. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Two commenters believed that current Air AMS programming did not allow for alpha-numeric characters of house air waybill numbers to be transmitted as printed on the paper house air waybill. They inquired as to how this would be handled. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Each party providing electronic cargo information must support alphanumeric characters for house air waybill records when alpha characters appear on the printed house air waybill. The CBP recognizes that some current Air AMS participants will need to undergo programming changes in order to support this feature. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter noted that, quite often, the Importer of Record and the “deliver to” party (the ultimate consignee) were not the same party. The commenter wanted to know whether there would be a problem if the consignee were located somewhere other than the arrival and/or destination port. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The consignee need not be located at the arrival or destination port. Paragraphs (d)(1)(xi) and (d)(2)(vii) of proposed § 122.48a are revised in this final rule to so indicate. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter urged that CBP allow disclaimers such as “said to contain” or “shipper's load and count”. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The characterization, “Said to contain”, is not an acceptable cargo description. The approved use of “shipper's load and count” is outlined in § 4.7a(c)(3)(ii), Customs Regulations (19 CFR 4.7a(c)(3)(ii)). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Three commenters did not agree with the requirement that the smallest external packaging unit be stated; a simple pallet count should be allowed. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP disagrees. Such reporting is essential to ensure that no additional packages have been introduced into palletized cargo. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         It was requested that the Automated Broker Interface (ABI) be made mandatory for all forwarders and brokers to transmit house data to CBP for air shipments. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The ABI is not the system by which electronic cargo information is to be collected under the provisions of § 122.48a. 
                    </P>
                    <HD SOURCE="HD1">Definitions </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Under proposed § 122.48a(b)(1), one commenter wanted to know what was meant by the time of departure for the United States; and in proposed § 122.48a(b)(2), it was asked whether the time of arrival in the United States would be the scheduled or the actual time of arrival. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         As expressly stated in § 122.48a(b)(1), the electronic cargo information must be received no later than the time of departure of the aircraft from foreign, which is the time that the wheels are up on the aircraft and it is en route directly to the United States (the trigger time is the time of departure of the aircraft for the United States). Proposed § 122.48a(b)(1) is thus further clarified in this final rule. And in § 122.48a(b)(2), the electronic cargo information must be received 4 hours prior to the actual arrival of the aircraft in the United States. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter stated that gray areas still persisted as to the cargo covered by the regulation, and asked, in this respect, whether company material or aircraft parts for use by the airline would need to be reported. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         As specified in the background discussion of the proposed rule (see 68 FR at 43580), merchandise brought in by an air carrier for its own use would be subject to the same advance cargo information filing requirements that would apply to other incoming cargo. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         With reference to proposed § 122.48a(d)(1)(xii), the identity of the party who issued the “consolidation identifier” was requested. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The consolidation identifier is transmitted by the incoming air carrier to designate an air waybill record as a “master” air waybill. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         In proposed § 122.48a(d)(1)(xvii), one commenter wanted to know what a “local transfer facility” was. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         A local transfer facility is merely a Container Freight Station as identified by its FIRMS code or the warehouse of another air carrier as identified by its carrier code. Proposed § 122.48a(d)(1)(xvii) is revised in this final rule to include this additional explanatory material. 
                    </P>
                    <HD SOURCE="HD1">Air AMS Issues </HD>
                    <P>
                        <E T="03">Comment:</E>
                         It was asserted that mandatory participation in the Air Automated Manifest System (Air AMS) could not be required due to the fact that it was a voluntary program. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Section 343(a)(1) of the Trade Act of 2002, as amended (19 U.S.C. 2071 note, section (a)(1)), gives CBP the authority to require the advance reporting of cargo information through an electronic data interchange system; and Air AMS is such a system. Moreover, Air AMS was developed as a component of the National Customs Automation Program (NCAP) (19 U.S.C. 1411(a)); and, in section 338 of the Trade Act of 2002, Congress amended 19 U.S.C. 1411(b) to permit CBP to 
                        <PRTPAGE P="68152"/>
                        require the electronic submission of information that CBP is obliged to collect. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked when the Air AMS specifications and testing protocol would be made available to the trade. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP will post the Air AMS specifications and testing protocols on its Web site as soon as possible. Such specifications and testing protocols will set forth the programming and operational details of the system. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Since a filer could be a party with a Container Freight Station (CFS) location or a Facilities and Information Resources Management System (FIRMS) code, two commenters inquired as to whether this implied that the advance cargo transmission would have to be made from a particular U.S. location. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The electronic cargo information may be sent from any location, provided that the electronic filer is one of the parties specified in § 122.48a(c)(1). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         It was declared that carriers currently participating in Air AMS did not have uniform system requirements or uniform procedures at all ports of entry. The CBP should compel uniformity in system requirements and procedures at all ports. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The promulgation and implementation of these regulations and the enforcement of their provisions will increase uniformity of carrier participation in Air AMS. For instance, currently, there are several methods to process cargo information and they vary at each location. This is due to the lack of authority for CBP to require automation of cargo information. This regulation will provide that authority and therefore increase uniformity. The CBP believes that all cargo declarations will be processed the same at each location. However, variations may exist in the execution of the entry not in the manifest. Each port is a little different and therefore some variations will exist but not to the extent that is occurring on a daily basis.
                    </P>
                    <HD SOURCE="HD1">Implementation of Advance Air Cargo Data Filing Requirements</HD>
                    <P>
                        <E T="03">Comment:</E>
                         Seven commenters wanted more time to obtain access to relevant Air AMS software and communications equipment in order to make their computer interface with the system operational. The CBP was requested to accommodate the interface schedules of the carriers in this regard. Three other commenters wanted a general delayed effective date of 180 days from the date the final rule was published. One commenter recommended that the rule be delayed until all ports were operational on the system and all necessary training had been completed. Another commenter believed that CBP was not properly staffed or trained in Air AMS to support its nationwide implementation. A further commenter suggested that CBP implement a phased-in approach, by carrier, origin and destination, and that a “web portal” be installed for use by carriers and other authorized filers unable to interface with the Air AMS system.
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Section 343(a), as amended, was enacted on August 6, 2002, and clearly required that cargo data would need to be filed electronically. To this end, in the public meeting that was held for incoming air cargo on January 14, 2003, CBP stated that the accepted electronic interface would be the Air AMS system. Therefore, air carriers have had over one year to conduct proper research as to what type of software and computer interface options are available and what each has to offer. As such, CBP will only delay the general effective date of § 122.48a until March 4, 2004 for the specific reasons described in § 122.48a(e)(2).
                    </P>
                    <P>Additionally, CBP has already identified all airports that require training in Air AMS and whether those air carriers that call on those airports are automated. By making use of this list and working with the air carriers concerned, CBP will coordinate with carriers that are ready to go online in airports that are not yet automated in order to ensure that the inspectors are properly trained, and that the air carrier has proper points of contact at that airport. However, CBP has determined that a web portal feature is not feasible at this time.</P>
                    <P>Furthermore, it is vital that the training for inspectors coincide as closely as possible with air carriers becoming automated in a port. If CBP trains the inspectors and there are no automated air carriers for several months, the training is not useful because the inspectors will not be utilizing their new skills. Therefore, the training must occur within a few weeks of an air carrier notifying CBP that it is going to become automated in a specific port.</P>
                    <P>Toward this end, CBP is striving to improve the Air AMS training that is available to the field inspectors. Currently, there are four Air AMS training classes that are held at the Federal Law Enforcement Training Center (FLETC) each year. In addition, CBP is developing a computer-based training course that will be required for each inspector at all airport locations.</P>
                    <HD SOURCE="HD1">System Irregularities; Paper Manifest Requirement</HD>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter requested specific details regarding the technical support for any problems that might be experienced during data transmissions.
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Requests for resolution of ordinary cargo transmission problems should be coordinated with CBP personnel at each port. In addition, each Air AMS participant has been/will be assigned a CBP client representative who is available to assist with more technical guidance.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Three commenters no longer wanted to keep a paper air cargo manifest on board the aircraft since CBP was mandating electronic cargo information. In addition, the requirement for keeping a paper General Declaration on board should be deleted since all the information was sent in advance of arrival through the Advance Passenger Information System (APIS).
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         As already noted, a paper air cargo manifest (Customs Form (CF) 7509) will no longer be required to be kept aboard the aircraft, but must otherwise be available for production upon demand. Proposed § 122.48(a) is changed in this final rule to reflect this. However, the General Declaration (CF 7507) will still be required as it contains data elements not otherwise collected through APIS or Air AMS.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Five commenters asked how an air carrier would comply with the advance cargo notification requirements without keeping a record of every single house air waybill in addition to the archived copy of each master air waybill.
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Section 122.48a does not require the incoming air carrier to transmit or maintain records for house air waybill data when such data is transmitted by another electronic filer.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Seven commenters recommended that a CBP office be established at all airports to respond to various irregularities.
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Each airport concerned will have a designated point of contact to address and resolve matters involving Air AMS.
                    </P>
                    <HD SOURCE="HD1">In-Transit Issues</HD>
                    <P>
                        <E T="03">Comment:</E>
                         Four commenters suggested that in-transit cargo that remained on board the aircraft should be excluded from the proposed rule.
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP disagrees. Such cargo could pose a cargo safety or security risk to the same extent as other cargo that arrives in the United States.
                        <PRTPAGE P="68153"/>
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         It was believed that the proposed regulations did not clearly address whether air cargo that merely transited, and would not be discharged in, the United States was subject to compliance with the advance reporting time frames.
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         In accordance with § 122.48a(a)(1), cargo that transits the United States, whether or not it is unladen from the aircraft, is subject to the advance reporting requirements of the regulation. Technical requirements to report such information electronically will be specified in the Air AMS technical manual.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter was concerned about who would be required to report required cargo data for in-transit cargo.
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Such information must be provided either by the incoming air carrier or one of the other specified parties in § 122.48a(c)(1).
                    </P>
                    <HD SOURCE="HD1">Hand-Carried Baggage </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Five commenters advocated that hand-carried merchandise should be subject to the advance cargo reporting provisions. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Hand-carried merchandise is covered by the requirements for passenger baggage and is not considered cargo subject to advance reporting under § 122.48a. 
                    </P>
                    <HD SOURCE="HD1">Landing Rights </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Five commenters suggested that CBP specify in proposed § 122.14(d) that denial of landing rights would occur only if a known security threat aboard a particular aircraft posed a higher threat to safety and security than an emergency diversion to alternative airports that could also refuse landing rights. Four other commenters believed that CBP should not deny landing rights or permission to unlade cargo based upon inaccurate information received from other parties. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The provision to deny landing rights is generally intended for those air carriers that fail, repeatedly and egregiously, to furnish timely and accurate cargo information in advance. In such a situation, CBP would have the authority to deny landing rights for that air carrier in the future. Assuredly, this provision would not be executed without careful deliberation and dialogue with the air carrier as to its lack of compliance. 
                    </P>
                    <P>In addition, pursuant to section 343(a)(3)(B), as amended, and § 122.48a(c)(5), as already noted, if the carrier electronically transmitting cargo information has received any of this information from another party, CBP, in deciding issues of liability, will take into account how, in accordance with ordinary commercial practices, the carrier acquired the transmitted information and whether the carrier was reasonably able to verify the information. Depending upon these circumstances, CBP reserves the authority to deny landing rights or permission to unlade if an air carrier fails to fulfill its responsibilities under these regulations. </P>
                    <HD SOURCE="HD1">Corrections to Cargo Information </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Five commenters wanted clarification as to the procedure for making any changes to the cargo information already transmitted for a flight. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Complete and accurate information would need to be presented to CBP for cargo laden aboard the aircraft no later than the applicable time specified in § 122.48a(b). As for any changes in the cargo information already transmitted for a flight, the procedures for amending the cargo declaration including discrepancy reporting will be the subject of a separate rulemaking. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Two commenters inquired about who would be responsible in the case of a data discrepancy between a master air waybill and a house air waybill. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The party that transmits the information would be responsible for its correction. Communication between the air carrier and any other electronic filer for the incoming cargo should be maintained in order to avoid such discrepancies. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         It was asked whether an electronic transmission to correct inaccurate data could be initiated from the port of destination when the initial electronic transmission occurred at the point of departure for the United States. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Any party supplying information will be able to correct such information, regardless of the station from which its transmission electronically originated. 
                    </P>
                    <HD SOURCE="HD1">Cargo Transfer </HD>
                    <P>
                        <E T="03">Comment:</E>
                         A question arose as to whether the deconsolidator's Facilities and Information Resources Management System (FIRMS) code or the carrier's identifier would be needed for incoming cargo that would be handled through a local transfer facility; and whether such information could be transmitted after arrival of the cargo. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         A FIRMS code is the necessary data element for cargo that would be transferred to a deconsolidator or a Container Freight Station (CFS) within the limits of the port. Should the cargo be intended for transfer to another carrier's station within the port, the code of that carrier is required. Proposed § 122.48a(d)(1)(xvii), as already mentioned, is revised in this final rule to include this additional explanation. This information must be transmitted in advance of arrival together with the other required data in § 122.48a(d)(1) and (d)(2). 
                    </P>
                    <HD SOURCE="HD1">Split Shipments </HD>
                    <P>Comment: Because shipments that were split by the incoming carrier would affect the transmission for that cargo by another electronic filer, the rules for the handling of split shipments in Air AMS should be further clarified. </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         When the incoming air carrier elects to split a master air waybill into multiple arrivals, the carrier will be required to transmit to CBP a number of additional data elements for each house air waybill covered by the master air waybill record. Specifically, the carrier will be required to transmit the house air waybill number, certain transportation and arrival information, the manifested and boarded quantities, and the manifested and boarded weights. As such, the informational requirements for split shipments described in proposed § 122.48a(d)(1)(xiii) are revised and included in this final rule as a new § 122.48a(d)(3) (proposed § 122.48a(d)(3) dealing with the summary manifesting of letters and documents, as previously noted, is deleted from this final rule and will be the subject of a separate 
                        <E T="04">Federal Register</E>
                         publication). Also, further technical specifications regarding the issue of split shipments will be provided in the Air AMS technical guidelines. 
                    </P>
                    <HD SOURCE="HD1">Changes in Business Practices </HD>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter stated that it was an undue hardship to force companies onto Air AMS if another system were going to supersede it later on, and that companies would be forced to undergo the expense of conforming to new computer programming. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                        The CBP will rely, at least initially, upon the Air AMS, with appropriate future modifications, as the principal vehicle to achieve the goal of advance cargo data filing under section 343(a), as amended, in order that these regulations may be implemented at the earliest practicable time, as an urgent and critical national security imperative. However, it is assured that any new system developed within the framework of the Automated Commercial Environment (ACE) will be compatible with these implementing regulations. For this reason, the 
                        <PRTPAGE P="68154"/>
                        regulations refer generically to a CBP-approved electronic data interchange system (rather than to Air AMS, specifically). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                        Companies would need to shift current workload that was done at destination ports to the ports of departure, and those ports were not properly staffed to handle the workload. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                        The CBP is fully aware that some changes in business practices may be necessary. For example, it has been a common practice for the industry to input cargo information while the aircraft is in-transit to its destination. This practice will need to change to require the information in a timely manner so as to meet the time frames identified by this final rule. The CBP has attempted to balance the concerns of the trade by affording a delayed effective date in the implementation of the advance air cargo reporting regulations as provided in § 122.48a(e), while, at the same time, recognizing the compelling national security need to move as deliberately as possible to protect cross-border commerce from the threat posed to cargo safety and security by international terrorism. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                        It was observed that for shipments with multiple intermediate foreign stops before final departure for the United States, freight forwarders needed the ability to transmit data elements to CBP at the time of departure from the departure station/location. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                        Those parties authorized to transmit house air waybill level information, as specified in § 122.48a(c)(1), will be able to do so prior to the transmission of the master air waybill information by the incoming air carrier. 
                    </P>
                    <HD SOURCE="HD1">General/Miscellaneous Issues </HD>
                    <P>
                        <E T="03">Comment:</E>
                        When an incoming air carrier has transmitted data to CBP for incoming cargo, one commenter inquired whether that carrier's ground handling agent, or other party, holding the goods following their arrival would also need to be automated in order to have access to the electronic freight status notifications concerning the cargo. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                        Participants in Air AMS, including the incoming air carrier, must be able to honor all electronic freight status notifications transmitted by CBP. Whether the carrier elects to employ a ground handling agent or not, the carrier is responsible for maintaining control of the cargo pending CBP disposition. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                        A question was raised as to how the carrier was to be advised that the house air waybill information had been transmitted to CBP. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                        The CBP does not anticipate transmitting a message to the carrier when the house air waybills are transmitted by another party. However, the failure to transmit house air waybill information for consolidated shipments, as prescribed in § 122.48a(d)(2), would preclude the release or transfer of any cargo covered by the consolidation. Thus, communication between the incoming carrier and any other electronic filer of house air waybill information, if applicable, would be essential. 
                    </P>
                    <P>In this latter connection, the Air Automated Manifest System (AAMS) has a feature known as the Freight Status Query (FSQ) message. The party that transmitted the message or another AAMS participant that has been authorized by the message originator may query the status of an air waybill record in AAMS. This feature may be invoked on a transactional basis to provide the AAMS participant with confirmation that an air waybill is on file along with details about the record. </P>
                    <P>However, to provide an automatic confirmation receipt message for every air waybill transmission would create substantial programming costs for CBP and AAMS participants. It would also substantially increase data storage and communications costs. The FSQ message provides the same information but need only be invoked on a case-by-case basis. </P>
                    <P>
                        <E T="03">Comment:</E>
                        An issue was raised as to whether a party that was both an Automated Broker Interface (ABI) filer as well as a Container Freight Station/Deconsolidator and in possession of an international carrier bond could transmit cargo data at ports where the consolidation cargo remained under the custody of the air carrier. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                        A party authorized to transmit electronic cargo information, as provided in § 122.48a(c)(1) and (d)(2), will be able to do, even if the cargo remains in the custody of the incoming carrier. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                        One commenter wanted to know if there would be any amendment of requirements pertaining to international carrier bonds. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                        The changes to the international carrier bond requirements are set forth in § 113.64(a) and (c) in this final rule. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                        Additional explanation was sought concerning what procedures an air carrier would need to follow if cargo were targeted for inspection by CBP. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         If it is found that a physical inspection of the cargo is necessary, CBP will electronically notify the carrier or other cargo custodian and make arrangements for its examination. In so doing, CBP would work with the carrier to ascertain an appropriate location to examine the potentially high-risk cargo.
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Air cargo that would arrive in the United States on a permit to proceed from the port of arrival should be allowed to move to the port of unlading notwithstanding that a hold was placed on the air waybill covering the cargo due to insufficient data.
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         If CBP determines that a physical inspection is necessary or if additional information is required, the cargo will be held at the port of first arrival pending resolution of the matter. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Concern was expressed that CBP ABI/AMS client representatives would not be able to sufficiently handle the additional workload under the new regulations. It was suggested that a study be done to measure the current level of service to the trade and that such a study should be shared with the trade. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP does not believe that a study of client representative workload is necessary to the implementation of this rule. In the unlikely event that such a contingency should arise, § 122.48a(e)(2), as previously observed, does provide that the effective date of the rule may be further delayed if more time is needed to complete the certification testing of new participants. 
                    </P>
                    <HD SOURCE="HD1">Rail Cargo Destined to the United States </HD>
                    <HD SOURCE="HD2">Time Frame </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Four commenters mentioned that cargo manifest information transmitted to CBP through the Rail Automated Manifest System (Rail AMS) could be made available two hours prior to arrival. However, information on the train sheet, sometimes called a consist (consisting of data such as the train's identification, locomotives' and cars' numbers and initials and the train's schedule) was not part of the advance cargo manifest data. This information would only be available when the final trans-border train was assembled, and in many cases, would only be available for transmission one hour prior to arrival at the border. One other commenter also advocated that the time period be reduced to one hour prior to arrival consistent with incoming truck traffic. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP remains of the opinion that the 2-hour period for presenting rail cargo data prior to arrival effectively balances the impact on rail cargo safety and security with the likely impact on the flow of rail commerce into the United States. As such, this 
                        <PRTPAGE P="68155"/>
                        time frame represents the minimum period during which CBP is confident that essential targeting can still be accomplished, without a concomitant undue disruption to rail business practices.
                    </P>
                    <P>In addition, without proper consist information (which identifies the incoming train, and gives its locomotives' and cars' numbers and initials and the train's schedule), CBP would not have the complete information essential for targeting on the incoming cargo in connection with the particular train on which the cargo would arrive. The availability of information on both the cargo and the arriving conveyance as provided in the rail consist is vital in order to enable CBP to do its targeting effectively in the time required.</P>
                    <HD SOURCE="HD2">Required Data; Carrier Responsibility </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Four commenters wanted it made clear that a railroad was required to provide the scheduled date and time of arrival to the best of its knowledge, and that a railroad should not be penalized or held responsible should that date and time prove inaccurate within some reasonable time frame. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The railroad carrier must provide the scheduled date and time of arrival to the best of its information, knowledge and belief at the time that this information is filed. However, carriers will be held responsible for failure to keep CBP informed of any changes in this information as it becomes available. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Rail carriers should not be held responsible for the accuracy of information supplied by others. The CBP should change the language in proposed § 123.91(c)(2) to state that where the rail carrier electronically presenting the cargo information received any of this information from another party, the rail carrier would not be held responsible for the inaccuracy of any information supplied by that other party. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP disagrees. Section 123.91(c)(2) repeats, and CBP is bound by, the statutory standard against which the potential liability of a rail carrier would effectively be gauged in presenting inaccurate cargo data to CBP that had been acquired from another party. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         It was important that Rail AMS be able to manage multiple shipment data. The CBP would need to coordinate implementation of this aspect of the process with all elements of the supply chain and with U.S. trading partners. 
                    </P>
                    <P>Specifically, the requirement that the rail carrier supply information from the house bill of lading was problematic. In most cases, railroads would only have the capability of receiving one bill of lading and that bill would generally be a master bill of lading. Also, if the railroad had a container holding several consolidated shipments with individual house bills associated with each shipment, even if the railroad had the capability of receiving the individual house bills, information from such bills could not be transmitted to CBP inasmuch as Rail AMS could only handle the transmission of one bill of lading in association with the cargo manifest data for that one shipment. </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP is currently reviewing Rail AMS programming requirements to release the edit that only allows one bill of lading per shipment, which will enable house bills of lading to be utilized in the rail environment. In addition to possible programming changes, CBP is reviewing the prospect of authorizing other parties to transmit information via Rail AMS. This would further facilitate the submission of the house bill of lading information that is required on all shipments. 
                    </P>
                    <P>
                        Should CBP decide to allow another electronic filer to voluntarily present house bill information for a shipment through Rail AMS, a test program notice to this effect would first be published in the 
                        <E T="04">Federal Register</E>
                         pursuant to § 101.9(b) and (b)(1), Customs Regulations (19 CFR 101.9(b) and (b)(1)), inviting public comments on any aspect of the proposed test and informing interested members of the public of the basis for selecting participants, the eligibility criteria for participation in the test, and the effect of such participation on the responsibilities of incoming rail carriers for the transmission of required advance cargo data to CBP. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Proposed § 123.91(d)(4) stated that carriers would have to supply the numbers and quantities of the cargo laden, as contained in the carrier's bill of lading, either master or house, as applicable, which meant the quantity of the lowest external packaging unit. This information was contained in the house bill, not the master bill. For a container shipment, the railroads would only know the quantity expressed on the master bill, which might not be at the level of the lowest external packaging unit.
                    </P>
                    <P>Similarly, proposed § 123.91(d)(6) and (d)(7) would require that the railroad carrier provide the complete name and address for the shipper and consignee respectively. Again, however, the master bill of lading possessed by the rail carrier could contain only the name of a freight forwarder instead of the actual shipper and consignee; if so, the rail carrier would not know the identity of the actual shipper and consignee. </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         House bill of lading information is required under this regulation; therefore, as already discussed, CBP is reviewing programming changes to Rail AMS that would enable the system to accept such information. Hence, when Rail AMS is programmed to capture house bill of lading information, and when the rail industry has been given additional time to make essential adjustments to its own programming for the transmission of such house bill data through Rail AMS, all the referenced data elements would, at such time, need to be presented to CBP, which would include information for the shipper and consignee, including the full name and address of each, as well as the numbers and quantities (of the lowest external packaging unit) of the cargo laden aboard the train. To this end, CBP will take these programming matters into account in establishing the effective date(s) for implementing the incoming rail cargo data regulation (see § 123.91(e) in this final rule). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter suggested that it might be difficult or impossible for the rail carrier to obtain the necessary cargo information when the rail cargo had initially arrived in Canada or Mexico by vessel or air carrier from another foreign country. In such a case, unless the ocean or air carrier had first required the complete disclosure of all information at the port of loading in the other foreign country, and thereafter passed this information along to the rail carrier, there would be no way that the required information would be available to the railroad. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         For cargo that is transferred in Canada or Mexico to a rail carrier for shipment to the United States, whether such cargo originated in Canada or Mexico or was first brought there by a vessel or air carrier from another foreign country, the rail carrier, as explained above, will be required to provide the requisite data elements for such cargo to CBP. 
                    </P>
                    <HD SOURCE="HD1">Line Release </HD>
                    <P>
                        <E T="03">Comment:</E>
                         The CBP should retain Line Release not only for the present as stated in the proposed rule, but for the long term, as it was declared to be critical for cross-border rail traffic. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP fully recognizes the importance of Line Release for Rail AMS. In fact, CBP has recently made Line Release available, for rail shipments only, to ports that ordinarily would not have access to it, 
                        <PRTPAGE P="68156"/>
                        as part of CBP's Rail AMS port automation efforts. 
                    </P>
                    <P>Automated Line Release in rail is what is known as the Border Release Advanced Screening and Selectivity program (BRASS) in the Truck environment. The difference is that the information is all electronic and supplied in advance of arrival. </P>
                    <HD SOURCE="HD1">Implementation Date(s) for Rule </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Further guidance was sought as to the implementation date(s) for the proposed regulation. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Quite plainly, under § 123.91(e), rail carriers must commence the advance electronic transmission of required cargo information 90 days from the date that CBP publishes a notice in the 
                        <E T="04">Federal Register</E>
                         informing affected carriers that the data interchange system is in place and operational at the port of entry where the train would first arrive in the United States. As such, before the rule can become operational at any port, including any port(s) where Rail AMS is now operational, the initial publication of a 
                        <E T="04">Federal Register</E>
                         notice naming such port(s) would be a mandatory prerequisite. At present, there are 35 CBP ports that have rail crossings, 8 of which are not rail AMS. The CBP will require all ports that handle rail cargo to become automated. 
                    </P>
                    <HD SOURCE="HD1">Exemption for Cargo Transiting Contiguous Foreign Country </HD>
                    <P>
                        <E T="03">Comment:</E>
                         The proposed rule (§ 123.91(b)) would expressly exempt from advance electronic information filing requirements domestic cargo transported by train from one port to another in the United States by way of a foreign country. However, the proposed rule did not deal with whether such an exception applied when the shipment partly involved transportation by sea or air. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Only a land-based conveyance, such as rail or truck, would be involved with carrying goods on a continuous movement from one port to another in the United States by way of a contiguous foreign country, whether Canada or Mexico. This is the specific situation addressed in § 123.91(b); such a situation would simply not arise in the vessel or air mode. Proposed §§ 123.91(b) and 123.92(b)(1) (for trucks) are revised in this final rule to explicitly reference Canada and Mexico in this respect. 
                    </P>
                    <HD SOURCE="HD1">Truck Cargo Destined to the United States </HD>
                    <HD SOURCE="HD2">Implementation Issues </HD>
                    <P>
                        <E T="03">Comment:</E>
                         As was done in the 24-hour rule, one commenter wanted a grace period between the implementation date of the final rule and its enforcement date (no penalties assessed for non-fraudulent violations). 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Similar to that which was done in the context of the 24-hour rule (67 FR 66318), as previously detailed, 
                        <E T="03">supra,</E>
                         CBP will follow a phased-in enforcement/compliance program, after § 123.92 becomes effective at a specific port of arrival. As such, during the phased-in period, CBP would not customarily initiate enforcement actions such as assessing penalties for non-fraudulent violations of § 123.92. And, under § 123.92(e), the effective date for advance data filing for incoming truck cargo is itself initially delayed until 90 days from the date that CBP publishes a notice in the 
                        <E T="04">Federal Register</E>
                         informing affected carriers at the given port that the approved data interchange is operational there and that carriers must commence the filing of the required data. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Two commenters sought to delay the implementation of proposed § 123.92 until carriers, brokers, and importers had direct communication links electronically with CBP. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP disagrees. The advance notification requirement is largely intended to collect advance cargo information via two outstanding methods—the Automated Broker Interface (ABI), or the fully electronic version of the Free And Secure Trade (FAST) System. Delaying the implementation of § 123.92 until all parties related to the reporting of the data for incoming cargo are fully electronically interfaced with CBP, such as through FAST, or the Automated Commercial Environment (ACE), once it is deployed, would be incompatible with the expeditious implementation of section 343(a), as amended, as a national security necessity. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         It was suggested that CBP implement separate rules for emergency importations. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Emergency situations will be handled on a case-by-case basis, depending on the facts, in CBP's enforcement discretion. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         It was recommended that an education enforcement contingency plan be devised to avoid possible chaotic situations at the border under the new rules. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Outreach and marketing efforts are currently being undertaken to reach out to both foreign and domestic trade participants to avoid such situations at the border. 
                    </P>
                    <HD SOURCE="HD1">Time Frame for Advance Filing </HD>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter sought further explanation as to the actual start time for advance notification requirements, 
                        <E T="03">i.e.</E>
                        , at the time of transmission, or at the time CBP received the transmission. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         As expressly set forth in § 123.92(a), CBP must receive the cargo data no later than 30 minutes or 1 hour prior to the carrier's arrival at a United States port of entry, or such lesser time as authorized, based upon the CBP-approved system employed in presenting the information. Also, this point was directly addressed in the background of the proposed rule (see 68 FR at 43586). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Twelve commenters recommended an abbreviated advance notification time line of 30 minutes for standard shipments and 15 minutes for Free And Secure Trade (FAST) shipments, specifically for trucks loaded within a designated border zone, to support the “Just-in-Time” (JIT) shipping industry. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         This identical comment was broached in the proposed rule (68 FR at 43586; 
                        <E T="03">Summary of Principal Comments,</E>
                         item “1.”). At that time, CBP concluded, and continues to firmly believe, that the 30-minute or 1-hour advance time frame, in relation to the particular automated system used, is the minimum period needed to perform a targeting analysis for cargo selectivity, and, if found warranted, to arrange for an inspection or examination of the cargo following its arrival. The effect on JIT inventory practices, given these relatively brief reporting periods, should be essentially nugatory. 
                    </P>
                    <P>Against this backdrop, it is submitted that BRASS (the Border Release Advanced Screening and Selectivity program) and CAFES (the Customs Automated Forms Entry System), where the filing period would be less, will only be employed exclusively as interim, transitional systems in the truck environment prior to the development and deployment of fully electronic replacements for these systems in the new truck manifest module scheduled for delivery under the Automated Commercial Environment (ACE); the employment of BRASS and CAFES under the circumstances is thus due in large measure to the conspicuous lack of electronic information systems prevalent in the trucking industry, especially along the Southern Border. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Six commenters asked that CBP implement the 15-minute advance electronic notification period currently used under the FAST voluntary test program. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The FAST program is designed to enhance security and safety in processing commercial importations 
                        <PRTPAGE P="68157"/>
                        along the Northern and Southern borders, while also enhancing the economic prosperity of the U.S., Canada, and Mexico by aligning, to the maximum extent possible, their customs commercial programs. While the program will still, of course, function in this capacity, nevertheless, with reference to its relationship with section 343(a), as amended, FAST will also be used for purposes of ensuring cargo safety and security and preventing smuggling. As such, and for the reasons set forth above, CBP finds it advisable to extend the overall time frame for FAST transactions to a full 30 minutes prior to arrival as an additional security measure under the program. 
                    </P>
                    <P>Thus, shipments eligible for FAST must be reported at least 30 minutes before the arrival of the conveyance at the first port of entry. FAST shipments may be reported through one of two release mechanisms: Through the all-electronic transmission of conveyance, driver and shipment information, formerly known as the National Customs Automation Program (NCAP) prototype; or through the use of the Pre-Arrival Processing System (PAPS) version of cargo selectivity. All other truck shipments still not allowed release via BRASS, must utilize PAPS and submit the data one hour before arrival of the truck. For an additional extensive review of the FAST, PAPS, BRASS, and CAFES systems, see the proposed rule at 68 FR 43586-43587. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Seven commenters requested that CBP initiate an electronic confirmation/receipt system, that would notify the broker/carrier that information was received, thus starting the 30-minute/1-hour clock. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP already has a system in place that notifies the ABI transmitter that the data was received. This information is only available to the ABI transmitter. At this time, any notification to the carrier of successful data transmission must come via the ABI filer. Additionally, it should be pointed out that this program has already been successfully used without the need for direct electronic confirmation from CBP. 
                    </P>
                    <HD SOURCE="HD1">Data Systems To Be Used; In-Bond Reporting </HD>
                    <HD SOURCE="HD2">Free And Secure Trade System (FAST) </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Four commenters wanted to know when FAST, which was only available at a limited number of Northern Border ports, would be extended to other ports, including those along the Southern Border. Four other commenters wanted the FAST program defined in the regulations as a method of acceptable cargo release. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         A general notice published in the 
                        <E T="04">Federal Register</E>
                         (68 FR 55405) on September 25, 2003, announced the expansion of, and the eligibility requirements for, FAST along the Southern Border. The Southern and Northern border implementation schedule for FAST is also available on the CBP Web site (
                        <E T="03">http://www.cbp.gov</E>
                        ). This general notice also clearly defines FAST and its requirements. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Four commenters advocated that less-than-truckload (LTL) carriers be allowed to participate in FAST. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The current eligibility criteria for participation in the FAST program is set forth in the general notice that was published in the 
                        <E T="04">Federal Register</E>
                         (68 FR 55405) on September 25, 2003 (see 68 FR at 55406). 
                    </P>
                    <HD SOURCE="HD1">Pre-Arrival Processing System (PAPS) </HD>
                    <P>
                        <E T="03">Comment:</E>
                         It was suggested that CBP utilize the pre-file system, as was being done along the Southern Border. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP contemplates mandating the implementation of the Pre-Arrival Processing System (PAPS) for all land border sites. The PAPS system, which uses the Automated Broker Interface (ABI), provides CBP with advance arrival information and includes carrier and importer information that is not included in the Southern Border Pre-file system. The PAPS system will basically also mesh with the advance truck manifest module when it is developed in ACE, while the Pre-file system would not. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The CBP should not deny the entry of PAPS shipments for failure to meet the required advance notification time. This could occur where Commercial Vehicle Processing Centers (CVPC) were not present. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         In instances where CVPCs are not present, it is still the responsibility of the carrier or the importer/broker, as applicable, to ensure that the ABI transmitter receives the appropriate entry information via fax or by other means. 
                    </P>
                    <P>Should cargo information not be received within the allotted time frame, CBP may pursue any of the following options: (1) Denying a permit to unlade; (2) Delaying the release of the cargo until security screening is complete; and/or (3) Assessing a penalty/liquidated damages. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Three commenters sought the continued use of bar code labels until transponders were available. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP will continue to support the use of bar codes to identify PAPS shipments, as an acceptable method for processing the entry and release of cargo. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Four commenters questioned what software would be called for and what cost and training investment would be needed. Four other commenters wanted the proposed rule to deal with alternative methods of advance electronic presentation of cargo for those parties without access to an approved data interchange. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         All current ABI transmitters in the truck mode have access to the ABI transmission module, which requires no new additional modifications or software changes. New individual filers may have to make some changes to their existing software, either through in-house programming or via their software vendors. However, the ABI capabilities to be utilized have been available within ABI for many years. It is the carrier's, shipper's or other trade partner's responsibility to ensure that the ABI transmitter receives the appropriate entry information via fax or by other means. 
                    </P>
                    <P>A party seeking to file cargo information with CBP electronically, who does not have an approved data interchange, may employ either the services of an automated Customs broker, or a service provider or an ABI service bureau for this purpose (see § 143.1(a) and (c), Customs Regulations; 19 CFR 143.1(a) and (c)). </P>
                    <HD SOURCE="HD1">Border Release Advanced Screening And Selectivity (BRASS) </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Two commenters desired that CBP expand system capabilities to include advance manifest procedures for BRASS and in-bond shipments and include instructions for a Monthly Manifest. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The BRASS system, which is largely paper-based, will be employed, on an interim basis, for reporting data for incoming cargo. However, additional requirements may be implemented for BRASS to ensure that BRASS transactions achieve the basic objectives of cargo safety and security pursuant to section 343(a), as amended. 
                    </P>
                    <P>
                        As additional interim measures, CBP will continue to employ CAFES or ABI in-bond reporting systems where available. The CBP also intends to continue support for what is known as Monthly Manifest (which applies to automotive products), until the periodic summary reporting that Monthly Manifest supports is available electronically. The Monthly Manifest program, and instructions for this program, however, fall outside the scope of this document. 
                        <PRTPAGE P="68158"/>
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Five commenters sought additional explanation concerning the use of BRASS as a cargo reporting system under proposed § 123.92. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         As a strictly interim, transitional procedure, CBP intends to allow the continuation of BRASS for trucks, but anticipates instituting some additional measures that would otherwise modify BRASS to enhance the security of BRASS transactions. To this end, CBP will take those measures deemed necessary to safeguard the integrity of the BRASS program, which could include program requirements such as FAST Driver registration and participation in the Customs-Trade Partnership Against Terrorism (C-TPAT). However, with the incorporation of a fully electronic version of BRASS planned in the new truck manifest module in ACE, CBP does not propose making any changes to the method in which the current paper-based BRASS operates. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter advocated that CBP restrict the use of BRASS to C-TPAT approved importers. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP will consider adding this type of security enhancement to the BRASS system. However, for the present, CBP will use C-TPAT membership in targeting incoming cargo for examination, including cargo that is subject to reporting through the BRASS system. 
                    </P>
                    <HD SOURCE="HD1">In-Bond Systems; Bar Codes </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Five commenters desired further guidance under the proposed rule concerning in-bond entries for immediate transportation to another port of entry, and the use of the 2-D bar code label under in-bond provisions. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         As explained in the proposed rule (68 FR at 43587), CBP will continue to employ CAFES or ABI in-bond reporting systems where available. The CAFES system handles in-bond shipments utilizing 2-D bar codes that are printed on the Customs Form (CF) 7512 in-bond entry document. Because the use of bar codes is required for CAFES, BRASS, PAPS, and other functions, CBP will continue to support the use of such bar codes in accordance with these systems. 
                    </P>
                    <HD SOURCE="HD1">Required Data Elements </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Two commenters pointed out that proposed § 123.92(c)(2) allowed for dual party presentation of the required data, but did not indicate which data elements were required from the carrier, importer or broker. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Where there is dual-party presentation of the data elements listed for incoming cargo in § 123.92(d), the parties to the transaction should decide which data elements each will submit. It is, of course, presumed that if an importer or its broker elected to file advance cargo information with CBP, such data would typically encompass any required commodity and other related information that it possessed with respect to the cargo, as such information would likely be better known to the importer or its broker; and, for the same reason, the carrier would present the required data pertaining to the carriage of the cargo (see 68 FR at 43587). However, CBP will not parse the data elements in § 123.92(d), and rigidly mandate their respective assignment between the carrier and importer or broker. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         In proposed § 123.92(d)(2), one commenter desired the elimination of the Standard Carrier Alpha (SCAC) code, because carriers along the U.S.-Mexican border did not have SCAC codes. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP disagrees. The ability to identify the carrier is critical to target and assess the risk posed by shipments crossing the border. In this regard, the SCAC code is a unique four-letter code used to identify transportation companies; this unique carrier identifier supports the electronic data interchange for all motor carriers. A carrier may obtain a SCAC code by contacting the National Motor Freight Traffic Association, Inc., 2200 Mill Rd., Alexandria, VA 22314-4654. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter mentioned that the proposed rule did not deal with a possible variation between the scheduled date of arrival and the actual date of arrival, and whether a difference in these times would result in a breach of the importer's entry bond. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         In § 123.92(d)(6), the specific information required is the scheduled date and time of the carrier's arrival at the first port of entry in the United States. However, should there be a delay in the carrier's arrival following its data transmission, this may raise targeting concerns and prompt further inquiry/inspection. In any event, notwithstanding the scheduled arrival of the truck, the presentation of the required cargo data is related to the carrier's actual time of arrival in § 123.92(a). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Four commenters wanted the data elements for inbound truck cargo aligned with those data elements that would be required under the Automated Commercial Environment (ACE) once it is developed. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         As the ACE is under development and its precise features have not as yet been determined, this comment falls outside the scope of this document. 
                    </P>
                    <HD SOURCE="HD1">Exemptions </HD>
                    <P>
                        <E T="03">Comment:</E>
                         The proposed rule should exempt informal entries from advance data reporting. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Section 123.92(b)(2) does exempt informal entries from the advance cargo information notification provisions. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         All radioactive materials entering the United States should be subject to prior notification, even if the shipment only transited a contiguous foreign country while en route from one port to another in the United States. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Upon arrival in the United States, all shipments, including those merely in-transit through a contiguous foreign country, will be scanned for radiation in primary truck lanes, and in-transit manifests, if applicable, must be tendered at that time. 
                    </P>
                    <HD SOURCE="HD1">Examination/Inspection; Penalties/Liquidated Damages; Refusal of Admission </HD>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter suggested processing trucks away from the border, prior to reaching the bridge, especially for Detroit and Buffalo. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The concept of examining and processing trucks prior to their entry into the United States is currently being explored with Canada. It is a complex and sensitive issue involving matters of national sovereignty and the authority to enforce laws outside the United States. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter inquired as to whether it would be acceptable for a carrier to arrive physically and wait in a holding area while the driver/carrier coordinated with the broker to ensure that proper advance information had been provided. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Because secondary examination areas are limited in space, CBP will not allow the shipment to be staged at a designated waiting area in the port of arrival either while the entry documentation is being processed or while the carrier consults with a broker to determine if the information has been presented in the manner prescribed. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Thirteen commenters expressed alarm over the prospect that the admission of cargo to the United States could be refused if the advance notice was not received. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Once implemented at a port, the advance cargo reporting provisions would be obligatory for all required cargo. For any inward carrier for which advance electronic commodity and transportation information was not presented to CBP, as otherwise required in the regulations, the transporting carrier, depending on 
                        <PRTPAGE P="68159"/>
                        the specific circumstances involved, could be refused permission to unlade until all security screening and necessary examination was initiated and concluded, in addition to being subject to applicable statutory penalties. In the alternative, the carrier could be refused admission to the United States depending, once again, upon the particular circumstances involved. 
                    </P>
                    <HD SOURCE="HD1">Type of Carrier; Carriage of Instruments of International Traffic </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Two commenters sought the creation of procedures for the movement of instruments of international traffic, including the movement of empty containers aboard trucks. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         With the exception of FAST, CBP will not require any advance notification if the shipment consists solely of empty articles (pallets, tanks, cores, containers, and the like) that have been designated as instruments of international traffic (IITs). However, if the IITs are commingled with other commercial cargo, CBP will, of course, require the requisite arrival notification for such commercial cargo via the authorized CBP-approved electronic data interchange system; and any empty IITs carried aboard the conveyance must be identified as such and listed on the carrier's paper manifest. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Three commenters questioned whether there was a distinction between an inward truck carrier as opposed to a drayage carrier. Also, they wanted to know whether there would be any differences in treatment between carriers on the Northern and Southern Borders. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP defines a drayage carrier as one that only moves cargo locally (such as a cartman who only moves cargo within the limits of a port), as opposed to an incoming truck carrier which is understood to be engaged in the international movement of cargo coming from Canada or Mexico. Also, as previously assured, until the development of the truck manifest module in ACE, CBP will employ existing data systems on both the Northern and Southern Borders to receive and evaluate cargo information for incoming truck shipments. 
                    </P>
                    <HD SOURCE="HD1">Cargo Departing From the United States; All Modes </HD>
                    <HD SOURCE="HD2">Time Frames for Transmitting Required Data for Outbound Cargo </HD>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter wanted to know whether there could be a pre-departure report for cargo that did not have an export license. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         There may be pre-departure reporting for shipments without an export license. General export reporting requirements may be found in the Bureau of Census Regulations (15 CFR 30.1-30.2). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The proposed twenty-four hour advance notification for outgoing vessel cargo in proposed § 192.14(b)(1)(i) would considerably add to transit time, with adverse impact especially upon perishable goods. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Since the responsibility rests with the USPPI, and not the ocean carrier, to provide the advance data to CBP, there should be no undue burden placed upon the carrier. The Option 4 post-departure filing program will remain and will be available to exporters of perishables that meet requirements for volume, low-risk commodity, and compliance with export regulations. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The phrase, “no later than 24 hours prior to the departure of the vessel”, in proposed § 192.14(b)(1)(i), should be further explained. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         For greater clarity, this phrase in § 192.14(b)(1)(i) is changed to read: “no later than 24 hours prior to departure from the U.S. port where the vessel cargo is to be laden”. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         In proposed § 192.14(b)(1)(ii), one commenter suggested a longer time frame for submitting air cargo data, while two commenters wanted the proposed 2-hour advance time frame reduced. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP finds that the 2-hour advance time frame in § 192.14(b)(1)(ii) is necessary for CBP targeting purposes, and should not unduly disrupt the flow of outbound air commerce. The CBP will continue to work with the express consignment industry to explore interim use of the External Transaction Number (XTN) by those companies that are able to provide CBP access to existing automated export manifest systems with targeting capabilities. 
                    </P>
                    <P>However, for further clarification, § 192.14(b)(1)(ii) is amended in this final rule to state that for air cargo, including cargo being transported by Air Express Couriers, the USPPI or its authorized agent must transmit and verify system acceptance of export air cargo information no later than 2 hours prior to the scheduled departure time of the aircraft from the last U.S. port. </P>
                    <P>
                        <E T="03">Comment:</E>
                         Two commenters recommended that information be submitted prior to the export shipment being delivered to the outgoing carrier, but no less that 2 hours prior to departure of the flight for foreign. The concern was expressed that an air carrier would be penalized for shipments which were tendered for movement before the electronic information filing through the Automated Export System (AES) had been completed. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The USPPI or its authorized agent must have the Internal Transaction Number (ITN) available to provide to the carrier when the cargo is tendered for export. The ITN verifies that the cargo data filing has already been completed. Carriers are only responsible for collecting the proof of electronic filing (ITN) for annotation on the carrier's outward manifest, waybill, or other export documentation covering the cargo to be shipped. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Three commenters proposed that data be submitted for outbound Shippers Export Declaration (SED) shipments at the time of departure for air cargo and upon arrival at the border for truck cargo. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         This would not be permissible. The CBP simply cannot perform its necessary targeting and selectivity responsibilities if the information is received at the time of departure or arrival at the border. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         It was stated that the 4-hour notification for rail as initially proposed by CBP would directly impact operations and result in delayed shipments. On this ground, it was recommended that the time frame for reporting outbound rail cargo be consistent with the 2-hour pre-arrival time frame for incoming rail cargo. 
                    </P>
                    <P>Also, it was stated that U.S. Principal Parties in Interest (USPPIs) who would be obligated to transmit the required cargo information at least 4 hours prior to the engine being attached to the train generally had little knowledge of rail operations. Therefore, it was urged that a mechanism should be put in place whereby a problem container could be held at a Canadian port until reporting issues were resolved. </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP will adopt the recommendation for outbound rail that was put forth by COAC (the Treasury Advisory Committee on the Commercial Operations of the U.S. Customs Service). Thus, export cargo information must be transmitted no later than two hours prior to the arrival of the train at the border, thereby creating symmetry with the advance time frame for inbound rail cargo coming from Canada or Mexico. 
                    </P>
                    <P>
                        The CBP observes that this two-hour time frame is established as a minimum guideline. All parties involved in export transactions are encouraged to file export cargo information as far in advance as is practicable to reduce the need for CBP to delay the export of cargo because of the need for screening, examinations, and the resolution of incomplete or incorrect records. It 
                        <PRTPAGE P="68160"/>
                        should be recognized that CBP will continue to exercise its authority to remove a container from an outbound train at the time of border crossing. Further, in the event that a shipment crosses into Canada without proper reporting and is determined to be high-risk after CBP has utilized all targeting tools and information at its disposal, CBP will work with the carrier to have the container redelivered to the port of export. 
                    </P>
                    <HD SOURCE="HD1">Exemptions From Pre-Departure Reporting </HD>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter sought information about the export exemption list; and whether there was any reason to standardize the format of the citation which the USPPI furnished to the outbound carrier. Exemptions for low value shipments and shipments to Canada should remain the same. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The Bureau of Census already publishes export reporting exemptions in its regulations (see 15 CFR 30.50-30.58). Exemptions for low value shipments and shipments to Canada do remain the same. Also, the citation format is already standardized and available to the trade in Census Foreign Trade Statistics Regulations (FTSR) Letter 168, Amendment 2, a copy of which may be obtained from the Bureau of Census. Additionally, it is understood that information required to be submitted under Bureau of Census regulations for exports made through the U.S. Postal Service (USPS) will not be subject to being reported within the advance filing time frames of § 192.14(b) in this final rule. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Two commenters inquired about the reporting status of shipments to U.S. territories and Puerto Rico. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The reporting requirements for shipments to U.S. territories and to Puerto Rico also remain unchanged. Such requirements are outlined in the Bureau of Census Regulations (see 15 CFR 30.1). 
                    </P>
                    <HD SOURCE="HD1">Internal Transaction Number (ITN)/External Transaction Number (XTN) </HD>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter—The U.S. Department of Defense—wanted to be excepted from the requirement to obtain an Internal Transaction Number (ITN) for export shipments, preferring instead to continue using the External Transaction Number for this purpose. This was said to be necessary to achieve an interface between DoD shipper systems and the AES. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP will review the ITN requirement for non-licensed DoD shipments. However, it is emphasized that for those DoD shipments which are subject to the Department of State's International Traffic in Arms Regulations (ITAR), the requirement of an ITN, to be reported within the advance time frames stipulated by State, will be mandatory. Proposed § 192.14(b)(2) is amended in this final rule to add a specific cross reference to State's ITAR Regulations (22 CFR parts 120-130) that contain the advance notification provisions for exports of items on the U.S. Munitions List. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Specifications of the format and electronic transmission requirements for the ITN should be provided, especially for airlines. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Many carriers already annotate the XTN/ITN, Option 4 statement, or other exemption on the manifest. Carriers should refer to FTSR Letter 168, Amendment 2, for the proper formats. This FTSR Letter may be obtained from the Bureau of Census. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Since carriers could not accept cargo from the shipper/exporter until an electronic filing number or exemption code had been annotated on the export documentation at the time of freight acceptance, it would then follow that freight acceptance times would have to be restricted to 2 hours out from the flight. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Carriers should currently not be accepting cargo without a paper SED, XTN/ITN, Option 4 or reporting exemption statement (15 CFR 30.50-30.58). Hence, the carrier's responsibility under these regulations should not perceptibly change from the proper procedure it should be following at present. It is actually the USPPI or its agent who will have to plan ahead and accomplish transmission and acceptance of the data earlier, so that the ITN will be available when the cargo is tendered to the exporting carrier. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The ITN requirement should be revised to allow export shipments to proceed once the USPPI/Agent has received the ITN/AES confirmation message; and the same policy should apply for export shipments that qualified for exemptions to the pre-departure electronic filing requirements. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         If the USPPI/Agent is already waiting for the ITN message to be returned, the step of noting it on the export documents would be a fairly minor exercise. Also, export exemptions follow a standard format and are listed in 15 CFR 30.50-30.58 and FTSR Letter 168, Amendment 2, 
                        <E T="03">supra.</E>
                         The ITN is provided via a return message from AES. Carriers are required to obtain, and, therefore, USPPIs or their agents must provide to the carrier, an AES proof of filing citation, low-risk exporter citation (currently the Option 4 citation), or an exemption statement under current Census Bureau regulations. This procedure will remain the same under section 343(a) of the Trade Act of 2002, as amended. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         It was not at all clear how a driver, who was out picking up freight on various shippers' loading docks, would have access to the ITN. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The USPPI/Agent should have the ITN already annotated on the export documentation that would be presented to the driver. All the driver would have to do is simply verify that the shipping documents include an ITN, Option 4, or other exemption statement. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Two commenters were of the opinion that the performance of AES in the past in timely returning ITN confirmation numbers had led to the trade's preference for the XTN numbers. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The AES development team is required to set performance standards for system performance. One of the 2003 performance measures requires system “through-put” (the time it takes for data to reach the AES, be processed and put back out for return to the filer) to be routinely less than 1 minute. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked whether there would be any merit in adding the time that the ITN was obtained by the USPPI, so that the carrier would know when the 24 hours had expired (in the case of outbound vessel cargo). 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The current ITN format is sufficient. It is the responsibility of the USPPI or its agent to make sure the advance filing window is met. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The AESDirect system could only return the ITN via email, which would not be timely enough for express business. Three commenters believed that since the AES redesign was not scheduled for completion until mid-2004, and AESDirect sent the ITN via email, the ITN should not be required. One commenter requested that the XTN be used instead. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP wants to especially emphasize that the annotation of the ITN number on any export documentation will not be mandated or enforced until the implementation of the redesign of the AES Commodity Module, which, as noted, is not anticipated to be completed until mid-2004. The redesign of the AES Commodity Module will make the ITN stable when records are updated. 
                    </P>
                    <P>
                        The CBP, after consulting with the Bureau of Census, has informally estimated that its AESDirect system returns the ITN via email within 5-15 minutes. While this response period 
                        <PRTPAGE P="68161"/>
                        may have some impact on business practices, it should prove to be a return time that is, on balance, reasonably prompt and commercially acceptable. The preference for the XTN number is understandable, but since the XTN is generated by the USPPI or its agent and may be annotated on the export documentation without the shipment data having been transmitted to AES, this number is, and has repeatedly been, subject to abuse, which will make its continued use, as a general proposition, wholly unacceptable. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Under the proposed regulations, the exporter could present either the ITN number, the Option 4 filing number, or an exemption statement. It was asked whether this would also comply with the statute concerning the documentation of outbound waterborne cargo (19 U.S.C. 1431a). The CBP should clarify that under Option 4 filing and for exporters that were otherwise exempt from pre-departure filing, there would also be no requirement to provide separate shipping documents to the vessel carrier under 19 U.S.C. 1431a. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Issues relating to section 343(b) of the Trade Act of 2002, as amended (codified at 19 U.S.C.1431a), fall outside the scope of this rulemaking. As made clear in the proposed rule (68 FR at 43592), section 343(b), requiring proper documentation for all cargo to be exported by vessel, will be the subject of a separate publication in the 
                        <E T="04">Federal Register.</E>
                         To the extent legally and operationally permissible, however, the administrative implementation of the requirements of section 343(b) will be synchronized and dovetailed with these regulations under section 343(a). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asked how the carrier would know whether the AES filer was the USPPI or its agent. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         All the carriers need to do is ensure that the proper AES proof of filing citation (including the ITN), the low-risk exporter citation, or an exemption statement is on the shipping documents that they receive with the cargo. The carrier is not required to check the validity of the ITN or the identity of the party presenting it. 
                    </P>
                    <HD SOURCE="HD1">Option 4 Filing (Post Departure) </HD>
                    <P>
                        <E T="03">Comment:</E>
                         The CBP and Census should grandfather existing Option 4 holders into the “new” Option 4 to be jointly constructed by the two agencies. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP cannot guarantee that current Option 4 USPPIs will retain the privilege under program requirements that have yet to be finalized. The current Option 4 was conceived prior to September 11, 2001, and it is the goal of the Bureau of Census and CBP to ensure cargo safety and seaport security while at the same time fostering the continued smooth flow of commerce. The new Option 4 will emphasize volume, repetitive low-risk commodities and compliance. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The CBP should take into account those exporters who repeatedly shipped the same low-risk commodities to related parties. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP does take such exporters into consideration. Current Option 4 is intended for repetitive exports of low-risk commodities by compliant USPPIs. The CBP will explore with the Bureau of Census the possibility of using related parties as a requirement or factor to determine Option 4 eligibility. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Two commenters sought assurance that any revisions to Option 4 filing would not reduce the ability for legitimate, low-risk exporters (such as exporters of agricultural commodities) to qualify for such filing if they were otherwise in compliance, even though they did not meet minimum export volume requirements. Another commenter wanted the program expanded to additional companies that faced new lead time requirements. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP and the Bureau of Census are in the early phase of redesigning the program. While export volume will be a significant factor, there may be an appeals procedure wherein a compliant low-volume exporter can demonstrate a legitimate need for Option 4 filing under the redesigned system. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Two commenters strongly urged the continuation of Option 4 filing for C-TPAT (The Customs-Trade Partnership Against Terrorism) members with low-risk commodity exports. Also, it was thought that such exemptions (as Option 4) and programs for exports should match those provided for imports. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Current Option 4 filing is available to compliant exporters of low-risk commodities, regardless of C-TPAT status. The CBP does not anticipate that this will change. 
                    </P>
                    <HD SOURCE="HD1">Automated Export System (AES)/Technical Issues </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Under the planned redesign of AES to be developed by mid-2004, air carriers would be able to send transportation data directly to CBP. Two commenters sought guidance on how the CBP electronic data interchange would be interfaced with the airlines' systems. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The system enhancement projected for completion in mid-2004 is the AES Commodity Redesign which will improve the ability of the AES to process automated Shipper's Export Declaration (SED) information. These enhancements will not enable AES to accept electronic manifest information directly from air, rail, or truck carriers, nor will the new regulations require the exporting carriers to submit such manifest data via the AES. The vessel manifest module in AES will remain optional. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Three commenters questioned how CBP would notify the carrier of high-risk cargo that was targeted for inspection/examination. It was recommended that a predetermined time should be set following which a carrier could confidently assume that no further hold status would be issued for the cargo. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The AES commodity module is not capable of sending electronic hold messages to carriers, so the current methods of communication by fax and/or phone will need to continue. The CBP cannot set a time frame after which a carrier could assume no further holds. Given the current design and functionality of the system, commodity records are transmitted to AES on a transaction-by-transaction basis rather than as part of a manifest, where the end of the transmission is marked. Thus, not knowing which AES commodity transaction is the last for a particular conveyance makes it impossible for CBP to provide an absolute, finite time after which no further holds will occur. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The proposed outbound cargo reporting provisions should be changed so that motor carriers would not have to transmit specific data elements to AES. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Carriers are not responsible for transmitting the information required by section 343(a) of the Trade Act of 2002, as amended. Section 192.14(c)(4), as proposed and as appearing in this final rule, details carrier responsibility which, as already explained, is largely limited to collecting AES proof of filing citations (ITN), Option 4 exemptions, and regular reporting exemptions (see 15 CFR 30.50-30.58). Likewise, the transmission of all automated SED commodity data (which already includes data relating to the transportation of the cargo) by the USPPI/Agent is covered in § 192.14(c)(1) and (c)(2) in this final rule. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Two commenters were of the view that the data elements for the estimated date of exportation and the port of exportation (proposed § 192.14(c)(2)(v) and (c)(2)(vi)) would cause potential difficulty for the motor 
                        <PRTPAGE P="68162"/>
                        industry which did not operate on strict routes and schedules. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The 6 transportation data elements in § 192.14(c)(2), including the estimated date of exportation and the port of exportation, are data elements that are at present mandatory for AES participants under current 15 CFR 30.63. The trade should already be reporting them. To be consistent with 15 CFR 30.63, the term, “mode of transportation”, where appearing in proposed § 192.14(c)(2)(i), is changed in this final rule to “method of transportation.” 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The USPPI should provide only the intended port of exportation because the actual port of exportation might not be known to the USPPI. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The USPPI or its authorized agent must report the port of exportation as known when the USPPI or its agent tenders the cargo to the outbound carrier. Should the carrier export the cargo from a different port, and the carrier so informs the USPPI or agent, the port of exportation must be corrected by the filer in AES. Proposed § 192.14(c)(2)(vi) is revised in this final rule to clarify this issue. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter wanted a more specific estimate of the expected completion and implementation date for the AES commodity module and whether it was on target for completion. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The target date for the redesign of the AES commodity module remains mid-2004. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The automated systems in place should be able to accommodate the required manifest reporting sufficiently for legitimate trade to continue to flow smoothly. Also, there should be a generous and realistic grace period. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP supports the use of AES systems that are already heavily in use and widely available to USPPIs; and with Internet connections, new users can be brought into the system fairly easily and inexpensively. Moreover, outbound implementation of these regulations is contingent upon the completion of the AES Commodity Redesign and implementation by the Bureau of Census of mandatory AES for all export shipments which currently require a Shipper's Export Declaration (SED) (see § 192.14(e) in this final rule). 
                    </P>
                    <HD SOURCE="HD1">Comments on Economic Analysis </HD>
                    <HD SOURCE="HD2">General </HD>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters stated that the proposed rule is a significant regulatory action. It was contended that CBP did not completely appreciate the magnitude of the impact of the proposed requirements. Importers, exporters, brokers, carriers, forwarders, consolidators and many others will be required to modify their business practices. Before implementation and enforcement begins, it is strongly believed that further economic impact analysis is warranted. 
                    </P>
                    <P>Several commenters stated that the preliminary economic analysis understated the true impact on the affected enterprises. In addition, some questioned that the preliminary analysis conclusion only addressed the impact on small entities, making it insufficient to make a proper determination of impact on the U.S. economy as a whole. Others expressed their belief that the real effect of the proposed rule would be far greater than the $100 million threshold, making the proposal a significant regulatory action. </P>
                    <P>It was said to be hard to believe that the transportation and trade industry would not have a similar cost increase [to the $4-$6 USPS estimate]. This increased cost exceeded the $100 million impact threshold. Already industry was seeing increases in transportation and operational costs associated with new security measures. The economic analysis presented seriously underestimated the true cost to industry. </P>
                    <P>It was believed that CBP failed to recognize the majority of other carriers [non-express], mostly non AMS, and other smaller carriers where the cost impact would be greater; these carriers would incur significant costs to redesign their systems. Moreover, the costs to consolidators, indirect air carriers, shippers and brokers were not factored in at all. </P>
                    <P>It was also asserted that the impact study had been too limited to support the conclusion that the cost was acceptable. </P>
                    <P>Finally, it was contended that the proposed rule stated that the effect of the rule on the economy would be slight to negligible. Yet, the study did not define negligible. The proposed rules would increase the cost of transportation for all goods imported into the U.S. other than by USPS. A significant portion, and perhaps all of these increased costs would be reflected in the increased costs of imported goods. </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         After further analysis of the proposed rule, CBP agrees that the rule is a significant regulatory action under Executive Order 12866, and that the cost of the rule will exceed $100 million. Accordingly, CBP has conducted a regulatory impact analysis (RIA) of the rule, which is available at the following Web site, 
                        <E T="03">http://www.cbp.gov.</E>
                    </P>
                    <P>
                        The CBP's economic analysis for the final rule has estimated the cost to all affected sectors unless it was determined that the costs would be insignificant or that the costs would be passed to a different sector (
                        <E T="03">e.g.</E>
                        , from brokers to importers). 
                    </P>
                    <HD SOURCE="HD2">Air </HD>
                    <P>
                        <E T="03">Comment:</E>
                         New automation systems and interfaces should be developed to gather the additional data elements required, at considerable costs. Additional labor costs will be incurred for systems administration, data entry, and subsequent carrier activities as a result of any targeted shipments. 
                    </P>
                    <P>It is estimated that the express industry will incur development and implementation costs in excess of $25 million. Additional labor costs for delivery of the data and subsequent required actions for targeted shipments for the express industry will exceed $15 million annually. </P>
                    <P>There are issues of additional handling for late shipments that must be held for the next day, lost revenues for transit shipments that will no longer be shipped on U.S. carriers, additional inventory to be carried by importers as defense against supply outages or factory shutdowns; labor reductions, and similar related actions. </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP's economic analysis for the final rule has estimated the cost of service degradation caused by delays using a logistics cost calculator for a range of delay times. The analysis always includes estimates for additional programming. The CBP has no basis on which to estimate the percentage of cargo (by weight or value) currently being transshipped through the U.S. that might be diverted through non-U.S. airports. The CBP recognizes that targeted shipments may require additional steps for air carriers, but has no basis for estimating the number of shipments that will be targeted or the degree to which the targeting will result in additional costs. For inbound shipments, the targeted shipment will be examined on arrival, which should impose a limited burden on the air carrier. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Many carriers are evaluating options for AAMS. The costs indicated by CBP for transmission fees are low compared to average costs by AAMS vendors. In addition, the cost of purchasing software is above any amounts identified by CBP. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The costs used in the final economic analysis are based on estimates provided by vendors. These costs vary by vendor and by the complexity of the software and its integration into the user's system. The 
                        <PRTPAGE P="68163"/>
                        analysis assumes that larger carriers will develop their own software integration packages and that existing users of AMS will modify their internal systems to provide the more detailed cargo information. Only carriers that enter fewer than 500 air bills per month incur minimum costs. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Labor costs do not appear to include employee benefits, which would increase the labor rate by 30%. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Labor rates used in the final economic analysis are loaded with fringe benefits and overhead. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The “wheels up” requirement will result in a significant increase in staffing to meet deadlines. Air carriers will see a shift from air to truck. The rule will result in a revenue loss of premium services. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The final economic analysis estimates the costs of delays for a range of times. These costs include personnel costs. Although it is possible that some short-haul shipments will shift to truck, most shipments from Canada and northern Mexico destined for locations beyond the immediate border will probably still be shipped by air because of the considerable time-savings. Shipments from other parts of Latin America north of the equator and the Caribbean are likely to continue being sent by air. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Significant costs will be associated with changes in operating schedules. A high percentage of express volume is provided late in the day, close to cut-off time. New requirements which force an earlier cut-off time would be a binding constraint. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The final economic analysis estimates costs for both delays and service degradation resulting from the new requirements. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Further skewing the results is the fact that no costs are included for training personnel, restructuring operational systems to allow time to receive and submit information, or handling rejected shipments. The proposed scheme would directly negatively impact the key elements of the air cargo business—speed and reliability—and would severely jeopardize the needs of the global shipping community. These costs are not captured in the study. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The final economic analysis estimates costs for both delays and service degradation. Rule familiarization costs were estimated based on U.S. wage rates for all modes, but represent a very small part of total costs. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Business will be lost in the transit sector. Shipments transiting the U.S. would be diverted to competitors that do not transit the U.S. The costs of compliance will have an asymmetric impact, placing us at a competitive disadvantage. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP has no basis on which to estimate the percentage of cargo (by weight or value) currently being transshipped through the U.S. that might be diverted through non-U.S. airports. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         “Just in time” (JIT) shippers will also be affected by an earlier cut-off time. Earlier shipping or delayed arrival of shipments create higher costs for seller and buyer. Shippers close to the border may switch shipping modes; warehousing costs may increase; inventory and associated carrying costs will rise. 
                    </P>
                    <P>The statement in the proposed rule that JIT considerations are eliminated is simply not true. The CBP has failed to acknowledge the carrier requirements for handling and manifest preparation. Current post-departure manifesting allows manifesting on a different later schedule than sorting and loading. To complete a manifest at wheels up, the carrier will be forced to cut off receipt of shipments several hours earlier, especially for shorter flights, delaying shipments by a day or diverting them to another mode. </P>
                    <P>Removing even one or two hours available shipping time could remove 20-30% of volume for a specific market. Air carriers (express and conventional) carry time-sensitive parts and supplies every day. The CBP's claim of no impact to JIT fails to acknowledge operational realities of transportation handling requirements, at least for air shipments. </P>
                    <P>The proposal will require earlier deadlines for shippers. Shippers of perishable commodities such as flowers, produce, and fish will increase their losses from damaged and spoiled product. The cost-benefit analysis overlooks this fact. </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP's economic analysis for the final rule has estimated the cost of delays and service degradation caused by delays using a logistics cost calculator for a range of delay times and cargo mix (perishables, non perishables). 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         There is an additional cost for educating customers about the requirements of the rule. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The cost of educating shippers is not possible to estimate. The majority of shipments by value or weight are likely from companies that ship on a regular basis. They will incur one-time costs to understand the new requirements. There will always be new shippers entering the system who will need to learn what is needed. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The estimate of 2.41 million air waybills per month for express carriers is grossly understated. Some carriers use summary manifesting, under which multiple consignments of letters or documents are manifested as one record. One entry may cover hundreds of individual consignments. It is important that each waybill be counted, rather than entries, as the individual shipment record will require screening. The CBP is urged to review these numbers, and validate their accuracy. Understatement will severely affect the calculated capacity and system performance of the Automated Targeting System (ATS). 
                    </P>
                    <P>The number of express air bills counted may only be those requiring formal entry, which represent about 15 to 25 percent of the total shipment count. The real annual number of express bills is closer to 25 million rather than 3.27 million. The economic analysis for USPS resulted in a cost of $4-$6 per package. </P>
                    <P>The number of other air cargo waybills were likely master air bills; no accounting was made for house bills. One may reasonably increase master bills by a factor of 10 for a total air bill count, closer to 8 million instead of 800,000. That leaves about 7 million new transactions to be entered into the automated system for regular air cargo shipments. For the express group, their volume of air bills may be a very narrow slice of what will now be required. </P>
                    <P>The question is presented as to how CBP reconciles its claim that there is virtually no cost to carriers when CBP estimates an annual cost to USPS of at least $120 million. While automation does exist in the carrier community, the staggering increase in the number of transactions that will require reporting has a significant cost. Most of the forwarder and airline expense associated with air AMS will be new expense. Using the USPS estimate, the required reporting of potentially 32 million transactions in AMS meets the $100 million threshold. </P>
                    <P>The assumption that USPS will not absorb these costs or pass them directly to users implies that USPS may have a competitively advantaged position. </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The final economic analysis includes cost estimates for entering new information into Air AMS using a range of scenarios to reflect variations in the number of additional bills that will be entered. These cost estimates may be overstated because they are based on U.S. and Canadian wages; many shipments will be arriving from countries where wages are much lower. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The assumption that all large express carriers have AAMS capability at present and need only flip 
                        <PRTPAGE P="68164"/>
                        a switch to immediately begin transmitting the required data is patently incorrect and ignores a multitude of operational realities of physical shipment handling, sorting, loading, weight and balance calculations, and coordinating with manifesting. Manifest preparation entails multiple automated systems that are not currently interfaced with AAMS. The simple hard fact is that large express carriers are heavily impacted through significant operational changes, earlier cut-off times, and development of new software. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The final economic analysis estimates costs for operational changes and earlier cut-off times. Because the two major express carriers do not use AMS for express consignments, but allow CBP to access their proprietary systems for data, CBP is uncertain that they will incur new costs for automated systems. Nonetheless, the final economic analysis includes costs for 4,000 hours of programming per AMS carrier to cover any new interfaces that are needed. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Numerous carriers arriving in the U.S. have limited or no electronic messaging capabilities in their origin locations. It would be beneficial for CBP to reevaluate the economic impact created by implementing the proposed rule. If carriers cannot currently comply or will require significant investment in systems and manpower to comply in the time allotted, JIT shipping will be in jeopardy. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The final economic analysis estimates costs for acquiring or developing the software needed to file electronically. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Not all affected parties were considered during the analysis. Foreign flag carriers and shippers were not part of the analysis. This rule has worldwide implications. A similar regulation has been proposed in Canada and is likely to appear in other countries. The rule will significantly impact the global trade community. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Executive Order 12866 requires a focus on the U.S. economy, thus enumerating all possible impacts to global trade may be beyond the scope of the analysis. To the extent that foreign entities, however, participate in the U.S. economy and impacts to foreign entities affect the U.S. economy, the Executive Order does apply to foreign entities. To that end, the accompanying regulatory impact analysis to this final rule does estimate the impact on foreign entities, although in many cases it is difficult to separate the impact on foreign entities from the overall estimate. On the other hand, the Regulatory Flexibility Act does not apply to small foreign entities. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Forwarder and air carriers are obliged to have a huge investment to develop or modify their Electronic Data Interchange (EDI) system; they will also have a large operating cost day to day. They are afraid they will not be able to bear this huge cost. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The RIA estimates costs for implementing AMS. These costs are likely to vary considerably based on the level of imports being handled by a carrier or forwarder. The CBP notes that forwarders are not required to file information; they have the option to provide the information to the carrier. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The requirement for hard copy filing in the event of EDI failure is time-consuming and very costly. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP assumes that carriers can easily e-mail or fax a hard copy to their agents at the destination airport should this be necessary. 
                    </P>
                    <HD SOURCE="HD2">Truck </HD>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter stated that the economic analysis is inadequate and unscientific. They assert that the proposed rule is a significant regulatory action. They assert that the combined annual impact of the air and truck rules on their company would be $695,000. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         These comments are very general. Without knowing how the impact on their company was estimated, CBP cannot comment on the estimate. The CBP agrees that the rule is a significant action. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Several commenters stated that the “economic assumptions” used by CBP did not include additional labor and equipment needed to do the “same quantity of work in a shorter time.” 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         These comments are not specific enough to permit direct response. The commenters do not offer any support for the assertion that time available to do required work has been reduced. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Some commenters refer to inaccuracies in the economic analysis, but do not specify them. They recommend that CBP conduct a comprehensive economic analysis. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP has completed an economic analysis of the rule. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         One commenter asserts that the rule will have a significant impact because many small truckers do not have the technology to use PAPS. The commenter also states that fewer than ten percent of Mexican trucking firms have automated systems in place. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP agrees that the rule will have a significant economic impact. In order to use Selectivity PAPS, a trucking firm will have to obtain a SCAC number and bar-code strips. These costs are included in the RIA prepared by CBP. While many Mexican carriers may not have automated systems, U.S. customs brokers now make electronic pre-filings based on information supplied by Mexican brokers. This is true for all shipments except those coming through under BRASS. The RIA includes the cost to U.S. brokers for preparing the pre-entry filing for shipments now using BRASS. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         The CBP is planning, in due course, full implementation of ACE. Therefore, the costs of adapting to ACE should be treated as costs of the rule. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP's plans for implementation of ACE are not driven by the Trade Act and would be implemented whether or not the rule is implemented. Therefore, the costs of adaptation to ACE may not be attributed properly to the rule. Costs of adapting to Selectivity PAPS are included in the RIA. 
                    </P>
                    <HD SOURCE="HD2">Vessel </HD>
                    <P>
                        <E T="03">Comment:</E>
                         It is incumbent on CBP to provide a more meaningful and realistic analysis of the impact of the rules on small businesses before it promulgates a final rule and commences mandatory implementation and enforcement. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The Regulatory Flexibility Act, which establishes the “significant impact to a substantial number of small entities” test, applies to small U.S. businesses. The CBP's Regulatory Impact Analysis (RIA) for the final rule has estimated the impact of the rule on small businesses. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         There is no analysis of the effects that the proposed rule will have on NVOCCs, air forwarders, and surface forwarders. In most, if not all instances, NVOCCs and other forwarders will be required to make substantial investments in software, employ additional personnel and enter into contractual arrangements with data service centers. 
                    </P>
                    <P>The regulatory flexibility analysis (RFA) should be broadened to consider both the dollar costs on forwarders and any operational consequences of the proposed rules. </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP estimates that 650 Non-Vessel Operating Common Carriers (NVOCC) are already automated. The CBP believes that the proposed requirements will not have a significant impact on a substantial number of NVOCCs. Those that choose not to automate, can instead use the services of an authorized service provider, a qualified port authority, or provide the shipment information to the 
                        <PRTPAGE P="68165"/>
                        carrier. Therefore, in the final economic analysis, CBP has not estimated the costs of the proposed rule on NVOCCs. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         Although a large percentage of manifests presently submitted to Customs are submitted electronically, this does not mean that a large percentage of the organizations presently submitting manifests are presently doing so via AMS or are capable of doing so. 
                    </P>
                    <P>One company stated that it submits approximately 100 single page manifests for vessels that import over 5 million tons of bulk commodities in a year. Due to this insignificant number of manifests, which cover a large amount of cargo, the company stated that it is not equipped to submit cargo manifests electronically and to do so would represent a substantial financial penalty. </P>
                    <P>At the present time pre-arrival manifests are submitted by fax at basically no cost even though they are sent to several branches of the Federal government. An investigation into obtaining a “provider” via whom manifests could be submitted electronically had indicated a set up cost of $1,000 and a monthly minimum for one SCAC code of $200. </P>
                    <P>Therefore, strong disagreement was noted with the initial analysis that the proposed rule would not have a significant economic impact upon a substantial number of small entities. </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         Virtually all shipping companies that are owned by U.S. citizens or are U.S. flagged are currently filing manifests electronically. The CBP has been able to identify only 24 shipping companies that carry cargo into U.S. ports from the Caribbean that do not use AMS. The CBP does not believe that any of these companies are U.S. owned nor are any of the ships U.S. flag. Consequently, the proposed rule on vessels is not expected to have any economic impact on U.S. companies. 
                    </P>
                    <P>
                        <E T="03">Comment:</E>
                         It is estimated that 25 million bills of lading are issued annually for container cargo from Japan to the United States. Shipping companies are charged a $25 fee for transforming and inputting a shipper's cargo data to the AMS. This means that the cost of trade between Japan and the United States will increase $625 million per year through the introduction of the 24-hour rule. Contrary to the CBP's claim that much of the trade already uses electronic transmission systems and therefore would not incur significant compliance costs, this fact indicates that substantial costs would be imposed on the trade when the requirements of advance electronic cargo information are implemented. 
                    </P>
                    <P>
                        <E T="03">CBP Response:</E>
                         The CBP believes that virtually all shipping companies that are owned by U.S. citizens or are U.S. flagged are currently filing manifests electronically. Further, even if none of the non-U.S. trade participants were automated, the estimated annual cost of trade of $625 million would represent less than one percent of a total value of U.S. imports from Japan (this calculation is based on the 2001 import values; Source: Bureau of Transportation Statistics). 
                    </P>
                    <HD SOURCE="HD1">Summary of Significant Changes </HD>
                    <P>
                        As referenced in the Discussion of Comments, supra, this final rule document makes three significant changes from the proposed rule. These changes consist of: (1) Removing the provision concerning advance cargo data for air shipments listed as letters and documents and making it the subject of a separate 
                        <E T="04">Federal Register</E>
                         publication (proposed § 122.48a(d)(3) as such is removed from this final rule); (2) requiring certain additional data elements from the incoming air carrier in the case of split shipments (a new § 122.48a(d)(3) is thus added in this final rule); and (3) decreasing the rail outbound time frame from “4 hours prior to the attachment of the locomotive before going foreign” to “2 hours prior to arrival at the border” (§ 192.14(b)(1)(iv)). 
                    </P>
                    <HD SOURCE="HD1">Adoption of Proposal </HD>
                    <P>In view of the foregoing, and following careful consideration of the comments received and further review of the matter, CBP has concluded that the proposed regulations with the modifications discussed above should be adopted as a final rule. </P>
                    <HD SOURCE="HD1">Additional Changes </HD>
                    <P>For greater editorial accuracy, the reference in proposed § 113.64(a) and (c) to “§ 122.48a(c)(2)” is changed in this final rule to “§ 122.48a(c)(1)(ii)-(c)(1)(iv)”. Also, proposed § 122.48a(a)(2) is revised in this final rule to distinguish between Diplomatic Pouches and Diplomatic Cargo, the latter of which is subject to the full advance cargo data reporting requirements of § 122.48a. In addition, proposed § 123.8 is amended consistent with § 122.38(g) in this final rule. Lastly, proposed §§ 123.91(a) and 123.92(a) are changed to make clear that cargo data must be received within the relevant time frame before the subject cargo reaches the first port of arrival in the United States. </P>
                    <HD SOURCE="HD1">Transportation Security Administration—Cargo Security Programs </HD>
                    <P>It is also stressed that these final regulations to implement section 343(a), as amended, may, in the foreseeable future, be subject to modification as necessary to accommodate a cargo security program that may be developed by the Transportation Security Administration (TSA) in accordance with the Aviation and Transportation Security Act (Pub. L. 107-71, 115 Stat. 597; November 19, 2001 (49 U.S.C. 114(d), (f)(10); 44901(a), (f)). </P>
                    <HD SOURCE="HD1">Regulatory Analyses </HD>
                    <HD SOURCE="HD2">Executive Order 12866 </HD>
                    <P>Under Executive Order 12866 (58 FR 51735, October 4, 1993), CBP must determine whether a regulatory action is “significant” and, therefore, subject to OMB review and the requirements of the Executive Order. The Order defines “significant regulatory action” as one that is likely to result in a rule that may: </P>
                    <P>(1) Have an annual effect on the economy of $100 million or more or adversely affect in a material way the economy, a sector of the economy, productivity, competition, jobs, the environment, public health or safety, or state, local, or tribal government or communities. </P>
                    <P>(2) Create a serious inconsistency or otherwise interfere with an action taken or planned by another agency. </P>
                    <P>(3) Materially alter the budgetary impact of entitlements, grants, user fees, or loan programs or the rights and obligations of recipients thereof. </P>
                    <P>(4) Raise novel legal or policy issues arising out of legal mandates, the President's priorities, or the principles set forth in the Executive Order. </P>
                    <P>
                        The CBP has determined that the rule will have an annual effect on the economy of more than $100 million and is, therefore, an economically significant regulatory action. Accordingly, it has prepared a regulatory impact analysis for the rule, which is available on the CBP Web site, 
                        <E T="03">http://www.cbp.gov.</E>
                    </P>
                    <HD SOURCE="HD3">Costs </HD>
                    <P>
                        The analysis examined each of the modes and identified changes that are likely to impose new costs on U.S. carriers. Because virtually all vessels and railroads are already filing electronically, costs were estimated for these sectors to be insignificant. Exports to Canada by truck are generally exempted from regulation. For exports by air, shippers complete the shipper's export declaration prior to presenting the shipment to a carrier; therefore, the 
                        <PRTPAGE P="68166"/>
                        new time requirements for filing will be met. 
                    </P>
                    <HD SOURCE="HD2">Truck </HD>
                    <P>The analysis estimated costs and cost savings for inbound trucks from Canada, and inbound and outbound trucks to Mexico. Although the rule will impose costs on trucks that are not currently filing electronically, the analysis estimates that these costs are offset by the savings that will result from faster movement across the border. Overall, the analysis estimates that the rule will impose new costs of $91 million on trucking, which will be offset by savings of $142 million. </P>
                    <HD SOURCE="HD2">Air </HD>
                    <P>The analysis indicates that the rule will impose substantial costs on the 39 U.S. air carriers currently certificated for foreign operations as well as more than 100 foreign carriers that fly cargo into the U.S. These costs arise from three factors: the need to implement electronic filing systems and improve existing systems; delays and service degradation that will result from the requirement to file information at wheels up from airports north of the equator in the western hemisphere; and the requirement to file detailed information on all cargo including documents. Because passenger-carrying carriers cannot easily delay operations to complete cargo information, the analysis assumed that these carriers would limit cargo and reduce revenues rather than delay flights. Comments on the proposed rule cited other changes that could result from the rule and impose costs: diversion of air cargo to trucks, diversion of in-transit cargo to other carriers who do not fly through the U.S., and targeting of shipments, delaying unloading of the aircraft. Because CBP has no basis for estimating the degree to which diversion or targeting may occur, the analysis did not quantify costs for these impacts. The analysis examined four options for air: </P>
                    <P>(1) The proposed rule, which required information on all cargo including documents; </P>
                    <P>(2) An option that required information on all cargo except documents that weigh less than one pound (16 ounces); </P>
                    <P>(3) An option that required information on all cargo except documents; and, </P>
                    <P>(4) An option originally recommended by the Treasury Advisory Committee on the Commercial Operations of the U.S. Customs Service (COAC), but modified by CBP, that would require no detailed information on documents and filing an hour before arrival for flights into the U.S. from airports north of the equator in the western hemisphere. </P>
                    <P>
                        The options allow an examination of the impact of varying requirements on cargo and filing times. The CBP has elected option three above because the proposal to cover advance electronic cargo information on letters and documents will be the subject of a separate 
                        <E T="04">Federal Register</E>
                         publication. However, the RIA for this final rule document will cover the other publication as well. As noted, the RIA is available on the CBP Web site, 
                        <E T="03">http://www.cbp.gov.</E>
                    </P>
                    <P>
                        Because of the considerable uncertainty that exists about the impacts on delays and service degradation as well as about the number of air bills that will need to be filed under the rule, the analysis examined each of these impacts across a range of scenarios from low impacts (
                        <E T="03">e.g.</E>
                        , 30 minute delays, 10 percent loss of revenues, twice as many air bills) to high impacts (2 hour delays, 40 percent loss of revenue, 8 times as many air bills). The analysis indicated that the total annualized cost to the air carriers could range from $345 million for the low impact COAC option to $4.7 billion for the high impact proposed rule option. Table 1 presents the costs for the four options, annualized over five years (7 percent discount rate). 
                    </P>
                    <GPOTABLE COLS="4" OPTS="L2,i1" CDEF="s25,6,6,6">
                        <TTITLE>Table 1.—Annualized Total Cost to Air Carriers [millions] </TTITLE>
                        <BOXHD>
                            <CHED H="1">  </CHED>
                            <CHED H="1">Low </CHED>
                            <CHED H="1">Medium </CHED>
                            <CHED H="1">High </CHED>
                        </BOXHD>
                        <ROW>
                            <ENT I="01">All Documents </ENT>
                            <ENT>$2,914 </ENT>
                            <ENT>$3,652 </ENT>
                            <ENT>$4,736 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">Large Documents </ENT>
                            <ENT>930 </ENT>
                            <ENT>2,177</ENT>
                            <ENT>3,770 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">No Documents </ENT>
                            <ENT>422 </ENT>
                            <ENT>1,160</ENT>
                            <ENT>2,244 </ENT>
                        </ROW>
                        <ROW>
                            <ENT I="01">COAC Option </ENT>
                            <ENT>345 </ENT>
                            <ENT>994 </ENT>
                            <ENT>1,889 </ENT>
                        </ROW>
                    </GPOTABLE>
                    <P>As can be seen from Table 1, the degree to which detailed information is required for documents drives the cost of the rule. Overall, the requirement for filing house bill rather than master bill information electronically imposes the greatest cost. The costs of delays and service degradation, although significant to a few carriers, are limited because only about 25 percent of inbound air cargo on U.S. carriers and 10 percent of inbound cargo on foreign carriers is Canada, the Caribbean, and Latin America north of the equator. </P>
                    <HD SOURCE="HD3">Benefits </HD>
                    <P>
                        Examination of the benefits was largely qualitative because the most significant benefits are essentially unquantifiable. The most important benefit of the rule will be the improvement in national security, an issue that is difficult to measure in monetary terms. However, there are some additional benefits expected that were quantified. Most of the incremental quantifiable benefits are expected from changes taking place at the northern border crossings for inbound truck traffic. The rule is expected to streamline the process for checking inbound trucks at Canadian border crossings, leading to benefits from time savings due to reduced congestion that are in addition to the time savings realized by trucks that change their border-crossing procedures under the rules. The analysis estimated the value of the time savings at $18 million. Additionally, reduced congestion would lead to less truck idling (or moving at very slow speeds) and consequent reductions in air pollution and fuel costs. The fuel savings were estimated at $4 million. Because of the lack of data on how congestion reductions for commercial traffic can affect non-commercial traffic at the border (
                        <E T="03">e.g.</E>
                        , cars), the analysis did not quantify this benefit. Finally, trucks leaving the country through the Mexican border are expected to provide some qualitative benefits through improvements in data collection. 
                    </P>
                    <HD SOURCE="HD3">Summary </HD>
                    <P>Combining the costs, cost savings, and monetized benefits, the analysis estimates that the rules produce net savings to the trucking sector of $78 million, and net costs to U.S. air carriers of $345 million to $4.7 billion. </P>
                    <HD SOURCE="HD1">Regulatory Flexibility Act </HD>
                    <P>
                        Under the Regulatory Flexibility Act of 1980, as amended by the Small Business Regulatory Enforcement Fairness Act of 1996 (5 U.S.C. 601 
                        <E T="03">et seq.</E>
                        ), Federal agencies must evaluate the impact of rules on small entities and consider less burdensome alternatives. As discussed in the previous section, CBP has conducted a cost benefit analysis on this rule. As part of that analysis, CBP evaluated the impact on small entities. The CBP has determined that this rule could have a significant economic impact on a substantial number of small air carriers. Companies in the other modes are unlikely to incur substantial costs to comply and may benefit from the rule. 
                    </P>
                    <P>
                        For air, the lowest cost option would impose costs in excess of one percent of operating revenues for 7 of the 19 small carriers. The high cost options would impose significant costs on 12 of the 19 small carriers; four of the carriers could have costs in excess of 10 percent of their operating revenues. Seven of the 19 carriers operated at a loss in 2002. 
                        <PRTPAGE P="68167"/>
                        Despite the uncertainty that exists in estimating costs, it is, therefore, likely that the rule would create a significant economic impact on small air carriers. Because most of these costs are driven by the cost of electronic data entry, which is mandated by statute, mitigating the impacts is difficult. Many of the small entities may address this issue by having the shipper or consolidator submit the information to CBP. 
                    </P>
                    <P>
                        A copy of the small business analysis for this rule, which is chapter 6 of the regulatory impact analysis, is available on the CBP Web site, 
                        <E T="03">http://www.cbp.gov.</E>
                    </P>
                    <HD SOURCE="HD2">Paperwork Reduction Act </HD>
                    <P>The collection of information in this final rule document was submitted for review and has been approved by the Office of Management and Budget (OMB) in accordance with the requirements of the Paperwork Reduction Act of 1995 (44 U.S.C. 3507(d)) under OMB control number 1651-0001 (Transportation Manifest (Cargo Declaration)). An agency may not conduct, and a person is not required to respond to, a collection of information unless the collection of information displays a valid control number assigned by OMB. </P>
                    <P>The collection of information in this document is contained in §§ 4.7a(c)(4), 122.48a, 123.91, 123.92, and 192.14. Under these sections, the information would be required and used to determine the safety and security conditions under which cargo to be brought into or sent from the United States was maintained prior to its arrival or departure. The likely respondents and/or recordkeepers are air, truck, rail and vessel carriers, Non Vessel Operating Common Carriers (NVOCCs), freight forwarders, deconsolidators, express consignment facilities, importers, exporters, and Customs brokers. The estimated average annual burden associated with this information collection is 52.3 hours per respondent or recordkeeper. </P>
                    <P>Comments on the accuracy of this burden estimate and suggestions for reducing this burden should be sent to the Regulations Branch, Office of Regulations and Rulings, Bureau of Customs and Border Protection, 1300 Pennsylvania Avenue, NW., Washington, DC 20229. </P>
                    <P>Part 178, Customs Regulations (19 CFR part 178), containing the list of approved information collections, is revised as appropriate to reflect the approved information collections covered by this final rule. </P>
                    <HD SOURCE="HD2">Executive Order 12988 </HD>
                    <P>This regulation meets the applicable standards set forth in Sections 3(a) and 3(b)(2) of Executive Order 12988 Civil Justice Reform. </P>
                    <HD SOURCE="HD2">Executive Order 13132 </HD>
                    <P>This rulemaking does not preempt or modify any provision of state law; nor does it impose enforcement responsibilities on any state; nor does it diminish the power of any state to enforce its own laws. Accordingly, this rulemaking does not have federalism implications warranting the application of Executive Order 13132. </P>
                    <HD SOURCE="HD2">Unfunded Mandates Reform Act of 1995 </HD>
                    <P>
                        Title II of the Unfunded Mandates Reform Act of 1995 (UMRA; 2 U.S.C. 1501 
                        <E T="03">et seq.</E>
                        ) requires cost-benefit and other analyses before any rulemaking if the rule would include a “Federal mandate that may result in the expenditure by State, local, and tribal governments, in the aggregate, or by the private sector, of $100,000,000 or more (adjusted annually for inflation) in any 1 year”. The current inflation-adjusted statutory threshold is $113 million. 
                    </P>
                    <P>This rule will not have a significant effect on state, local or tribal governments within the scope of the UMRA. However, CBP has determined that this final rule is significant under UMRA because it anticipates that the rule will result in an aggregate expenditure by the private sector of $113,000,000 or more in any one year. </P>
                    <P>Consequently, CBP has conducted the required economic impact analyses as noted in the above section, “EXECUTIVE ORDER 12866”. The other requirements under UMRA include assessing the rule's effects on:</P>
                    <P>• Future costs </P>
                    <P>• Particular regions, communities, or industrial sectors </P>
                    <P>• National productivity </P>
                    <P>• Economic growth </P>
                    <P>• Full employment </P>
                    <P>• Job creation </P>
                    <P>• Exports</P>
                    <P>The regulatory impact analysis, discussed in the “EXECUTIVE ORDER 12866” section, covered many of these issues in greater detail. To summarize, the regulations will impose costs into the future; most costs are presented in the impact analysis on an annual basis. The regulations will impact many different regions, communities, and sectors; but with the exception of air carriers the impact will be disbursed and will not be concentrated geographically. In addition, these regulatory impacts, although large in absolute terms, generally do not rise to the level where they could cause any sort of macro effects on productivity, growth, employment, or jobs. </P>
                    <P>With regard to the impacts on trade, although most of the information required for advance manifest notification and SED (Shippers Export Declaration) notification is already supplied to CBP, this new notice requirement may cause a reduction of imports of certain products into the U.S. and exports out of the U.S. Some entities may choose to stop exporting products from the U.S. (or importing products to the U.S.) if the additional costs of complying increase the price of the products to the point where they cannot compete with lower-priced products produced within domestic markets. On the other hand, there are products for which substitutes are not available. In these cases, and in cases where demand for the product greatly exceeds domestic supply, importers may pay an increased price for the product. The CBP believes, however, that the “per shipment” cost of these requirements is quite small and therefore this rulemaking will not have a significant impact on the relative competitiveness of foreign versus domestically produced products either within or outside of the U.S. </P>
                    <P>When a rule would result in expenditures greater than $113 million, UMRA requires outreach to the regulated community and discussion of proposals. The CBP conducted extensive discussions with the regulated community prior to the development of the rule. In January 2003 CBP held separate meetings with each of the transportation modes to solicit information and comments. The CBP also accepted comments from members of the regulated community as it developed its proposed rule and held numerous meetings with the COAC committees, which submitted recommendations. Finally, CBP received more than 100 comments on the proposed rule, which were considered in the development of the final rule. </P>
                    <P>
                        For a more detailed analysis, please refer to the regulatory impact analysis prepared for this rule, which is available on the CBP Web site, 
                        <E T="03">http://www.cbp.gov.</E>
                    </P>
                    <HD SOURCE="HD1">CBP Issuance of Rule Under DHS Authority; 19 CFR 0.2(a) </HD>
                    <P>
                        When the Trade Act of 2002 was enacted (Pub. L. 107-210; August 6, 2002), the Customs Service existed as part of the Department of the Treasury. Thereafter, the Homeland Security Act of 2002 was enacted (Public Law 107-296; November 25, 2002), which created 
                        <PRTPAGE P="68168"/>
                        the Department of Homeland Security (DHS). Section 403 of the Homeland Security Act (the Act) transferred to the newly created Department the functions, personnel, assets, and liabilities of the Customs Service, including the functions of the Secretary of the Treasury relating thereto. Customs, later renamed as CBP, thereby became a component of DHS. Furthermore, the Department of the Treasury recently issued an order (Treasury Order 100-16, dated May 15, 2003) delegating to DHS certain Customs revenue functions that were otherwise retained by the Treasury Department under sections 412 and 415 of the Act. In accordance with the Homeland Security Act and this transfer and delegation of functions, certain matters, such as this rule which is designed to ensure cargo safety and security rather than revenue assessment, now fall solely within the jurisdiction of DHS. Therefore, this regulation is being issued by CBP under the authority of DHS in accordance with 19 CFR 0.2(a) (see CBP Dec. 03-24, 68 FR 51868, August 28, 2003). 
                    </P>
                    <HD SOURCE="HD3">Coordination of Final Rule With Congress </HD>
                    <P>Pursuant to section 343(a)(3)(L) (19 U.S.C. 2071 note, section (a)(3)(L)), the required report regarding this final rule document has been timely made to the committees on finance and commerce, science, and transportation of the Senate and the committees on ways and means and transportation and infrastructure of the House of Representatives. </P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects </HD>
                        <CFR>19 CFR Part 4 </CFR>
                        <P>Administrative practice and procedure, Arrival, Cargo vessels, Common carriers, Customs duties and inspection, Declarations, Entry, Exports, Foreign commerce and trade statistics, Freight, Imports, Inspection, Maritime carriers, Merchandise, Penalties, Reporting and recordkeeping requirements, Shipping, Vessels. </P>
                        <CFR>19 CFR Part 103 </CFR>
                        <P>Administrative practice and procedure, Computer technology, Confidential business information, Electronic filing, Freedom of information, Reporting and recordkeeping requirements. </P>
                        <CFR>19 CFR Part 113 </CFR>
                        <P>Air carriers, Bonds, Common carriers, Customs duties and inspection, Exports, Foreign commerce and trade statistics, Freight, Imports, Reporting and recordkeeping requirements, Vessels. </P>
                        <CFR>19 CFR Part 122 </CFR>
                        <P>Administrative practice and procedure, Advance notice of arrival, Advance notice requirements, Air cargo, Air cargo manifest, Air carriers, Aircraft, Air transportation, Commercial aircraft, Customs duties and inspection, Entry procedure, Foreign commerce and trade statistics, Freight, Imports, Penalties, Reporting and recordkeeping requirements, Security measures. </P>
                        <CFR>19 CFR Part 123 </CFR>
                        <P>Administrative practice and procedure, Aircraft, Canada, Common carriers, Customs duties and inspection, Entry of merchandise, Freight, Imports, International traffic, Mexico, Motor carriers, Railroads, Reporting and recordkeeping requirements, Vehicles, Vessels. </P>
                        <CFR>19 CFR Part 178 </CFR>
                        <P>Administrative practice and procedure, Collections of information, Exports, Imports, Paperwork requirements, Reporting and recordkeeping requirements. </P>
                        <CFR>19 CFR Part 192 </CFR>
                        <P>Administrative practice and procedure, Aircraft, Customs duties and inspection, Exports, Foreign trade statistics, Law enforcement, Motor vehicles, Reporting and recordkeeping procedures, Vehicles, Vessels. </P>
                    </LSTSUB>
                    <HD SOURCE="HD1">Amendments to the Regulations </HD>
                    <REGTEXT TITLE="19" PART="4">
                        <AMDPAR>Parts 4, 103, 113, 122, 123, 178, and 192, Customs Regulations (19 CFR parts 4, 103, 113, 122, 123, 178, and 192), are amended as set forth below. </AMDPAR>
                        <PART>
                            <HD SOURCE="HED">PART 4—VESSELS IN FOREIGN AND DOMESTIC TRADES </HD>
                        </PART>
                        <AMDPAR>1. The general authority citation for part 4 is revised, and the relevant specific authority citations continue, to read as follows: </AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>5 U.S.C. 301; 19 U.S.C. 66, 1431, 1433, 1434, 1624, 2071 note; 46 U.S.C. App. 3, 91; </P>
                        </AUTH>
                        <STARS/>
                        <EXTRACT>
                            <P>Section 4.5 also issued under 19 U.S.C. 1441; </P>
                            <P>Section 4.7 also issued under 19 U.S.C. 1581(a); 46 U.S.C. App. 883a, 883b; </P>
                            <STARS/>
                            <P>Section 4.61 also issued under 46 U.S.C. App. 883; </P>
                        </EXTRACT>
                        <STARS/>
                    </REGTEXT>
                    <REGTEXT TITLE="19" PART="4">
                        <AMDPAR>2. Amend § 4.5(a) by: </AMDPAR>
                        <AMDPAR>a. Removing the references to the numerical terms “(1)” and “(2)” appearing in the first sentence; and </AMDPAR>
                        <AMDPAR>b. Adding two new sentences after the first sentence to read as follows: </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 4.5 </SECTNO>
                            <SUBJECT>Government vessels. </SUBJECT>
                            <P>(a) * * * In addition, any vessel chartered by, and transporting only cargo that is the property of, the U.S. Department of Defense (DoD) will be treated as a Government vessel for the purpose of being exempt from entry, where the DoD-chartered vessel is manned entirely by the civilian crew of the vessel carrier under contract to DoD. Notwithstanding § 4.60(b)(3) of this part, such DoD-chartered vessel is not exempt from vessel clearance requirements. * * * </P>
                            <STARS/>
                        </SECTION>
                        <AMDPAR>3. Amend § 4.7 by: </AMDPAR>
                        <AMDPAR>a. Revising the first sentence of paragraph (b)(1); </AMDPAR>
                        <AMDPAR>b. Revising paragraph (b)(2); </AMDPAR>
                        <AMDPAR>c. Removing the words, “if automated”, where appearing in paragraph (b)(3)(i); </AMDPAR>
                        <AMDPAR>d. Adding a new paragraph (b)(3)(iii); and </AMDPAR>
                        <AMDPAR>e. Adding a new paragraph (b)(5). </AMDPAR>
                        <P>The revisions and additions read as follows:</P>
                        <SECTION>
                            <SECTNO>§ 4.7 </SECTNO>
                            <SUBJECT>Inward foreign manifest; production on demand; contents and form; advance filing of cargo declaration. </SUBJECT>
                            <STARS/>
                            <P>(b)(1) With the exception of any Cargo Declaration that has been filed in advance as prescribed in paragraph (b)(2) of this section, the original and one copy of the manifest must be ready for production on demand. * * * </P>
                            <P>(2) Subject to the effective date provided in paragraph (b)(5) of this section, and with the exception of any bulk or authorized break bulk cargo as prescribed in paragraph (b)(4) of this section, Customs and Border Protection (CBP) must receive from the incoming carrier, for any vessel covered under paragraph (a) of this section, the CBP-approved electronic equivalent of the vessel's Cargo Declaration (Customs Form 1302), 24 hours before the cargo is laden aboard the vessel at the foreign port (see § 4.30(n)(1)). The current approved system for presenting electronic cargo declaration information to CBP is the Vessel Automated Manifest System (AMS). </P>
                            <P>(3)(i) * * * </P>
                            <P>
                                (iii) Where the party electronically presenting to CBP the cargo information required in § 4.7a(c)(4) receives any of this information from another party, CBP will take into consideration how, in accordance with ordinary commercial practices, the presenting party acquired such information, and whether and how the presenting party is able to verify this information. Where the presenting party is not reasonably able to verify such information, CBP will permit the party 
                                <PRTPAGE P="68169"/>
                                to electronically present the information on the basis of what the party reasonably believes to be true.
                            </P>
                            <STARS/>
                            <P>(5) Within 90 days of December 5, 2003, all ocean carriers, and NVOCCs electing to participate, must be automated on the Vessel AMS system at all ports of entry in the United States. </P>
                            <STARS/>
                              
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="19" PART="4">
                        <AMDPAR>4. Amend § 4.7a by: </AMDPAR>
                        <AMDPAR>a. Revising paragraphs (c)(4)(viii) and (c)(4)(ix); </AMDPAR>
                        <AMDPAR>b. Removing the word “and” after paragraph (c)(4)(xiii); </AMDPAR>
                        <AMDPAR>c. Removing the period after paragraph (c)(4)(xiv), and adding, in its place, a semicolon; and </AMDPAR>
                        <AMDPAR>d. Adding new paragraphs (c)(4)(xv) and (c)(4)(xvi). </AMDPAR>
                        <AMDPAR>Revised paragraphs (c)(4)(viii) and (c)(4)(ix) and new paragraphs (c)(4)(xv) and (c)(4)(xvi) read as follows: </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 4.7a </SECTNO>
                            <SUBJECT>Inward manifest; information required; alternative forms. </SUBJECT>
                            <STARS/>
                            <P>
                                (c) 
                                <E T="03">Cargo Declaration.</E>
                                 * * * 
                            </P>
                            <P>(4) * * * </P>
                            <P>(viii) The shipper's complete name and address, or identification number, from all bills of lading. (At the master bill level, for consolidated shipments, the identity of the Non Vessel Operating Common Carrier (NVOCC), freight forwarder, container station or other carrier is sufficient; for non-consolidated shipments, and for each house bill in a consolidated shipment, the identity of the foreign vendor, supplier, manufacturer, or other similar party is acceptable (and the address of the foreign vendor, etc., must be a foreign address); by contrast, the identity of the carrier, NVOCC, freight forwarder or consolidator is not acceptable; the identification number will be a unique number assigned by CBP upon the implementation of the Automated Commercial Environment); </P>
                            <P>(ix) The complete name and address of the consignee, or identification number, from all bills of lading. (For consolidated shipments, at the master bill level, the NVOCC, freight forwarder, container station or other carrier may be listed as the consignee. For non-consolidated shipments, and for each house bill in a consolidated shipment, the consignee is the party to whom the cargo will be delivered in the United States, with the exception of “FROB” (foreign cargo remaining on board). However, in the case of cargo shipped “to order of [a named party],” the carrier must report this named “to order” party as the consignee; and, if there is any other commercial party listed in the bill of lading for delivery or contact purposes, the carrier must also report this other commercial party's identity and contact information (address) in the “Notify Party” field of the advance electronic data transmission to CBP, to the extent that the CBP-approved electronic data interchange system is capable of receiving this data. The identification number will be a unique number assigned by CBP upon implementation of the Automated Commercial Environment); </P>
                            <STARS/>
                            <P>(xv) Date of departure from foreign, as reflected in the vessel log (this element relates to the departure of the vessel from the foreign port with respect to which the advance cargo declaration is filed (see § 4.7(b)(2)); the time frame for reporting this data element will be either: </P>
                            <P>(A) No later than 24 hours after departure from the foreign port of lading, for those vessels that will arrive in the United States more than 24 hours after sailing from that foreign port; or </P>
                            <P>(B) No later than the presentation of the permit to unlade (Customs Form (CF) 3171, or electronic equivalent), for those vessels that will arrive less than 24 hours after sailing from the foreign port of lading); and </P>
                            <P>(xvi) Time of departure from foreign, as reflected in the vessel log (see § 4.7a(c)(4)(xv) for the applicable foreign port and the time frame within which this data element must be reported to CBP). </P>
                            <STARS/>
                              
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="19" PART="4">
                        <AMDPAR>5. Amend § 4.61 by adding a new paragraph (c)(24) to read as follows: </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 4.61 </SECTNO>
                            <SUBJECT>Requirements for clearance. </SUBJECT>
                            <STARS/>
                            <P>
                                (c) 
                                <E T="03">Verification of compliance.</E>
                            </P>
                            <STARS/>
                            <P>(24) Electronic receipt of required vessel cargo information (see § 192.14(c) of this chapter). </P>
                            <STARS/>
                              
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="19" PART="103">
                        <PART>
                            <HD SOURCE="HED">PART 103—AVAILABILITY OF INFORMATION </HD>
                        </PART>
                        <AMDPAR>1. The general authority citation for part 103 continues, and a specific authority citation is added for § 103.31a in appropriate numerical order, to read as follows: </AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>5 U.S.C. 301, 552, 552a; 19 U.S.C. 66, 1624; 31 U.S.C. 9701; </P>
                        </AUTH>
                        <STARS/>
                        <EXTRACT>
                            <P>Section 103.31a also issued under 19 U.S.C. 2071 note; </P>
                        </EXTRACT>
                    </REGTEXT>
                    <REGTEXT TITLE="19" PART="103">
                        <STARS/>
                        <AMDPAR>2. Amend subpart C of part 103 by adding a new § 103.31a to read as follows: </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 103.31a </SECTNO>
                            <SUBJECT>Advance electronic information for air, truck, and rail cargo. </SUBJECT>
                            <P>Advance cargo information that is electronically presented to Customs and Border Protection (CBP) for inbound or outbound air, rail, or truck cargo in accordance with § 122.48a, 123.91, 123.92, or 192.14 of this chapter, is per se exempt from disclosure under § 103.12(d), unless CBP receives a specific request for such records pursuant to § 103.5, and the owner of the information expressly agrees in writing to its release. </P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="19" PART="113">
                        <PART>
                            <HD SOURCE="HED">PART 113—CUSTOMS BONDS </HD>
                        </PART>
                        <AMDPAR>1. The authority citation for part 113 continues to read as follows: </AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>19 U.S.C. 66, 1623, 1624.</P>
                        </AUTH>
                        <AMDPAR>2. Amend § 113.62 by: </AMDPAR>
                    </REGTEXT>
                    <REGTEXT TITLE="19" PART="113">
                        <AMDPAR>a. Revising the heading of paragraph (j), and redesignating its current text as paragraph (j)(1); </AMDPAR>
                        <AMDPAR>b. Adding a new paragraph (j)(2); and </AMDPAR>
                        <AMDPAR>c. Amending paragraph (l)(1) by adding the citation, “(j)(2),”, after the citation, “(i),”. </AMDPAR>
                        <P>The revision and addition to paragraph (j) read as follows: </P>
                        <SECTION>
                            <SECTNO>§ 113.62 </SECTNO>
                            <SUBJECT>Basic importation and entry bond conditions. </SUBJECT>
                            <STARS/>
                            <P>
                                (j) 
                                <E T="03">Agreement to comply with electronic entry and/or advance cargo information filing requirements.</E>
                            </P>
                            <P>(1) * * * </P>
                            <P>(2) If the principal elects to provide advance inward air or truck cargo information to Customs and Border Protection (CBP) electronically, the principal agrees to provide such cargo information to CBP in the manner and in the time period required, respectively, under § 122.48a or 123.92 of this chapter. If the principal defaults with regard to these obligations, the principal and surety (jointly and severally) agree to pay liquidated damages of $5,000 for each regulation violated. </P>
                            <STARS/>
                              
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="19" PART="113">
                        <AMDPAR>3. Amend § 113.64 by revising the first sentence of paragraph (a); and by revising paragraph (c) to read as follows: </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 113.64 </SECTNO>
                            <SUBJECT>International carrier bond conditions. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Agreement to Pay Penalties, Duties, Taxes, and Other Charges.</E>
                                 If any vessel, vehicle, or aircraft, or any master, owner, or person in charge of a vessel, vehicle or aircraft, slot charterer, or any non-vessel operating common 
                                <PRTPAGE P="68170"/>
                                carrier as defined in § 4.7(b)(3)(ii) of this chapter or other party as specified in § 122.48a(c)(1)(ii)-(c)(1)(iv) of this chapter, incurs a penalty, duty, tax or other charge provided by law or regulation, the obligors (principal and surety, jointly and severally) agree to pay the sum upon demand by Customs and Border Protection (CBP). * * * 
                            </P>
                            <STARS/>
                            <P>
                                (c) 
                                <E T="03">Non-vessel operating common carrier (NVOCC); other party.</E>
                                 If a slot charterer, non-vessel operating common carrier (NVOCC) as defined in § 4.7(b)(3)(ii) of this chapter, or other party specified in § 122.48a(c)(1)(ii)-(c)(1)(iv) of this chapter, elects to provide advance cargo information to CBP electronically, the NVOCC or other party, as a principal under this bond, in addition to compliance with the other provisions of this bond, also agrees to provide such cargo information to CBP in the manner and in the time period required under those respective sections. If the NVOCC or other party, as principal, defaults with regard to these obligations, the principal and surety (jointly and severally) agree to pay liquidated damages of $5,000 for each regulation violated. 
                            </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="19" PART="122">
                        <PART>
                            <HD SOURCE="HED">PART 122—AIR COMMERCE REGULATIONS </HD>
                        </PART>
                        <AMDPAR>1. The general authority citation for part 122 is revised to read as follows: </AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>5 U.S.C. 301; 19 U.S.C. 58b, 66, 1431, 1433, 1436, 1448, 1459, 1590, 1594, 1623, 1624, 1644, 1644a, 2071 note. </P>
                        </AUTH>
                    </REGTEXT>
                    <STARS/>
                    <REGTEXT TITLE="19" PART="122">
                        <AMDPAR>2. Amend § 122.12 by revising the heading of paragraph (c) and adding a sentence at the end of paragraph (c) to read as follows: </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 122.12 </SECTNO>
                            <SUBJECT>Operation of international airports. </SUBJECT>
                            <STARS/>
                            <P>
                                (c) 
                                <E T="03">FAA rules; denial of permission to land.</E>
                                 * * * In addition, except in the case of an emergency or forced landing (see § 122.35), permission to land at an international airport may be denied if advance electronic information for incoming foreign cargo aboard the aircraft has not been received as provided in § 122.48a. 
                            </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="19" PART="122">
                        <AMDPAR>3. Amend § 122.14 by: </AMDPAR>
                        <AMDPAR>a. Redesignating paragraphs (d)(4) and (d)(5) as paragraphs (d)(5) and (d)(6), respectively; </AMDPAR>
                        <AMDPAR>b. Adding a new paragraph (d)(4); and </AMDPAR>
                        <AMDPAR>c. Revising newly redesignated paragraph (d)(5). </AMDPAR>
                        <P>The addition and revision read as follows:</P>
                        <SECTION>
                            <SECTNO>§ 122.14 </SECTNO>
                            <SUBJECT>Landing rights airport. </SUBJECT>
                            <STARS/>
                            <P>
                                (d) 
                                <E T="03">Denial or withdrawal of landing rights.</E>
                                 * * * 
                            </P>
                            <P>(4) Advance cargo information has not been received as provided in § 122.48a; </P>
                            <P>(5) Other reasonable grounds exist to believe that Federal rules and regulations pertaining to safety, including cargo safety and security, and Customs, or other inspectional activities have not been followed; or </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="19" PART="122">
                        <AMDPAR>4. Amend § 122.33 by: </AMDPAR>
                        <AMDPAR>a. Revising paragraph (a), introductory text; and </AMDPAR>
                        <AMDPAR>b. Revising paragraph (a)(1). </AMDPAR>
                        <P>The revisions read as follows:</P>
                        <SECTION>
                            <SECTNO>§ 122.33 </SECTNO>
                            <SUBJECT>Place of first landing. </SUBJECT>
                            <P>(a) The first landing of an aircraft entering the United States from a foreign area will be: </P>
                            <P>(1) At a designated international airport (see § 122.13), provided that permission to land has not been denied pursuant to § 122.12(c); </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="19" PART="122">
                        <AMDPAR>5. Amend § 122.38 by: </AMDPAR>
                        <AMDPAR>a. Adding a sentence at the end of paragraph (c); and </AMDPAR>
                        <AMDPAR>b. Adding a new paragraph (g). </AMDPAR>
                        <P>The additions read as follows:</P>
                        <SECTION>
                            <SECTNO>§ 122.38 </SECTNO>
                            <SUBJECT>Permit and special license to unlade and lade. </SUBJECT>
                            <STARS/>
                            <P>
                                (c) 
                                <E T="03">Term permit or special license.</E>
                                 * * * In addition, a term permit or special license to unlade or lade already issued will not be applicable to any inbound or outbound flight, with respect to which Customs and Border Protection (CBP) has not received the advance electronic cargo information required, respectively, under § 122.48a or 192.14(b)(1)(ii) of this chapter (see paragraph (g) of this section). 
                            </P>
                            <STARS/>
                            <P>
                                (g) 
                                <E T="03">Advance receipt of electronic cargo information.</E>
                                 The CBP will not issue a permit to unlade or lade cargo upon arrival or departure of an aircraft, and a term permit or special license already issued will not be applicable to any inbound or outbound flight, with respect to which CBP has not received the advance electronic cargo information required, respectively, under § 122.48a or 192.14 of this chapter. In cases in which CBP does not receive complete cargo information in the time and manner and in the electronic format required by § 122.48a or 192.14 of this chapter, as applicable, CBP may delay issuance of a permit or special license to unlade or lade cargo, and a term permit or special license to unlade or lade already issued may not apply, until all required information is received. The CBP may also decline to issue a permit or special license to unlade or lade, and a term permit or special license already issued may not apply, with respect to the specific cargo for which advance information is not timely received electronically, as specified in § 122.48a or 192.14(b)(1)(ii) of this chapter. 
                            </P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="19" PART="122">
                        <AMDPAR>6. Amend § 122.41 by: </AMDPAR>
                        <AMDPAR>a. Revising its introductory text; </AMDPAR>
                        <AMDPAR>b. Removing the word “and” following paragraph (a), and redesignating paragraph (b) as paragraph (c); and </AMDPAR>
                        <AMDPAR>c. Adding a new paragraph (b). </AMDPAR>
                        <P>The revision and addition read as follows:</P>
                        <SECTION>
                            <SECTNO>§ 122.41 </SECTNO>
                            <SUBJECT>Aircraft required to enter. </SUBJECT>
                            <P>All aircraft coming into the United States from a foreign area must make entry under this subpart except: </P>
                            <STARS/>
                            <P>(b) Aircraft chartered by, and transporting only cargo that is the property of, the U.S. Department of Defense (DoD), where the DoD-chartered aircraft is manned entirely by the civilian crew of the air carrier under contract to DoD; and </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="19" PART="122">
                        <AMDPAR>7. Amend § 122.48 by revising paragraph (a) to read as follows: </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 122.48 </SECTNO>
                            <SUBJECT>Air cargo manifest. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">When required.</E>
                                 Except as provided in paragraphs (d) and (e) of this section, an air cargo manifest need not be filed or retained aboard the aircraft for any aircraft required to enter under § 122.41. However, an air cargo manifest for all cargo on board must otherwise be available for production upon demand. The general declaration must be filed as provided in § 122.43. 
                            </P>
                            <STARS/>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="19" PART="122">
                        <AMDPAR>8. Amend subpart E of part 122 by adding a new § 122.48a to read as follows: </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 122.48a </SECTNO>
                            <SUBJECT>Electronic information for air cargo required in advance of arrival. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">General requirement.</E>
                                 Pursuant to section 343(a), Trade Act of 2002, as amended (19 U.S.C. 2071 note), and subject to paragraph (e) of this section, for any inbound aircraft required to enter under § 122.41, that will have commercial cargo aboard, Customs and Border Protection (CBP) must electronically receive from the inbound air carrier and, if applicable, an approved party as specified in 
                                <PRTPAGE P="68171"/>
                                paragraph (c)(1) of this section, certain information concerning the incoming cargo, as enumerated, respectively, in paragraphs (d)(1) and (d)(2) of this section. The CBP must receive such information no later than the time frame prescribed in paragraph (b) of this section. The advance electronic transmission of the required cargo information to CBP must be effected through a CBP-approved electronic data interchange system. 
                            </P>
                            <P>
                                (1) 
                                <E T="03">Cargo remaining aboard aircraft; cargo to be entered under bond.</E>
                                 Air cargo arriving from and departing for a foreign country on the same through flight and cargo that is unladen from the arriving aircraft and entered, in bond, for exportation, or for transportation and exportation (see subpart J of this part), are subject to the advance electronic information filing requirement under paragraph (a) of this section. 
                            </P>
                            <P>
                                (2) 
                                <E T="03">Diplomatic Pouches and Diplomatic Cargo.</E>
                                 When goods comprising a diplomatic or consular bag (including cargo shipments, containers, and the like identified as Diplomatic Pouch) that belong to the United States or to a foreign government are shipped under an air waybill, such cargo is subject to the advance reporting requirements, but the description of the shipment as Diplomatic Pouch will be sufficient detail for description. Shipments identified as Diplomatic Cargo, such as office supplies or unaccompanied household goods, are subject to the advance reporting requirements of paragraph (a) of this section. 
                            </P>
                            <P>
                                (b) 
                                <E T="03">Time frame for presenting data.</E>
                                 (1) 
                                <E T="03">Nearby foreign areas.</E>
                                 In the case of aircraft under paragraph (a) of this section that depart for the United States from any foreign port or place in North America, including locations in Mexico, Central America, South America (from north of the Equator only), the Caribbean, and Bermuda, CBP must receive the required cargo information no later than the time of the departure of the aircraft for the United States (the trigger time is no later than the time that wheels are up on the aircraft, and the aircraft is en route directly to the United States). 
                            </P>
                            <P>
                                (2) 
                                <E T="03">Other foreign areas.</E>
                                 In the case of aircraft under paragraph (a) of this section that depart for the United States from any foreign area other than that specified in paragraph (b)(1) of this section, CBP must receive the required cargo information no later than 4 hours prior to the arrival of the aircraft in the United States. 
                            </P>
                            <P>
                                (c) 
                                <E T="03">Party electing to file advance electronic cargo data.</E>
                                 (1) 
                                <E T="03">Other filer.</E>
                                 In addition to incoming air carriers for whom participation is mandatory, one of the following parties meeting the qualifications of paragraph (c)(2) of this section, may elect to transmit to CBP the electronic data for incoming cargo that is listed in paragraph (d)(2) of this section: 
                            </P>
                            <P>(i) An Automated Broker Interface (ABI) filer (importer or its Customs broker) as identified by its ABI filer code; </P>
                            <P>(ii) A Container Freight Station/deconsolidator as identified by its FIRMS (Facilities Information and Resources Management System) code; </P>
                            <P>(iii) An Express Consignment Carrier Facility as identified by its FIRMS code; or, </P>
                            <P>(iv) An air carrier as identified by its carrier IATA (International Air Transport Association) code, that arranged to have the incoming air carrier transport the cargo to the United States. </P>
                            <P>
                                (2) 
                                <E T="03">Eligibility.</E>
                                 To be qualified to file cargo information electronically, a party identified in paragraph (c)(1) of this section must establish the communication protocol required by CBP for properly presenting cargo information through the approved data interchange system. Also, other than a broker or an importer (see § 113.62(j)(2) of this chapter), the party must possess a Customs international carrier bond containing all the necessary provisions of § 113.64 of this chapter. 
                            </P>
                            <P>
                                (3) 
                                <E T="03">Nonparticipation by other party.</E>
                                 If another party as specified in paragraph (c)(1) of this section does not participate in advance electronic cargo information filing, the party that arranges for and/or delivers the cargo shipment to the incoming carrier must fully disclose and present to the carrier the cargo information listed in paragraph (d)(2) of this section; and the incoming carrier, on behalf of the party, must present this information electronically to CBP under paragraph (a) of this section. 
                            </P>
                            <P>
                                (4) 
                                <E T="03">Required information in possession of third party.</E>
                                 Any other entity in possession of required cargo data that is not the incoming air carrier or a party described in paragraph (c)(1) of this section must fully disclose and present the required data for the inbound air cargo to either the air carrier or other electronic filer, as applicable, which must present such data to CBP. 
                            </P>
                            <P>
                                (5) 
                                <E T="03">Party receiving information believed to be accurate.</E>
                                 Where the party electronically presenting the cargo information required in paragraph (d) of this section receives any of this information from another party, CBP will take into consideration how, in accordance with ordinary commercial practices, the presenting party acquired such information, and whether and how the presenting party is able to verify this information. Where the presenting party is not reasonably able to verify such information, CBP will permit the party to electronically present the information on the basis of what that party reasonably believes to be true. 
                            </P>
                            <P>
                                (d) 
                                <E T="03">Non-consolidated/consolidated shipments.</E>
                                 For non-consolidated shipments, the incoming air carrier must transmit to CBP all of the information for the air waybill record, as enumerated in paragraph (d)(1) of this section. For consolidated shipments: the incoming air carrier must transmit to CBP the information listed in paragraph (d)(1) of this section that is applicable to the master air waybill; and the air carrier must transmit cargo information for all associated house air waybills as enumerated in paragraph (d)(2) of this section, unless another party as described in paragraph (c)(1) of this section electronically transmits this information directly to CBP. 
                            </P>
                            <P>
                                (1) 
                                <E T="03">Cargo information from air carrier.</E>
                                 The incoming air carrier must present to CBP the following data elements for inbound air cargo (an “M” next to any listed data element indicates that the data element is mandatory in all cases; a “C” next to the listed data element indicates that the data element is conditional and must be transmitted to CBP only if the particular information pertains to the inbound cargo): 
                            </P>
                            <P>(i) Air waybill number (M) (The air waybill number is the International Air Transport Association (IATA) standard 11-digit number); </P>
                            <P>(ii) Trip/flight number (M); </P>
                            <P>(iii) Carrier/ICAO (International Civil Aviation Organization) code (M) (The approved electronic data interchange system supports both 3- and 2-character ICAO codes, provided that the final digit of the 2-character code is not a numeric value); </P>
                            <P>(iv) Airport of arrival (M) (The 3-alpha character ICAO code corresponding to the first airport of arrival in the Customs territory of the United States (for example, Chicago O'Hare = ORD; Los Angeles International Airport = LAX)); </P>
                            <P>(v) Airport of origin (M) (The 3-alpha character ICAO code corresponding to the airport from which a shipment began its transportation by air to the United States (for example, if a shipment began its transportation from Hong Kong (HKG), and it transits through Narita, Japan (NRT), en route to the United States, the airport of origin is HKG, not NRT)); </P>
                            <P>(vi) Scheduled date of arrival (M); </P>
                            <P>
                                (vii) Total quantity based on the smallest external packing unit (M) (for 
                                <PRTPAGE P="68172"/>
                                example, 2 pallets containing 50 pieces each would be considered as 100, not 2); 
                            </P>
                            <P>(viii) Total weight (M) (may be expressed in either pounds or kilograms);</P>
                            <P>(ix) Precise cargo description (M) (for consolidated shipments, the word “Consolidation” is a sufficient description for the master air waybill record; for non-consolidated shipments, a precise cargo description or the 6-digit Harmonized Tariff Schedule (HTS) number must be provided (generic descriptions, specifically those such as “FAK” (“freight of all kinds”), “general cargo”, and “STC” (“said to contain”) are not acceptable)); </P>
                            <P>(x) Shipper name and address (M) (for consolidated shipments, the identity of the consolidator, express consignment or other carrier, is sufficient for the master air waybill record; for non-consolidated shipments, the name of the foreign vendor, supplier, manufacturer, or other similar party is acceptable (and the address of the foreign vendor, etc., must be a foreign address); by contrast, the identity of a carrier, freight forwarder or consolidator is not acceptable); </P>
                            <P>(xi) Consignee name and address (M) (for consolidated shipments, the identity of the container station, express consignment or other carrier is sufficient for the master air waybill record; for non-consolidated shipments, the name and address of the party to whom the cargo will be delivered is required, with the exception of “FROB” (Foreign Cargo Remaining On Board); this party need not be located at the arrival or destination port); </P>
                            <P>(xii) Consolidation identifier (C); </P>
                            <P>(xiii) Split shipment indicator (C) (see paragraph (d)(3) of this section for the specific data elements that must be presented to CBP in the case of a split shipment); </P>
                            <P>(xiv) Permit to proceed information (C) (this element includes the permit-to-proceed destination airport (the 3-alpha character ICAO code corresponding to the permit-to-proceed destination airport); and the scheduled date of arrival at the permit-to-proceed destination airport); </P>
                            <P>(xv) Identifier of other party which is to submit additional air waybill information (C); </P>
                            <P>(xvi) In-bond information (C) (this data element includes the destination airport; the international/domestic identifier (the in-bond type indicator); the in-bond control number, if there is one (C); and the onward carrier identifier, if applicable (C)); and </P>
                            <P>(xvii) Local transfer facility (C) (this facility is a Container Freight Station as identified by its FIRMS code, or the warehouse of another air carrier as identified by its carrier code). </P>
                            <P>
                                (2) 
                                <E T="03">Cargo information from carrier or other filer.</E>
                                 The incoming air carrier must present the following additional information to CBP for the incoming cargo, unless another party as specified in paragraph (c)(1) of this section elects to present this information directly to CBP. Information for all house air waybills under a single master air waybill consolidation must be presented electronically to CBP by the same party. (An “M” next to any listed data element indicates that the data element is mandatory in all cases; a “C” next to any listed data element indicates that the data element is conditional and must be transmitted to CBP only if the particular information pertains to the inbound cargo): 
                            </P>
                            <P>(i) The master air waybill number and the associated house air waybill number (M) (the house air waybill number may be up to 12 alphanumeric characters (each alphanumeric character that is indicated on the paper house air waybill document must be included in the electronic transmission; alpha characters may not be eliminated)); </P>
                            <P>(ii) Foreign airport of origin (M) (The 3-alpha character ICAO code corresponding to the airport from which a shipment began its transportation by air to the United States (for example, if a shipment began its transportation from Hong Kong (HKG), and it transits through Narita, Japan (NRT), en route to the United States, the airport of origin is HKG, not NRT)); </P>
                            <P>(iii) Cargo description (M) (a precise description of the cargo or the 6-digit Harmonized Tariff Schedule (HTS) number must be provided); </P>
                            <P>(iv) Total quantity based on the smallest external packing unit (M) (for example, 2 pallets containing 50 pieces each would be considered as 100, not 2); </P>
                            <P>(v) Total weight of cargo (M) (may be expressed in either pounds or kilograms); </P>
                            <P>(vi) Shipper name and address (M) (the name of the foreign vendor, supplier, manufacturer, or other similar party is acceptable (and the address of the foreign vendor, etc., must be a foreign address); by contrast, the identity of a carrier, freight forwarder or consolidator is not acceptable); </P>
                            <P>(vii) Consignee name and address (M) (the name and address of the party to whom the cargo will be delivered in the United States, with the exception of “FROB” (Foreign Cargo Remaining On Board); this party need not be located at the arrival or destination port); and </P>
                            <P>(viii) In-bond information (C) (this data element includes the destination airport; the international/domestic identifier (the in-bond type indicator); the in-bond control number, if there is one (C); and the onward carrier identifier, if applicable (C)). </P>
                            <P>
                                (3) 
                                <E T="03">Additional cargo information from air carrier; split shipment.</E>
                                 When the incoming air carrier elects to transport cargo covered under a single consolidated air waybill on more than one aircraft as a split shipment (see § 141.57 of this chapter), the carrier must report the following additional information for each house air waybill covered under the consolidation (An “M” next to any listed data element indicates that the data element is mandatory in all cases; a “C” next to any listed data element indicates that the data element is conditional and must be transmitted to CBP only if the particular information pertains to the inbound cargo): 
                            </P>
                            <P>(i) The master and house air waybill number (M) (The master air waybill number is the IATA standard 11-digit number; the house air waybill number may be up to 12 alphanumeric characters (each alphanumeric number that is indicated on the paper house air waybill must be included in the electronic transmission; alpha characters may not be eliminated)); </P>
                            <P>(ii) The trip/flight number (M); </P>
                            <P>(iii) The carrier/ICAO code (M) (The approved electronic data interchange system supports both 3- and 2-character ICAO codes, provided that the final digit of the 2-character code is not a numeric value); </P>
                            <P>(iv) The airport of arrival (M) (The 3-alpha character ICAO code corresponding to the first airport of arrival in the Customs territory of the United States (for example, Chicago O'Hare = ORD; Los Angeles International Airport = LAX)); </P>
                            <P>(v) The airport of origin (M) (The 3-alpha character ICAO code corresponding to the airport from which a shipment began its transportation by air to the United States (for example, if a shipment began its transportation from Hong Kong (HKG), and it transits through Narita, Japan (NRT), en route to the United States, the airport of origin is HKG, not NRT)); </P>
                            <P>(vi) Scheduled date of arrival (M); </P>
                            <P>(vii) The total quantity of the cargo covered by the house air waybill based on the smallest external packing unit (M) (For example, 2 pallets containing 50 pieces each would be considered as 100, not 2); </P>
                            <P>(viii) The total weight of the cargo covered by the house air waybill (M) (May be expressed in either pounds or kilograms); </P>
                            <P>
                                (ix) Description (M) (This description should mirror the precise level of cargo 
                                <PRTPAGE P="68173"/>
                                description information that is furnished to the incoming carrier by the other electronic filer, if applicable (see paragraph (c)(1) of this section)); 
                            </P>
                            <P>(x) Permit-to-proceed information (C) (This element includes the permit-to-proceed destination airport (the 3-alpha character ICAO code corresponding to the permit-to-proceed destination airport); and the scheduled date of arrival at the permit-to-proceed destination airport); </P>
                            <P>(xi) Boarded quantity (C) (The quantity of the cargo covered by the house air waybill (see paragraph (d)(3)(vii) of this section) that is included in the incoming portion of the split shipment); and </P>
                            <P>(xii) Boarded weight (C) (The weight of the cargo covered by the house air waybill (see paragraph (d)(3)(viii) of this section) that is included in the incoming portion of the split shipment). </P>
                            <P>
                                (e) 
                                <E T="03">Compliance date of this section.</E>
                                 (1) 
                                <E T="03">General.</E>
                                 Subject to paragraph (e)(2) of this section, all affected air carriers, and other parties as specified in paragraph (c)(1) of this section that elect to participate in advance automated cargo information filing, must comply with the requirements of this section on and after March 4, 2004. 
                            </P>
                            <P>
                                (2) 
                                <E T="03">Delay in compliance date of section.</E>
                                 The CBP may delay the general compliance date set forth in paragraph (e)(1) of this section in the event that any necessary modifications to the approved electronic data interchange system are not yet in place. Also, CBP may delay the general compliance date of this section at a given port until CBP has afforded any necessary training to CBP personnel at that port. In addition, CBP may delay implementation if further time is required to complete certification testing of new participants. Any such delay would be the subject of an announcement in the 
                                <E T="04">Federal Register.</E>
                            </P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="19" PART="122">
                        <AMDPAR>9. Amend subpart G of part 122 by adding a new § 122.66 to read as follows: </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 122.66 </SECTNO>
                            <SUBJECT>Clearance or permission to depart denied. </SUBJECT>
                            <P>If advance electronic air cargo information is not received as provided in § 192.14 of this chapter, Customs and Border Protection may deny clearance or permission for the aircraft to depart from the United States. </P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="19" PART="123">
                        <PART>
                            <HD SOURCE="HED">PART 123—CUSTOMS RELATIONS WITH CANADA AND MEXICO </HD>
                        </PART>
                        <AMDPAR>1. The general authority citation for part 123 is revised, and the relevant specific sectional authority citation continue, to read as follows: </AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>19 U.S.C. 66, 1202 (General Note 23, Harmonized Tariff Schedule of the United States (HTSUS)), 1431, 1433, 1436, 1448, 1624, 2071 note. </P>
                        </AUTH>
                        <STARS/>
                        <EXTRACT>
                            <P>Section 123.8 also issued under 19 U.S.C. 1450-1454, 1459;</P>
                        </EXTRACT>
                        <STARS/>
                    </REGTEXT>
                    <REGTEXT TITLE="19" PART="123">
                        <AMDPAR>2. Amend § 123.8 by: </AMDPAR>
                        <AMDPAR>a. Adding two sentences after the second sentence in paragraph (a); and </AMDPAR>
                        <AMDPAR>b. Adding a sentence at the end of paragraph (d). </AMDPAR>
                        <P>The additions read as follows: </P>
                        <SECTION>
                            <SECTNO>§ 123.8 </SECTNO>
                            <SUBJECT>Permit or special license to unlade or lade a vessel or vehicle. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Permission to unlade or lade.</E>
                                 * * * Permission to unlade or lade a truck will be denied for any cargo with respect to which advance electronic information has not been received as provided in § 123.92 or 192.14 of this chapter, as applicable. In cases in which CBP does not receive complete cargo information in the time and manner and in the electronic format required by § 123.92 or 192.14 of this chapter, as applicable, CBP may delay issuance of a permit or special license to unlade or lade a truck. * * * 
                            </P>
                            <STARS/>
                            <P>
                                (d) 
                                <E T="03">Term permit or special license.</E>
                                 * * * A term permit or special license to unlade or lade a truck already issued will not be applicable as to any cargo with respect to which advance electronic information has not been received as provided in § 123.92 or 192.14 of this chapter, as applicable. 
                            </P>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="?" PART="???">
                        <AMDPAR>3. Amend part 123 by adding a new subpart J to read as follows: </AMDPAR>
                        <CONTENTS>
                            <SUBPART>
                                <HD SOURCE="HED">Subpart J—Advance Information for Cargo Arriving by Rail or Truck </HD>
                                <SECHD>Sec.</SECHD>
                                <SECTNO>123.91 </SECTNO>
                                <SUBJECT>Electronic information for rail cargo required in advance of arrival. </SUBJECT>
                                <SECTNO>123.92 </SECTNO>
                                <SUBJECT>Electronic information for truck cargo required in advance of arrival.</SUBJECT>
                            </SUBPART>
                        </CONTENTS>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart J—Advance Information for Cargo Arriving by Rail or Truck </HD>
                            <SECTION>
                                <SECTNO>§ 123.91 </SECTNO>
                                <SUBJECT>Electronic information for rail cargo required in advance of arrival. </SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">General requirement.</E>
                                     Pursuant to section 343(a), Trade Act of 2002, as amended (19 U.S.C. 2071 note), and subject to paragraph (e) of this section, for any train requiring a train sheet under § 123.6, that will have commercial cargo aboard, Customs and Border Protection (CBP) must electronically receive from the rail carrier certain information concerning the incoming cargo, as enumerated in paragraph (d) of this section, no later than 2 hours prior to the cargo reaching the first port of arrival in the United States. Specifically, to effect the advance electronic transmission of the required rail cargo information to CBP, the rail carrier must use a CBP-approved electronic data interchange system. 
                                </P>
                                <P>
                                    (1) 
                                    <E T="03">Through cargo in transit to a foreign country.</E>
                                     Cargo arriving by train for transportation in transit across the United States from one foreign country to another; and cargo arriving by train for transportation through the United States from point to point in the same foreign country are subject to the advance electronic information filing requirement for incoming cargo under paragraph (a) of this section. 
                                </P>
                                <P>
                                    (2) 
                                    <E T="03">Cargo under bond.</E>
                                     Cargo that is to be unladed from the arriving train and entered, in bond, for exportation, or for transportation and exportation, in another vehicle or conveyance is also subject to the advance electronic information filing requirement under paragraph (a) of this section. 
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Exception; cargo in transit from point to point in the United States.</E>
                                     Domestic cargo transported by train to one port from another in the United States by way of Canada or Mexico is not subject to the advance electronic information filing requirement for incoming cargo under paragraph (a) of this section. 
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Incoming rail carrier.</E>
                                     (1) 
                                    <E T="03">Receipt of data; acceptance of cargo.</E>
                                     As a pre-requisite to accepting the cargo, the carrier must receive, from the foreign shipper and owner of the cargo or from a freight forwarder, as applicable, any necessary cargo shipment information, as listed in paragraph (d) of this section, for electronic transmission to CBP. 
                                </P>
                                <P>
                                    (2) 
                                    <E T="03">Accuracy of information received by rail carrier.</E>
                                     Where the rail carrier electronically presenting the cargo information required in paragraph (d) of this section receives any of this information from another party, CBP will take into consideration how, in accordance with ordinary commercial practices, the rail carrier acquired such information, and whether and how the carrier is able to verify this information. Where the rail carrier is not reasonably able to verify such information, CBP will permit the carrier to electronically present the information on the basis of what the carrier reasonably believes to be true. 
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Cargo information required.</E>
                                     The rail carrier must electronically transmit to CBP the following information for all required incoming cargo that will arrive in the United States by train: 
                                </P>
                                <P>
                                    (1) The rail carrier identification SCAC code (the unique Standard Carrier Alpha Code assigned for each carrier by the National Motor Freight Traffic 
                                    <PRTPAGE P="68174"/>
                                    Association; see § 4.7a(c)(2)(iii) of this chapter); 
                                </P>
                                <P>(2) The carrier-assigned conveyance name, equipment number and trip number; </P>
                                <P>(3) The scheduled date and time of arrival of the train at the first port of entry in the United States; </P>
                                <P>(4) The numbers and quantities of the cargo laden aboard the train as contained in the carrier's bill of lading, either master or house, as applicable (this means the quantity of the lowest external packaging unit; containers and pallets do not constitute acceptable information; for example, a container holding 10 pallets with 200 cartons should be described as 200 cartons); </P>
                                <P>(5) A precise cargo description (or the Harmonized Tariff Schedule (HTS) number(s) to the 6-digit level under which the cargo is classified if that information is received from the shipper) and weight of the cargo; or, for a sealed container, the shipper's declared description and weight of the cargo (generic descriptions, specifically those such as “FAK” (“freight of all kinds”), “general cargo,” and “STC” (“said to contain”) are not acceptable); </P>
                                <P>(6) The shipper's complete name and address, or identification number, from the bill(s) of lading (for each house bill in a consolidated shipment, the identity of the foreign vendor, supplier, manufacturer, or other similar party is acceptable (and the address of the foreign vendor, etc., must be a foreign address); by contrast, the identity of the carrier, freight forwarder, consolidator, or broker, is not acceptable; the identification number will be a unique number to be assigned by CBP upon the implementation of the Automated Commercial Environment); </P>
                                <P>(7) The complete name and address of the consignee, or identification number, from the bill(s) of lading (The consignee is the party to whom the cargo will be delivered in the United States. However, in the case of cargo shipped “to order of [a named party],” the carrier must identify this named “to order” party as the consignee; and, if there is any other commercial party listed in the bill of lading for delivery or contact purposes, the carrier must also report this other commercial party's identity and contact information (address) in the “Notify Party” field of the advance electronic data transmission to CBP, to the extent that the CBP-approved electronic data interchange system is capable of receiving this data. The identification number will be a unique number assigned by CBP upon implementation of the Automated Commercial Environment); </P>
                                <P>(8) The place where the rail carrier takes possession of the cargo shipment; </P>
                                <P>(9) Internationally recognized hazardous material code when such materials are being shipped by rail; </P>
                                <P>(10) Container numbers (for containerized shipments) or the rail car numbers; and </P>
                                <P>(11) The seal numbers for all seals affixed to containers and/or rail cars to the extent that CBP's data system can accept this information (for example, if a container has more than two seals, and only two seal numbers can be accepted through the system per container, the carrier's electronic presentation of two of these seal numbers for the container would be considered as constituting full compliance with this data element). </P>
                                <P>
                                    (e) 
                                    <E T="03">Date for compliance with this section.</E>
                                     Rail carriers must commence the advance electronic transmission to CBP of the required cargo information, 90 days from the date that CBP publishes notice in the 
                                    <E T="04">Federal Register</E>
                                     informing affected carriers that the approved electronic data interchange system is in place and operational at the port of entry where the train will first arrive in the United States. 
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 123.92 </SECTNO>
                                <SUBJECT>Electronic information for truck cargo required in advance of arrival. </SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">General requirement.</E>
                                     Pursuant to section 343(a) of the Trade Act of 2002, as amended (19 U.S.C. 2071 note), and subject to paragraph (e) of this section, for any truck required to report its arrival under § 123.1(b), that will have commercial cargo aboard, Customs and Border Protection (CBP) must electronically receive from the party described in paragraph (c) of this section certain information concerning the cargo, as enumerated in paragraph (d) of this section. The CBP must receive such cargo information by means of a CBP-approved electronic data interchange system no later than either 30 minutes or 1 hour prior to the carrier's reaching the first port of arrival in the United States, or such lesser time as authorized, based upon the CBP-approved system employed to present the information. 
                                </P>
                                <P>
                                    (1) 
                                    <E T="03">Through cargo in transit to a foreign country.</E>
                                     Cargo arriving by truck in transit through the United States from one foreign country to another (§ 123.31(a)); and cargo arriving by truck for transportation through the United States from one point to another in the same foreign country (§ 123.31(b); § 123.42) are subject to the advance electronic information filing requirement in paragraph (a) of this section. 
                                </P>
                                <P>
                                    (2) 
                                    <E T="03">Cargo entered under bond.</E>
                                     Cargo that is to be unladed from the arriving truck and entered, in bond, for exportation, or for transportation and exportation, in another vehicle or conveyance are also subject to the advance electronic information filing requirement in paragraph (a) of this section. 
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Exceptions from advance reporting requirements.</E>
                                </P>
                                <P>
                                    (1) 
                                    <E T="03">Cargo in transit from point to point in the United States.</E>
                                     Domestic cargo transported by truck and arriving at one port from another in the United States after transiting Canada or Mexico (§ 123.21; § 123.41) is exempt from the advance electronic filing requirement for incoming cargo under paragraph (a) of this section. 
                                </P>
                                <P>
                                    (2) 
                                    <E T="03">Certain informal entries.</E>
                                     The following merchandise is exempt from the advance cargo information reporting requirements under paragraph (a) of this section, to the extent that such merchandise qualifies for informal entry pursuant to part 143, subpart C, of this chapter: 
                                </P>
                                <P>(i) Merchandise which may be informally entered on Customs Form (CF) 368 or 368A (cash collection or receipt); </P>
                                <P>(ii) Merchandise unconditionally or conditionally free, not exceeding $2,000 in value, eligible for entry on CF 7523; and </P>
                                <P>(iii) Products of the United States being returned, for which entry is prescribed on CF 3311. </P>
                                <P>
                                    (c) 
                                    <E T="03">Carrier; and importer or broker.</E>
                                     (1) 
                                    <E T="03">Single party presentation.</E>
                                     Except as provided in paragraph (c)(2) of this section, the incoming truck carrier must present all required information to CBP in the time and manner prescribed in paragraph (a) of this section. 
                                </P>
                                <P>
                                    (2) 
                                    <E T="03">Dual party presentation.</E>
                                     The United States importer, or its Customs broker, may elect to present to CBP a portion of the required information that it possesses in relation to the cargo. Where the broker, or the importer (see § 113.62(j)(2) of this chapter), elects to submit such data, the carrier is responsible for presenting to CBP the remainder of the information specified in paragraph (d) of this section. 
                                </P>
                                <P>
                                    (3) 
                                    <E T="03">Party receiving information believed to be accurate.</E>
                                     Where the party electronically presenting the cargo information required in paragraph (d) of this section receives any of this information from another party, CBP will take into consideration how, in accordance with ordinary commercial practices, the presenting party acquired such information, and whether and how the presenting party is able to verify this information. Where the presenting party is not reasonably able to verify such information, CBP will permit the party 
                                    <PRTPAGE P="68175"/>
                                    to electronically present the information on the basis of what the party reasonably believes to be true. 
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Cargo information required.</E>
                                     The following commodity and transportation information, as applicable, must be electronically transmitted to and received by CBP for all required incoming cargo arriving in the United States by truck, to the extent that the particular CBP-approved electronic data interchange system employed can accept this information: 
                                </P>
                                <P>(1) Conveyance number, and (if applicable) equipment number (the number of the conveyance is its Vehicle Identification Number (VIN) or its license plate number and state of issuance; the equipment number, if applicable, refers to the identification number of any trailing equipment or container attached to the power unit); </P>
                                <P>(2) Carrier identification (this is the truck carrier identification SCAC code (the unique Standard Carrier Alpha Code) assigned for each carrier by the National Motor Freight Traffic Association; see § 4.7a(c)(2)(iii) of this chapter); </P>
                                <P>(3) Trip number and, if applicable, the transportation reference number for each shipment (the transportation reference number is the freight bill number, or Pro Number, if such a number has been generated by the carrier); </P>
                                <P>(4) Container number(s) (for any containerized shipment) (if different from the equipment number), and the seal numbers for all seals affixed to the equipment or container(s); </P>
                                <P>(5) The foreign location where the truck carrier takes possession of the cargo destined for the United States; </P>
                                <P>(6) The scheduled date and time of arrival of the truck at the first port of entry in the United States; </P>
                                <P>(7) The numbers and quantities for the cargo laden aboard the truck as contained in the bill(s) of lading (this means the quantity of the lowest external packaging unit; containers and pallets do not constitute acceptable information; for example, a container holding 10 pallets with 200 cartons should be described as 200 cartons); </P>
                                <P>(8) The weight of the cargo, or, for a sealed container, the shipper's declared weight of the cargo; </P>
                                <P>(9) A precise description of the cargo or the Harmonized Tariff Schedule (HTS) numbers to the 6-digit level under which the cargo will be classified (generic descriptions, specifically those such as FAK (“freight of all kinds”), “general cargo,” and “STC” (“said to contain”) are not acceptable); </P>
                                <P>(10) Internationally recognized hazardous material code when such cargo is being shipped by truck; </P>
                                <P>(11) The shipper's complete name and address, or identification number, from the bill(s) of lading (for each house bill in a consolidated shipment, the identity of the foreign vendor, supplier, manufacturer, or other similar party is acceptable (and the address of the foreign vendor, etc., must be a foreign address); by contrast, the identity of the carrier, freight forwarder, consolidator, or broker, is not acceptable; the identification number will be a unique number to be assigned by CBP upon the implementation of the Automated Commercial Environment); and </P>
                                <P>(12) The complete name and address of the consignee, or identification number, from the bill(s) of lading (the consignee is the party to whom the cargo will be delivered in the United States, with the exception of “FROB” (Foreign Cargo Remaining On Board); the identification number will be a unique number assigned by CBP upon implementation of the Automated Commercial Environment). </P>
                                <P>
                                    (e) 
                                    <E T="03">Date for compliance with this section.</E>
                                     The incoming truck carrier and, if electing to do so, the United States importer, or its Customs broker, must present the necessary cargo data to CBP at the particular port of entry where the truck will arrive in the United States on and after 90 days from the date that CBP has published a notice in the 
                                    <E T="04">Federal Register</E>
                                     informing affected carriers that: 
                                </P>
                                <P>(1) The approved data interchange is in place and fully operational at that port; and </P>
                                <P>(2) The carrier must commence the presentation of the required cargo information through the approved system. </P>
                            </SECTION>
                        </SUBPART>
                    </REGTEXT>
                    <REGTEXT TITLE="19" PART="178">
                        <PART>
                            <HD SOURCE="HED">PART 178—APPROVAL OF INFORMATION COLLECTION REQUIREMENTS </HD>
                        </PART>
                        <AMDPAR>1. The authority citation for part 178 continues to read as follows: </AMDPAR>
                    </REGTEXT>
                    <REGTEXT TITLE="19" PART="178">
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>
                                5 U.S.C. 301; 19 U.S.C. 1624; 44 U.S.C. 3501 
                                <E T="03">et seq.</E>
                            </P>
                        </AUTH>
                        <AMDPAR>2. Section 178.2 is amended as follows: </AMDPAR>
                        <AMDPAR>a. In the listing for § 4.7a(c)(4), by removing the number “1515-0001” under the heading “OMB Control No.”, and adding, in its place, the number “1651-0001”; and </AMDPAR>
                        <AMDPAR>b. By adding new listings for §§ 122.48a, 123.91, 123.92 and 192.14 in appropriate numerical sequence according to the section number under the columns indicated. </AMDPAR>
                        <P>The listings for §§ 4.7a(c)(4), 122.48a, 123.91, 123.92, and 192.14 read as follows: </P>
                        <SECTION>
                            <SECTNO>§ 178.2 </SECTNO>
                            <SUBJECT>Listing of OMB control numbers. </SUBJECT>
                            <GPOTABLE COLS="3" OPTS="L1,tp0,i1" CDEF="s100,r125,14">
                                <TTITLE>  </TTITLE>
                                <BOXHD>
                                    <CHED H="1">19 CFR section </CHED>
                                    <CHED H="1">Description </CHED>
                                    <CHED H="1">
                                        OMB 
                                        <LI>Control No. </LI>
                                    </CHED>
                                </BOXHD>
                                <ROW>
                                    <ENT I="11">  </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="28">*         *         *         *         *         *         * </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">§ 4.7a(c)(4) </ENT>
                                    <ENT>Transportation manifest (cargo declaration) </ENT>
                                    <ENT>1651-0001 </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22">  </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="28">*         *         *         *         *         *         * </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">§ 122.48a </ENT>
                                    <ENT>Transportation manifest (cargo declaration) </ENT>
                                    <ENT>1651-0001 </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22">  </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="28">*         *         *         *         *         *         * </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">§ 123.91 </ENT>
                                    <ENT>Transportation manifest (cargo declaration) </ENT>
                                    <ENT>1651-0001 </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22">  </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="28">*         *         *         *         *         *         * </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">§ 123.92 </ENT>
                                    <ENT>Transportation manifest (cargo declaration) </ENT>
                                    <ENT>1651-0001 </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="22">  </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="28">*         *         *         *         *         *         * </ENT>
                                </ROW>
                                <ROW>
                                    <ENT I="01">§ 192.14 </ENT>
                                    <ENT>Transportation manifest (cargo declaration) </ENT>
                                    <ENT>1651-0001 </ENT>
                                </ROW>
                            </GPOTABLE>
                        </SECTION>
                    </REGTEXT>
                    <REGTEXT TITLE="19" PART="192">
                        <PART>
                            <PRTPAGE P="68176"/>
                            <HD SOURCE="HED">PART 192—EXPORT CONTROL </HD>
                        </PART>
                        <AMDPAR>1. The authority citation for part 192 is revised to read as follows: </AMDPAR>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>19 U.S.C. 66, 1624, 1646c. Subpart A also issued under 19 U.S.C. 1627a, 1646a, 1646b; subpart B also issued under 13 U.S.C. 303; 19 U.S.C. 2071 note; 46 U.S.C. 91. </P>
                        </AUTH>
                        <AMDPAR>2. Amend subpart B of part 192 by adding a new § 192.14 to read as follows: </AMDPAR>
                        <SECTION>
                            <SECTNO>§ 192.14 </SECTNO>
                            <SUBJECT>Electronic information for outward cargo required in advance of departure. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">General requirement.</E>
                                 Pursuant to section 343(a), Trade Act of 2002, as amended (19 U.S.C. 2071 note), and subject to paragraph (e) of this section, for any commercial cargo that is to be transported out of the United States by vessel, aircraft, rail, or truck, unless exempted under paragraph (d) of this section, the United States Principal Party in Interest (USPPI), or its authorized agent, must electronically transmit for receipt by Customs and Border Protection (CBP), no later than the time period specified in paragraph (b) of this section, certain cargo information, as enumerated in paragraph (c) of this section. Specifically, to effect the advance electronic transmission of the required cargo information to CBP, the USPPI or its authorized agent must use a CBP-approved electronic data interchange system (currently, the Automated Export System (AES)). 
                            </P>
                            <P>
                                (b) 
                                <E T="03">Presentation of data.</E>
                                 (1) 
                                <E T="03">Time for presenting data.</E>
                                 USPPIs or their authorized agents must electronically transmit and verify system acceptance of required cargo information for outbound cargo no later than the time period specified as follows (see paragraph (b)(3) of this section): 
                            </P>
                            <P>(i) For vessel cargo, the USPPI or its authorized agent must transmit and verify system acceptance of export vessel cargo information no later than 24 hours prior to departure from the U.S. port where the vessel cargo is to be laden; </P>
                            <P>(ii) For air cargo, including cargo being transported by Air Express Couriers, the USPPI or its authorized agent must transmit and verify system acceptance of export air cargo information no later than 2 hours prior to the scheduled departure time of the aircraft from the last U.S. port; </P>
                            <P>(iii) For truck cargo, including cargo departing by Express Consignment Courier, the USPPI or its authorized agent must transmit and verify system acceptance of export truck cargo information no later than 1 hour prior to the arrival of the truck at the border; and </P>
                            <P>(iv) For rail cargo, the USPPI or its authorized agent must transmit and verify system acceptance of export rail cargo information no later than two hours prior to the arrival of the train at the border. </P>
                            <P>
                                (2) 
                                <E T="03">Applicability of time frames</E>
                                . The time periods in paragraph (b)(1) of this section for reporting required export cargo information to CBP for outward vessel, air, truck, or rail cargo only apply to shipments without an export license, that require full pre-departure reporting of shipment data, in order to comply with the advance cargo information filing requirements under section 343(a), as amended. Paragraph (e) of this section details dates for compliance with the time frames provided in paragraph (b)(1) of this section. Requirements placed on exports controlled by other Government agencies will remain in force unless changed by the agency having the regulatory authority to do so. The CBP will also continue to require 72-hour advance notice for used vehicle exports pursuant to § 192.2(c)(1) and (c)(2)(i) of this part. USPPIs or their authorized agents should refer to the relevant titles of the Code of Federal Regulations (CFR) for pre-filing requirements of other Government agencies. In particular, for the advance reporting requirements for exports of U.S. Munitions List items, see the U.S. Department of State's International Traffic in Arms Regulations (ITAR) (22 CFR parts 120 through 130). 
                            </P>
                            <P>
                                (3) 
                                <E T="03">System verification of data acceptance</E>
                                . Once the USPPI or its authorized agent has transmitted the data required under paragraphs (c)(1) and (c)(2) of this section, and the CBP-approved electronic system has received and accepted this data, the system will generate and transmit to the USPPI or its authorized agent (whichever is the filer in AES) a confirmation number (this number is known as the Internal Transaction Number (ITN)), which verifies that the data has been accepted as transmitted for the outgoing shipment. 
                            </P>
                            <P>
                                (c) 
                                <E T="03">Information required</E>
                                . (1) 
                                <E T="03">Currently collected commodity data</E>
                                . The export cargo information to be collected from USPPIs or their authorized agents for outbound cargo is already contained in the Bureau of Census electronic Shipper's Export Declaration (SED) that the USPPI or its authorized agent currently presents to CBP through the approved electronic system. The AES Commodity Module already captures the requisite export data, so no new data elements for export cargo are required under this section. The export cargo data elements that are required to be reported electronically through the approved system are also found in § 30.63 of the Bureau of Census Regulations (15 CFR 30.63). 
                            </P>
                            <P>
                                (2) 
                                <E T="03">Transportation data</E>
                                . Reporting of the following transportation information is currently mandatory for AES participants under 15 CFR 30.63 for the vessel, air, truck, and rail modes (see also paragraph (c)(3) of this section): 
                            </P>
                            <P>(i) Method of transportation (the method of transportation is defined as that by which the goods are exported or shipped (vessel, air, rail, or truck)); </P>
                            <P>(ii) Carrier identification (for vessel, rail and truck shipments, the unique carrier identifier is the 4-character Standard Carrier Alpha Code (SCAC); for aircraft, the carrier identifier is the 2- or 3-character International Air Transport Association (IATA) code); </P>
                            <P>(iii) Conveyance name (the conveyance name is the name of the carrier; for sea carriers, this is the name of the vessel; for others, the carrier name); </P>
                            <P>(iv) Country of ultimate destination (this is the country as known to the USPPI or its authorized agent at the time of exportation, where the cargo is to be consumed or further processed or manufactured; this country would be identified by the 2-character International Standards Organization (ISO) code for the country of ultimate destination); </P>
                            <P>(v) Estimated date of exportation (the USPPI or its authorized agent must report the date the cargo is scheduled to leave the United States for all modes of transportation; if the actual date is not known, the USPPI or its authorized agent must report the best estimate as to the time of departure); and </P>
                            <P>(vi) Port of exportation (the port where the outbound cargo departs from the United States is designated by its unique code, as set forth in Annex C, Harmonized Tariff Schedule of the United States (HTSUS); the USPPI or its authorized agent must report the port of exportation as known when the USPPI or its agent tenders the cargo to the outbound carrier; should the carrier export the cargo from a different port and the carrier so informs the USPPI or agent, the port of exportation must be corrected by the filer in AES.). </P>
                            <P>
                                (3) 
                                <E T="03">Proof of electronic filing; exemption from filing.</E>
                                 The USPPI, or its authorized agent, must furnish to the outbound carrier a proof of electronic filing citation (the ITN), low-risk exporter citation (currently, the Option 4 filing citation), or exemption statement, for annotation on the carrier's outward manifest, waybill, or other export documentation covering the cargo to be shipped. The proof of 
                                <PRTPAGE P="68177"/>
                                electronic filing citation, low-risk exporter citation, or exemption statement, will conform to the approved data formats found in the Bureau of Census Foreign Trade Statistics Regulations (FTSR) (15 CFR part 30) and FTSR Letter 168, Amendment 2 (this Letter may be obtained from the Census Bureau). 
                            </P>
                            <P>
                                (4) 
                                <E T="03">Carrier responsibility</E>
                                . (i) 
                                <E T="03">Loading of cargo</E>
                                . The carrier may not load cargo without first receiving from the USPPI or its authorized agent either the related electronic filing citation as prescribed under paragraph (c)(3) of this section, or an appropriate exemption statement for the cargo as specified in paragraph (d) of this section. 
                            </P>
                            <P>
                                (ii) 
                                <E T="03">High-risk cargo</E>
                                . For cargo that CBP has identified as potentially high-risk, the carrier, after being duly notified by CBP, will be responsible for delivering the cargo for inspection/examination. If the cargo identified as high risk has already departed, CBP may demand that the export carrier redeliver the cargo in accordance with the terms of its international carrier bond (see § 113.64(g)(2) of this chapter). 
                            </P>
                            <P>
                                (5) 
                                <E T="03">USPPI receipt of information believed to be accurate</E>
                                . Where the USPPI or its authorized agent electronically presenting the cargo information required in paragraphs (c)(1) and (c)(2) of this section receives any of this information from another party, CBP will take into consideration how, in accordance with ordinary commercial practices, the USPPI or its authorized agent acquired this information, and whether and how the USPPI or authorized agent is able to verify this information. Where the USPPI or authorized agent is not reasonably able to verify any information received, CBP will permit this party to electronically present the information on the basis of what it reasonably believes to be true. 
                            </P>
                            <P>
                                (d) 
                                <E T="03">Exemptions from reporting; Census exemptions applicable</E>
                                . The USPPI or authorized agent must furnish to the outbound carrier an appropriate exemption state-ment (low-risk exporter or other exemption) for any export shipment laden that is not subject to pre-departure electronic information filing under this section. The exemption statement will conform to the proper format approved by the Bureau of Census. Any exemptions from reporting requirements for export cargo are enumerated in §§ 30.50 through 30.58 of the Bureau of Census Regulations (15 CFR 30.50 through 30.58). These exemptions are equally applicable under this section. 
                            </P>
                            <P>
                                (e) 
                                <E T="03">Date for compliance</E>
                                . The requirements of this section, including the pre-departure time frames for reporting export cargo information for required shipments, and the requirement of the ITN, will be implemented concurrent with the completion of the redesign of the AES commodity module and the effective date of mandatory filing regulations that will be issued by the Department of Commerce pursuant to the Security Assistance Act (Pub. L. 107-228). This date will be announced in the 
                                <E T="04">Federal Register</E>
                                . 
                            </P>
                        </SECTION>
                    </REGTEXT>
                    <SIG>
                        <NAME>Robert C. Bonner,</NAME>
                        <TITLE>Commissioner, Customs and Border Protection.</TITLE>
                    </SIG>
                    <SIG>
                        <APPR>Approved: November 17, 2003. </APPR>
                        <NAME>Tom Ridge, </NAME>
                        <TITLE>Secretary, Department of Homeland Security. </TITLE>
                    </SIG>
                </SUPLINF>
                <FRDOC>[FR Doc. 03-29798 Filed 12-4-03; 8:45 am] </FRDOC>
                <BILCOD>BILLING CODE 4820-02-P</BILCOD>
            </RULE>
        </RULES>
    </NEWPART>
    <VOL>68</VOL>
    <NO>234</NO>
    <DATE>Friday, December 5, 2003</DATE>
    <UNITNAME>Notices</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="68179"/>
            <PARTNO>Part III</PARTNO>
            <AGENCY TYPE="P">Department of the Interior</AGENCY>
            <SUBAGY>Bureau of Indian Affairs </SUBAGY>
            <HRULE/>
            <TITLE>Indian Entities Recognized and Eligible To Receive Services From the United States Bureau of Indian Affairs; Notice</TITLE>
        </PTITLE>
        <NOTICES>
            <NOTICE>
                <PREAMB>
                    <PRTPAGE P="68180"/>
                    <AGENCY TYPE="S">DEPARTMENT OF THE INTERIOR</AGENCY>
                    <SUBAGY>Bureau of Indian Affairs</SUBAGY>
                    <SUBJECT>Indian Entities Recognized and Eligible To Receive Services From the United States Bureau of Indian Affairs</SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Bureau of Indian Affairs, Interior.</P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Notice.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>Notice is hereby given of the current list of 562 tribal entities recognized and eligible for funding and services from the Bureau of Indian Affairs by virtue of their status as Indian tribes. This notice is published pursuant to section 104 of the Act of November 2, 1994 (Pub. L. 103-454; 108 Stat. 4791, 4792).</P>
                    </SUM>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>Daisy West, Bureau of Indian Affairs, Division of Tribal Government Services, MS-320-MIB, 1849 C Street, NW., Washington, DC 20240. Telephone number: (202) 513-7641.</P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P>This notice is published in exercise of authority delegated to the Assistant Secretary—Indian Affairs under 25 U.S.C. 2 and 9 and 209 DM 8.</P>
                    <P>Published below is a list of federally acknowledged tribes in the contiguous 48 states and in Alaska. The list is updated from the notice published on July 12, 2002 (67 FR 46328).</P>
                    <P>Several tribes have made changes to their tribal name. To aid in identifying tribal name changes, the tribe's former name is included with the new tribal name. We will continue to list the tribe's former name for several years before dropping the former name from the list. We have also made several corrections. To aid in identifying corrections, the tribe's previously listed name is included with the tribal name.</P>
                    <P>The listed entities are acknowledged to have the immunities and privileges available to other federally acknowledged Indian tribes by virtue of their government-to-government relationship with the United States as well as the responsibilities, powers, limitations and obligations of such tribes. We have continued the practice of listing the Alaska Native entities separately solely for the purpose of facilitating identification of them and reference to them given the large number of complex Native names.</P>
                    <SIG>
                        <DATED>Dated: November 21, 2003.</DATED>
                        <NAME>Aurene M. Martin,</NAME>
                        <TITLE>Principal Deputy Assistant Secretary—Indian Affairs.</TITLE>
                    </SIG>
                    <HD SOURCE="HD1">Indian Tribal Entities Within the Contiguous 48 States Recognized and Eligible To Receive Services From the United States Bureau of Indian Affairs</HD>
                    <FP SOURCE="FP-1">Absentee-Shawnee Tribe of Indians of Oklahoma</FP>
                    <FP SOURCE="FP-1">Agua Caliente Band of Cahuilla Indians of the Agua Caliente Indian Reservation, California</FP>
                    <FP SOURCE="FP-1">Ak Chin Indian Community of the Maricopa (Ak Chin) Indian Reservation, Arizona</FP>
                    <FP SOURCE="FP-1">Alabama-Coushatta Tribes of Texas</FP>
                    <FP SOURCE="FP-1">Alabama-Quassarte Tribal Town, Oklahoma</FP>
                    <FP SOURCE="FP-1">Alturas Indian Rancheria, California</FP>
                    <FP SOURCE="FP-1">Apache Tribe of Oklahoma</FP>
                    <FP SOURCE="FP-1">Arapahoe Tribe of the Wind River Reservation, Wyoming</FP>
                    <FP SOURCE="FP-1">Aroostook Band of Micmac Indians of Maine</FP>
                    <FP SOURCE="FP-1">Assiniboine and Sioux Tribes of the Fort Peck Indian Reservation, Montana</FP>
                    <FP SOURCE="FP-1">Augustine Band of Cahuilla Mission Indians of the Augustine Reservation, California</FP>
                    <FP SOURCE="FP-1">Bad River Band of the Lake Superior Tribe of Chippewa Indians of the Bad River Reservation, Wisconsin</FP>
                    <FP SOURCE="FP-1">Bay Mills Indian Community, Michigan</FP>
                    <FP SOURCE="FP-1">Bear River Band of the Rohnerville Rancheria, California</FP>
                    <FP SOURCE="FP-1">Berry Creek Rancheria of Maidu Indians of California</FP>
                    <FP SOURCE="FP-1">Big Lagoon Rancheria, California</FP>
                    <FP SOURCE="FP-1">Big Pine Band of Owens Valley Paiute Shoshone Indians of the Big Pine Reservation, California</FP>
                    <FP SOURCE="FP-1">Big Sandy Rancheria of Mono Indians of California</FP>
                    <FP SOURCE="FP-1">Big Valley Band of Pomo Indians of the Big Valley Rancheria, California</FP>
                    <FP SOURCE="FP-1">Blackfeet Tribe of the Blackfeet Indian Reservation of Montana</FP>
                    <FP SOURCE="FP-1">Blue Lake Rancheria, California</FP>
                    <FP SOURCE="FP-1">Bridgeport Paiute Indian Colony of California</FP>
                    <FP SOURCE="FP-1">Buena Vista Rancheria of Me-Wuk Indians of California</FP>
                    <FP SOURCE="FP-1">Burns Paiute Tribe of the Burns Paiute Indian Colony of Oregon</FP>
                    <FP SOURCE="FP-1">Cabazon Band of Mission Indians, California (previously listed as the Cabazon Band of Cahuilla Mission Indians of the Cabazon Reservation)</FP>
                    <FP SOURCE="FP-1">Cachil DeHe Band of Wintun Indians of the Colusa Indian Community of the Colusa Rancheria, California</FP>
                    <FP SOURCE="FP-1">Caddo Nation of Oklahoma (formerly the Caddo Indian Tribe of Oklahoma)</FP>
                    <FP SOURCE="FP-1">Cahuilla Band of Mission Indians of the Cahuilla Reservation, California</FP>
                    <FP SOURCE="FP-1">Cahto Indian Tribe of the Laytonville Rancheria, California</FP>
                    <FP SOURCE="FP-1">California Valley Miwok Tribe, California (formerly the Sheep Ranch Rancheria of Me-Wuk Indians of California)</FP>
                    <FP SOURCE="FP-1">Campo Band of Diegueno Mission Indians of the Campo Indian Reservation, California</FP>
                    <FP SOURCE="FP-1">Capitan Grande Band of Diegueno Mission Indians of California: </FP>
                    <FP SOURCE="FP-1">Barona Group of Capitan Grande Band of Mission Indians of the Barona Reservation, California</FP>
                    <FP SOURCE="FP-1">Viejas (Baron Long) Group of Capitan Grande Band of Mission Indians of the Viejas Reservation, California</FP>
                    <FP SOURCE="FP-1">Catawba Indian Nation (aka Catawba Tribe of South Carolina)</FP>
                    <FP SOURCE="FP-1">Cayuga Nation of New York</FP>
                    <FP SOURCE="FP-1">Cedarville Rancheria, California</FP>
                    <FP SOURCE="FP-1">Chemehuevi Indian Tribe of the Chemehuevi Reservation, California</FP>
                    <FP SOURCE="FP-1">Cher-Ae Heights Indian Community of the Trinidad Rancheria, California</FP>
                    <FP SOURCE="FP-1">Cherokee Nation, Oklahoma</FP>
                    <FP SOURCE="FP-1">Cheyenne-Arapaho Tribes of Oklahoma</FP>
                    <FP SOURCE="FP-1">Cheyenne River Sioux Tribe of the Cheyenne River Reservation, South Dakota</FP>
                    <FP SOURCE="FP-1">Chickasaw Nation, Oklahoma</FP>
                    <FP SOURCE="FP-1">Chicken Ranch Rancheria of Me-Wuk Indians of California</FP>
                    <FP SOURCE="FP-1">Chippewa-Cree Indians of the Rocky Boy's Reservation, Montana</FP>
                    <FP SOURCE="FP-1">Chitimacha Tribe of Louisiana</FP>
                    <FP SOURCE="FP-1">Choctaw Nation of Oklahoma</FP>
                    <FP SOURCE="FP-1">Citizen Potawatomi Nation, Oklahoma</FP>
                    <FP SOURCE="FP-1">Cloverdale Rancheria of Pomo Indians of California</FP>
                    <FP SOURCE="FP-1">Cocopah Tribe of Arizona</FP>
                    <FP SOURCE="FP-1">Coeur D'Alene Tribe of the Coeur D'Alene Reservation, Idaho</FP>
                    <FP SOURCE="FP-1">Cold Springs Rancheria of Mono Indians of California</FP>
                    <FP SOURCE="FP-1">Colorado River Indian Tribes of the Colorado River Indian Reservation, Arizona and California</FP>
                    <FP SOURCE="FP-1">Comanche Nation, Oklahoma (formerly the Comanche Indian Tribe)</FP>
                    <FP SOURCE="FP-1">Confederated Salish &amp; Kootenai Tribes of the Flathead Reservation, Montana</FP>
                    <FP SOURCE="FP-1">Confederated Tribes of the Chehalis Reservation, Washington</FP>
                    <FP SOURCE="FP-1">Confederated Tribes of the Colville Reservation, Washington</FP>
                    <FP SOURCE="FP-1">Confederated Tribes of the Coos, Lower Umpqua and Siuslaw Indians of Oregon</FP>
                    <FP SOURCE="FP-1">Confederated Tribes of the Goshute Reservation, Nevada and Utah</FP>
                    <FP SOURCE="FP-1">Confederated Tribes of the Grand Ronde Community of Oregon</FP>
                    <FP SOURCE="FP-1">Confederated Tribes of the Siletz Reservation, Oregon</FP>
                    <FP SOURCE="FP-1">Confederated Tribes of the Umatilla Reservation, Oregon</FP>
                    <FP SOURCE="FP-1">Confederated Tribes of the Warm Springs Reservation of Oregon</FP>
                    <FP SOURCE="FP-1">
                        Confederated Tribes and Bands of the Yakama Nation, Washington (formerly 
                        <PRTPAGE P="68181"/>
                        the Confederated Tribes and Bands of the Yakama Indian Nation of the Yakama Reservation)
                    </FP>
                    <FP SOURCE="FP-1">Coquille Tribe of Oregon</FP>
                    <FP SOURCE="FP-1">Cortina Indian Rancheria of Wintun Indians of California</FP>
                    <FP SOURCE="FP-1">Coushatta Tribe of Louisiana</FP>
                    <FP SOURCE="FP-1">Cow Creek Band of Umpqua Indians of Oregon</FP>
                    <FP SOURCE="FP-1">Cowlitz Indian Tribe, Washington</FP>
                    <FP SOURCE="FP-1">Coyote Valley Band of Pomo Indians of California</FP>
                    <FP SOURCE="FP-1">Crow Tribe of Montana</FP>
                    <FP SOURCE="FP-1">Crow Creek Sioux Tribe of the Crow Creek Reservation, South Dakota</FP>
                    <FP SOURCE="FP-1">Death Valley Timbi-Sha Shoshone Band of California</FP>
                    <FP SOURCE="FP-1">Delaware Nation, Oklahoma (formerly the Delaware Tribe of Western Oklahoma)</FP>
                    <FP SOURCE="FP-1">Delaware Tribe of Indians, Oklahoma</FP>
                    <FP SOURCE="FP-1">Dry Creek Rancheria of Pomo Indians of California</FP>
                    <FP SOURCE="FP-1">Duckwater Shoshone Tribe of the Duckwater Reservation, Nevada</FP>
                    <FP SOURCE="FP-1">Eastern Band of Cherokee Indians of North Carolina</FP>
                    <FP SOURCE="FP-1">Eastern Shawnee Tribe of Oklahoma</FP>
                    <FP SOURCE="FP-1">Elem Indian Colony of Pomo Indians of the Sulphur Bank Rancheria, California</FP>
                    <FP SOURCE="FP-1">Elk Valley Rancheria, California</FP>
                    <FP SOURCE="FP-1">Ely Shoshone Tribe of Nevada</FP>
                    <FP SOURCE="FP-1">Enterprise Rancheria of Maidu Indians of California</FP>
                    <FP SOURCE="FP-1">Ewiiaapaayp Band of Kumeyaay Indians, California (formerly the Cuyapaipe Community of Diegueno Mission Indians of the Cuyapaipe Reservation)</FP>
                    <FP SOURCE="FP-1">Federated Indians of Graton Rancheria, California (formerly the Graton Rancheria)</FP>
                    <FP SOURCE="FP-1">Flandreau Santee Sioux Tribe of South Dakota</FP>
                    <FP SOURCE="FP-1">Forest County Potawatomi Community, Wisconsin</FP>
                    <FP SOURCE="FP-1">Fort Belknap Indian Community of the Fort Belknap Reservation of Montana</FP>
                    <FP SOURCE="FP-1">Fort Bidwell Indian Community of the Fort Bidwell Reservation of California</FP>
                    <FP SOURCE="FP-1">Fort Independence Indian Community of Paiute Indians of the Fort Independence Reservation, California</FP>
                    <FP SOURCE="FP-1">Fort McDermitt Paiute and Shoshone Tribes of the Fort McDermitt Indian Reservation, Nevada and Oregon</FP>
                    <FP SOURCE="FP-1">Fort McDowell Yavapai Nation, Arizona (formerly the Fort McDowell Mohave-Apache Community of the Fort McDowell Indian Reservation)</FP>
                    <FP SOURCE="FP-1">Fort Mojave Indian Tribe of Arizona, California &amp; Nevada</FP>
                    <FP SOURCE="FP-1">Fort Sill Apache Tribe of Oklahoma</FP>
                    <FP SOURCE="FP-1">Gila River Indian Community of the Gila River Indian Reservation, Arizona</FP>
                    <FP SOURCE="FP-1">Grand Traverse Band of Ottawa and Chippewa Indians, Michigan</FP>
                    <FP SOURCE="FP-1">Greenville Rancheria of Maidu Indians of California</FP>
                    <FP SOURCE="FP-1">Grindstone Indian Rancheria of Wintun-Wailaki Indians of California</FP>
                    <FP SOURCE="FP-1">Guidiville Rancheria of California</FP>
                    <FP SOURCE="FP-1">Hannahville Indian Community, Michigan</FP>
                    <FP SOURCE="FP-1">Havasupai Tribe of the Havasupai Reservation, Arizona</FP>
                    <FP SOURCE="FP-1">Ho-Chunk Nation of Wisconsin (formerly the Wisconsin Winnebago Tribe)</FP>
                    <FP SOURCE="FP-1">Hoh Indian Tribe of the Hoh Indian Reservation, Washington</FP>
                    <FP SOURCE="FP-1">Hoopa Valley Tribe, California</FP>
                    <FP SOURCE="FP-1">Hopi Tribe of Arizona</FP>
                    <FP SOURCE="FP-1">Hopland Band of Pomo Indians of the Hopland Rancheria, California</FP>
                    <FP SOURCE="FP-1">Houlton Band of Maliseet Indians of Maine</FP>
                    <FP SOURCE="FP-1">Hualapai Indian Tribe of the Hualapai Indian Reservation, Arizona</FP>
                    <FP SOURCE="FP-1">Huron Potawatomi, Inc., Michigan</FP>
                    <FP SOURCE="FP-1">Inaja Band of Diegueno Mission Indians of the Inaja and Cosmit Reservation, California</FP>
                    <FP SOURCE="FP-1">Ione Band of Miwok Indians of California</FP>
                    <FP SOURCE="FP-1">Iowa Tribe of Kansas and Nebraska</FP>
                    <FP SOURCE="FP-1">Iowa Tribe of Oklahoma</FP>
                    <FP SOURCE="FP-1">Jackson Rancheria of Me-Wuk Indians of California</FP>
                    <FP SOURCE="FP-1">Jamestown S'Klallam Tribe of Washington</FP>
                    <FP SOURCE="FP-1">Jamul Indian Village of California</FP>
                    <FP SOURCE="FP-1">Jena Band of Choctaw Indians, Louisiana</FP>
                    <FP SOURCE="FP-1">Jicarilla Apache Nation, New Mexico (formerly the Jicarilla Apache Tribe of the Jicarilla Apache Indian Reservation)</FP>
                    <FP SOURCE="FP-1">Kaibab Band of Paiute Indians of the Kaibab Indian Reservation, Arizona</FP>
                    <FP SOURCE="FP-1">Kalispel Indian Community of the Kalispel Reservation, Washington</FP>
                    <FP SOURCE="FP-1">Karuk Tribe of California</FP>
                    <FP SOURCE="FP-1">Kashia Band of Pomo Indians of the Stewarts Point Rancheria, California</FP>
                    <FP SOURCE="FP-1">Kaw Nation, Oklahoma</FP>
                    <FP SOURCE="FP-1">Keweenaw Bay Indian Community, Michigan</FP>
                    <FP SOURCE="FP-1">Kialegee Tribal Town, Oklahoma</FP>
                    <FP SOURCE="FP-1">Kickapoo Tribe of Indians of the Kickapoo Reservation in Kansas</FP>
                    <FP SOURCE="FP-1">Kickapoo Tribe of Oklahoma</FP>
                    <FP SOURCE="FP-1">Kickapoo Traditional Tribe of Texas</FP>
                    <FP SOURCE="FP-1">Kiowa Indian Tribe of Oklahoma</FP>
                    <FP SOURCE="FP-1">Klamath Indian Tribe of Oregon</FP>
                    <FP SOURCE="FP-1">Kootenai Tribe of Idaho</FP>
                    <FP SOURCE="FP-1">La Jolla Band of Luiseno Mission Indians of the La Jolla Reservation, California</FP>
                    <FP SOURCE="FP-1">La Posta Band of Diegueno Mission Indians of the La Posta Indian Reservation, California</FP>
                    <FP SOURCE="FP-1">Lac Courte Oreilles Band of Lake Superior Chippewa Indians of Wisconsin</FP>
                    <FP SOURCE="FP-1">Lac du Flambeau Band of Lake Superior Chippewa Indians of the Lac du Flambeau Reservation of Wisconsin</FP>
                    <FP SOURCE="FP-1">Lac Vieux Desert Band of Lake Superior Chippewa Indians, Michigan</FP>
                    <FP SOURCE="FP-1">Las Vegas Tribe of Paiute Indians of the Las Vegas Indian Colony, Nevada</FP>
                    <FP SOURCE="FP-1">Little River Band of Ottawa Indians, Michigan</FP>
                    <FP SOURCE="FP-1">Little Traverse Bay Bands of Odawa Indians, Michigan</FP>
                    <FP SOURCE="FP-1">Lower Lake Rancheria, California</FP>
                    <FP SOURCE="FP-1">Los Coyotes Band of Cahuilla &amp; Cupeno Indians of the Los Coyotes Reservation, California (formerly the Los Coyotes Band of Cahuilla Mission Indians of the Los Coyotes Reservation)</FP>
                    <FP SOURCE="FP-1">Lovelock Paiute Tribe of the Lovelock Indian Colony, Nevada</FP>
                    <FP SOURCE="FP-1">Lower Brule Sioux Tribe of the Lower Brule Reservation, South Dakota</FP>
                    <FP SOURCE="FP-1">Lower Elwha Tribal Community of the Lower Elwha Reservation, Washington</FP>
                    <FP SOURCE="FP-1">Lower Sioux Indian Community in the State of Minnesota</FP>
                    <FP SOURCE="FP-1">Lummi Tribe of the Lummi Reservation, Washington</FP>
                    <FP SOURCE="FP-1">Lytton Rancheria of California</FP>
                    <FP SOURCE="FP-1">Makah Indian Tribe of the Makah Indian Reservation, Washington</FP>
                    <FP SOURCE="FP-1">Manchester Band of Pomo Indians of the Manchester-Point Arena Rancheria, California</FP>
                    <FP SOURCE="FP-1">Manzanita Band of Diegueno Mission Indians of the Manzanita Reservation, California</FP>
                    <FP SOURCE="FP-1">Mashantucket Pequot Tribe of Connecticut</FP>
                    <FP SOURCE="FP-1">Match-e-be-nash-she-wish Band of Pottawatomi Indians of Michigan</FP>
                    <FP SOURCE="FP-1">Mechoopda Indian Tribe of Chico Rancheria, California</FP>
                    <FP SOURCE="FP-1">Menominee Indian Tribe of Wisconsin</FP>
                    <FP SOURCE="FP-1">Mesa Grande Band of Diegueno Mission Indians of the Mesa Grande Reservation, California</FP>
                    <FP SOURCE="FP-1">Mescalero Apache Tribe of the Mescalero Reservation, New Mexico</FP>
                    <FP SOURCE="FP-1">Miami Tribe of Oklahoma</FP>
                    <FP SOURCE="FP-1">Miccosukee Tribe of Indians of Florida</FP>
                    <FP SOURCE="FP-1">Middletown Rancheria of Pomo Indians of California</FP>
                    <FP SOURCE="FP-1">Minnesota Chippewa Tribe, Minnesota (Six component reservations: Bois Forte Band (Nett Lake); Fond du Lac Band; Grand Portage Band; Leech Lake Band; Mille Lacs Band; White Earth Band)</FP>
                    <FP SOURCE="FP-1">Mississippi Band of Choctaw Indians, Mississippi</FP>
                    <FP SOURCE="FP-1">Moapa Band of Paiute Indians of the Moapa River Indian Reservation, Nevada</FP>
                    <FP SOURCE="FP-1">Modoc Tribe of Oklahoma</FP>
                    <FP SOURCE="FP-1">Mohegan Indian Tribe of Connecticut</FP>
                    <FP SOURCE="FP-1">Mooretown Rancheria of Maidu Indians of California</FP>
                    <FP SOURCE="FP-1">
                        Morongo Band of Cahuilla Mission Indians of the Morongo Reservation, California
                        <PRTPAGE P="68182"/>
                    </FP>
                    <FP SOURCE="FP-1">Muckleshoot Indian Tribe of the Muckleshoot Reservation, Washington</FP>
                    <FP SOURCE="FP-1">Muscogee (Creek) Nation, Oklahoma</FP>
                    <FP SOURCE="FP-1">Narragansett Indian Tribe of Rhode Island</FP>
                    <FP SOURCE="FP-1">Navajo Nation, Arizona, New Mexico &amp; Utah</FP>
                    <FP SOURCE="FP-1">Nez Perce Tribe of Idaho</FP>
                    <FP SOURCE="FP-1">Nisqually Indian Tribe of the Nisqually Reservation, Washington</FP>
                    <FP SOURCE="FP-1">Nooksack Indian Tribe of Washington</FP>
                    <FP SOURCE="FP-1">Northern Cheyenne Tribe of the Northern Cheyenne Indian Reservation, Montana</FP>
                    <FP SOURCE="FP-1">Northfork Rancheria of Mono Indians of California</FP>
                    <FP SOURCE="FP-1">Northwestern Band of Shoshoni Nation of Utah (Washakie)</FP>
                    <FP SOURCE="FP-1">Oglala Sioux Tribe of the Pine Ridge Reservation, South Dakota</FP>
                    <FP SOURCE="FP-1">Omaha Tribe of Nebraska</FP>
                    <FP SOURCE="FP-1">Oneida Nation of New York</FP>
                    <FP SOURCE="FP-1">Oneida Tribe of Indians of Wisconsin</FP>
                    <FP SOURCE="FP-1">Onondaga Nation of New York</FP>
                    <FP SOURCE="FP-1">Osage Tribe, Oklahoma</FP>
                    <FP SOURCE="FP-1">Ottawa Tribe of Oklahoma</FP>
                    <FP SOURCE="FP-1">Otoe-Missouria Tribe of Indians, Oklahoma</FP>
                    <FP SOURCE="FP-1">Paiute Indian Tribe of Utah (Cedar City Band of Paiutes, Kanosh Band of Paiutes, Koosharem Band of Paiutes, Indian Peaks Band of Paiutes, and Shivwits Band of Paiutes)</FP>
                    <FP SOURCE="FP-1">Paiute-Shoshone Indians of the Bishop Community of the Bishop Colony, California</FP>
                    <FP SOURCE="FP-1">Paiute-Shoshone Tribe of the Fallon Reservation and Colony, Nevada</FP>
                    <FP SOURCE="FP-1">Paiute-Shoshone Indians of the Lone Pine Community of the Lone Pine Reservation, California</FP>
                    <FP SOURCE="FP-1">Pala Band of Luiseno Mission Indians of the Pala Reservation, California</FP>
                    <FP SOURCE="FP-1">Pascua Yaqui Tribe of Arizona</FP>
                    <FP SOURCE="FP-1">Paskenta Band of Nomlaki Indians of California</FP>
                    <FP SOURCE="FP-1">Passamaquoddy Tribe of Maine</FP>
                    <FP SOURCE="FP-1">Pauma Band of Luiseno Mission Indians of the Pauma &amp; Yuima Reservation, California</FP>
                    <FP SOURCE="FP-1">Pawnee Nation of Oklahoma</FP>
                    <FP SOURCE="FP-1">Pechanga Band of Luiseno Mission Indians of the Pechanga Reservation, California</FP>
                    <FP SOURCE="FP-1">Penobscot Tribe of Maine</FP>
                    <FP SOURCE="FP-1">Peoria Tribe of Indians of Oklahoma</FP>
                    <FP SOURCE="FP-1">Picayune Rancheria of Chukchansi Indians of California</FP>
                    <FP SOURCE="FP-1">Pinoleville Rancheria of Pomo Indians of California</FP>
                    <FP SOURCE="FP-1">Pit River Tribe, California (includes XL Ranch, Big Bend, Likely, Lookout, Montgomery Creek and Roaring Creek Rancherias)</FP>
                    <FP SOURCE="FP-1">Poarch Band of Creek Indians of Alabama</FP>
                    <FP SOURCE="FP-1">Pokagon Band of Potawatomi Indians, Michigan and Indiana</FP>
                    <FP SOURCE="FP-1">Ponca Tribe of Indians of Oklahoma</FP>
                    <FP SOURCE="FP-1">Ponca Tribe of Nebraska</FP>
                    <FP SOURCE="FP-1">Port Gamble Indian Community of the Port Gamble Reservation, Washington</FP>
                    <FP SOURCE="FP-1">Potter Valley Rancheria of Pomo Indians of California</FP>
                    <FP SOURCE="FP-1">Prairie Band of Potawatomi Nation, Kansas (formerly the Prairie Band of Potawatomi Indians)</FP>
                    <FP SOURCE="FP-1">Prairie Island Indian Community in the State of Minnesota</FP>
                    <FP SOURCE="FP-1">Pueblo of Acoma, New Mexico</FP>
                    <FP SOURCE="FP-1">Pueblo of Cochiti, New Mexico</FP>
                    <FP SOURCE="FP-1">Pueblo of Jemez, New Mexico</FP>
                    <FP SOURCE="FP-1">Pueblo of Isleta, New Mexico</FP>
                    <FP SOURCE="FP-1">Pueblo of Laguna, New Mexico</FP>
                    <FP SOURCE="FP-1">Pueblo of Nambe, New Mexico</FP>
                    <FP SOURCE="FP-1">Pueblo of Picuris, New Mexico</FP>
                    <FP SOURCE="FP-1">Pueblo of Pojoaque, New Mexico</FP>
                    <FP SOURCE="FP-1">Pueblo of San Felipe, New Mexico</FP>
                    <FP SOURCE="FP-1">Pueblo of San Juan, New Mexico</FP>
                    <FP SOURCE="FP-1">Pueblo of San Ildefonso, New Mexico</FP>
                    <FP SOURCE="FP-1">Pueblo of Sandia, New Mexico</FP>
                    <FP SOURCE="FP-1">Pueblo of Santa Ana, New Mexico</FP>
                    <FP SOURCE="FP-1">Pueblo of Santa Clara, New Mexico</FP>
                    <FP SOURCE="FP-1">Pueblo of Santo Domingo, New Mexico</FP>
                    <FP SOURCE="FP-1">Pueblo of Taos, New Mexico</FP>
                    <FP SOURCE="FP-1">Pueblo of Tesuque, New Mexico</FP>
                    <FP SOURCE="FP-1">Pueblo of Zia, New Mexico</FP>
                    <FP SOURCE="FP-1">Puyallup Tribe of the Puyallup Reservation, Washington</FP>
                    <FP SOURCE="FP-1">Pyramid Lake Paiute Tribe of the Pyramid Lake Reservation, Nevada</FP>
                    <FP SOURCE="FP-1">Quapaw Tribe of Indians, Oklahoma</FP>
                    <FP SOURCE="FP-1">Quartz Valley Indian Community of the Quartz Valley Reservation of California</FP>
                    <FP SOURCE="FP-1">Quechan Tribe of the Fort Yuma Indian Reservation, California &amp; Arizona</FP>
                    <FP SOURCE="FP-1">Quileute Tribe of the Quileute Reservation, Washington</FP>
                    <FP SOURCE="FP-1">Quinault Tribe of the Quinault Reservation, Washington</FP>
                    <FP SOURCE="FP-1">Ramona Band or Village of Cahuilla Mission Indians of California</FP>
                    <FP SOURCE="FP-1">Red Cliff Band of Lake Superior Chippewa Indians of Wisconsin</FP>
                    <FP SOURCE="FP-1">Red Lake Band of Chippewa Indians, Minnesota</FP>
                    <FP SOURCE="FP-1">Redding Rancheria, California</FP>
                    <FP SOURCE="FP-1">Redwood Valley Rancheria of Pomo Indians of California</FP>
                    <FP SOURCE="FP-1">Reno-Sparks Indian Colony, Nevada</FP>
                    <FP SOURCE="FP-1">Resighini Rancheria, California (formerly the Coast Indian Community of Yurok Indians of the Resighini Rancheria)</FP>
                    <FP SOURCE="FP-1">Rincon Band of Luiseno Mission Indians of the Rincon Reservation, California</FP>
                    <FP SOURCE="FP-1">Robinson Rancheria of Pomo Indians of California</FP>
                    <FP SOURCE="FP-1">Rosebud Sioux Tribe of the Rosebud Indian Reservation, South Dakota</FP>
                    <FP SOURCE="FP-1">Round Valley Indian Tribes of the Round Valley Reservation, California (formerly the Covelo Indian Community)</FP>
                    <FP SOURCE="FP-1">Rumsey Indian Rancheria of Wintun Indians of California</FP>
                    <FP SOURCE="FP-1">Sac &amp; Fox Tribe of the Mississippi in Iowa</FP>
                    <FP SOURCE="FP-1">Sac &amp; Fox Nation of Missouri in Kansas and Nebraska</FP>
                    <FP SOURCE="FP-1">Sac &amp; Fox Nation, Oklahoma</FP>
                    <FP SOURCE="FP-1">Saginaw Chippewa Indian Tribe of Michigan</FP>
                    <FP SOURCE="FP-1">St. Croix Chippewa Indians of Wisconsin</FP>
                    <FP SOURCE="FP-1">St. Regis Band of Mohawk Indians of New York</FP>
                    <FP SOURCE="FP-1">Salt River Pima-Maricopa Indian Community of the Salt River Reservation, Arizona</FP>
                    <FP SOURCE="FP-1">Samish Indian Tribe, Washington</FP>
                    <FP SOURCE="FP-1">San Carlos Apache Tribe of the San Carlos Reservation, Arizona</FP>
                    <FP SOURCE="FP-1">San Juan Southern Paiute Tribe of Arizona</FP>
                    <FP SOURCE="FP-1">San Manual Band of Serrano Mission Indians of the San Manual Reservation, California</FP>
                    <FP SOURCE="FP-1">San Pasqual Band of Diegueno Mission Indians of California</FP>
                    <FP SOURCE="FP-1">Santa Rosa Indian Community of the Santa Rosa Rancheria, California</FP>
                    <FP SOURCE="FP-1">Santa Rosa Band of Cahuilla Mission Indians of the Santa Rosa Reservation, California</FP>
                    <FP SOURCE="FP-1">Santa Ynez Band of Chumash Mission Indians of the Santa Ynez Reservation, California</FP>
                    <FP SOURCE="FP-1">Santa Ysabel Band of Diegueno Mission Indians of the Santa Ysabel Reservation, California</FP>
                    <FP SOURCE="FP-1">Santee Sioux Nation, Nebraska (formerly the Santee Sioux Tribe of the Santee Reservation of Nebraska)</FP>
                    <FP SOURCE="FP-1">Sauk-Suiattle Indian Tribe of Washington</FP>
                    <FP SOURCE="FP-1">Sault Ste. Marie Tribe of Chippewa Indians of Michigan</FP>
                    <FP SOURCE="FP-1">Scotts Valley Band of Pomo Indians of California</FP>
                    <FP SOURCE="FP-1">Seminole Nation of Oklahoma</FP>
                    <FP SOURCE="FP-1">Seminole Tribe of Florida, Dania, Big Cypress, Brighton, Hollywood &amp; Tampa Reservations</FP>
                    <FP SOURCE="FP-1">Seneca Nation of New York</FP>
                    <FP SOURCE="FP-1">Seneca-Cayuga Tribe of Oklahoma</FP>
                    <FP SOURCE="FP-1">Shakopee Mdewakanton Sioux Community of Minnesota</FP>
                    <FP SOURCE="FP-1">Shawnee Tribe, Oklahoma</FP>
                    <FP SOURCE="FP-1">Sherwood Valley Rancheria of Pomo Indians of California</FP>
                    <FP SOURCE="FP-1">Shingle Springs Band of Miwok Indians, Shingle Springs Rancheria (Verona Tract), California</FP>
                    <FP SOURCE="FP-1">Shoalwater Bay Tribe of the Shoalwater Bay Indian Reservation, Washington</FP>
                    <FP SOURCE="FP-1">Shoshone Tribe of the Wind River Reservation, Wyoming</FP>
                    <FP SOURCE="FP-1">Shoshone-Bannock Tribes of the Fort Hall Reservation of Idaho</FP>
                    <FP SOURCE="FP-1">Shoshone-Paiute Tribes of the Duck Valley Reservation, Nevada</FP>
                    <FP SOURCE="FP-1">
                        Sisseton-Wahpeton Oyate of the Lake Traverse Reservation, South Dakota (formerly the Sisseton-Wahpeton 
                        <PRTPAGE P="68183"/>
                        Sioux Tribe of the Lake Traverse Reservation)
                    </FP>
                    <FP SOURCE="FP-1">Skokomish Indian Tribe of the Skokomish Reservation, Washington</FP>
                    <FP SOURCE="FP-1">Skull Valley Band of Goshute Indians of Utah</FP>
                    <FP SOURCE="FP-1">Smith River Rancheria, California</FP>
                    <FP SOURCE="FP-1">Snoqualmie Tribe, Washington</FP>
                    <FP SOURCE="FP-1">Soboba Band of Luiseno Indians, California (formerly the Soboba Band of Luiseno Mission Indians of the Soboba Reservation)</FP>
                    <FP SOURCE="FP-1">Sokaogon Chippewa Community, Wisconsin</FP>
                    <FP SOURCE="FP-1">Southern Ute Indian Tribe of the Southern Ute Reservation, Colorado</FP>
                    <FP SOURCE="FP-1">Spirit Lake Tribe, North Dakota</FP>
                    <FP SOURCE="FP-1">Spokane Tribe of the Spokane Reservation, Washington</FP>
                    <FP SOURCE="FP-1">Squaxin Island Tribe of the Squaxin Island Reservation, Washington</FP>
                    <FP SOURCE="FP-1">Standing Rock Sioux Tribe of North &amp; South Dakota</FP>
                    <FP SOURCE="FP-1">Stockbridge Munsee Community, Wisconsin</FP>
                    <FP SOURCE="FP-1">Stillaguamish Tribe of Washington</FP>
                    <FP SOURCE="FP-1">Summit Lake Paiute Tribe of Nevada</FP>
                    <FP SOURCE="FP-1">Suquamish Indian Tribe of the Port Madison Reservation, Washington</FP>
                    <FP SOURCE="FP-1">Susanville Indian Rancheria, California</FP>
                    <FP SOURCE="FP-1">Swinomish Indians of the Swinomish Reservation, Washington</FP>
                    <FP SOURCE="FP-1">Sycuan Band of Diegueno Mission Indians of California</FP>
                    <FP SOURCE="FP-1">Table Bluff Reservation—Wiyot Tribe, California</FP>
                    <FP SOURCE="FP-1">Table Mountain Rancheria of California</FP>
                    <FP SOURCE="FP-1">Te-Moak Tribe of Western Shoshone Indians of Nevada (Four constituent bands: Battle Mountain Band; Elko Band; South Fork Band and Wells Band)</FP>
                    <FP SOURCE="FP-1">Thlopthlocco Tribal Town, Oklahoma</FP>
                    <FP SOURCE="FP-1">Three Affiliated Tribes of the Fort Berthold Reservation, North Dakota</FP>
                    <FP SOURCE="FP-1">Tohono O'odham Nation of Arizona</FP>
                    <FP SOURCE="FP-1">Tonawanda Band of Seneca Indians of New York</FP>
                    <FP SOURCE="FP-1">Tonkawa Tribe of Indians of Oklahoma</FP>
                    <FP SOURCE="FP-1">Tonto Apache Tribe of Arizona</FP>
                    <FP SOURCE="FP-1">Torres-Martinez Band of Cahuilla Mission Indians of California</FP>
                    <FP SOURCE="FP-1">Tule River Indian Tribe of the Tule River Reservation, California</FP>
                    <FP SOURCE="FP-1">Tulalip Tribes of the Tulalip Reservation, Washington</FP>
                    <FP SOURCE="FP-1">Tunica-Biloxi Indian Tribe of Louisiana</FP>
                    <FP SOURCE="FP-1">Tuolumne Band of Me-Wuk Indians of the Tuolumne Rancheria of California</FP>
                    <FP SOURCE="FP-1">Turtle Mountain Band of Chippewa Indians of North Dakota</FP>
                    <FP SOURCE="FP-1">Tuscarora Nation of New York</FP>
                    <FP SOURCE="FP-1">Twenty-Nine Palms Band of Mission Indians of California</FP>
                    <FP SOURCE="FP-1">United Auburn Indian Community of the Auburn Rancheria of California</FP>
                    <FP SOURCE="FP-1">United Keetoowah Band of Cherokee Indians in Oklahoma</FP>
                    <FP SOURCE="FP-1">Upper Lake Band of Pomo Indians of Upper Lake Rancheria of California</FP>
                    <FP SOURCE="FP-1">Upper Sioux Community, Minnesota</FP>
                    <FP SOURCE="FP-1">Upper Skagit Indian Tribe of Washington</FP>
                    <FP SOURCE="FP-1">Ute Indian Tribe of the Uintah &amp; Ouray Reservation, Utah</FP>
                    <FP SOURCE="FP-1">Ute Mountain Tribe of the Ute Mountain Reservation, Colorado, New Mexico &amp; Utah</FP>
                    <FP SOURCE="FP-1">Utu Utu Gwaitu Paiute Tribe of the Benton Paiute Reservation, California</FP>
                    <FP SOURCE="FP-1">Walker River Paiute Tribe of the Walker River Reservation, Nevada</FP>
                    <FP SOURCE="FP-1">Wampanoag Tribe of Gay Head (Aquinnah) of Massachusetts</FP>
                    <FP SOURCE="FP-1">Washoe Tribe of Nevada &amp; California (Carson Colony, Dresslerville Colony, Woodfords Community, Stewart Community, &amp; Washoe Ranches)</FP>
                    <FP SOURCE="FP-1">White Mountain Apache Tribe of the Fort Apache Reservation, Arizona</FP>
                    <FP SOURCE="FP-1">Wichita and Affiliated Tribes (Wichita, Keechi, Waco &amp; Tawakonie), Oklahoma</FP>
                    <FP SOURCE="FP-1">Winnebago Tribe of Nebraska</FP>
                    <FP SOURCE="FP-1">Winnemucca Indian Colony of Nevada</FP>
                    <FP SOURCE="FP-1">Wyandotte Nation, Oklahoma (formerly the Wyandotte Tribe of Oklahoma)</FP>
                    <FP SOURCE="FP-1">Yankton Sioux Tribe of South Dakota</FP>
                    <FP SOURCE="FP-1">Yavapai-Apache Nation of the Camp Verde Indian Reservation, Arizona</FP>
                    <FP SOURCE="FP-1">Yavapai-Prescott Tribe of the Yavapai Reservation, Arizona</FP>
                    <FP SOURCE="FP-1">Yerington Paiute Tribe of the Yerington Colony &amp; Campbell Ranch, Nevada</FP>
                    <FP SOURCE="FP-1">Yomba Shoshone Tribe of the Yomba Reservation, Nevada</FP>
                    <FP SOURCE="FP-1">Ysleta Del Sur Pueblo of Texas</FP>
                    <FP SOURCE="FP-1">Yurok Tribe of the Yurok Reservation, California</FP>
                    <FP SOURCE="FP-1">Zuni Tribe of the Zuni Reservation, New Mexico</FP>
                    <HD SOURCE="HD1">Native Entities Within the State of Alaska Recognized and Eligible To Receive Services From the United States Bureau of Indian Affairs</HD>
                    <FP SOURCE="FP-1">Native Village of Afognak (formerly the Village of Afognak)</FP>
                    <FP SOURCE="FP-1">Agdaagux Tribe of King Cove</FP>
                    <FP SOURCE="FP-1">Native Village of Akhiok</FP>
                    <FP SOURCE="FP-1">Akiachak Native Community</FP>
                    <FP SOURCE="FP-1">Akiak Native Community</FP>
                    <FP SOURCE="FP-1">Native Village of Akutan</FP>
                    <FP SOURCE="FP-1">Village of Alakanuk</FP>
                    <FP SOURCE="FP-1">Alatna Village</FP>
                    <FP SOURCE="FP-1">Native Village of Aleknagik</FP>
                    <FP SOURCE="FP-1">Algaaciq Native Village (St. Mary's)</FP>
                    <FP SOURCE="FP-1">Allakaket Village</FP>
                    <FP SOURCE="FP-1">Native Village of Ambler</FP>
                    <FP SOURCE="FP-1">Village of Anaktuvuk Pass</FP>
                    <FP SOURCE="FP-1">Yupiit of Andreafski</FP>
                    <FP SOURCE="FP-1">Angoon Community Association</FP>
                    <FP SOURCE="FP-1">Village of Aniak</FP>
                    <FP SOURCE="FP-1">Anvik Village</FP>
                    <FP SOURCE="FP-1">Arctic Village (See Native Village of Venetie Tribal Government)</FP>
                    <FP SOURCE="FP-1">Asa'carsarmiut Tribe (formerly the Native Village of Mountain Village)</FP>
                    <FP SOURCE="FP-1">Native Village of Atka</FP>
                    <FP SOURCE="FP-1">Village of Atmautluak</FP>
                    <FP SOURCE="FP-1">Atqasuk Village (Atkasook)</FP>
                    <FP SOURCE="FP-1">Native Village of Barrow Inupiat Traditional Government</FP>
                    <FP SOURCE="FP-1">Beaver Village</FP>
                    <FP SOURCE="FP-1">Native Village of Belkofski</FP>
                    <FP SOURCE="FP-1">Village of Bill Moore's Slough</FP>
                    <FP SOURCE="FP-1">Birch Creek Tribe</FP>
                    <FP SOURCE="FP-1">Native Village of Brevig Mission</FP>
                    <FP SOURCE="FP-1">Native Village of Buckland</FP>
                    <FP SOURCE="FP-1">Native Village of Cantwell</FP>
                    <FP SOURCE="FP-1">Native Village of Chanega (aka Chenega)</FP>
                    <FP SOURCE="FP-1">Chalkyitsik Village</FP>
                    <FP SOURCE="FP-1">Cheesh-Na Tribe (formerly the Native Village of Chistochina)</FP>
                    <FP SOURCE="FP-1">Village of Chefornak</FP>
                    <FP SOURCE="FP-1">Chevak Native Village</FP>
                    <FP SOURCE="FP-1">Chickaloon Native Village</FP>
                    <FP SOURCE="FP-1">Native Village of Chignik</FP>
                    <FP SOURCE="FP-1">Native Village of Chignik Lagoon</FP>
                    <FP SOURCE="FP-1">Chignik Lake Village</FP>
                    <FP SOURCE="FP-1">Chilkat Indian Village (Klukwan)</FP>
                    <FP SOURCE="FP-1">Chilkoot Indian Association (Haines)</FP>
                    <FP SOURCE="FP-1">Chinik Eskimo Community (Golovin)</FP>
                    <FP SOURCE="FP-1">Native Village of Chitina</FP>
                    <FP SOURCE="FP-1">Native Village of Chuathbaluk (Russian Mission, Kuskokwim)</FP>
                    <FP SOURCE="FP-1">Chuloonawick Native Village</FP>
                    <FP SOURCE="FP-1">Circle Native Community</FP>
                    <FP SOURCE="FP-1">Village of Clarks Point</FP>
                    <FP SOURCE="FP-1">Native Village of Council</FP>
                    <FP SOURCE="FP-1">Craig Community Association</FP>
                    <FP SOURCE="FP-1">Village of Crooked Creek</FP>
                    <FP SOURCE="FP-1">Curyung Tribal Council (formerly the Native Village of Dillingham)</FP>
                    <FP SOURCE="FP-1">Native Village of Deering</FP>
                    <FP SOURCE="FP-1">Native Village of Diomede (aka Inalik)</FP>
                    <FP SOURCE="FP-1">Village of Dot Lake</FP>
                    <FP SOURCE="FP-1">Douglas Indian Association</FP>
                    <FP SOURCE="FP-1">Native Village of Eagle</FP>
                    <FP SOURCE="FP-1">Native Village of Eek</FP>
                    <FP SOURCE="FP-1">Egegik Village</FP>
                    <FP SOURCE="FP-1">Eklutna Native Village</FP>
                    <FP SOURCE="FP-1">Native Village of Ekuk</FP>
                    <FP SOURCE="FP-1">Ekwok Village</FP>
                    <FP SOURCE="FP-1">Native Village of Elim</FP>
                    <FP SOURCE="FP-1">Emmonak Village</FP>
                    <FP SOURCE="FP-1">Evansville Village (aka Bettles Field)</FP>
                    <FP SOURCE="FP-1">Native Village of Eyak (Cordova)</FP>
                    <FP SOURCE="FP-1">Native Village of False Pass</FP>
                    <FP SOURCE="FP-1">Native Village of Fort Yukon</FP>
                    <FP SOURCE="FP-1">Native Village of Gakona</FP>
                    <FP SOURCE="FP-1">Galena Village (aka Louden Village)</FP>
                    <FP SOURCE="FP-1">Native Village of Gambell</FP>
                    <FP SOURCE="FP-1">Native Village of Georgetown</FP>
                    <FP SOURCE="FP-1">Native Village of Goodnews Bay</FP>
                    <FP SOURCE="FP-1">Organized Village of Grayling (aka Holikachuk)</FP>
                    <FP SOURCE="FP-1">Gulkana Village</FP>
                    <FP SOURCE="FP-1">Native Village of Hamilton</FP>
                    <FP SOURCE="FP-1">Healy Lake Village</FP>
                    <FP SOURCE="FP-1">Holy Cross Village</FP>
                    <FP SOURCE="FP-1">Hoonah Indian Association</FP>
                    <FP SOURCE="FP-1">Native Village of Hooper Bay</FP>
                    <FP SOURCE="FP-1">Hughes Village</FP>
                    <FP SOURCE="FP-1">Huslia Village</FP>
                    <FP SOURCE="FP-1">Hydaburg Cooperative Association</FP>
                    <FP SOURCE="FP-1">Igiugig Village</FP>
                    <FP SOURCE="FP-1">
                        Village of Iliamna
                        <PRTPAGE P="68184"/>
                    </FP>
                    <FP SOURCE="FP-1">Inupiat Community of the Arctic Slope</FP>
                    <FP SOURCE="FP-1">Iqurmuit Traditional Council (formerly the Native Village of Russian Mission)</FP>
                    <FP SOURCE="FP-1">Ivanoff Bay Village</FP>
                    <FP SOURCE="FP-1">Kaguyak Village</FP>
                    <FP SOURCE="FP-1">Organized Village of Kake</FP>
                    <FP SOURCE="FP-1">Kaktovik Village (aka Barter Island)</FP>
                    <FP SOURCE="FP-1">Village of Kalskag</FP>
                    <FP SOURCE="FP-1">Village of Kaltag</FP>
                    <FP SOURCE="FP-1">Native Village of Kanatak</FP>
                    <FP SOURCE="FP-1">Native Village of Karluk</FP>
                    <FP SOURCE="FP-1">Organized Village of Kasaan</FP>
                    <FP SOURCE="FP-1">Native Village of Kasigluk</FP>
                    <FP SOURCE="FP-1">Kenaitze Indian Tribe</FP>
                    <FP SOURCE="FP-1">Ketchikan Indian Corporation</FP>
                    <FP SOURCE="FP-1">Native Village of Kiana</FP>
                    <FP SOURCE="FP-1">King Island Native Community</FP>
                    <FP SOURCE="FP-1">King Salmon Tribe</FP>
                    <FP SOURCE="FP-1">Native Village of Kipnuk</FP>
                    <FP SOURCE="FP-1">Native Village of Kivalina</FP>
                    <FP SOURCE="FP-1">Klawock Cooperative Association</FP>
                    <FP SOURCE="FP-1">Native Village of Kluti Kaah (aka Copper Center)</FP>
                    <FP SOURCE="FP-1">Knik Tribe</FP>
                    <FP SOURCE="FP-1">Native Village of Kobuk</FP>
                    <FP SOURCE="FP-1">Kokhanok Village</FP>
                    <FP SOURCE="FP-1">Native Village of Kongiganak</FP>
                    <FP SOURCE="FP-1">Village of Kotlik</FP>
                    <FP SOURCE="FP-1">Native Village of Kotzebue</FP>
                    <FP SOURCE="FP-1">Native Village of Koyuk</FP>
                    <FP SOURCE="FP-1">Koyukuk Native Village</FP>
                    <FP SOURCE="FP-1">Organized Village of Kwethluk</FP>
                    <FP SOURCE="FP-1">Native Village of Kwigillingok</FP>
                    <FP SOURCE="FP-1">Native Village of Kwinhagak (aka Quinhagak)</FP>
                    <FP SOURCE="FP-1">Native Village of Larsen Bay</FP>
                    <FP SOURCE="FP-1">Levelock Village</FP>
                    <FP SOURCE="FP-1">Lesnoi Village (aka Woody Island)</FP>
                    <FP SOURCE="FP-1">Lime Village</FP>
                    <FP SOURCE="FP-1">Village of Lower Kalskag</FP>
                    <FP SOURCE="FP-1">Manley Hot Springs Village</FP>
                    <FP SOURCE="FP-1">Manokotak Village</FP>
                    <FP SOURCE="FP-1">Native Village of Marshall (aka Fortuna Ledge)</FP>
                    <FP SOURCE="FP-1">Native Village of Mary's Igloo</FP>
                    <FP SOURCE="FP-1">McGrath Native Village</FP>
                    <FP SOURCE="FP-1">Native Village of Mekoryuk</FP>
                    <FP SOURCE="FP-1">Mentasta Traditional Council</FP>
                    <FP SOURCE="FP-1">Metlakatla Indian Community, Annette Island Reserve</FP>
                    <FP SOURCE="FP-1">Native Village of Minto</FP>
                    <FP SOURCE="FP-1">Naknek Native Village</FP>
                    <FP SOURCE="FP-1">Native Village of Nanwalek (aka English Bay)</FP>
                    <FP SOURCE="FP-1">Native Village of Napaimute</FP>
                    <FP SOURCE="FP-1">Native Village of Napakiak</FP>
                    <FP SOURCE="FP-1">Native Village of Napaskiak</FP>
                    <FP SOURCE="FP-1">Native Village of Nelson Lagoon</FP>
                    <FP SOURCE="FP-1">Nenana Native Association</FP>
                    <FP SOURCE="FP-1">New Koliganek Village Council (formerly the Koliganek Village)</FP>
                    <FP SOURCE="FP-1">New Stuyahok Village</FP>
                    <FP SOURCE="FP-1">Newhalen Village</FP>
                    <FP SOURCE="FP-1">Newtok Village</FP>
                    <FP SOURCE="FP-1">Native Village of Nightmute</FP>
                    <FP SOURCE="FP-1">Nikolai Village</FP>
                    <FP SOURCE="FP-1">Native Village of Nikolski</FP>
                    <FP SOURCE="FP-1">Ninilchik Village</FP>
                    <FP SOURCE="FP-1">Native Village of Noatak</FP>
                    <FP SOURCE="FP-1">Nome Eskimo Community</FP>
                    <FP SOURCE="FP-1">Nondalton Village</FP>
                    <FP SOURCE="FP-1">Noorvik Native Community</FP>
                    <FP SOURCE="FP-1">Northway Village</FP>
                    <FP SOURCE="FP-1">Native Village of Nuiqsut (aka Nooiksut)</FP>
                    <FP SOURCE="FP-1">Nulato Village</FP>
                    <FP SOURCE="FP-1">Nunakauyarmiut Tribe (formerly the Native Village of Toksook Bay)</FP>
                    <FP SOURCE="FP-1">Native Village of Nunapitchuk</FP>
                    <FP SOURCE="FP-1">Village of Ohogamiut</FP>
                    <FP SOURCE="FP-1">Village of Old Harbor</FP>
                    <FP SOURCE="FP-1">Orutsararmuit Native Village (aka Bethel)</FP>
                    <FP SOURCE="FP-1">Oscarville Traditional Village</FP>
                    <FP SOURCE="FP-1">Native Village of Ouzinkie</FP>
                    <FP SOURCE="FP-1">Native Village of Paimiut</FP>
                    <FP SOURCE="FP-1">Pauloff Harbor Village</FP>
                    <FP SOURCE="FP-1">Pedro Bay Village</FP>
                    <FP SOURCE="FP-1">Native Village of Perryville</FP>
                    <FP SOURCE="FP-1">Petersburg Indian Association</FP>
                    <FP SOURCE="FP-1">Native Village of Pilot Point</FP>
                    <FP SOURCE="FP-1">Pilot Station Traditional Village</FP>
                    <FP SOURCE="FP-1">Native Village of Pitka's Point</FP>
                    <FP SOURCE="FP-1">Platinum Traditional Village</FP>
                    <FP SOURCE="FP-1">Native Village of Point Hope</FP>
                    <FP SOURCE="FP-1">Native Village of Point Lay</FP>
                    <FP SOURCE="FP-1">Native Village of Port Graham</FP>
                    <FP SOURCE="FP-1">Native Village of Port Heiden</FP>
                    <FP SOURCE="FP-1">Native Village of Port Lions</FP>
                    <FP SOURCE="FP-1">Portage Creek Village (aka Ohgsenakale)</FP>
                    <FP SOURCE="FP-1">Pribilof Islands Aleut Communities of St. Paul &amp; St. George Islands</FP>
                    <FP SOURCE="FP-1">Qagan Tayagungin Tribe of Sand Point Village</FP>
                    <FP SOURCE="FP-1">Qawalangin Tribe of Unalaska</FP>
                    <FP SOURCE="FP-1">Rampart Village</FP>
                    <FP SOURCE="FP-1">Village of Red Devil</FP>
                    <FP SOURCE="FP-1">Native Village of Ruby</FP>
                    <FP SOURCE="FP-1">Saint George Island (See Pribilof Islands Aleut Communities of St. Paul &amp; St. George Islands)</FP>
                    <FP SOURCE="FP-1">Native Village of Saint Michael</FP>
                    <FP SOURCE="FP-1">Saint Paul Island (See Pribilof Islands Aleut Communities of St. Paul &amp; St. George Islands)</FP>
                    <FP SOURCE="FP-1">Village of Salamatoff</FP>
                    <FP SOURCE="FP-1">Native Village of Savoonga</FP>
                    <FP SOURCE="FP-1">Organized Village of Saxman</FP>
                    <FP SOURCE="FP-1">Native Village of Scammon Bay</FP>
                    <FP SOURCE="FP-1">Native Village of Selawik</FP>
                    <FP SOURCE="FP-1">Seldovia Village Tribe</FP>
                    <FP SOURCE="FP-1">Shageluk Native Village</FP>
                    <FP SOURCE="FP-1">Native Village of Shaktoolik</FP>
                    <FP SOURCE="FP-1">Native Village of Sheldon's Point</FP>
                    <FP SOURCE="FP-1">Native Village of Shishmaref</FP>
                    <FP SOURCE="FP-1">Shoonaq' Tribe of Kodiak</FP>
                    <FP SOURCE="FP-1">Native Village of Shungnak</FP>
                    <FP SOURCE="FP-1">Sitka Tribe of Alaska</FP>
                    <FP SOURCE="FP-1">Skagway Village</FP>
                    <FP SOURCE="FP-1">Village of Sleetmute</FP>
                    <FP SOURCE="FP-1">Village of Solomon</FP>
                    <FP SOURCE="FP-1">South Naknek Village</FP>
                    <FP SOURCE="FP-1">Stebbins Community Association</FP>
                    <FP SOURCE="FP-1">Native Village of Stevens</FP>
                    <FP SOURCE="FP-1">Village of Stony River</FP>
                    <FP SOURCE="FP-1">Takotna Village</FP>
                    <FP SOURCE="FP-1">Native Village of Tanacross</FP>
                    <FP SOURCE="FP-1">Native Village of Tanana</FP>
                    <FP SOURCE="FP-1">Native Village of Tatitlek</FP>
                    <FP SOURCE="FP-1">Native Village of Tazlina</FP>
                    <FP SOURCE="FP-1">Telida Village</FP>
                    <FP SOURCE="FP-1">Native Village of Teller</FP>
                    <FP SOURCE="FP-1">Native Village of Tetlin</FP>
                    <FP SOURCE="FP-1">Central Council of the Tlingit &amp; Haida Indian Tribes</FP>
                    <FP SOURCE="FP-1">Traditional Village of Togiak</FP>
                    <FP SOURCE="FP-1">Tuluksak Native Community</FP>
                    <FP SOURCE="FP-1">Native Village of Tuntutuliak</FP>
                    <FP SOURCE="FP-1">Native Village of Tununak</FP>
                    <FP SOURCE="FP-1">Twin Hills Village</FP>
                    <FP SOURCE="FP-1">Native Village of Tyonek</FP>
                    <FP SOURCE="FP-1">Ugashik Village</FP>
                    <FP SOURCE="FP-1">Umkumiute Native Village</FP>
                    <FP SOURCE="FP-1">Native Village of Unalakleet</FP>
                    <FP SOURCE="FP-1">Native Village of Unga</FP>
                    <FP SOURCE="FP-1">Village of Venetie (See Native Village of Venetie Tribal Government)</FP>
                    <FP SOURCE="FP-1">Native Village of Venetie Tribal Government (Arctic Village and Village of Venetie)</FP>
                    <FP SOURCE="FP-1">Village of Wainwright</FP>
                    <FP SOURCE="FP-1">Native Village of Wales</FP>
                    <FP SOURCE="FP-1">Native Village of White Mountain</FP>
                    <FP SOURCE="FP-1">Wrangell Cooperative Association</FP>
                    <FP SOURCE="FP-1">Yakutat Tlingit Tribe</FP>
                </SUPLINF>
                <FRDOC>[FR Doc. 03-30244 Filed 12-4-03; 8:45 am]</FRDOC>
                <BILCOD>BILLING CODE 4310-4J-P</BILCOD>
            </NOTICE>
        </NOTICES>
    </NEWPART>
    <VOL>68</VOL>
    <NO>234</NO>
    <DATE>Friday, December 5, 2003</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="68185"/>
            <PARTNO>Part IV</PARTNO>
            <AGENCY TYPE="P">Securities and Exchange Commission</AGENCY>
            <CFR>17 CFR Parts 200, 201, and 240</CFR>
            <TITLE>Proposed Amendments to the Rules of Practice and Related Provisions; Proposed Rule</TITLE>
        </PTITLE>
        <PRORULES>
            <PRORULE>
                <PREAMB>
                    <PRTPAGE P="68186"/>
                    <AGENCY TYPE="S">SECURITIES AND EXCHANGE COMMISSION</AGENCY>
                    <CFR>17 CFR Parts 200, 201, and 240</CFR>
                    <DEPDOC>[Release No. 34-48832; File No. S7-25-03]</DEPDOC>
                    <RIN>RIN 3235-AI</RIN>
                    <SUBJECT>Proposed Amendments to the Rules of Practice and Related Provisions</SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Securities and Exchange Commission.</P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Proposed rule.</P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>The Securities and Exchange Commission (“Commission”) is proposing for public comment amendments to its Rules of Practice and related provisions in light of the Sarbanes-Oxley Act of 2002. The Sarbanes-Oxley Act, among other things, authorizes the Commission to review disciplinary actions of the Public Company Accounting Oversight Board (“Board”) and to create “Fair Funds” in Commission administrative proceedings. The Commission is also proposing for public comment amendments to other provisions of the Rules of Practice (“Rules”) as a result of its experience with those rules and to correct certain citations. The proposed amendments are intended to enhance the transparency and facilitate parties' understanding of the applicability of the review process to Board proceedings, and to make practice under the rules easier and more efficient.</P>
                    </SUM>
                    <EFFDATE>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>Comments must be submitted on or before January 5, 2004.</P>
                    </EFFDATE>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P>To help us process and review your comments efficiently, comments should be sent by hard copy or e-mail, but not by both methods.</P>
                        <P>
                            Comments sent by hard copy should be submitted in triplicate to Jonathan G. Katz, Secretary, U.S. Securities and Exchange Commission, 450 Fifth Street, NW., Washington, DC 20549-0609. Alternatively, comments may be submitted electronically to the following e-mail address: 
                            <E T="03">rule-comments@sec.gov.</E>
                             All comment letters should refer to File No. S7-25-03. This file number should be included on the subject line if e-mail is used. All comment letters received will be available for public inspection and copying in the Commission's Public Reference Room, 450 Fifth Street, NW., Washington, DC 20549. Electronically submitted comment letters will be posted on the Commission's Internet Web site (
                            <E T="03">http://www.sec.gov)</E>
                            .
                            <SU>1</SU>
                            <FTREF/>
                        </P>
                        <FTNT>
                            <P>
                                <SU>1</SU>
                                 The Commission does not edit personal identifying information, such as names or electronic mail addresses, from electronic submissions. Interested persons submitting comments should submit only information that they wish to make publicly available.
                            </P>
                        </FTNT>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>Diane V. White, Office of the General Counsel, (202) 942-0950, Securities and Exchange Commission, 450 5th Street, NW., Washington, DC 20549-0208.</P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <P>
                        The Commission proposes to amend its Rules of Practice and related provisions. The amendments are being proposed in accordance with the provisions of the Sarbanes-Oxley Act of 2002 
                        <SU>2</SU>
                        <FTREF/>
                         and as a result of the Commission's experience with its existing rules. Additional amendments correct typographical errors and change certain citations to conform to the amended rules.
                        <SU>3</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>2</SU>
                             15 U.S.C. 7201 
                            <E T="03">et seq.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>3</SU>
                             Any necessary delegations will be adopted when the rules become final.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">I. Discussion</HD>
                    <HD SOURCE="HD2">A. Proposed Amendments as a Result of the Sarbanes-Oxley Act</HD>
                    <P>
                        Section 107(c) of the Sarbanes-Oxley Act 
                        <SU>4</SU>
                        <FTREF/>
                         authorizes the Commission to review disciplinary actions imposed by the Board and actions that result in the disapproval of registration of a public accounting firm.
                        <SU>5</SU>
                        <FTREF/>
                         Sections 105(d) and 107(c) of the Sarbanes-Oxley Act require the Board to give the Commission notice if it disapproves the registration of a public accounting firm or if it disciplines a registered public accounting firm or a person associated with a registered public accounting firm.
                    </P>
                    <FTNT>
                        <P>
                            <SU>4</SU>
                             15 U.S.C. 7217(c).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>5</SU>
                             Under section 102(c) of the Sarbanes-Oxley Act, 15 U.S.C. 7212(c), the Board's written notice of disapproval of a complete application for registration as a registered public accounting firm is treated as a “disciplinary sanction” for purposes of sections 105(d) and 107(c) of that act, 15 U.S.C. 7215(d), 7217(c).
                        </P>
                    </FTNT>
                    <P>
                        In creating its framework for Commission review of Board actions, section 107(c) of the Sarbanes-Oxley Act specifies that sections 19(d)(2) and 19(e)(1) of the Securities Exchange Act of 1934,
                        <SU>6</SU>
                        <FTREF/>
                         which govern Commission review of self-regulatory organization disciplinary proceedings, shall govern Commission review of final disciplinary sanctions imposed by the Board “as fully as if the Board were a self-regulatory organization and the Commission were the appropriate regulatory agency for such organization for purposes of those sections 19(d)(2) and 19(e)(1) * * *” The effect of this statutory provision is to make Board actions subject to Commission review under those Exchange Act provisions on the same basis as actions by existing self-regulatory organizations, and to make relevant rules under those provisions applicable to that review. Thus, the administrative structure currently used by the Commission in reviewing self-regulatory disciplinary organization proceedings, including relevant provisions of the Rules, is applicable to persons seeking review of Board actions.
                    </P>
                    <FTNT>
                        <P>
                            <SU>6</SU>
                             15 U.S.C. 78s(d)(2), 78s(e)(1).
                        </P>
                    </FTNT>
                    <P>The Commission nonetheless has determined to propose amendments to certain of its rules in order to enhance the transparency and facilitate parties' understanding of the applicability of the review process to Board proceedings. Certain of those changes to its Rules will include specific references to Commission review of Board actions and, for example, identify the process by which the Board will provide notice to the Commission of its actions. The Commission asks for comment as to whether adjustments to the existing rules, in addition to those the Commission proposes, are warranted in order to permit the Commission more effectively to exercise its statutory review authority with respect to Board proceedings. </P>
                    <HD SOURCE="HD3">1. Disapproval of Registration </HD>
                    <P>
                        Proposed Rule 19d-4(a) would add definitions. Proposed Rule 19d-4(b) would require the Board to file with the Commission and serve on the public accounting firm a notice of disapproval of registration within 30 days of the Board's action.
                        <SU>7</SU>
                        <FTREF/>
                         The notice would include the firm's name and last known address (as reflected in the Board's records) the basis for the Board's disapproval, a copy of the Board's written notice of disapproval, and such other information as the Board deems relevant. 
                    </P>
                    <FTNT>
                        <P>
                            <SU>7</SU>
                             The thirty-day period for filing is consistent with the thirty days provided in section 19(d)(2) of the Exchange Act for the filing of an application for review by a person aggrieved by certain actions taken by a self-regulatory organization. The Commission requests comment as to whether this period is appropriate in the context of review of actions by the Board, or whether a longer or shorter period would be preferable.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">2. Review of Disciplinary Sanctions </HD>
                    <P>
                        Proposed Rule 19d-4(c) would require the Board to file and serve a notice of any disciplinary sanction, other than a disapproval of registration, within 30 days of the Board's action.
                        <SU>8</SU>
                        <FTREF/>
                         The notice would provide the name and last address (as reflected in the Board's records) of the associated person or registered public accounting firm 
                        <PRTPAGE P="68187"/>
                        disciplined and a description of the acts or omissions upon which the sanction is based. The notice would also specify the sanction imposed, give the effective date of the sanction, and include a statement of the reasons for the sanction or a copy of the Board's statement justifying the sanction, as well as such other information as the Board deems relevant. 
                    </P>
                    <FTNT>
                        <P>
                            <SU>8</SU>
                             Comment is requested as to whether the thirty-day period is appropriate in this context, or whether a longer or shorter period would be preferable.
                        </P>
                    </FTNT>
                    <P>
                        Proposed Rule 440(a) would permit any person aggrieved by a final disciplinary sanction (including disapproval of a completed application for registration of a public accounting firm) imposed by the Board to file an application for review with the Commission. Proposed Rule 440(b) would require that any application be filed within 30 days after the Board's notice under proposed Rule 19d-4 is received by the aggrieved person.
                        <SU>9</SU>
                        <FTREF/>
                         The application would identify the determination complained of and would contain a brief statement of the alleged errors in the determination. The application would be accompanied by a notice of appearance by counsel, if any, filed in accordance with Rule 102(d). Under proposed Rule 440(d), the Board would have fourteen days after receipt of the application to certify the record to the Commission and serve one copy of the record index on each party. 
                    </P>
                    <FTNT>
                        <P>
                            <SU>9</SU>
                             Comment is requested as to whether the thirty-day period is appropriate in this context, or whether a longer or shorter period would be preferable.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">3. Stay of Board Action </HD>
                    <P>
                        In accordance with section 105(e)(1) of the Sarbanes-Oxley Act, 
                        <SU>10</SU>
                        <FTREF/>
                         proposed Rule 440(c) would provide that filing of an application for review acts as a stay of the Board's action unless the Commission otherwise orders. Proposed Rule 401(e)(1) would permit any person aggrieved by the automatic stay to ask the Commission to lift the stay. The Commission may, in any event, lift the stay on its own motion. The Commission requests comment as to whether other persons should be permitted to request that the stay be lifted. 
                    </P>
                    <FTNT>
                        <P>
                            <SU>10</SU>
                             15 U.S.C. 7215(c)(1).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">4. Summary Action; Expedition </HD>
                    <P>
                        As permitted under section 105(e)(1) of the Sarbanes-Oxley Act, proposed Rule 401(e)(2) would provide that the Commission may act summarily, without notice and opportunity for hearing. The Commission may also expedite consideration of a motion to lift a stay of Board action to the extent expedition is consistent with the Commission's other responsibilities. If the consideration of a motion to lift is expedited, proposed Rule 401(e)(3) would provide that persons opposing the lifting of the stay may file an opposition within two days of service of the motion to lift unless the Commission orders a different period. 
                        <SU>11</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>11</SU>
                             The two-day period is modeled after current Rule 401(d)(3), which permits persons opposing a motion to the Commission for a stay to file a statement in opposition within two days of service of the motion. Comment is requested as to whether this period is appropriate, or whether a longer or shorter period would be preferable.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">5. Review on Motion of the Commission </HD>
                    <P>
                        Proposed Rule 441(a) would permit the Commission to review a Board disciplinary sanction on its own motion. The Commission proposes that it would determine whether to take review of a Board disciplinary sanction within 40 days after the Board files its notice of the action. 
                        <SU>12</SU>
                        <FTREF/>
                         Proposed Rule 441(b) permits the Commission to give notice to the parties that it wishes to raise any material matter, whether or not the parties previously raised that matter. The Commission may provide an opportunity for supplemental briefing if the Commission believes that such briefing would significantly aid its decisional process. 
                    </P>
                    <FTNT>
                        <P>
                            <SU>12</SU>
                             Rule 421(a) permits the Commission to order review of certain determinations by self-regulatory organization within 40 days after notice thereof is filed with the Commission. The Commission requests comment as to whether this period is appropriate, or whether a longer or shorter period would be preferable.
                        </P>
                    </FTNT>
                    <HD SOURCE="HD3">6. Amendments to Existing Rules </HD>
                    <P>The Commission is also proposing amendments to the following Rules of Practice with respect to the review proceedings created by the Sarbanes-Oxley Act: </P>
                    <P>• The definition of “proceeding” in Rule 101(a)(9) (Definitions) would be amended to include review of Board disciplinary sanctions under proposed Rule 440. </P>
                    <P>• The Commission would amend Rule 202(a) (Specification of procedures by parties in certain proceedings) and Rule 210 (Parties, limited participants and amici curiae), which permits intervention and leave to participate on a limited basis, to exclude review of Board disciplinary sanctions under proposed Rule 440. These Rules currently do not apply to Commission enforcement or disciplinary proceedings or review of determinations by self-regulatory organizations. The Commission asks for comment as to whether proposed Rules 440 and 441 would provide sufficient procedures for review of Board disciplinary sanctions, or whether intervention or limited participation would be appropriate in Commission review of Board disciplinary sanctions. </P>
                    <P>• Rule 450(a)(2) (Briefs filed with the Commission) would be amended to provide for briefs to be filed in the Commission's review of final disciplinary sanctions imposed by the Board. Under the proposed Rule, the Commission would issue a briefing schedule order within 21 days (or such longer time as provided by the Commission) following its receipt of the Board's index of the record of the Board's determination. </P>
                    <P>• The Commission would define the contents of the record before it in its review of Board action to include the record certified to the Commission by the Board, any application for review, and any submissions made to the Commission, by adding Rule 460(a)(3) (Record before the Commission). </P>
                    <P>
                        The Commission would also revise its 
                        <E T="03">ex parte</E>
                         rule, 17 CFR 200.111 (Prohibitions; application, definitions), to provide that, in proceedings to review Board action, the prohibitions against 
                        <E T="03">ex parte</E>
                         communications would commence when a copy of the application for review of the Board's action is served on the Secretary to the Commission. 
                    </P>
                    <HD SOURCE="HD2">B. Fair Funds and Disgorgement </HD>
                    <P>
                        Section 308(a) of the Sarbanes-Oxley Act 
                        <SU>13</SU>
                        <FTREF/>
                         provides that, in a Commission administrative proceeding where the Commission or a hearing officer enters an order requiring disgorgement from a respondent for a violation of the securities laws, or the respondent agrees in settlement to payment of such disgorgement, any civil penalty also ordered against that respondent may be added to the disgorgement funds to create a “Fair Fund” to be disbursed by the Commission for the benefit of the victims of such violation. Section 308(b) of the Sarbanes-Oxley Act 
                        <SU>14</SU>
                        <FTREF/>
                         authorizes the Commission to accept gifts or bequests to the United States of real and personal property for deposit in a Fair Fund. 
                    </P>
                    <FTNT>
                        <P>
                            <SU>13</SU>
                             15 U.S.C. 7246(a).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>14</SU>
                             15 U.S.C. 7246(b).
                        </P>
                    </FTNT>
                    <P>
                        Administration of, and distribution to investors under, Fair Funds and disgorgement plans, occurs after the conclusion of the principal action against a respondent. The functions involved are administrative, and are not subject to provisions such as Rule 120 of the Rules of Practice, the 
                        <E T="03">ex parte</E>
                         communication rule in subpart D of the Rules of Practice. Recognizing this, the Commission proposes to remove from subpart D of the Rules of Practice Rules 610 through 620, which relate to the 
                        <PRTPAGE P="68188"/>
                        development, submission, approval, and administration of orders of disgorgement, and to the right to challenge orders of disgorgement, and to include them in a new subpart F. 
                    </P>
                    <P>
                        Proposed Rule 1100 would state that the Commission is authorized to create a Fair Fund in any administrative proceeding in which a final order is entered against a respondent requiring disgorgement and payment of a civil money penalty. The Commission may also create a Fair Fund if it approves a settlement of an administrative proceeding that provides for a respondent's payment of disgorgement and a civil money penalty. The proposed Rule would also explain that the Commission may add to the Fair Fund any property received in accordance with section 308(b) of the Sarbanes-Oxley Act.
                        <SU>15</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>15</SU>
                             Section 308(b) of the Sarbanes-Oxley Act provides that the Commission may accept, hold, and utilize gifts of property for a Fair Fund. Gifts of property received pursuant to this section may be deposited only in a Fair Fund.
                        </P>
                    </FTNT>
                    <P>
                        Certain requirements for Fair Funds would suggest that the Commission's Rules should make some distinctions between Fair Funds and disgorgement funds. For example, Fair Funds must be disbursed to the investors harmed by the securities law violations at issue. The purpose of disgorgement is to require a wrong-doer to pay back the ill-gotten gains that the wrong-doer obtained by virtue of his or her violation. Thus, the Commission can order a wrong-doer to disgorge ill-gotten gains whether or not investors suffered any damages as a result of the violation.
                        <SU>16</SU>
                        <FTREF/>
                         Where there are no identifiable victims of a violation, the Commission proposes to permit that the disgorgement and civil money penalty amounts be paid to the United States Treasury. The Commission asks for comment on this proposal. 
                    </P>
                    <FTNT>
                        <P>
                            <SU>16</SU>
                             
                            <E T="03">See e.g., SEC</E>
                             v. 
                            <E T="03">First City Financial Corp.,</E>
                             890 F. 2d 1215, 1230 (D.C. Cir. 1989) (defendant who violated Exchange Act section 13 required to disgorge although harm was to the market as a whole, not to particular persons).
                        </P>
                    </FTNT>
                    <P>
                        In other respects, the Commission believes that the requirements for Fair Funds and disgorgement funds should be similar. In some cases, the Commission may conclude that it is in the public interest to impose a civil money penalty and order disgorgement even though the relative value of the ill-gotten gains and the number of potential claimants would result in high administrative costs and 
                        <E T="03">de minimis</E>
                         distributions to individual investors. Under such circumstances, the Commission would continue its practice of ordering that the disgorgement and civil penalty amount be paid directly to the United States Treasury. 
                    </P>
                    <P>Current Rule 611(b) provides that the Commission may authorize payment of disgorgement funds to any court registry or court-appointed receiver in any case that alleges the same or similar facts against the respondent. The Commission proposes to continue this authority with respect to disgorgement funds and Fair Funds in proposed Rule 1102(a). </P>
                    <P>The proposed Rules would permit either the Commission or the hearing officer, as appropriate, to oversee the administration of both disgorgement funds and Fair Funds. </P>
                    <P>Proposed Rule 1101(a) would continue the practice under current Rule 610 of allowing the Commission or the hearing officer at any time to order a party to submit a plan for the administration of either a Fair Fund or a disgorgement fund. Unless ordered otherwise, the Division of Enforcement would be required to submit such a plan within 60 days after the respondent has tendered the funds or other assets pursuant to the Commission's order to pay disgorgement and, if applicable, a civil money penalty. </P>
                    <P>Proposed Rule 1101(b) would extend the requirements of current Rule 611(a) to require that both Fair Fund or disgorgement fund plans provide for: receiving and holding additional funds, including funds received under section 308(b) of the Sarbanes-Oxley Act; identifying categories of persons who are potentially eligible to receive funds; providing notice to potentially eligible persons of the fund's existence and their potential eligibility; handling claims; termination of the fund and disposition of any remaining assets; administration of the fund; and such other provisions as the Commission or hearing officer deem appropriate. </P>
                    <P>As discussed above, proposed Rule 1102(b) would continue to permit the Commission or the hearing officer to order that funds be paid directly to the United States Treasury if the cost of administering the fund and the relative value of the disgorgement fund, together with any civil money penalty, and the number of potential claimants would not justify distribution of the funds. </P>
                    <P>
                        Proposed Rule 1103 would amend and renumber current Rule 612 to require that notice of either a proposed disgorgement plan or a proposed Fair Fund plan be published in the 
                        <E T="03">SEC News Digest</E>
                        , the 
                        <E T="03">SEC Docket</E>
                        , and such other publications as the Commission or the hearing officer directs. The notice would specify how to obtain copies of the proposed plan and inform those desiring to comment to submit their written views to the Commission. The Commission also proposes posting notice of a proposed plan on its website. The Commission seeks comment as to how website posting can be done most effectively. 
                    </P>
                    <P>Proposed Rule 1104 would replace and renumber current Rule 613 to provide that, at any time after 30 days following publication of the notice of a proposed disgorgement plan or a proposed Fair Fund plan, the Commission or the hearing officer may approve, modify, or disapprove the proposed plan. The Commission or the hearing officer may order publication of a substantially modified plan prior to adoption. </P>
                    <P>Proposed Rule 1105 would replace and amend current Rule 614 to provide for administration of Fair Funds, as well as disgorgement funds. The proposed Rule would continue to permit the Commission or hearing officer to appoint any person, including a Commission employee, as fund administrator. Either the Commission or the hearing officer would be able to remove an administrator. </P>
                    <P>An administrator who is not a Commission employee must post a bond in an amount approved by the Commission. An administrator who is not a Commission employee may receive a fee for reasonable services, subject to approval by the Commission or the hearing officer. Commission employees may not receive such fees. Fees and expenses from fund administration would be paid first from interest and then, if the interest were insufficient, from corpus. The administrator would give periodic accountings, as ordered, and submit a final accounting prior to his or her discharge and cancellation of any bond. </P>
                    <P>Current Rule 614(a) would be renumbered Rule 1105(b). The Rule currently provides that a respondent may be required or permitted to administer a plan of disgorgement, subject to terms the Commission or the hearing officer deems appropriate. At this time, the Commission does not propose to extend this provision to Fair Funds although it invites comment on this issue. A Fair Fund would include a civil penalty and might include funds conveyed to the United States pursuant to section 308(b) of the Sarbanes-Oxley Act. </P>
                    <P>
                        Proposed Rule 1106 would renumber Rule 620 to make clear that no person would be granted the right to intervene or appear in a proceeding to challenge an order of disgorgement, an order creating a Fair Fund, an order approving, modifying, or disapproving a disgorgement plan or a Fair Fund plan, 
                        <PRTPAGE P="68189"/>
                        or any determination relating to a plan based solely upon the person's eligibility or potential eligibility to participate in a fund or based on a private right of action. Under the proposed Rule, as is the case under the existing disgorgement Rule, such person's participation would be limited to submitting comments in accordance with proposed Rule 1103. 
                    </P>
                    <HD SOURCE="HD2">C. Other Proposed Amendments </HD>
                    <P>In 1995, the Commission substantially amended its Rules of Practice. After several years of experience with these Rules, the Commission believes that certain changes to the Rules would make practice under those Rules easier and more efficient. The Commission invites comments with respect to these proposed modifications. </P>
                    <P>1. The existing Rules do not make explicit the Commission's authority to order a variation from the rules governing proceedings before it. The Commission is proposing to include in Rule 100 a new paragraph (c) that would specify that the Commission may by order direct, in a particular proceeding, that an alternative procedure shall apply or that compliance with an otherwise applicable rule is unnecessary, upon its determination that to do so would serve the interests of justice and not result in prejudice to any party to the proceeding. </P>
                    <P>
                        2. Under section 11A of the Exchange Act and the rules thereunder, the Commission is authorized to adjudicate certain disputes involving registered securities information processors, national market system plans, or transaction reporting plans.
                        <SU>17</SU>
                        <FTREF/>
                         In addition to the inclusion of review of Board disciplinary sanctions discussed above, the Commission proposes to amend Rule 101(a)(9) to expand the definition of “proceedings” to make clear that the Rules of Practice are applicable to such adjudications.
                        <SU>18</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>17</SU>
                             
                            <E T="03">See</E>
                             Exchange Act section 11A(b)(5) (requiring Commission to review prohibitions or limitations of access to services offered by registered securities information processors); Exchange Act Rule 11Aa3-2(e) (giving Commission discretion to entertain appeals from actions under national market system plans); Exchange Act Rule 11Aa3-1(f) (giving Commission discretion to entertain appeals in connection with implementation or operation of transaction reporting plans).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>18</SU>
                             Because the current Rules of Practice do not specify a particular procedure for proceedings under Exchange Act section 11A, the Commission has been required to specify by order the procedural rules that are to be employed in section 11A review proceedings. 
                            <E T="03">See, e.g., The Cincinnati Stock Exchange,</E>
                             Exchange Act Rel. No. 43316 (Sept. 21, 2000), 73 SEC Docket 1006 (Order Accepting Jurisdiction, Establishing Procedures, and Ordering Briefs).
                        </P>
                        <P>Proposed Rule 101(a)(12) would also define the term “Board” to refer to the Public Company Accounting Oversight Board. </P>
                    </FTNT>
                    <P>3. The Commission currently requires counsel to file a motion to withdraw as counsel. Many agencies instead permit counsel to file a notice of withdrawal, which does not require agency action but informs the agency and parties of counsel's withdrawal. The Commission believes that a notice would preserve the intended benefits of the existing requirement by providing timely notice to both the Commission and the parties of the withdrawal. It would also eliminate the need for the Commission or the hearing officer to rule on a motion for withdrawal. </P>
                    <P>The proposed amendment of Rule 102(d)(4) would require any person seeking to withdraw his or her appearance in a representative capacity to file a notice of withdrawal with the Commission or the hearing officer, stating the name, address, and telephone number of the withdrawing representative; the name, address, and telephone number of the person for whom the appearance was made; and the effective date of the withdrawal. If the person seeking to withdraw knows the name, address, and telephone number of the new representative, or knows that the person for whom the appearance was made intends to represent him- or herself, that information would also have to be included in the notice. The amended Rule would require that notice be served on the parties in accordance with Rule 150, and that the notice be filed at least five days before the proposed effective date of the withdrawal. </P>
                    <P>4. The Commission is considering a proposed amendment that would specifically recognize the authority of hearing officers to correct manifest errors of fact in initial decisions. The Commission has found that some appeals to it could be streamlined if certain issues were addressed first to the hearing officer. The proposed amendment would add to the enumeration of powers of hearing officers in Rule 111 the authority to consider and rule upon a motion to correct a manifest error of fact, provided that such a motion is filed within ten days of the initial decision. </P>
                    <P>5. Currently, Rule 141(a)(3) requires the Secretary to “place in the record of the proceeding a certificate of service” of orders instituting proceedings. The proposed amendment of the Rule would delete this requirement, substituting a requirement that the Secretary “maintain a record of service on parties.” The amendment would allow the Secretary to maintain computerized rather than hard copy records of service. </P>
                    <P>6. Current Rule 141(a)(3) also requires that, if service is effected by mail, the certificate “shall be accompanied by a confirmation of receipt or of attempted delivery,” which is also to be maintained in the record of the proceeding. The proposed amendment of Rule 141(a)(3) would delete the requirement that such documents be retained in the record of the proceeding, allowing the Secretary to retain all the confirmation or records of attempted delivery in a single file. The Commission believes that this form of recordkeeping will permit easier retrieval of these documents. </P>
                    <P>7. Current Rule 141(b) provides for the service of written orders or decisions by the Commission or a hearing officer, other than an order instituting proceedings, to be served by any method of service authorized under Rule 141(a) or Rule 150(c). The proposed amendment of Rule 150(c) discussed below would, among other things, eliminate the requirement that parties seeking to serve each other by facsimile transmission agree to do so in writing. The Commission proposes to retain the requirement of a written agreement as a precondition to service of orders and decisions by facsimile. The proposed amendment of Rule 141(b) would replace the reference to Rule 150(c) with a reference to Rules 150(c)(1)-(3). </P>
                    <P>8. Consistent with Rule 5(b)(2)(D) of the Federal Rules of Civil Procedure, existing Rule 150(c)(4), which governs service of documents on parties by facsimile transmission, requires parties who choose to serve each other by facsimile to agree to do so in a signed writing. The existing Rule also requires that receipt of each document served by facsimile be confirmed by a manually signed receipt. The proposed amendment would delete both of these requirements. It would, however, allow a party to decline to receive service by facsimile. Such a declination would have to be made in writing and served in accordance with Rule 150. The proposed Rule would also require that facsimile transmissions be made at a time that results in their receipt during the Commission's business hours as defined in Rule 104. </P>
                    <P>
                        The Commission's experience shows that in many instances parties are serving one another by facsimile but are not entering into the agreements or confirming by manually signed receipt. Under the new Rule, parties who choose service by facsimile would be required to provide the Commission and the parties with notice of the facsimile machine telephone number to be used and the hours of facsimile machine operation. 
                        <PRTPAGE P="68190"/>
                    </P>
                    <P>
                        The Commission solicits views about what might constitute sufficient evidence of completion of facsimile service. 
                        <E T="03">See</E>
                         current Rule 150(d). The Commission also seeks comment as to whether parties making service by facsimile, or the Commission serving orders and decisions by facsimile, should be required to transmit a non-facsimile original contemporaneously with service by facsimile. The current Rule allows parties to specify in the written agreement providing for service by facsimile whether a non-facsimile document is to be provided. 
                    </P>
                    <P>9. Rule 151 currently does not permit filing of documents with the Commission by facsimile transmission. The proposed amendment would allow such filing. The proposed amendment makes clear, however, that one who seeks to file by facsimile assumes the risk that the transmission will not be completed in a timely or legible fashion. As proposed, Rule 151 would require that parties filing by facsimile should be required to transmit a non-facsimile original contemporaneously. At present, the Commission receives a hard copy of filings to satisfy Rule 153(a), which requires that filings be signed by at least one counsel of record, or if a party is acting as his or her own counsel, by the party. The Commission requests comments as to how the signature requirement should be implemented if filings are by facsimile and if no hard copy original is required to be filed. </P>
                    <P>In addition, the Commission requests comments as to whether filing by e-mail should be permitted. If such filing is permitted, the Commission requests comments as to whether the requirements applicable to filing by facsimile transmission would also be appropriate in that context. </P>
                    <P>Current Rule 151 requires that papers required to be served on a party shall be filed with the Commission “at the time of service or promptly thereafter.” To conform with other Rules, the proposed amendment would require filing with the Commission “contemporaneously” with service on a party. </P>
                    <P>10. Rule 152(a)(2) currently allows the use of either 10-point or 12-point type in papers filed in Commission proceedings. To enhance the legibility of filings, the proposed amendment would require the use of 12-point or larger type. </P>
                    <P>11. Current Rule 154 limits a brief in support of or in opposition to a motion to 10 pages, exclusive of pages containing any table of contents, table of authorities, and/or addendum. The Commission has received filings by parties who attempt to circumvent this page limitation by filing 10-page briefs and extremely lengthy motions. The proposed amendment seeks to establish a combined page limit of 15 pages for the motion and brief.</P>
                    <P>12. Current Rule 151 provides that persons must file papers with the Commission within the time limit for filing. Rule 160 gives an additional three days for service by mail. Questions have been raised about whether a person receives three additional days to respond if service is made by mail when the Commission's or hearing officer's order specifies a date certain for filing a response. The proposed amendment to Rule 160 would make clear that the person does not receive additional time. If a party requires a short extension, the Commission believes that the party could request that extension under Rule 161. </P>
                    <P>13. Rule 201 currently provides for the consolidation of proceedings. The proposed amendment would permit the Commission also to order any proceeding severed with respect to some or all of the parties. The proposed amendment would provide that motions to sever must be addressed to the Commission and represent that a settlement offer has been submitted to the Secretary for Commission consideration, or otherwise show good cause. The Commission asks for comment as to whether the law judges should have the power to sever parties from a proceeding. </P>
                    <P>14. Current Rule 230(a)(1)(vi) requires the Division of Enforcement to make available for inspection and copying by any party any final examination or inspection reports prepared by the Office of Compliance Inspections and Examinations, the Division of Market Regulation, or the Division of Investment Management that have been obtained by the Division of Enforcement prior to the institution of the proceedings, in connection with the investigation leading to the Division of Enforcement's recommendation to institute proceedings. The proposed amendment would state that such reports must be produced only if the Division intends either to introduce them into evidence, or to use them to refresh the recollection of any witness. </P>
                    <P>Examined parties receive notice of examination findings in the examination process, and do not require notice through the Rules of Practice. Therefore, in order to protect the confidentiality of examination reports, the proposed amendment would limit production of examination and inspection reports to circumstances where the Division intends to introduce the report into evidence, either in reliance on the report to prove its case, or to refresh the recollection of any witness. </P>
                    <P>
                        The proposed amendment would not alter the requirement that the Division produce documents that contain material exculpatory evidence as required by 
                        <E T="03">Brady</E>
                         v. 
                        <E T="03">Maryland</E>
                        .
                        <SU>19</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>19</SU>
                             373 U.S. 83, 87 (1963).
                        </P>
                    </FTNT>
                    <P>Current Rule 230(c) permits the hearing officer to require the Division of Enforcement to submit for review a list of withheld documents. The proposed amendment would provide that when similar documents are withheld, those documents may be identified by category instead of individual document. Under the proposed amendment, the hearing officer would retain discretion to determine when an identification by category is insufficient. The proposed amendment would also correct typographical errors in the cross-reference to paragraphs pursuant to which documents may be withheld. </P>
                    <P>
                        15. Current Rule 231(a), relating to production of witness statements, refers to “any statement * * * that would be required to be produced by the Jencks Act, 18 U.S.C. 3500.” There has been some question as to what constitutes a “statement” under this provision. The proposed change would make clear that the Commission will rely on the definition of “statement” contained in the Jencks Act 
                        <SU>20</SU>
                        <FTREF/>
                         in applying this Rule. 
                    </P>
                    <FTNT>
                        <P>
                            <SU>20</SU>
                             18 U.S.C. 3500(e).
                        </P>
                    </FTNT>
                    <P>16. Current Rule 232(e)(1) allows only the person to whom a subpoena is directed or a person who is an owner, creator, or the subject of the documents to be produced pursuant to a subpoena, to oppose the subpoena. The proposed amendment would add that any party may also oppose a subpoena. </P>
                    <P>Subpoenas directed at third party witnesses can be overly broad. Some recipients of such subpoenas may lack the sophistication or resources to dispute the scope of the subpoenas, and it would be unfair to require them to make filings in opposition. The proposed amendment would allow the Division of Enforcement, or any other party, to present arguments about whether subpoenas to any witnesses are unreasonable, oppressive, or unduly burdensome. </P>
                    <P>
                        17. Current Rule 235(a) provides that a hearing officer may grant a motion to introduce a prior sworn statement of a witness who is out of the United States, unless it appears that the absence of the witness was procured by the party offering the prior sworn statement. Current Rule 233, however, which sets forth the basis for ordering a deposition, does not permit the taking of a deposition when it is anticipated that a 
                        <PRTPAGE P="68191"/>
                        witness will be absent from the United States. Since depositions can be used only to preserve testimony of a witness who is unlikely to attend the hearing, the proposed revision of Rule 233 would allow the taking of a deposition of a witness currently within the United States who is expected to be outside the United States so long as the deposition will serve the interests of justice and it appears that the party requesting the deposition did not procure the witness's absence. 
                    </P>
                    <P>18. Rule 350(b) currently requires the Secretary to retain documents that are marked for identification but not offered into evidence. There does not seem to be any reason to keep documents that the party did not seek to introduce, and the proposed amendment would delete that requirement. The Secretary would continue to retain documents offered into evidence but excluded from the record so that, in the event of an objection, the Commission could consider any arguments that the documents should be admitted. </P>
                    <P>19. Proposed Rule 351(a) deletes a reference to a practice abandoned several years ago whereby the interested division took custody of the exhibits after a hearing and was responsible for having them sent to the Secretary. Currently the court reporter takes custody of exhibits. </P>
                    <P>20. Current Rule 360(d)(1) provides that an initial decision of a hearing officer becomes the final decision of the Commission unless a party or aggrieved person entitled to review files a petition for review, or the Commission orders review on its own initiative. Current Rule 360(e) further provides that, if an initial decision becomes the final decision of the Commission as to a party, the Commission shall issue an order that the decision has become final as to that party. The interplay of these Rules appears to have engendered confusion as to when a decision is final and enforceable. The proposed amendments would renumber paragraph 360(d)(2) as (d)(1) and combine paragraphs (d)(1) and (e) as (d)(2), clarifying that a decision becomes final upon the issuance of a finality order by the Commission. </P>
                    <P>21. Current Rule 400 provides for the Commission to grant interlocutory review only in “extraordinary circumstances.” The proposed amendment would instruct the parties that petitions for interlocutory review are “disfavored,” making clear that such petitions rarely would be granted. The proposed amendment would recognize, however, that the Commission retains discretion to undertake such review on its own motion at any time. </P>
                    <P>22. A proposed amendment to Rules 400 and 430 would provide that certain matters are subject to interlocutory review under Rule 400, not Rule 430. Rule 430 permits review of matters delegated to the staff. Under 17 CFR 200.30-9 and 30-10, certain functions are delegated to the administrative law judges and the chief administrative law judge. As the Rules are currently drafted, such determinations arguably might be reviewable under Rule 430 although the determination would not merit interlocutory review under Rule 400. The amendment would make clear that Rule 400 is the sole route for interlocutory review of determinations by a hearing officer. </P>
                    <P>23. Current Rule 401(d)(1) provides that any person aggrieved by an action by a self-regulatory organization for which the Commission is the appropriate review agency, for which action review may be sought pursuant to Rule 420, may seek a stay of that action. The proposed amendment would clarify that a stay can be sought only at the time an application for review is filed or thereafter. Filing an application for review brings the action before the Commission. Since the proposed amendment of Rule 420(c) reduces the content requirements for an application for review, the requirement that an application be filed when or before a stay is sought would not impose a significant delay. </P>
                    <P>24. The Commission requests comment on the proposed amendment of Rule 410(b), which would permit an opposing party to file a cross-petition for review within ten days from the filing of a petition for review, making it unnecessary for parties to file protective defensive petitions for review. </P>
                    <P>Another proposed amendment would delete Rule 410(d), thus abolishing the opposition to the petition for review. The Commission requests comment on the proposal to abolish the petition for review. In the Commission's experience, the utility of such oppositions has been quite limited, given that the Commission has long had a policy of granting petitions for review, believing that there is a benefit to Commission review when a party takes exception to a decision. Moreover, the Commission believes that a motion for summary affirmance would permit the Commission to dispose of matters suited to more abbreviated review. </P>
                    <P>25. The proposed amendment of Rule 411(e) would provide a 21-day time limit for filing a motion for summary affirmance. The proposed amendment would also set forth standards both for granting and for denying summary affirmance. Summary affirmance would be granted if the Commission finds that no issue raised in the initial decision warrants consideration by the Commission of further oral or written argument. Summary affirmance would be denied upon a reasonable showing that a prejudicial error was committed in the conduct of the proceeding or that the decision embodies an exercise of discretion or decision of law or policy that is important and that the Commission should review. </P>
                    <P>
                        26. Section 19(d) of the Exchange Act requires a person who appeals from self-regulatory organization disciplinary action to do so within 30 days “or within such longer period as” the Commission “may determine.” The proposed amendment to Rule 420(b) would make clear that an appeal from self-regulatory organization action must be filed within 30 days, absent a showing of extraordinary circumstances, and will not be extended by the Commission under Rule 161. This standard is consistent with prior Commission precedent.
                        <SU>21</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>21</SU>
                             
                            <E T="03">See, e.g., Lance E. Van Alstyne,</E>
                             53 S.E.C. 1093, 1099 (1998) (Commission will not authorize late filing of appeals by self-regulatory organizations absent extraordinary circumstances).
                        </P>
                    </FTNT>
                    <P>Current Rule 420 contains language that might suggest that the applicant's address be used to serve only the record index. The proposed amendment would provide that the applicant identify where he or she may be served for all purposes. </P>
                    <P>27. Rule 450(c), which sets limits on the page length of briefs, would be amended to limit instead the number of words in briefs. The proposed word limits—14,000 for principal briefs and 7,000 for any reply brief—are based on Rule 32 of the Federal Rules of Appellate Procedure. The proposed amendment would also state that motions to file oversized briefs are disfavored. In exceptional cases, however, where more pages may be needed to address the issues—for example, where the Division of Enforcement must address arguments by multiple respondents—the Commission may, upon motion, allow longer filings. </P>
                    <P>
                        Except when a principal brief does not exceed 30 pages in length, or a reply brief does not exceed 15 pages in length, the proposed amendment would require the attorney filing the brief (or an unrepresented party) to certify that the brief complies with the length limitation and to state the number of words in the brief. The proposed amendment would permit the party certifying the length of the brief to rely on the word count of the word processing system used to prepare the brief. 
                        <PRTPAGE P="68192"/>
                    </P>
                    <P>The Commission has received briefs which sought to incorporate by reference briefs filed before the hearing officer in the proceeding on appeal. Such incorporation by reference, if allowed, would erode the page-limit requirements of Rule 450(c). The proposed amendment provides that pleadings incorporated by reference will be included in determining the word count of briefs. The amendment is intended to promote adherence to the length limitations of Rule 450(c) and to encourage parties to exercise judgment in selecting the arguments that best advance their positions rather than simply repeating previously formulated contentions. </P>
                    <P>
                        28. The current Rules make no provision for the use of visual aids at oral argument. The proposed amendment of Rule 451(b) would prohibit the use of visual aids unless copies are provided to the Commission and all parties at least five business days before the argument is to be held.
                        <SU>22</SU>
                        <FTREF/>
                         The Commission requests comment as to whether five business days provides sufficient time for the parties to prepare adequate responses to proposed visual aids. 
                    </P>
                    <FTNT>
                        <P>
                            <SU>22</SU>
                             A further proposed amendment would conform the language of Rule 451(b) to reflect Commission practice not to issue the order setting oral argument in a Commission administrative proceeding until the date for argument is set.
                        </P>
                    </FTNT>
                    <P>29. Current Rule 360(a)(2) directs the hearing officer to issue an initial decision within the time period specified in the order instituting proceedings. To address the hearing officer's inability to comply with this directive where a proceeding is stayed by order of the hearing officer or the Commission under Rule 210(c)(3) because a criminal investigation or prosecution is pending, the proposed amendment of Rule 360(a)(2) would specify that, if a proceeding is stayed under the authority of Rule 210(c)(3), the specified time period for issuance of the initial decision, as well as any other time limits established in orders issued by the hearing officer under Rule 360(a)(2), will be automatically tolled during the period in which the stay is in effect. </P>
                    <P>30. Rule 360(d)(2) provides that the initial decision shall not become final as to a party or person if a timely petition for review is filed by that party or person. The proposed amendment would add the timely filing, by a party or an aggrieved person entitled to review, of a motion to correct an initial decision to the hearing officer as an event that prevents the initial decision from becoming the final decision of the Commission as to that party or person until the hearing officer has decided the motion. The proposed amendment would also make conforming changes to Rule 360(b), which specifies that an initial decision shall include a statement reflecting the provisions of Rule 360(d). </P>
                    <P>A proposed amendment of Rule 410(b) would provide that the time to file a petition for review is stayed until 21 days after resolution of any motion to correct an initial decision filed before the hearing officer so that, while a motion to correct is pending, a party need not file a petition for review to preserve its appeal rights. </P>
                    <P>Current Rule 470 specifies a 15-page limit for a motion for reconsideration, rather than the ten pages permitted for other motions. There does not seem to be any reason for treating motions for reconsideration differently from other motions. The amendment proposes to limit the party seeking reconsideration to the same number of pages and the same format used for other motions under the Rules of Practice. The Commission requests comment as to whether motions for reconsideration should be subject to different requirements from other motions, and if so, what differences would be appropriate. </P>
                    <P>31. The proposed amendment of Rule 601 would codify existing practice for payment of disgorgement, interest, and penalties. The proposal standardizes the language currently used by hearing officers in initial decisions and the Commission in its orders, as follows: </P>
                    <EXTRACT>
                        <P>
                            (c) 
                            <E T="03">Method of making payment.</E>
                             Payment shall be made by United States postal money order, wire transfer, certified check, bank cashier's check, or bank money order made payable to the Securities and Exchange Commission. The payment shall be mailed or delivered to the Office of Financial Management of the Commission. Payment shall be accompanied by a letter that identifies the name and number of the case and the name of the respondent making payment. A copy of the letter and the instrument of payment shall be sent to counsel for the Division of Enforcement. 
                        </P>
                    </EXTRACT>
                    <HD SOURCE="HD1">II. Request for Public Comments </HD>
                    <P>We request and encourage any interested person to submit comments regarding: (1) The proposed changes that are the subject of this release, (2) additional or different changes, or (3) other matters that may have an effect on the proposals contained in this release. </P>
                    <HD SOURCE="HD1">III. Administrative Procedure Act, Regulatory Flexibility Act, and Paperwork Reduction Act </HD>
                    <P>
                        The Commission finds, in accordance with section 533(b)(3)(A) of the Administrative Procedure Act, 
                        <SU>23</SU>
                        <FTREF/>
                         that this revision relates solely to agency organization, procedure, or practice. It is therefore not subject to the provisions of the Administrative Procedure Act requiring notice, opportunity for public comment, and publication. The Regulatory Flexibility Act 
                        <SU>24</SU>
                        <FTREF/>
                         therefore does not apply. Similarly, because these rules relate to “agency organization, procedure or practice that does not substantially affect the rights or obligations of non-agency parties,” the Commission is not soliciting comment for purposes of the Small Business Regulatory Enforcement Fairness Act. 
                        <SU>25</SU>
                        <FTREF/>
                         Nonetheless, the Commission has determined that it would be useful to publish these proposed rules for notice and comment, before adoption. 
                        <SU>26</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>23</SU>
                             5 U.S.C. 553(b)(3)(A).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>24</SU>
                             5 U.S.C. 601 
                            <E T="03">et seq.</E>
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>25</SU>
                             5 U.S.C. 804(3)(C).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>26</SU>
                             
                            <E T="03">See</E>
                             5 U.S.C. 603.
                        </P>
                    </FTNT>
                    <P>
                        These rules do not contain any collection of information requirements as defined by the Paperwork Reduction Act of 1995, as amended. 
                        <SU>27</SU>
                        <FTREF/>
                    </P>
                    <FTNT>
                        <P>
                            <SU>27</SU>
                             44 U.S.C. 3501 
                            <E T="03">et seq.</E>
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">IV. Costs and Benefits of the Proposed Rules and Amendments </HD>
                    <P>The Sarbanes-Oxley Act of 2002 authorizes the Commission to review disciplinary actions by the Public Company Accounting Oversight Board as well as actions resulting in disapproval of registration of public accounting firms. In response, the Commission proposes to revise certain of its rules in order to enhance the transparency and facilitate parties' understanding of the applicability of the review process to Board proceedings. The Sarbanes-Oxley Act also provides that where the Commission or a hearing officer in a Commission administrative proceeding enters an order requiring disgorgement and a civil money penalty, the Commission may create a “Fair Fund” combining the disgorgement and the civil money penalty to be disbursed for the benefit of the victims of the securities law violations at issue in the proceeding. In response, the Commission proposes regulatory provisions for the submission and administration of Fair Fund plans and disgorgement plans. The Commission also proposes to take this opportunity to amend other provisions of the rules. </P>
                    <P>
                        Taken as a whole, the Commission's Rules of Practice (“Rules”) create governmental review and remedial processes. That is, they are procedural and administrative in nature. The benefits to the parties are the familiar benefits of due process: notice, 
                        <PRTPAGE P="68193"/>
                        opportunity to be heard, efficiency and fairness. The cost of these processes, on the other hand, falls largely on the oversight bodies. 
                    </P>
                    <P>For purposes of cost/benefit analysis, the processes created by the regulatory provisions proposed in this release, given their procedural nature, might best be viewed as a whole. Nonetheless, to the extent possible, specific benefits and costs that can be more narrowly associated with separate provisions are identified below. However, because there are so many provisions, and because the costs tend to be primarily governmental, we do not provide separate sections for our respective cost and benefit analyses. Rather, we simply identify each provision proposed and discuss any benefits and costs that may be associated with it beyond the more general points summarized above. </P>
                    <P>Proposed Rule 19d-4(b) requires the Board to file with the Commission and serve on the public accounting firm a notice of disapproval of registration within 30 days of the Board's action. Proposed Rule 19d-4(c) imposes on the Board a similar filing and service requirement for notices of any disciplinary sanction other than a disapproval of registration. Timely notice is a fundamental aspect of due process. It benefits those who receive notice by allowing them to plan and take action in light of the Board's findings. Timely filing with the Commission lets the Commission know of the conclusion of Board proceedings so that it can exert oversight over the quality and fairness of those proceedings, which benefits parties to the proceedings as well as the general public. These rules would impose a small administrative cost on the Board. </P>
                    <P>Proposed Rules 440 and 441 provide for Commission review of Board actions. Proposed Rule 440 allows review upon application of a person aggrieved by a final Board disciplinary sanction, including disapproval of a completed application for registration of a public accounting firm, and proposed Rule 441 permits Commission review of Board disciplinary sanctions upon the Commission's own motion. The Rules pertain to the review mechanism required by the Sarbanes-Oxley Act, informing those upon whom Board sanctions are imposed of the option of Commission review and instructing them about procedures involved in initiating the review process. </P>
                    <P>Commission review of Board findings benefits parties to Board proceedings (and, to a lesser extent, the general public) by protecting against arbitrary, capricious, or otherwise unlawful treatment. Review also allows the Commission to exercise a check on, and protect the public interest in, the quality and consistency of Board findings. </P>
                    <P>Parties involved in review proceedings will incur legal and other costs. Review upon application by a person aggrieved, under proposed Rule 440, is optional. Thus, a party would only incur these costs if it expected a net benefit from the review process. In the case of review upon the Commission's own motion under proposed Rule 441, however, the parties involved might otherwise have chosen to avoid incurring the costs. </P>
                    <P>In accordance with section 105(e)(1) of the Sarbanes-Oxley Act, proposed Rule 440(c) provides that filing an application for review with the Commission acts as a stay of the Board's action unless the Commission orders otherwise. Proposed Rule 401(e) allows (1) persons aggrieved by such an automatic stay to ask the Commission to lift the stay; (2) the Commission to lift such a stay summarily, without notice and opportunity for a hearing; and (3) persons opposing the lifting of such a stay to file an opposition. </P>
                    <P>Rule 440(c) benefits the party upon whom Board sanctions have been imposed by allowing that party an opportunity to be heard in the review process before the Board's sanctions take effect. The automatic stay imposes a cost upon third parties who would benefit if the sanctions went into place immediately. </P>
                    <P>Allowing a person aggrieved by the automatic stay to ask to have the stay lifted benefits the aggrieved person by offering the option of a possible earlier termination of the stay. Those availing themselves of this option will incur legal and other costs, though since the procedure is optional, they will presumably do so only if they conclude that doing so yields an expected net benefit. Similarly, allowing opposition to a motion to lift allows those opposing the motion an opportunity to be heard. Although opposing a motion could involve legal and other expenses, since opposition is optional, parties would only incur those costs if they expected a net benefit from opposing. </P>
                    <P>Allowing the Commission to lift a stay summarily could benefit persons aggrieved by the stay by providing prompt and inexpensive relief. At the same time, those who might oppose the lifting of the stay would be denied notice and an opportunity to be heard in connection with the lifting of the stay. </P>
                    <P>Section 308(a) of the Sarbanes-Oxley Act provides that, in a Commission administrative proceeding where the Commission or a hearing officer enters an order requiring disgorgement and a civil money penalty, the Commission may create a “Fair Fund” by including the civil penalty with the disgorgement amount. The Commission is required to disburse money from a Fair Fund for the benefit of the victims of the securities law violations at issue in the proceeding. </P>
                    <P>
                        Proposed Rule 1101 would authorize the Commission to create a Fair Fund in any administrative proceeding in which a final order is entered imposing disgorgement and a civil money penalty, and would permit the Commission to add to the Fair Fund any property received in accordance with section 308(b) of the Sarbanes-Oxley Act. The Commission would also be allowed to create a Fair Fund if it approves a settlement of an administrative proceeding that provides for payment of disgorgement and a civil money penalty. Where the relative value of the ill-gotten gains and the number of potential claimants would result in high administrative costs and 
                        <E T="03">de minimis</E>
                         distributions to investors, the proposed rules would allow the Commission not to create a Fair Fund, and the disgorgement and civil penalty amounts would be paid directly to the United States Treasury. 
                    </P>
                    <P>
                        Creating and administering Fair Funds benefits victims of securities law violations, who would be more likely to be made whole. Allowing monies that would otherwise go into a Fair Fund to be paid to the Treasury where investors would receive only 
                        <E T="03">de minimis</E>
                         distributions would prevent those monies from being consumed by administrative costs, though at a cost to victims who might otherwise have received a minimal payment from a Fair Fund. 
                    </P>
                    <P>The proposed amendment of Rule 102(d)(4) would allow a person seeking to withdraw his or her appearance before the Commission in a representative capacity to file a notice of withdrawal rather than the motion to withdraw that is currently required. Filing a notice would preserve the benefits of the existing requirement by giving the Commission and the parties timely notice of withdrawal. Preparing and filing a notice may be less expensive than preparing and filing a motion. Additionally, the proposed amendment would increase efficiency by eliminating the need for the Commission or a hearing officer to rule on a motion for withdrawal. </P>
                    <P>
                        The proposed amendment of Rule 150(c)(4) would eliminate the requirements that parties who choose to serve each other by facsimile transmission (1) agree to do so in a 
                        <PRTPAGE P="68194"/>
                        signed writing, and (2) confirm receipt of each document by a manually signed receipt. Eliminating these requirements would result in lower costs to the serving parties. However, eliminating the requirement of a signed receipt could make it more difficult to prove that a transmission was received. 
                    </P>
                    <P>The proposed amendment of Rule 151 would allow parties to file documents with the Commission by facsimile transmission. This amendment provides parties an additional option for transmitting documents to the Commission. Facsimile filing would allow the Commission to receive, and be able to address, documents in as timely a fashion as possible. Costs of transmission by facsimile are likely to be lower than overnight or courier fees. The proposal would not impose any new costs, since the existing methods for filing with the Commission remain available. </P>
                    <P>The proposed amendment to Rule 154 establishes a combined page limit of 15 pages for a motion and a brief in support of the motion. The 15-page limit would also apply to a brief in opposition to a motion and to any reply brief. The proposed amendment to Rule 450(c) provides that pleadings incorporated by reference will be included in determining the page count of briefs. </P>
                    <P>Reducing page limits may result in lower legal costs to the parties. Limiting the number of pages submitted also keeps proceedings efficient. </P>
                    <P>The proposed amendment of Rule 233 would allow the taking of a deposition of a witness then within the United States, who is expected to be outside the United States at the time of an administrative hearing, so long as the deposition will serve the interests of justice and it appears that the party requesting the deposition did not procure the witness's absence. The proposal serves the interests of justice by making available a statement that otherwise might not have been made part of the record. If use of such a deposition results in the absence from a hearing of a witness who otherwise would have appeared, there would be a loss in that the hearing officer would have no opportunity to assess demeanor. However, since the Rule allows a deposition only where it appears that the party requesting the deposition did not procure the witness's absence, such a series of events should rarely occur. </P>
                    <P>The remaining proposals variously clarify existing practice, relate to internal agency management, increase the efficiency of proceedings, or promote due process. </P>
                    <P>The Commission requests data to quantify the costs and the value of the benefits identified. The Commission also seeks estimates and views regarding these costs and benefits for particular types of market participants, as well as any other costs or benefits that may result from the adoption of the proposed rules. </P>
                    <HD SOURCE="HD1">V. Effect on Efficiency, Competition and Capital Formation </HD>
                    <P>
                        Section 2(b) of the Securities Act of 1933,
                        <SU>28</SU>
                        <FTREF/>
                         section 3(f) of the Exchange Act,
                        <SU>29</SU>
                        <FTREF/>
                         section 2(c) of the Investment Company Act of 1940,
                        <SU>30</SU>
                        <FTREF/>
                         and section 202(c) of the Investment Advisers Act of 1940 
                        <SU>31</SU>
                        <FTREF/>
                         require us, when engaging in rulemaking that requires us to consider or determine whether an act is necessary or appropriate in the public interest, to consider whether the action will promote efficiency, competition, and capital formation. Section 23(a)(2) of the Exchange Act 
                        <SU>32</SU>
                        <FTREF/>
                         prohibits us from adopting any rule that would impose a burden on competition not necessary or appropriate in furtherance of the purposes of the Exchange Act. The proposed rules are intended to enhance the transparency and facilitate parties' understanding of the applicability of the Commission review process to Board proceedings. The proposed rules and amendments also include regulatory provisions for the submission and administration of Fair Funds plans and disgorgement plans, and the proposed amendments are intended to clarify existing practice and increase the efficiency of Commission enforcement and self-regulatory organization disciplinary review proceedings. The proposed rules and amendments would apply to all persons involved in administrative proceedings before the Commission and therefore the Commission does not expect the proposed rules and amendments to have an anti-competitive effect. To the extent the proposed rules and amendments would foster making whole victims of securities laws violations and would increase the transparency of the Commission's administrative practice and the efficiency of the Commission's proceedings, there might be an increase in investor confidence in market fairness and efficiency. However, the magnitude of the effect of the proposed amendments in this regard is difficult to quantify. We request comment on the possible effects of our rule proposals on efficiency, competition, and capital formation. Commenters are requested to provide empirical data and other factual support for their views if possible. 
                    </P>
                    <FTNT>
                        <P>
                            <SU>28</SU>
                             15 U.S.C. 77b(b).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>29</SU>
                             15 U.S.C. 78c(f).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>30</SU>
                             15 U.S.C. 80a-2(c).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>31</SU>
                             15 U.S.C. 80b-2(c).
                        </P>
                    </FTNT>
                    <FTNT>
                        <P>
                            <SU>32</SU>
                             15 U.S.C. 78w(a)(2).
                        </P>
                    </FTNT>
                    <HD SOURCE="HD1">VI. Statutory Basis and Text of Proposed Amendments </HD>
                    <P>These amendments to the Rules of Practice and related provisions are being adopted pursuant to statutory authority granted to the Commission, including section 3 of the Sarbanes-Oxley Act, 15 U.S.C. 7202; section 19 of the Securities Act, 15 U.S.C. 77s; sections 19 and 23 of the Securities Exchange Act, 15 U.S.C. 78s and 78w; section 20 of the Public Utility Holding Company Act, 15 U.S.C. 79t; section 319 of the Trust Indenture Act, 15 U.S.C. 77sss; sections 38 and 40 of the Investment Company Act, 15 U.S.C. 80a-37 and 80a-39; and section 211 of the Investment Advisers Act, 15 U.S.C. 80b-11. </P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects </HD>
                        <CFR>17 CFR Parts 200 and 201 </CFR>
                        <P>Administrative practice and procedure. </P>
                        <CFR>17 CFR Part 240 </CFR>
                        <P>Reporting and Recordkeeping Requirements; Securities. </P>
                    </LSTSUB>
                    <HD SOURCE="HD1">Text of the Amendment </HD>
                    <P>For the reasons set out in the preamble, Title 17, Chapter II of the Code of Federal Regulations is proposed to be amended as follows: </P>
                    <PART>
                        <HD SOURCE="HED">PART 200—ORGANIZATION; CONDUCT AND ETHICS; AND INFORMATION AND REQUESTS </HD>
                        <P>1. The general authority citation for part 200, subpart A is revised to read as follows: </P>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart A—Organization and Program Management </HD>
                        </SUBPART>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>
                                15 U.S.C. 77s, 77sss, 78d-1, 78d-2, 78w, 78
                                <E T="03">ll</E>
                                (d), 78mmm, 79t, 80a-37, 80b-11, and 7202, unless otherwise noted. 
                            </P>
                        </AUTH>
                        <STARS/>
                        <P>2. In § 200.21, paragraph (b), remove the words “Rule 2(e) of the Commission's Rules of Practice (§ 201.2(e) of this chapter)” and, in their place, add the words “Rule 102(e) of the Commission's Rules of Practice (§ 201.102(e) of this chapter)”. </P>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart B—Disposition of Commission Business </HD>
                        </SUBPART>
                        <P>3. The authority citation for subpart B continues to read as follows: </P>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>5 U.S.C. 552b; 15 U.S.C. 78d-1 and 78w. </P>
                        </AUTH>
                        <PRTPAGE P="68195"/>
                        <P>4. In § 200.43, paragraph (c)(3), remove the words “Rule 26 of the Commission's rules of practice, 17 CFR 201.26” and, in their place, add the words “Rules 430 and 431 of the Commission's Rules of Practice, §§ 201.430 and 201.431 of this chapter”. </P>
                        <P>5. The authority citation for part 200, subpart F, is revised to read as follows: </P>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart F—Code of Behavior Governing Ex Parte Communications Between Persons Outside the Commission and Decisional Employees </HD>
                            <AUTH>
                                <HD SOURCE="HED">Authority:</HD>
                                <P>15 U.S.C. 77s, 77sss, 78w, 79t, 80a-37, 80b-11, and 7202; and 5 U.S.C. 557. </P>
                            </AUTH>
                        </SUBPART>
                        <P>6. Section 200.111 is amended by: </P>
                        <P>a. Redesignating paragraph (c)(1)(iii) as paragraph (c)(1)(iv); and </P>
                        <P>b. Adding new paragraph (c)(1)(iii). </P>
                        <P>The addition reads as follows:</P>
                        <SECTION>
                            <SECTNO>§ 200.111 </SECTNO>
                            <SUBJECT>Prohibitions; application; definitions. </SUBJECT>
                            <STARS/>
                            <P>
                                (c) 
                                <E T="03">Period during which prohibitions apply.</E>
                                 (1) * * * 
                            </P>
                            <P>(iii) That, in proceedings under Title I of the Sarbanes-Oxley Act of 2002, 15 U.S.C. 7211-7219, these prohibitions shall commence at the time that a copy of an application for review has been filed with the Commission and served on the Public Company Accounting Oversight Board; and </P>
                            <STARS/>
                        </SECTION>
                    </PART>
                    <PART>
                        <HD SOURCE="HED">PART 201—RULES OF PRACTICE </HD>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart D—Rules of Practice </HD>
                        </SUBPART>
                        <P>7. The authority citation for part 201, subpart D, is revised to read as follows: </P>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>
                                15 U.S.C. 77f, 77g, 77h, 77h-1, 77j, 77s, 77sss, 77ttt, 77u, 78c(b), 78d-1, 78d-2, 78
                                <E T="03">l</E>
                                , 78m, 78n, 78
                                <E T="03">o</E>
                                (d), 78
                                <E T="03">o</E>
                                -3, 78s, 78u-2, 78u-3, 78v, 78w, 79c, 79s, 79t, 79z-5a, 80a-8, 80a-9, 80a-37, 80a-38, 80a-39, 80a-40, 80a-41, 80a-44, 80b-3, 80b-9, 80b-11, 80b-12, 7202, 7215, and 7217. 
                            </P>
                        </AUTH>
                        <P>8. Section 201.100 is amended by adding paragraph (c) to read as follows: </P>
                        <SECTION>
                            <SECTNO>§ 201.100 </SECTNO>
                            <SUBJECT>Scope of the rules of practice. </SUBJECT>
                            <STARS/>
                            <P>(c) The Commission, upon its determination that to do so would serve the interests of justice and not result in prejudice to the parties to the proceeding, may by order direct, in a particular proceeding, that an alternative procedure shall apply or that compliance with an otherwise applicable rule is unnecessary. </P>
                            <P>9. Section 201.101 is amended by: </P>
                            <P>a. Revising paragraph (a)(9); and </P>
                            <P>b. Adding paragraph (a)(12). </P>
                            <P>The revision and addition read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.101 </SECTNO>
                            <SUBJECT>Definitions. </SUBJECT>
                            <P>(a) * * * </P>
                            <P>
                                (9) 
                                <E T="03">Proceeding</E>
                                 means any agency process initiated: 
                            </P>
                            <P>(i) By an order instituting proceedings; or </P>
                            <P>(ii) By the filing, pursuant to § 201.410, of a petition for review of an initial decision by a hearing officer; or </P>
                            <P>(iii) By the filing, pursuant to § 201.420, of an application for review of a self-regulatory organization determination; or </P>
                            <P>(iv) By the filing, pursuant to § 201.430, of a notice of intention to file a petition for review of a determination made pursuant to delegated authority; or </P>
                            <P>(v) By the filing, pursuant to § 201.440, of an application for review of a determination by the Public Company Accounting Oversight Board; or </P>
                            <P>(vi) By the filing, pursuant to § 240.11Aa3-1(f) of this chapter, of an application for review of an action or failure to act in connection with the implementation or operation of any effective transaction reporting plan; or </P>
                            <P>(vii) By the filing, pursuant to § 240.11Aa3-2(e) of this chapter, of an application for review of an action taken or failure to act in connection with the implementation or operation of any effective national market system plan. </P>
                            <STARS/>
                            <P>
                                (12) 
                                <E T="03">Board</E>
                                 means the Public Company Accounting Oversight Board. 
                            </P>
                            <STARS/>
                            <P>10. Section 201.102 is amended by revising paragraph (d)(4) to read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.102 </SECTNO>
                            <SUBJECT>Appearance and practice before the Commission. </SUBJECT>
                            <STARS/>
                            <P>
                                (d) 
                                <E T="03">Designation of address for service; notice of appearance; power of attorney; withdrawal.</E>
                                 * * * 
                            </P>
                            <P>
                                (4) 
                                <E T="03">Withdrawal.</E>
                                 Any person seeking to withdraw his or her appearance in a representative capacity shall file a notice of withdrawal with the Commission or the hearing officer. The notice shall state the name, address, and telephone number of the withdrawing representative; the name, address, and telephone number of the person for whom the appearance was made; and the effective date of the withdrawal. If the person seeking to withdraw knows the name, address, and telephone number of the new representative, or knows that the person for whom the appearance was made intends to represent him- or herself, that information shall be included in the notice. The notice must be served on the parties in accordance with § 201.150. The notice shall be filed at least five days before the proposed effective date of the withdrawal. 
                            </P>
                            <STARS/>
                            <P>11. Section 201.111 is amended by revising paragraph (h) to read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.111 </SECTNO>
                            <SUBJECT>Hearing officer: Authority. </SUBJECT>
                            <STARS/>
                            <P>(h) Subject to any limitations set forth elsewhere in these Rules of Practice, considering and ruling upon all procedural and other motions, including a motion to correct a manifest error of fact in the initial decision, provided that such a motion to correct is filed within ten days of the initial decision; </P>
                            <STARS/>
                            <P>12. Section 201.141 is amended by: </P>
                            <P>a. Revising the section heading; and </P>
                            <P>b. Revising paragraphs (a)(3) and (b) to read as follows: </P>
                            <P>The revisions read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.141 </SECTNO>
                            <SUBJECT>Orders and decisions: Service of orders instituting proceedings and other orders and decisions.</SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Service of an order instituting proceedings.</E>
                            </P>
                            <STARS/>
                            <P>
                                (3) 
                                <E T="03">Record of service.</E>
                                 The Secretary shall maintain a record of service on parties, identifying the party given notice, the method of service, the date of service, the address to which service was made, and the person who made service. If service is made in person, the certificate of service shall state, if available, the name of the individual to whom the order was given. If service is made by U.S. Postal Service certified or Express Mail, the Secretary shall maintain the confirmation of receipt or of attempted delivery. If service is made to an agent authorized by appointment to receive service, the certificate of service shall be accompanied by evidence of the appointment. 
                            </P>
                            <STARS/>
                            <P>
                                (b) 
                                <E T="03">Service of orders or decisions other than an order instituting proceedings.</E>
                                 Written orders or decisions issued by the Commission or by a hearing officer shall be served promptly on each party pursuant to any method of service authorized under paragraph (a) of this section or § 201.150(c)(1)-(3). Such orders or decisions may also be served by facsimile transmission if the party to be served has agreed to accept such service in a writing, signed by the party, and has provided the Commission with information concerning the facsimile machine telephone number and hours of 
                                <PRTPAGE P="68196"/>
                                facsimile machine operation. Service of orders or decisions by the Commission, including those entered pursuant to delegated authority, shall be made by the Secretary or, as authorized by the Secretary, by a member of an interested division. Service of orders or decisions issued by a hearing officer shall be made by the Secretary or the hearing officer. 
                            </P>
                            <P>13. Section 201.150 is amended by revising paragraph (c)(4) to read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.150 </SECTNO>
                            <SUBJECT>Service of papers by parties. </SUBJECT>
                            <STARS/>
                            <P>
                                (c) 
                                <E T="03">How made.</E>
                                 * * * 
                            </P>
                            <P>(4) Transmitting the papers by facsimile transmission where the following conditions are met: </P>
                            <P>(i) The persons so serving each other have provided the Commission and the parties with notice of the facsimile machine telephone number to be used and the hours of facsimile machine operation; </P>
                            <P>(ii) The transmission is made at such a time that it is received during the Commission's business hours as defined in § 201.104; and </P>
                            <P>(iii) The sender of the transmission has not been served in accordance with § 201.150 with a written notice from the recipient of the transmission declining service by facsimile transmission. </P>
                            <STARS/>
                            <P>14. Section 201.151 is amended by revising paragraph (a) to read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.151 </SECTNO>
                            <SUBJECT>Filing of papers with the Commission: Procedure. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">When to file.</E>
                                 All papers required to be served by a party upon any person shall be filed contemporaneously with the Commission. Papers required to be filed with the Commission must be received within the time limit, if any, for such filing. Filing with the Commission may be made by facsimile transmission if the party also contemporaneously transmits to the Commission a non-facsimile original with a manual signature. However, any person filing with the Commission by facsimile transmission will be responsible for assuring that the Commission receives a complete and legible filing within the time limit set for such filing. 
                            </P>
                            <STARS/>
                            <P>15. Section 201.152 is amended by revising paragraph (a)(2) to read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.152 </SECTNO>
                            <SUBJECT>Filing of papers: Form. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Specifications.</E>
                                 * * * 
                            </P>
                            <P>(2) Be typewritten or printed in 12-point or larger typeface or otherwise reproduced by a process that produces permanent and plainly legible copies; </P>
                            <STARS/>
                            <P>16. Section 201.154 is amended by revising paragraph (c) to read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.154 </SECTNO>
                            <SUBJECT>Motions. </SUBJECT>
                            <STARS/>
                            <P>
                                (c) 
                                <E T="03">Length limitation.</E>
                                 A motion, together with the brief in support of the motion; the brief in opposition to the motion; or any reply brief, shall not exceed 15 pages, exclusive of pages containing any table of contents or table of authorities. The page limit shall not apply to any addendum that consists solely of copies of applicable cases, pertinent legislative provisions, or relevant exhibits. Requests for leave to file motions and briefs in excess of 15 pages are disfavored. 
                            </P>
                            <P>17. Section 201.160 is amended by revising paragraph (b) to read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.160 </SECTNO>
                            <SUBJECT>Time computation. </SUBJECT>
                            <STARS/>
                            <P>
                                (b) 
                                <E T="03">Additional time for service by mail.</E>
                                 If service is made by mail, three days shall be added to the prescribed period for response unless an order of the Commission or the hearing officer specifies a date certain for filing. In the event that an order of the Commission or the hearing officer specifies a date certain for filing, no time shall be added for service by mail. 
                            </P>
                            <P>18. Section 201.201 is amended by: </P>
                            <P>a. Revising the section heading; </P>
                            <P>b. Designating the current text as paragraph (a) and adding a paragraph heading; and </P>
                            <P>c. Adding paragraph (b). </P>
                            <P>The revision and additions read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.201 </SECTNO>
                            <SUBJECT>Consolidation and severance of proceedings. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Consolidation.</E>
                                * * * 
                            </P>
                            <P>
                                (b) 
                                <E T="03">Severance.</E>
                                 By order of the Commission, any proceeding may be severed with respect to some or all parties. Any motion to sever must be made solely to the Commission and must include a representation that a settlement offer is pending before the Commission or otherwise show good cause. 
                            </P>
                            <P>19. Section 201.202 is amended by revising the introductory text of paragraph (a) to read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.202 </SECTNO>
                            <SUBJECT>Specification of procedures by parties in certain proceedings. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Motion to specify procedures.</E>
                                 In any proceeding other than an enforcement or disciplinary proceeding, a proceeding to review a determination by a self-regulatory organization pursuant to §§ 201.420 and 201.421, or a proceeding to review a determination of the Board pursuant to §§ 201.440 and 201.441, a party may, at any time up to 20 days prior to the start of a hearing, make a motion to specify the procedures necessary or appropriate for the proceeding with particular reference to: 
                            </P>
                            <STARS/>
                            <P>20. Section 201.210 is amended by revising paragraph (a)(1) and the introductory text to paragraphs (b)(1) and (c) to read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.210 </SECTNO>
                            <SUBJECT>Parties, limited participants and amici curiae. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Parties in an enforcement or disciplinary proceeding, a proceeding to review a self-regulatory organization determination, or a proceeding to review a Board determination—</E>
                            </P>
                            <P>
                                (1) 
                                <E T="03">Generally.</E>
                                 No person shall be granted leave to become a party or a non-party participant on a limited basis in an enforcement or disciplinary proceeding, a proceeding to review a determination by a self-regulatory organization pursuant to §§ 201.420 and 201.421, or a proceeding to review a determination by the Board pursuant to §§ 201.440 and 201.441, except as authorized by paragraph (c) of this section. 
                            </P>
                            <STARS/>
                            <P>
                                (b) 
                                <E T="03">Intervention as a party.</E>
                                —(1) 
                                <E T="03">Generally.</E>
                                 In any proceeding, other than an enforcement proceeding, a disciplinary proceeding, a proceeding to review a self-regulatory determination, or a proceeding to review a Board determination, any person may seek leave to intervene as a party by filing a motion setting forth the person's interest in the proceeding: 
                            </P>
                            <STARS/>
                            <P>
                                (c) 
                                <E T="03">Leave to participate on a limited basis.</E>
                                 In any proceeding, other than an enforcement proceeding, a disciplinary proceeding, a proceeding to review a self-regulatory determination, or a proceeding to review a Board determination, any person may seek leave to participate on a limited basis as a non-party participant as to any matter affecting the person's interests: 
                            </P>
                            <STARS/>
                            <P>21. Section 201.230 is amended by revising paragraphs (a)(1)(vi) and (c) to read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.230 </SECTNO>
                            <SUBJECT>Enforcement and disciplinary proceedings: Availability of documents for inspection and copying. </SUBJECT>
                            <STARS/>
                            <P>
                                (a) 
                                <E T="03">Documents to be available for inspection and copying.</E>
                                 (1) * * * 
                            </P>
                            <P>
                                (vi) Any final examination or inspection reports prepared by the Office of Compliance Inspections and Examinations, the Division of Market 
                                <PRTPAGE P="68197"/>
                                Regulation, or the Division of Investment Management, if the Division of Enforcement intends either to introduce any such report into evidence or to use any such report to refresh the recollection of any witness. 
                            </P>
                            <STARS/>
                            <P>
                                (c) 
                                <E T="03">Withheld document list.</E>
                                 The hearing officer may require the Division of Enforcement to submit for review a list of documents or categories of documents withheld pursuant to paragraphs (b)(1)(i) through (b)(1)(iv) of this section or to submit any document withheld, and may determine whether any such document should be made available for inspection and copying. When similar documents are withheld pursuant to paragraphs (b)(1)(i) through (b)(1)(iv) of this section, those documents may be identified by category instead of by individual document. The hearing officer retains discretion to determine when an identification by category is insufficient. 
                            </P>
                            <STARS/>
                            <P>22. Section 201.231 is amended by revising paragraph (a) to read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.231 </SECTNO>
                            <SUBJECT>Enforcement and disciplinary proceedings: Production of witness statements. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Availability.</E>
                                 Any respondent in an enforcement or disciplinary proceeding may move that the Division of Enforcement produce for inspection and copying any statement of any person called or to be called as a witness by the Division of Enforcement that pertains, or is expected to pertain, to his or her direct testimony and that would be required to be produced pursuant to the Jencks Act, 18 U.S.C. 3500. For purposes of this section, 
                                <E T="03">statement</E>
                                 shall have the meaning set forth in 18 U.S.C. 3500(e). Such production shall be made at a time and place fixed by the hearing officer and shall be made available to any party, provided, however, that the production shall be made under conditions intended to preserve the items to be inspected or copied. 
                            </P>
                            <STARS/>
                            <P>23. Section 201.232 is amended by revising paragraph (e)(1) to read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>201.232 </SECTNO>
                            <SUBJECT>Subpoenas. </SUBJECT>
                            <STARS/>
                            <P>
                                (e) 
                                <E T="03">Application to quash or modify.</E>
                                 (1) Any person to whom a subpoena is directed, or who is an owner, creator or the subject of the documents that are to be produced pursuant to a subpoena, or any party may, prior to the time specified therein for compliance, but in no event more than 15 days after the date of service of such subpoena, request that the subpoena be quashed or modified. Such request shall be made by application filed with the Secretary and served on all parties pursuant to § 201.150. The party on whose behalf the subpoena was issued may, within five days of service of the application, file an opposition to the application. If a hearing officer has been assigned to the proceeding, the application to quash shall be directed to that hearing officer for consideration, even if the subpoena was issued by another person. 
                            </P>
                            <STARS/>
                            <P>24. Section 201.233 is amended by revising paragraph (b) to read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.233 </SECTNO>
                            <SUBJECT>Deposition upon oral examination. </SUBJECT>
                            <STARS/>
                            <P>
                                (b) 
                                <E T="03">Required finding when ordering a deposition.</E>
                                 In the discretion of the Commission or the hearing officer, an order for a deposition may be issued upon a finding that the prospective witness will likely give testimony material to the proceeding; that it is likely the prospective witness, who is then within the United States, will be unable to attend or testify at the hearing because of age, sickness, infirmity, imprisonment, other disability, or absence from the United States, unless it appears that the absence of the witness was procured by the party requesting the deposition; and that the taking of a deposition will serve the interests of justice. 
                            </P>
                            <STARS/>
                            <P>25. Section 201.350 is amended by revising paragraph (b) to read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.350 </SECTNO>
                            <SUBJECT>Record in proceedings before hearing officer; retention of documents; copies. </SUBJECT>
                            <STARS/>
                            <P>
                                (b) 
                                <E T="03">Retention of documents not admitted.</E>
                                 Any document offered into evidence but excluded shall not be considered a part of the record. The Secretary shall retain any such document until the later of the date upon which a Commission order ending the proceeding becomes final, or the conclusion of any judicial review of the Commission's order. 
                            </P>
                            <STARS/>
                            <P>26. Section 201.351 is amended by revising paragraph (a) to read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.351 </SECTNO>
                            <SUBJECT>Transmittal of documents to Secretary; record index; certification. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Transmittal from hearing officer to Secretary of partial record index.</E>
                                 The hearing officer may, at any time, transmit to the Secretary motions, exhibits or any other original documents filed with or accepted into evidence by the hearing officer, together with a list of such documents. 
                            </P>
                            <STARS/>
                            <P>27. Section 201.360 is amended by: </P>
                            <P>a. Adding a sentence at the end of paragraph (a)(2); </P>
                            <P>b. Revising paragraphs (b)(1), (b)(2) and (d); and </P>
                            <P>c. Removing paragraph (e). </P>
                            <P>The addition and revisions read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.360 </SECTNO>
                            <SUBJECT>Initial decision of hearing officer. </SUBJECT>
                            <P>(a)(1) * * * </P>
                            <P>
                                (2) 
                                <E T="03">Time period for filing initial decision.</E>
                                 * * * If a stay is granted pursuant to § 201.210(c)(3), the time period specified in the order instituting proceedings in which the hearing officer's initial decision must be filed with the Secretary, as well as any other time limits established in orders issued by the hearing officer in the proceeding, shall be automatically tolled during the period while the stay is in effect. 
                            </P>
                            <P>
                                (b) 
                                <E T="03">Content.</E>
                                 * * * 
                            </P>
                            <P>(1) The Commission will enter an order of finality as to each party unless a party or an aggrieved person entitled to review timely files a petition for review of the initial decision or a motion to correct a manifest error of fact in the initial decision with the hearing officer, or the Commission determines on its own initiative to review the initial decision; and </P>
                            <P>(2) If a party or an aggrieved person entitled to review timely files a petition for review or a motion to correct a manifest error of fact in the initial decision with the hearing officer, or if the Commission takes action to review as to a party or an aggrieved person entitled to review, the initial decision shall not become final as to that party or person. </P>
                            <STARS/>
                            <P>
                                (d) 
                                <E T="03">Finality.</E>
                                 (1) If a party or an aggrieved person entitled to review timely files a petition for review or a motion to correct a manifest error of fact in the initial decision, or if the Commission on its own initiative orders review of a decision with respect to a party or a person aggrieved who would be entitled to review, the initial decision shall not become final as to that party or person. 
                            </P>
                            <P>
                                (2) If a party or aggrieved person entitled to review fails to file timely a petition for review or a motion to correct a manifest error of fact in the initial decision, and if the Commission does not order review of a decision on its own initiative, the Commission will issue an order that the decision has become final as to that party. The decision becomes final upon issuance of 
                                <PRTPAGE P="68198"/>
                                the order. The order of finality shall state the date on which sanctions, if any, take effect. Notice of the order shall be published in the 
                                <E T="03">SEC News Digest</E>
                                 and the 
                                <E T="03">SEC Docket,</E>
                                 and on the SEC Web site. 
                            </P>
                            <P>28. Section 201.400 is amended by revising paragraph (a) to read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.400 </SECTNO>
                            <SUBJECT>Interlocutory review. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Availability.</E>
                                 The Commission may, at any time, on its own motion, direct that any matter be submitted to it for review. Petitions by parties for interlocutory review are disfavored, and the Commission ordinarily will grant a petition to review a hearing officer ruling prior to its consideration of an initial decision only in extraordinary circumstances. The Commission may decline to consider a ruling certified by a hearing officer pursuant to paragraph (c) of this section or the petition of a party who has been denied certification if it determines that interlocutory review is not warranted or appropriate under the circumstances. This section is the exclusive remedy for review of a hearing officer's ruling prior to Commission consideration of the entire proceeding and is the sole mechanism for appeal of actions delegated pursuant to 17 CFR 200.30-9 and 200.30-10. 
                            </P>
                            <STARS/>
                            <P>29. Section 201.401 is amended by: </P>
                            <P>a. Revising the section heading and paragraph (d)(1); and </P>
                            <P>b. Adding paragraph (e). </P>
                            <P>The revisions and addition read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.401 </SECTNO>
                            <SUBJECT>Consideration of stays. </SUBJECT>
                            <STARS/>
                            <P>
                                (d) 
                                <E T="03">Stay of an action by a self-regulatory organization.</E>
                            </P>
                            <P>
                                (1) 
                                <E T="03">Availability.</E>
                                 A motion for a stay of an action by a self-regulatory organization for which the Commission is the appropriate regulatory agency, for which action review may be sought pursuant to § 201.420, may be made by any person aggrieved thereby at the time an application for review is filed in accordance with § 201.420 or thereafter. 
                            </P>
                            <STARS/>
                            <P>
                                (e) 
                                <E T="03">Lifting of stay of action by the Public Company Accounting Oversight Board.</E>
                                 (1) 
                                <E T="03">Availability.</E>
                                 Any person aggrieved by the stay of action by the Board entered in accordance with 15 U.S.C. 7215(e) for which review has been sought pursuant to § 201.440 or which the Commission has taken up on its motion pursuant to § 201.441 may make a motion to lift the stay. The Commission may, at any time, on its own motion determine whether to lift the automatic stay. 
                            </P>
                            <P>
                                (2) 
                                <E T="03">Summary action.</E>
                                 The Commission may lift a stay summarily, without notice and opportunity for hearing. 
                            </P>
                            <P>
                                (3) 
                                <E T="03">Expedited consideration.</E>
                                 The Commission may expedite consideration of a motion to lift a stay of Board action, consistent with the Commission's other responsibilities. Where consideration is expedited, persons opposing the lifting of the stay may file a statement in opposition within two days of service of the motion requesting lifting of the stay unless the Commission, by written order, shall specify a different period. 
                            </P>
                            <P>30. Section 201.410 is amended by: </P>
                            <P>a. Revising paragraph (b); and </P>
                            <P>b. Removing and reserving paragraph (d). </P>
                            <P>The revision reads as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.410 </SECTNO>
                            <SUBJECT>Appeal of initial decisions by hearing officers. </SUBJECT>
                            <STARS/>
                            <P>
                                (b) 
                                <E T="03">Procedure.</E>
                                 The petition for review of an initial decision shall be filed with the Commission within such time after service of the initial decision as prescribed by the hearing officer pursuant to § 201.360(b) unless a party has filed a motion to correct an initial decision with the hearing officer. If such correction has been sought, a party shall have 21 days from the date of the hearing officer's order resolving the motion for to correct to file a petition for review. The petition shall set forth the specific findings and conclusions of the initial decision as to which exception is taken, together with supporting reasons for each exception. Supporting reasons may be stated in summary form. Any exception to an initial decision not stated in the petition for review, or in a previously filed proposed finding made pursuant to § 201.340 may, at the discretion of the Commission, be deemed to have been waived by the petitioner. In the event a petition for review is filed, any other party to the proceeding may file a cross-petition for review within the original time allowed for seeking review or within ten days from the date that the petition for review was filed, whichever is later. 
                            </P>
                            <STARS/>
                            <P>31. Section 201.411 is amended by revising paragraph (e) as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.411 </SECTNO>
                            <SUBJECT>Commission consideration of decisions by hearing officers. </SUBJECT>
                            <STARS/>
                            <P>
                                (e) 
                                <E T="03">Summary affirmance.</E>
                                 (1) At any time within 21 days after the filing of a petition for review pursuant to § 201.410(b), any party may file a motion in accordance with § 201.154 asking that the Commission summarily affirm an initial decision. Any party may file an opposition and reply to such motion in accordance with § 201.154. Pending determination of the motion for summary affirmance, the Commission, in its discretion, may delay issuance of a briefing schedule order pursuant to § 201.450. 
                            </P>
                            <P>(2) Upon consideration of the motion and any opposition or upon its own initiative, the Commission may summarily affirm an initial decision. The Commission may grant summary affirmance if it finds that no issue raised in the initial decision warrants consideration by the Commission of further oral or written argument. The Commission will decline to grant summary affirmance upon a reasonable showing that a prejudicial error was committed in the conduct of the proceeding or that the decision embodies an exercise of discretion or decision of law or policy that is important and that the Commission should review. </P>
                            <STARS/>
                            <P>32. Section 201.420 is amended by: </P>
                            <P>a. Revising paragraph (b); </P>
                            <P>b. Redesignating paragraphs (c) and (d) as paragraphs (d) and (e); and </P>
                            <P>c. Adding new paragraph (c). </P>
                            <P>The revision and addition read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.420 </SECTNO>
                            <SUBJECT>Appeal of determinations by self-regulatory organizations. </SUBJECT>
                            <STARS/>
                            <P>
                                (b) 
                                <E T="03">Procedure.</E>
                                 As required by section 19(d)(1) of the Securities Exchange Act of 1934, 15 U.S.C. 78s(d)(1), an applicant must file an application for review with the Commission within 30 days after the notice of the determination is filed with the Commission and received by the aggrieved person applying for review. The Commission will not extend this 30-day period, absent a showing of extraordinary circumstances. This section is the exclusive remedy for seeking an extension of the 30-day period. 
                            </P>
                            <P>
                                (c) 
                                <E T="03">Application.</E>
                                 The application shall be filed with the Commission pursuant to § 201.151. The applicant shall serve the application on the self-regulatory organization. The application shall identify the determination complained of and set forth in summary form a brief statement of the alleged errors in the determination and supporting reasons therefor. The application shall state an address where the applicant can be served. The application should not exceed two pages in length. The application shall be accompanied by the notice of appearance required by § 201.102(d). 
                            </P>
                            <STARS/>
                            <PRTPAGE P="68199"/>
                            <P>33. Section 201.430 is amended by revising paragraph (a) to read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.430 </SECTNO>
                            <SUBJECT>Appeal of actions made pursuant to delegated authority. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Scope of rule.</E>
                                 Any person aggrieved by an action made by authority delegated in §§ 200.30-1 through 200.30-8 or §§ 200.30-11 through 200.30-18 of this chapter may seek review of the action pursuant to paragraph (b) of this section. 
                            </P>
                            <STARS/>
                            <P>34. Sections 201.440 and 201.441 are added to read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.440 </SECTNO>
                            <SUBJECT>Appeal of determinations by the Public Company Accounting Oversight Board. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Application for review; when available.</E>
                                 Any person who is aggrieved by a determination of the Board with respect to any final disciplinary sanction, including disapproval of a completed application for registration of a public accounting firm, may file an application for review. 
                            </P>
                            <P>
                                (b) 
                                <E T="03">Procedure.</E>
                                 An aggrieved person may file an application for review with the Commission pursuant to § 201.151 within 30 days after the notice filed by the Board of its determination with the Commission pursuant to § 240.19d-4 of this chapter is received by the aggrieved person applying for review. The applicant shall serve the application on the Board at the same time. The application shall identify the determination complained of, set forth in summary form a brief statement of alleged errors in the determination and supporting reasons therefor, and state an address where the applicant can be served. The notice of appearance required by § 201.102(d) shall accompany the application. 
                            </P>
                            <P>
                                (c) 
                                <E T="03">Stay of determination.</E>
                                 Filing an application for review with the Commission pursuant to paragraph (b) of this section operates as a stay of the Board's determination unless the Commission otherwise orders either pursuant to a motion filed in accordance with § 201.401(e) or upon its own motion. 
                            </P>
                            <P>
                                (d) 
                                <E T="03">Certification of the record; service of the index.</E>
                                 Within fourteen days after receipt of an application for review, the Board shall certify and file with the Commission one copy of the record upon which it took the complained-of action. The Board shall file with the Commission three copies of an index of such record, and shall serve one copy of the index on each party. 
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.441 </SECTNO>
                            <SUBJECT>Commission consideration of Board determinations. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Commission review other than pursuant to an application for review.</E>
                                 The Commission may, on its own initiative, order review of any final disciplinary sanction, including disapproval of a completed application for registration of a public accounting firm, imposed by the Board that could be the subject to an application for review pursuant to § 201.440(a) within 40 days after the Board filed notice thereof pursuant to § 240.19d-4 of this chapter. 
                            </P>
                            <P>
                                (b) 
                                <E T="03">Supplemental briefing.</E>
                                 The Commission may at any time prior to the issuance of its decision raise or consider any matter that it deems material, whether or not raised by the parties. The Commission will give notice to the parties and an opportunity for supplemental briefing with respect to issues not briefed by the parties where the Commission believes that such briefing could significantly aid the decisional process. 
                            </P>
                            <P>35. Section 201.450 is amended by: </P>
                            <P>a. Redesignating paragraphs (a)(2)(iii) and (a)(2)(iv) as paragraphs (a)(2)(iv) and (a)(2)(v); </P>
                            <P>b. Adding new paragraph (a)(2)(iii); </P>
                            <P>c. Revising paragraph (c); and </P>
                            <P>d. Adding paragraph (d). </P>
                            <P>The additions and revision read as follows:</P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.450 </SECTNO>
                            <SUBJECT>Briefs filed with the Commission. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Briefing schedule order.</E>
                                 * * * 
                            </P>
                            <P>(2) * * * </P>
                            <P>(iii) Receipt by the Commission of an index to the record of a determination by the Board filed pursuant to § 201.440(d); </P>
                            <STARS/>
                            <P>
                                (c) 
                                <E T="03">Length limitation.</E>
                                 Except with leave of the Commission, opening and opposition briefs shall not exceed 14,000 words and reply briefs shall not exceed 7,000 words, exclusive of pages containing the table of contents, table of authorities, and any addendum that consists solely of copies of applicable cases, pertinent legislative provisions, or rules and exhibits. The number of words shall include pleadings incorporated by reference. Motions to file briefs in excess of these limitations are disfavored. 
                            </P>
                            <P>
                                (d) 
                                <E T="03">Certificate of compliance.</E>
                                 An opening or opposition brief that does not exceed 30 pages in length, exclusive of pages containing the table of contents, table of authorities, and any addendum that consists solely of copies of applicable cases, pertinent legislative provisions, or rules and exhibits, but inclusive of pleadings incorporated by reference, is presumptively considered to contain no more than 14,000 words. A reply brief that does not exceed 15 pages in length, exclusive of pages containing the table of contents, table of authorities, and any addendum that consists solely of copies of applicable cases, pertinent legislative provisions, or rules and exhibits, but inclusive of pleadings incorporated by reference, is presumptively considered to contain no more than 7,000 words. Any brief that exceeds these page limits must include a certificate by the attorney, or an unrepresented party, stating that the brief complies with the length limitation set forth in § 201.450(c) and stating the number of words in the brief. The person preparing the certificate may rely on the word count of the word-processing system used to prepare the brief. 
                            </P>
                            <P>36. Section 201.451 is amended by revising paragraph (b) to read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.451 </SECTNO>
                            <SUBJECT>Oral argument before the Commission. </SUBJECT>
                            <STARS/>
                            <P>
                                (b) 
                                <E T="03">Procedure.</E>
                                 Requests for oral argument shall be made by separate motion accompanying the initial brief on the merits. The Commission shall issue an order as to whether oral argument is to be heard, and if so, the time and place therefor. If oral argument is granted, the time fixed for oral argument shall be changed only by written order of the Commission, for good cause shown. The order shall state at whose request the change is made and the reasons for any such changes. No visual aids may be used at oral argument unless copies have been provided to the Commission and all parties at least five business days before the argument is to be held. 
                            </P>
                            <STARS/>
                            <P>37. Section 201.460 is amended by adding paragraph (a)(3) to read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.460</SECTNO>
                            <SUBJECT>Record before the Commission. </SUBJECT>
                            <STARS/>
                            <P>
                                (a) 
                                <E T="03">Contents of the record.</E>
                                 * * * 
                            </P>
                            <P>(3) In a proceeding for final decision before the Commission reviewing a determination of the Board, the record shall consist of: </P>
                            <P>(i) The record certified pursuant to § 201.440(d) by the Board; </P>
                            <P>(ii) Any application for review; and </P>
                            <P>(iii) Any submissions, moving papers and briefs filed on appeal or review. </P>
                            <STARS/>
                            <P>38. Section 201.470 is amended by revising paragraph (b) to read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.470</SECTNO>
                            <SUBJECT>Reconsideration. </SUBJECT>
                            <STARS/>
                            <P>
                                (b) 
                                <E T="03">Procedure.</E>
                                 A motion for reconsideration shall be filed within 10 days after service of the order complained of, or within such time as 
                                <PRTPAGE P="68200"/>
                                the Commission may prescribe upon motion for extension of time filed by the person seeking reconsideration, if the motion is made within the foregoing 10-day period. The motion for reconsideration shall briefly and specifically state the matters of record alleged to have been erroneously decided, the grounds relied upon, and the relief sought. A motion for reconsideration shall conform to the requirements, including page length, provided in § 201.154. No response to a motion for reconsideration shall be filed unless requested by the Commission. Any response so requested shall comply with § 201.154. 
                            </P>
                            <P>39. Section 201.601 is amended by adding paragraph (c) to read as follows: </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.601 </SECTNO>
                            <SUBJECT>Prompt payment of disgorgement, interest and penalties. </SUBJECT>
                            <STARS/>
                            <P>
                                (c) 
                                <E T="03">Method of making payment.</E>
                                 Payment shall be made by United States postal money order, wire transfer, certified check, bank cashier's check, or bank money order made payable to the Securities and Exchange Commission. The payment shall be mailed or delivered to the Office of Financial Management of the Commission. Payment shall be accompanied by a letter that identifies the name and number of the case and the name of the respondent making payment. A copy of the letter and the instrument of payment shall be sent to counsel for the Division of Enforcement. 
                            </P>
                            <P>40. Sections 201.610 through 201.614 and § 201.620 are removed and reserved. </P>
                            <P>41. Sections 201.1100 through 201.1106, Subpart F—Fair Fund and Disgorgement Plans—are added to read as follows: </P>
                        </SECTION>
                        <SUBPART>
                            <HD SOURCE="HED">Subpart F—Fair Fund and Disgorgement Plans </HD>
                        </SUBPART>
                        <CONTENTS>
                            <SECHD>Sec. </SECHD>
                            <SECTNO>201.1100 </SECTNO>
                            <SUBJECT>Creation of Fair Fund. </SUBJECT>
                            <SECTNO>201.1101 </SECTNO>
                            <SUBJECT>Submission of plan of distribution; contents of plan. </SUBJECT>
                            <SECTNO>201.1102 </SECTNO>
                            <SUBJECT>Provisions for payment. </SUBJECT>
                            <SECTNO>201.1103 </SECTNO>
                            <SUBJECT>Notice of proposed plan and opportunity for comment by non-parties. </SUBJECT>
                            <SECTNO>201.1104 </SECTNO>
                            <SUBJECT>Order approving, modifying, or disapproving proposed plan. </SUBJECT>
                            <SECTNO>201.1105 </SECTNO>
                            <SUBJECT>Administration of plan. </SUBJECT>
                            <SECTNO>201.1106 </SECTNO>
                            <SUBJECT>Right to challenge. </SUBJECT>
                        </CONTENTS>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>15 U.S.C. 77h-1, 77s, 77u, 78c(b), 78d-1, 78d-2, 78u-2, 78u-3, 78v, 78w, 80a-9, 80a-37, 80a-39, 80a-40, 80b-3, 80b-11, 80b-12, and 7246. </P>
                        </AUTH>
                        <SECTION>
                            <SECTNO>§ 201.1100 </SECTNO>
                            <SUBJECT>Creation of Fair Fund. </SUBJECT>
                            <P>In any agency process initiated by an order instituting proceedings in which the Commission issues an order requiring the payment of disgorgement by a respondent and also assessing a civil money penalty against that respondent, the Commission may order that the amount of the disgorgement and of the civil money penalty, together with any funds received by the Commission pursuant to 15 U.S.C. 7246(b), be used to create a fund for the benefit of investors who were harmed by the violation. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.1101 </SECTNO>
                            <SUBJECT>Submission of plan of distribution; contents of plan. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Submission.</E>
                                 The Commission or the hearing officer may, at any time, order any party to submit a plan for the administration and distribution of funds in a Fair Fund or disgorgement funds. Unless ordered otherwise, the Division of Enforcement shall submit a proposed plan no later than 60 days after the respondent has turned over the funds or other assets pursuant to the Commission's order imposing disgorgement and, if applicable, a civil money penalty and any appeals of the Commission's order have been waived or completed, or appeal is no longer available. 
                            </P>
                            <P>
                                (b) 
                                <E T="03">Contents of plan.</E>
                                 Unless otherwise ordered, a plan for the administration of a Fair Fund or a disgorgement fund shall include the following elements: 
                            </P>
                            <P>(1) Procedures for the receipt of additional funds, including the specification of any account where funds will be held, the instruments in which the funds may be invested; and, in the case of a Fair Fund, the receipt of any funds pursuant to 15 U.S.C. 7246(b), if applicable; </P>
                            <P>(2) Specification of categories of persons potentially eligible to receive proceeds from the fund; </P>
                            <P>(3) Procedures for providing notice to such persons of the existence of the fund and their potential eligibility to receive proceeds of the fund; </P>
                            <P>(4) Procedures for making and approving claims, procedures for handling disputed claims, and a cut-off date for the making of claims; </P>
                            <P>(5) A proposed date for the termination of the fund, including provision for the disposition of any funds not otherwise distributed; </P>
                            <P>(6) Procedures for the administration of the fund, including selection, compensation, and, as necessary, indemnification of a fund administrator to oversee the fund, process claims, prepare accountings, file tax returns, and, subject to the approval of the Commission, make distributions from the fund to investors who were harmed by the violation; and </P>
                            <P>(7) Such other provisions as the Commission or the hearing officer may require. </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.1102 </SECTNO>
                            <SUBJECT>Provisions for payment. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Payment to registry of the court or court-appointed receiver.</E>
                                 Subject to such conditions as the Commission or the hearing officer shall deem appropriate, a plan for the administration of a Fair Fund or a disgorgement fund may provide for payment of funds into a court registry or to a court-appointed receiver in any case pending in federal or state court against a respondent or any other person based upon a complaint alleging violations arising from the same or substantially similar facts as those alleged in the Commission's order instituting proceedings. 
                            </P>
                            <P>
                                (b) 
                                <E T="03">Payment to the United States Treasury under certain circumstances.</E>
                                 When, in the opinion of the Commission or the hearing officer, the cost of administering a plan of disgorgement relative to the value of the available disgorgement funds and the number of potential claimants would not justify distribution of the disgorgement funds to injured investors, the plan may provide that the disgorgement funds and any civil penalty shall be paid directly to the general fund of the United States Treasury. 
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.1103 </SECTNO>
                            <SUBJECT>Notice of proposed plan and opportunity for comment by non-parties. </SUBJECT>
                            <P>
                                Notice of a proposed plan of disgorgement or a proposed Fair Fund plan shall be published in the 
                                <E T="03">SEC News Digest</E>
                                 and the 
                                <E T="03">SEC</E>
                                 Docket, on the SEC website, and in such other publications as the Commission or the hearing officer may require. The notice shall specify how copies of the proposed plan may be obtained and shall state that persons desiring to comment on the proposed plan may submit their views, in writing, to the Commission. 
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.1104 </SECTNO>
                            <SUBJECT>Order approving, modifying, or disapproving proposed plan. </SUBJECT>
                            <P>At any time after 30 days following publication of notice of a proposed plan of disgorgement or of a proposed Fair Fund plan, the Commission shall, by order, approve, approve with modifications, or disapprove the proposed plan. In the discretion of the Commission, a proposed plan that is substantially modified prior to adoption may be republished for an additional comment period pursuant to § 201.1103. The order approving or disapproving the plan should be entered within 30 days after the end of the final period allowed for comments on the proposed plan unless the Commission or the hearing officer, by written order, allows a longer period for good cause shown. </P>
                        </SECTION>
                        <SECTION>
                            <PRTPAGE P="68201"/>
                            <SECTNO>§ 201.1105 </SECTNO>
                            <SUBJECT>Administration of plan. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Appointment and removal of administrator.</E>
                                 The Commission or the hearing officer shall have discretion to appoint any person, including a Commission employee, as administrator of a plan of disgorgement or a Fair Fund plan and to delegate to that person responsibility for administering the plan. An administrator may be removed at any time by order of the Commission or hearing officer. 
                            </P>
                            <P>
                                (b) 
                                <E T="03">Assistance by respondent.</E>
                                 A respondent may be required or permitted to administer or assist in administering a plan of disgorgement subject to such terms and conditions as the Commission or hearing officer deem appropriate to ensure the proper distribution of the funds. 
                            </P>
                            <P>
                                (c) 
                                <E T="03">Administrator to post bond.</E>
                                 If the administrator is not a Commission employee, the administrator shall be required to obtain a bond in the manner prescribed in 11 U.S.C. 322, in an amount to be approved by the Commission. The cost of the bond may be paid for as a cost of administration. The Commission may waive posting of a bond for good cause shown. 
                            </P>
                            <P>
                                (d) 
                                <E T="03">Administrator's fees.</E>
                                 If the administrator is a Commission employee, no fee shall be paid to the administrator for his or her services. If the administrator is not a Commission employee, the administrator may file an application for fees for completed services, and upon approval by the Commission or a hearing officer, may be paid a reasonable fee for those services. Any objections thereto shall be filed within 21 days of service of the application on the parties. 
                            </P>
                            <P>
                                (e) 
                                <E T="03">Source of funds.</E>
                                 Unless otherwise ordered, fees and other expenses of administering the plan shall be paid first from the interest earned on the funds, and if the interest is not sufficient, then from the corpus. 
                            </P>
                            <P>
                                (f) 
                                <E T="03">Accountings.</E>
                                 During the first 10 days of each calendar quarter, or as otherwise directed by the Commission or the hearing officer, the administrator shall file an accounting of all monies earned or received and all monies spent in connection with the administration of the plan of disgorgement. A final accounting shall be submitted for approval of the Commission or hearing officer prior to discharge of the administrator and cancellation of the administrator's bond, if any. 
                            </P>
                            <P>
                                (g) 
                                <E T="03">Amendment.</E>
                                 A plan may be amended upon motion by any party or by the plan administrator or upon the Commission's or the hearing officer's own motion. 
                            </P>
                        </SECTION>
                        <SECTION>
                            <SECTNO>§ 201.1106</SECTNO>
                            <SUBJECT>Right to challenge. </SUBJECT>
                            <P>Other than in connection with the opportunity to submit comments as provided in § 201.1103, no person shall be granted leave to intervene or to participate or otherwise to appear in any agency proceeding or otherwise to challenge an order of disgorgement or of creation of a Fair Fund; or an order approving, approving with modifications, or disapproving a plan of disgorgement or a Fair Fund plan; or any determination relating to a plan based solely upon that person's eligibility or potential eligibility to participate in a fund or based upon any private right of action such person may have against any person who is also a respondent in the proceeding. </P>
                        </SECTION>
                    </PART>
                    <PART>
                        <HD SOURCE="HED">PART 240—GENERAL RULES AND REGULATIONS, SECURITIES EXCHANGE ACT OF 1934 </HD>
                        <P>42. The authority citation for part 240 continues to read as follows: </P>
                        <AUTH>
                            <HD SOURCE="HED">Authority:</HD>
                            <P>
                                15 U.S.C. 77c, 77d, 77g, 77j, 77s, 77z-2, 77z-3, 77eee, 77ggg, 77nnn, 77sss, 77ttt, 78c, 78d, 78e, 78f, 78g, 78i, 78j, 78j-1, 78k, 78k-1, 78
                                <E T="03">l,</E>
                                 78m, 78n, 78o, 78p, 78q, 78s, 78u-5, 78w, 78x, 78
                                <E T="03">ll,</E>
                                 78mm, 79q, 79t, 80a-20, 80a-23, 80a-29, 80a-37, 80b-3, 80b-4, 80b-11, and 7201 
                                <E T="03">et seq.</E>
                                ; and 18 U.S.C. 1350, unless otherwise noted. 
                            </P>
                        </AUTH>
                        <STARS/>
                        <P>43. Section 240.19d-4 is added to read as follows: </P>
                        <SECTION>
                            <SECTNO>§ 240.19d-4</SECTNO>
                            <SUBJECT>Notice by the Public Company Accounting Oversight Board of disapproval of registration or of disciplinary action. </SUBJECT>
                            <P>
                                (a) 
                                <E T="03">Definitions.</E>
                            </P>
                            <P>
                                (1) 
                                <E T="03">Board</E>
                                 means the Public Company Accounting Oversight Board. 
                            </P>
                            <P>
                                (2) 
                                <E T="03">Public accounting firm</E>
                                 shall have the meaning set forth in 15 U.S.C. 7201(a)(11). 
                            </P>
                            <P>
                                (3) 
                                <E T="03">Registered public accounting firm</E>
                                 shall have the meaning set forth in 15 U.S.C. 7201(a)(12). 
                            </P>
                            <P>
                                (4) 
                                <E T="03">Associated person</E>
                                 shall mean a person associated with a registered public accounting firm as defined in 15 U.S.C. 7201(a)(9). 
                            </P>
                            <P>
                                (b)(1) 
                                <E T="03">Notice of disapproval of registration.</E>
                                 If the Board disapproves a completed application for registration by a public accounting firm, the Board shall file a notice of its disapproval with the Commission within 30 days and serve a copy on the public accounting firm. 
                            </P>
                            <P>
                                (2) 
                                <E T="03">Contents of the notice.</E>
                                 The notice required by paragraph (b)(1) of this section shall provide the following information: 
                            </P>
                            <P>(i) The name of the public accounting firm and the public accounting firm's last known address as reflected in the Board's records; </P>
                            <P>(ii) The basis for the Board's disapproval, and a copy of the Board's written notice of disapproval; and </P>
                            <P>(iii) Such other information as the Board may deem relevant. </P>
                            <P>
                                (c)(1) 
                                <E T="03">Notice of disciplinary action.</E>
                                 If the Board imposes any final disciplinary sanction on any registered public accounting firm or any associated person of a registered public accounting firm under 15 U.S.C. 7215(b)(3) or 7215(c), the Board shall file a notice of the disciplinary sanction with the Commission within 30 days and serve a copy on the person sanctioned. 
                            </P>
                            <P>
                                (2) 
                                <E T="03">Contents of the notice.</E>
                                 The notice required by paragraph (c)(1) of this section shall provide the following information: 
                            </P>
                            <P>(i) The name of the registered public accounting firm or the associated person, together with the firm's or the person's last known address as reflected in the Board's records; </P>
                            <P>(ii) A description of the acts or practices, or omissions to act, upon which the sanction is based; </P>
                            <P>(iii) A statement of the sanction imposed, the reasons therefor, or a copy of the Board's statement justifying the sanction, and the effective date of such sanction; and </P>
                            <P>(iv) Such other information as the Board may deem relevant. </P>
                        </SECTION>
                        <SIG>
                            <P>By the Commission. </P>
                            <DATED>Dated: November 23, 2003. </DATED>
                            <NAME>Margaret H. McFarland, </NAME>
                            <TITLE>Deputy Secretary. </TITLE>
                        </SIG>
                    </PART>
                </SUPLINF>
                <FRDOC>[FR Doc. 03-29932 Filed 12-4-03; 8:45 am] </FRDOC>
                <BILCOD>BILLING CODE 8010-01-P</BILCOD>
            </PRORULE>
        </PRORULES>
    </NEWPART>
    <VOL>68</VOL>
    <NO>234</NO>
    <DATE>Friday, December 5, 2003</DATE>
    <UNITNAME>Proposed Rules</UNITNAME>
    <NEWPART>
        <PTITLE>
            <PRTPAGE P="68203"/>
            <PARTNO>Part V</PARTNO>
            <AGENCY TYPE="P">Department of Energy</AGENCY>
            <CFR>10 CFR Part 300</CFR>
            <TITLE>General Guidelines for Voluntary Greenhouse Gas Reporting; Proposed Rule</TITLE>
        </PTITLE>
        <PRORULES>
            <PRORULE>
                <PREAMB>
                    <PRTPAGE P="68204"/>
                    <AGENCY TYPE="S">DEPARTMENT OF ENERGY </AGENCY>
                    <CFR>10 CFR Part 300 </CFR>
                    <RIN>RIN 1901-AB11 </RIN>
                    <SUBJECT>General Guidelines for Voluntary Greenhouse Gas Reporting </SUBJECT>
                    <AGY>
                        <HD SOURCE="HED">AGENCY:</HD>
                        <P>Office of Policy and International Affairs, U.S. Department of Energy. </P>
                    </AGY>
                    <ACT>
                        <HD SOURCE="HED">ACTION:</HD>
                        <P>Proposed rule and opportunity for public comment; proposed revised guidelines. </P>
                    </ACT>
                    <SUM>
                        <HD SOURCE="HED">SUMMARY:</HD>
                        <P>Section 1605(b) of the Energy Policy Act of 1992 (EPACT), 42 U.S.C. 13385(b), directed the Department of Energy (DOE or Department) to issue guidelines establishing a voluntary greenhouse gas reporting program. The guidelines issued by the Department in 1994 to establish the Voluntary Reporting of Greenhouse Gases Program were intentionally flexible to encourage the broadest possible participation. On February 14, 2002, the President directed DOE, together with other involved Federal agencies, to recommend reforms to enhance this voluntary reporting program. The purposes of the proposed revised Guidelines are to establish revised procedures and reporting requirements for filing voluntary reports, and encourage corporations, government agencies, non-profit organizations, households and other private and public entities to submit annual reports of their total entity-wide greenhouse gas emissions, net emission reductions, and carbon sequestration activities that are complete, reliable and consistent. Public comments on these proposed revised Guidelines are solicited and a public workshop has been scheduled to encourage an open exchange of views on this subject. </P>
                    </SUM>
                    <DATES>
                        <HD SOURCE="HED">DATES:</HD>
                        <P>Interested persons should submit written e-mail or written comments by February 3, 2004 to the addresses given below. You may present oral views and data at a public workshop that will be held at the Washington Plaza Hotel, 10 Thomas Circle, NW., Massachusetts Avenue at 14th Street, Washington, DC 20005, on January 12, 2004, from 8 a.m. to 5 p.m. </P>
                    </DATES>
                    <ADD>
                        <HD SOURCE="HED">ADDRESSES:</HD>
                        <P>
                            Send e-mail comments to: 
                            <E T="03">1605bgeneralguidelines.comments@hq.doe.gov.</E>
                             Alternatively, written comments may be sent to: Mark Friedrichs, PI-40; Office of Policy and International Affairs; U.S. Department of Energy; Room 1E190, 1000 Independence Ave., SW., Washington, DC 20585. DOE will hold a public workshop at the following address: Washington Plaza Hotel, 10 Thomas Circle, NW., Massachusetts Avenue at 14th Street, Washington, DC 20005. You may review comments received by DOE, the workshop transcript, and any other related material at the following Web site: 
                            <E T="03">http://www.pi.energy.gov/enhancingGHGregistry/proposedguidelines/generalguidelines.html.</E>
                             If you lack access to the Internet, you may access this Web site by visiting the DOE Freedom of Information Reading Room, 1000 Independence Avenue, SW., Washington, DC. See Section III of the 
                            <E T="02">SUPPLEMENTARY INFORMATION</E>
                             section of this notice for more information about public participation in this proceeding. 
                        </P>
                    </ADD>
                    <FURINF>
                        <HD SOURCE="HED">FOR FURTHER INFORMATION CONTACT:</HD>
                        <P>
                            Mark Friedrichs, PI-40, Office of Policy and International Affairs, U.S. Department of Energy, 1000 Independence Ave., SW., Washington, DC 20585, or email: 
                            <E T="03">1605bgeneralguidelines.comments@hq.doe.gov</E>
                             [Please indicate if your e-mail is a request for information, rather than a public comment.] 
                        </P>
                    </FURINF>
                </PREAMB>
                <SUPLINF>
                    <HD SOURCE="HED">SUPPLEMENTARY INFORMATION:</HD>
                    <EXTRACT>
                        <HD SOURCE="HD1">Table of Contents </HD>
                        <FP SOURCE="FP-2">I. Introduction </FP>
                        <FP SOURCE="FP1-2">A. Background. </FP>
                        <FP SOURCE="FP1-2">B. Process for Finalizing and Implementing Guidelines. </FP>
                        <FP SOURCE="FP-2">II. Discussion of Proposal and Requests for Comments </FP>
                        <FP SOURCE="FP1-2">A. Overview. </FP>
                        <FP SOURCE="FP1-2">B. Defining Reporting Entities. </FP>
                        <FP SOURCE="FP1-2">C. Defining Entity Boundaries. </FP>
                        <FP SOURCE="FP1-2">D. Emission Sources and Sinks Covered. </FP>
                        <FP SOURCE="FP1-2">E. Entity-Wide Reporting of Emissions Inventories. </FP>
                        <FP SOURCE="FP1-2">F. Entity-Wide Emission Reductions. </FP>
                        <FP SOURCE="FP1-2">G. Guidelines for Small Emitters. </FP>
                        <FP SOURCE="FP1-2">H. Emission Reduction Calculations. </FP>
                        <FP SOURCE="FP1-2">1. Reductions in Emissions Intensity. </FP>
                        <FP SOURCE="FP1-2">2. Absolute Reductions in Emissions. </FP>
                        <FP SOURCE="FP1-2">3. Increased Carbon Storage. </FP>
                        <FP SOURCE="FP1-2">4. Avoided Emissions. </FP>
                        <FP SOURCE="FP1-2">5. Project Emission Reductions. </FP>
                        <FP SOURCE="FP1-2">I. Recordkeeping, Report Certification, and Verification. </FP>
                        <FP SOURCE="FP1-2">J. Starting to Report. </FP>
                        <FP SOURCE="FP1-2">K. Report Acceptance. </FP>
                        <FP SOURCE="FP1-2">L. Registration of Emission Reductions. </FP>
                        <FP SOURCE="FP1-2">M. Sustaining Entity Reports of Emissions and Emission Reductions. </FP>
                        <FP SOURCE="FP1-2">N. EIA Database and Summary Reports. </FP>
                        <FP SOURCE="FP1-2">O. Cross-cutting and Other Important Issues. </FP>
                        <FP SOURCE="FP1-2">1. Entity-wide v. Sub-Entity or Project-Only Reporting. </FP>
                        <FP SOURCE="FP1-2">2. Treatment of Certain Small Emissions. </FP>
                        <FP SOURCE="FP1-2">3. Excluding the Effects of Changes in Output on Emissions. </FP>
                        <FP SOURCE="FP1-2">4. Emissions and Reductions Associated With Electricity Generation and Use. </FP>
                        <FP SOURCE="FP1-2">5. Reporting and Registering Changes in Terrestrial Carbon Stocks. </FP>
                        <FP SOURCE="FP1-2">6. Recognizing Emission Offsets. </FP>
                        <FP SOURCE="FP1-2">7. International Emission Reductions. </FP>
                        <FP SOURCE="FP1-2">8. Relationship of Proposed Guidelines to Climate VISION, Climate Leaders and Other Voluntary Programs To Reduce Greenhouse Gas Emissions. </FP>
                        <FP SOURCE="FP-2">III. Opportunity for Public Comment </FP>
                        <FP SOURCE="FP1-2">A. Written Comments. </FP>
                        <FP SOURCE="FP1-2">B. Participation in Public Workshop. </FP>
                        <FP SOURCE="FP-2">IV. Regulatory Review and Procedural Requirements </FP>
                        <FP SOURCE="FP1-2">A. Review Under Executive Order 12866. </FP>
                        <FP SOURCE="FP1-2">B. Review Under the Regulatory Flexibility Act. </FP>
                        <FP SOURCE="FP1-2">C. Review Under the Paperwork Reduction Act. </FP>
                        <FP SOURCE="FP1-2">D. Review Under the National Environmental Policy Act. </FP>
                        <FP SOURCE="FP1-2">E. Review Under Executive Order 13132. </FP>
                        <FP SOURCE="FP1-2">F. Review Under the Treasury and General Government Appropriations Act, 2001. </FP>
                        <FP SOURCE="FP1-2">G. Review Under Executive Order 12988. </FP>
                        <FP SOURCE="FP1-2">H. Review Under the Unfunded Mandates Reform Act of 1995. </FP>
                        <FP SOURCE="FP1-2">I. Review Under the Treasury and General Government Appropriations Act, 1999. </FP>
                        <FP SOURCE="FP1-2">J. Review Under Executive Order 13211. </FP>
                    </EXTRACT>
                    <HD SOURCE="HD1">I. Introduction </HD>
                    <HD SOURCE="HD2">A. Background </HD>
                    <P>Section 1605(b) of the Energy Policy Act of 1992 (EPACT) directed the Department of Energy, with the Energy Information Administration (EIA), to establish a voluntary reporting program and database on emissions of greenhouse gases, reductions of these gases, and carbon sequestration activities (42 U.S.C. 13385(b)). Section 1605(b) required that DOE's Guidelines provide for the “accurate” and “voluntary” reporting of information on: (1) Greenhouse gas emission levels for a baseline period (1987-1990) and thereafter, annually; (2) greenhouse gas emission reductions and carbon sequestration, regardless of the specific method used to achieve them; (3) greenhouse gas emission reductions achieved because of voluntary efforts, plant closings, or state or federal requirements; and (4) the aggregate calculation of greenhouse gas emissions by each reporting entity (42 U.S.C. 13385(b)(1)(A)-(D)). Section 1605(b) contemplates a program whereby voluntary efforts to reduce greenhouse gas emissions can be recorded, with the specific purpose that this record can be used “by the reporting entity to demonstrate achieved reductions of greenhouse gases” (42 U.S.C. 13385(b)(4)). </P>
                    <P>
                        In 1994, after notice and public comment, DOE issued General Guidelines and sector-specific guidelines that established the Voluntary Reporting of Greenhouse Gases Program for recording voluntarily submitted data and information on greenhouse gas emissions and the 
                        <PRTPAGE P="68205"/>
                        results of actions to reduce, avoid or sequester greenhouse gas emissions. The 1994 General Guidelines are appended to today's proposal to provide information with regard to reports that were filed under those Guidelines (The General Guidelines and supporting documents may be accessed at 
                        <E T="03">http://www.eia.doe.gov/oiaf/1605/guidelines.html).</E>
                         The Guidelines were intentionally flexible to encourage the broadest possible participation. They permit participants to decide which greenhouse gases to report, and allow for a range of reporting options, including reporting of total emissions or emissions reductions or reporting of just a single activity undertaken to reduce part of their emissions. From its establishment in 1995 through the 2001 reporting year, 365 entities, including utilities, manufacturers, coal mines, landfill operators and others, have reported their greenhouse gas emissions and/or their emission reductions to EIA. 
                    </P>
                    <P>On February 14, 2002, the President announced a series of programs and initiatives to address the issue of global climate change, including a greenhouse gas intensity reduction goal, energy technology research programs, targeted tax incentives to advance the development and adoption of new technologies, voluntary programs to promote actions to reduce greenhouse gases, and international initiatives. In addition, the President directed the Secretary of Energy, in consultation with the Secretary of Commerce, the Secretary of Agriculture, and the Administrator of the Environmental Protection Agency, to propose improvements to the current Voluntary Reporting of Greenhouse Gases Program required under section 1605(b) of EPACT. These improvements are to enhance measurement accuracy, reliability, and verifiability, working with and taking into account emerging domestic and international approaches. </P>
                    <P>On May 6, 2002, DOE published a Notice of Inquiry soliciting public comments on how best to improve the Voluntary Greenhouse Gas Reporting Program (67 FR 30370). Written comments were received from electric utilities, representatives of energy, manufacturing and agricultural sectors, Federal and State legislators, State agencies, waste management companies, and environmental and other non-profit research and advocacy organizations. </P>
                    <P>On July 8, 2002, after considering public comments, the Secretaries of Energy, Commerce and Agriculture, and the Administrator of the Environmental Protection Agency provided the President with ten recommendations on improvements to the Voluntary Greenhouse Gas Reporting Program. The four agencies also outlined a public process for developing specific revisions to the program Guidelines. Following are the ten recommendations for improving the greenhouse gas reporting program: </P>
                    <P>• Develop fair, objective and practical methods for reporting baselines, reporting boundaries, calculating real results, and awarding transferable credits for actions that lead to real reductions. </P>
                    <P>• Standardize widely accepted, transparent accounting methods. </P>
                    <P>• Support independent verification of registry reports. </P>
                    <P>• Encourage reporters to report greenhouse gas intensity (emissions per unit of output) as well as emissions or emissions reductions. </P>
                    <P>• Encourage corporate or entity-wide reporting. </P>
                    <P>• Provide credits for actions to remove carbon dioxide from the atmosphere as well as actions to reduce emissions. </P>
                    <P>• Develop a process for evaluating the extent to which past reductions may qualify for credits. </P>
                    <P>• Assure the voluntary reporting program is an effective tool for reaching the 18 percent goal. </P>
                    <P>• Factor in international strategies as well as State-level efforts; and </P>
                    <P>• Minimize transaction costs for reporters and administrative costs for the Government, where possible, without compromising the foregoing recommendations. </P>
                    <P>DOE held public workshops in Washington, D.C., Chicago, San Francisco and Houston during November and December of 2002 to receive oral views and information from interested persons. In addition, the U.S. Department of Agriculture sponsored two meetings in January 2003 to solicit input on the accounting rules and guidelines for reporting greenhouse gas emissions in the forestry and agriculture sectors. These workshops and meetings explored in greater depth many of the issues raised in the Notice of Inquiry and addressed in the written comments. The public comment covered a broad range of issues and views diverged widely on some key issues. Generally, there was substantial support for revising the current General Guidelines to enhance their utility and to accomplish the President's climate change goals. </P>
                    <P>DOE today is proposing revised General Guidelines, and subsequently will propose Technical Guidelines, that when effective will modify and replace the guidelines for the Voluntary Reporting of Greenhouse Gases issued by DOE in October 1994. The proposed revised General Guidelines would continue to provide procedures for entities to report their greenhouse gas emissions inventories and a wide range of actions they have taken to reduce, avoid or sequester greenhouse gas emissions. In addition, the proposal would enable entities that meet criteria established by DOE to register such reductions in a database maintained by the Energy Information Administration (EIA). The criteria established by DOE will ensure that units of registered reductions will be comparable with regard to the standards of accuracy, reliability and verifiability. Registered reductions will be recorded in a publicly accessible database. </P>
                    <P>The Secretary of Energy has approved issuance of this notice. </P>
                    <HD SOURCE="HD2">B. Process for Finalizing and Implementing Guidelines </HD>
                    <P>
                        After full consideration of the public comments received, DOE will develop and issue final revised General Guidelines. In parallel, DOE intends to propose Technical Guidelines that will, when finalized, specify the methods and factors to be used in measuring and estimating greenhouse gas emissions, emission reductions, and carbon sequestration. Concurrently with development of the General and Technical Guidelines, DOE's Energy Information Administration will, pursuant to the Paperwork Reduction Act of 1995 (44 U.S.C. Chapter 35), solicit public comment on the reporting elements to be contained in the reporting forms to be used under the revised program Guidelines. With respect to the existing 1994 General Guidelines, DOE intends to publish a 
                        <E T="04">Federal Register</E>
                         notice of termination on the same day that DOE publishes the notice of final rulemaking setting forth the revised guidelines under section 1605(b) of EPACT. Both the notice of termination and the notice of final rulemaking will contain an effective date, which will be the beginning of a future reporting period. 
                    </P>
                    <HD SOURCE="HD1">II. Discussion of Proposal and Requests for Comments </HD>
                    <P>The following section describes the proposed revised General Guidelines, summarizes the rationale for the key elements of the proposal and solicits public comments on a wide range of specific issues. </P>
                    <HD SOURCE="HD2">A. Overview </HD>
                    <P>
                        The proposed revisions to the General Guidelines are designed to enhance the measurement accuracy, reliability and verifiability of information reported 
                        <PRTPAGE P="68206"/>
                        under the 1605(b) program and to contribute to the President's climate change goals. The proposed revised Guidelines will continue to provide considerable flexibility to entities that wish to report emissions or emission reductions in the future, as they have in the past. In addition, the revised Guidelines will provide a means for entities that are able to meet additional requirements to register emission reductions achieved after 2002. This registry will provide special recognition to such emission reductions. 
                    </P>
                    <P>
                        To register emission reductions, reporting entities with substantial emissions (average annual emissions of over 10,000 tons of carbon dioxide (CO
                        <E T="52">2</E>
                        ) equivalent) will need to provide an inventory of their total emissions and calculate the net reductions associated with entity-wide efforts to reduce emissions or sequester carbon. Entities with average annual emissions of less than 10,000 tons of CO
                        <E T="52">2</E>
                         equivalent (small emitters) would be eligible, under certain conditions, to register emission reductions associated with specific activities even without completing an entity-wide inventory or reduction assessment. 
                    </P>
                    <P>The proposed revised Guidelines would enable and encourage entities to report (but not register) emission reductions achieved prior to 2003. The revised Guidelines would also permit entities to report (but not necessarily register) emission reductions associated with specific actions or with specific parts of the entity, even if these reports were not accompanied by entity-wide emissions and reductions reports. </P>
                    <P>The chief executive officer of the company or institution, an agency head, head of household or other responsible official would be required to certify that the reporting entity accurately followed the revised Guidelines for determining emissions, emission reductions and sequestration. Entities would be encouraged to obtain independent verification of the accuracy of their reports, and their compliance with DOE Guidelines. </P>
                    <P>For convenience, the basic elements of the proposed revised guidelines are graphically represented in Figure 1. DOE solicits public comments on this approach and any suggestions of alternative means of achieving the objectives outlined above.</P>
                    <BILCOD>BILLING CODE 6450-01-P</BILCOD>
                    <GPH SPAN="3" DEEP="640">
                        <PRTPAGE P="68207"/>
                        <GID>EP05DE03.000</GID>
                    </GPH>
                    <BILCOD>BILLING CODE 6450-01-C</BILCOD>
                    <PRTPAGE P="68208"/>
                    <HD SOURCE="HD2">B. Defining Reporting Entities </HD>
                    <P>Under the proposed revised Guidelines, the first step in the reporting process is the definition of the corporation, institution, household or other entity that will be submitting reports. At a minimum, entities would have to be legally distinct businesses, institutions, organizations or households, although reporters would be encouraged to define themselves at the highest meaningful level of aggregation. The legal basis for determining whether an entity (or its subparts) is distinct could be derived from any Federal, state or local law (or regulation) governing the entity, including regulations applicable to corporations, partnerships, cooperatives, government agencies, non-profit organizations, households, or other entities. This approach would permit a legally-distinct company, plant or activity to define itself as an entity, even if it is partially-or wholly-owned by another company. In such cases, any registered reductions would accrue only to the reporting entity, rather than the parent company. </P>
                    <P>Given the flexibility inherent in this definition, some companies and institutions could be all or part of a reporting entity at any one of several different levels. For example, an individual electric power generating plant might be owned by a partnership of several different companies or individuals. One of these partners might be an electric utility that owns and operates several other electric generating plants, and a transmission and distribution system. And this utility might, in turn, be owned by a regional holding company that also owns other utilities, as well as other non-electric generating companies. In this case, the reporting entity could be defined as the electric generating plant, the utility or the holding company. The program encourages reporting entities to report at the highest level of meaningful financial and operational control, which in this case is likely to be either the utility or the holding company. DOE solicits comment on whether the proposed guidelines are likely to cause entities to establish boundaries that reflect a higher level of corporate or institutional aggregation, as is desired. DOE also solicits recommendations on what additional provisions might preserve flexibility in the establishment of boundaries while also preventing or further discouraging the shifting of emissions to non-reporting parts of the entity in order to create the appearance of net emission reductions. Finally, DOE solicits comment on the desirability of more prescriptive approaches to the definition of entities, such as a requirement that entity definitions correspond to those used for Federal tax purposes. </P>
                    <P>The Guidelines would require that the name chosen to represent the entity generally correspond to the activity covered by the report. For example, a large multi-product manufacturer should not use its corporate name to report the emissions and emission reductions of just one of its many subsidiaries. However, there may be instances when some, but not all subsidiaries of a large corporation may want to report as a single entity. One reason to report as a single entity might be that certain subsidiaries have a common business activity, while others do not. However, another reason might be that some subsidiaries could demonstrate emission reductions, while others could not. DOE solicits comments on how the Guidelines might provide the flexibility needed by entities with special circumstances, while discouraging abuses of this flexibility that could produce misleading impressions of entity performance. </P>
                    <P>Another question concerns the possible role of trade associations and other third parties as consolidators of entity-specific reports into an aggregate report to DOE. While associations may report information collectively for their memberships under the current guidelines, this may have implications for the accuracy and reliability—and transparency—of reports submitted under the revised guidelines. Should trade associations and other third parties be required to submit some or all of the entity-specific data that might be required by the revised Guidelines? Should the CEOs, other senior officials, or heads of entities be required to certify the accuracy of their companies' reports when submitted to or through trade associations? Should trade associations and other third parties be able to “register emission reductions” or only file reports for the record? </P>
                    <HD SOURCE="HD2">C. Defining Entity Boundaries </HD>
                    <P>To report on an entity-wide basis and to register emissions reductions, reporting entities would have to provide an “entity statement” that meaningfully defines the operations and facilities (such as office buildings or vehicle fleets) covered by their entity-wide reports, and the greenhouse gas sources and sinks encompassed by these operations and facilities. Such operations would include those wholly owned and operated by the entity, and might include those operations that are partially-owned, leased or operated by the entity. Entities would be required to coordinate with other entities that shared ownership of particular operations to ensure that no double counting occurred. Entities would also have to ensure that each annual report consistently used the boundaries identified in prior year reports, unless an explicit description of any changes made and their effects on emissions accompanied the report. In cases where an entity undergoes a significant structural change, it may have to establish a new base year for all or part of its operations, or, in the case of acquisitions, recalculate its original baseline based on the prior year emissions of the acquired plant. </P>
                    <HD SOURCE="HD2">D. Emission Sources and Sinks Covered </HD>
                    <P>
                        Reports would be able to cover any greenhouse gas or sink that is consistent with the definitions established in the General Guidelines. An entity-wide inventory would need to cover all significant (determined by share of total emissions or absolute quantity of emissions), anthropogenic greenhouse gas emission sources within the entity's defined boundaries. Entity-wide reports must also cover all significant emission sinks. Entity-wide reports must encompass, at minimum, all six greenhouse gases specified in the Guidelines, whether emitted directly by the entity's operations and facilities, or indirectly in the generation of purchased electricity, steam or hot (or chilled) water used by the entity. Indirect emissions other than those specifically cited in the Guidelines may be reported separately, but reductions associated with such other indirect emissions may not be registered. Entities also may separately report, but not register, emissions and emission reductions associated with other gases (
                        <E T="03">e.g.</E>
                         chlorofluorocarbons, black soot) that may have significant, quantifiable climate forcing effects, provided that DOE's Technical Guidelines specify the methods for measuring and reporting their emissions. DOE is soliciting comment on criteria for identifying such gases and on procedures for developing the necessary Technical Guidelines. All DOE proposals to permit the reporting of additional gases will be made available for public comment before being put into effect. DOE solicits comment on this approach and on a possible alternative that would permit participating entities to report (but not register) the emissions and emission reductions associated with other gases, even if DOE's Technical Guidelines did not specifically cover such other gases. 
                        <PRTPAGE P="68209"/>
                    </P>
                    <HD SOURCE="HD2">E. Entity-Wide Reporting of Emissions Inventories </HD>
                    <P>
                        To be eligible to register emission reductions, entities with substantial emissions (an annual average in excess of 10,000 tons of CO
                        <E T="52">2</E>
                         equivalent) would need to report annual entity-wide inventories of their emissions and sequestration. Such inventories would provide a basis for assessing the significance of reported emission reductions relative to the entity's total emissions. 
                    </P>
                    <HD SOURCE="HD2">F. Entity-Wide Emission Reductions </HD>
                    <P>
                        To register emissions reductions, entities with average annual emissions over 10,000 tons of CO
                        <E T="52">2</E>
                         equivalent would be required to demonstrate, to the maximum extent practicable, that the reported reductions represent an actual net decrease in entity-wide emissions, as calculated using one or more of the methods allowed by the General and Technical Guidelines. Some entities, such as electricity generators, would be expected to calculate net emission reductions for their entire entity (using one or more of the methods described below and in the Technical Guidelines). Others, such as multi-product manufacturers, may not be able to determine the net emission reductions achieved by all elements of their entity using the methods allowed by the Guidelines. These types of reporters could report the net emission reductions for as much of their entity as was practicable, in addition to reporting their entity-wide emission inventories. 
                    </P>
                    <EXAMPLE>
                        <HD SOURCE="HED">Example:</HD>
                        <P>A multi-product manufacturer has instituted company-wide efforts to reduce emissions, but because its U.S. output is growing rapidly, its absolute U.S emissions have not declined. By using different calculation methods (intensity for many facilities and absolute emissions for others, as well as some project-specific calculations) it can quantify the emission reductions associated with 90% of its total emissions. It would report its total emissions and quantified emission reductions to DOE, and explain that it is not practicable to quantify the emission reductions associated with the remaining 10% of its operations because there are no year-to-year measures of output for these operations (because they involved the production of totally new products). In this case, the entity could register its reported emission reductions, but the data submitted in its report would clearly indicate that these reductions were based on an assessment of just 90 percent of the entity's emissions. </P>
                        <P>
                            Net emission reductions achieved by third parties (offsets) could be included in an entity's report and be registered as long as the third party or other entity involved observed all of the rules that would have applied had it chosen to report its net emission reductions directly, and the entities involved have agreed that the reporting entity can register the emission reductions identified (
                            <E T="03">see</E>
                             section II.O.5 below for additional discussion on the treatment of offsets). 
                        </P>
                    </EXAMPLE>
                    <P>The proposed Guidelines indicate that the owner of the facility, land or vehicle that generated the emission reductions or sequestration is the entity presumed to have the right to report and register any emission reductions or sequestration. For example, the owner of a wind turbine that sells its power to the grid is presumed to have the right to register such resulting emission reductions, even though this wind-generated electricity might be purchased at a premium by a local utility and, ultimately, resold at a premium rate to a local manufacturer. This presumption can be altered, however, if there is a written agreement between the entities involved to transfer this right. </P>
                    <HD SOURCE="HD2">G. Guidelines for Small Emitters </HD>
                    <P>
                        Entities with average annual emissions of less than 10,000 tons of CO
                        <E T="52">2</E>
                         equivalent, such as many farms and forest operations, small businesses and individuals, could report and register emission reductions that have occurred during and after 2003 without submitting the results of an entity-wide emissions inventory or an entity-wide assessment of the annual changes in their emissions, avoided emissions and sequestration. Entities reporting under this provision would be required to determine the total annual emissions and sequestration associated with the type of activities on which they choose to report, the net emission changes associated with these specific activities, and to certify that the changes reported were not caused by actions likely to cause increases in emissions elsewhere within the entity's operations. Small emitters would be required to use the same methods for calculating emission reductions available to other reporters. DOE's Technical Guidelines will provide a list of the types of activities about which small emitters might report. It is expected that households and many small businesses, farms, and forest operations would be exempt from the requirement to submit entity-wide inventories. The use of a multi-year average rate of emissions is intended to enable certain small entities that have periodic spikes in their annual emissions (for example, a land owner that periodically harvests trees) to qualify for this exemption. Comments are specifically solicited on (1) whether 10,000 tons of CO
                        <E T="52">2</E>
                        -equivalent emissions would be the appropriate threshold quantity to achieve this objective, and (2) the appropriate period of time over which small entities should be permitted to average their annual emission rates. DOE is also soliciting comments on whether these special rules for small emitters are appropriate and how to ensure that reductions reported by small emitters are not a result of shifting emissions to non-reporting parts of the entity. 
                    </P>
                    <HD SOURCE="HD2">H. Emission Reduction Calculations </HD>
                    <P>All reported and registered emission reductions would have to be calculated using one of the methods identified below, together with the procedures to be set forth in DOE's Technical Guidelines. The proposed revised General Guidelines recommend the use of emission intensity indicators as the basis for determining emission reductions, but would permit the use of several other methods to calculate emission reductions and sequestration as long as the method used excludes reductions caused by reductions in output. Regardless of the method used, a reporting entity would have to certify that none of the reported emission reductions were: Double counted by the reporting entity (or, to its knowledge, by any other reporting entity); or were the result of shifts in operations or activity from one part of the entity to another part of the entity, or to outside the boundaries of the entity. Entities would be required to report each emission reduction and sequestration calculation by type, indicate the types of actions taken that resulted in the reported emission reduction, and explain the selection of each indicator of output used. Comments are invited on the appropriateness of each of the methods described below and on the definitions provided in the proposed Guidelines. Additional guidance on each of these methods will be provided in the Technical Guidelines, including lists of possible output indicators, calculation methods for determining reductions associated with agricultural, forestry and geologic sequestration, methods and emission factors for calculating avoided emissions, and project-based methods, among others. </P>
                    <P>
                        1. 
                        <E T="03">Reductions in emissions intensity,</E>
                         as long as the reporting entity demonstrates that the intensity metrics used are based on measured (or estimated) emissions and measured indicators of output that accurately represent the physical (or, in some cases, economic) output associated with the covered emissions, and that acquisitions, divestures or changes in products have not contributed significantly to the reductions. 
                    </P>
                    <P>
                        2. 
                        <E T="03">Absolute reductions in emissions,</E>
                         as long as the entity demonstrates that these measured reductions were not caused by declines in its U.S. output. 
                        <PRTPAGE P="68210"/>
                    </P>
                    <P>
                        3. 
                        <E T="03">Increased carbon storage</E>
                         (for actions within entity boundaries), as long as the entity demonstrates the sequestration measured or estimated represents a net increase in the quantity stored by the entity and has not been re-released to the atmosphere (ongoing, annual reports would be required). 
                    </P>
                    <P>
                        4. 
                        <E T="03">Avoided emissions</E>
                         (for actions within entity boundaries that reduce emissions outside entity boundaries) that reflect the indirect emission reductions achieved as a result of a measured increase in the net sales of energy generated by low-or no-emission technologies. 
                    </P>
                    <P>
                        5. 
                        <E T="03">Project emission reductions</E>
                         (for actions taken to reduce direct or indirect emissions within entity boundaries), as long as they exclude any reductions that might have resulted from reduced output or from shifting emissions to operations not included in the reported projects, and are derived from measured performance data or by using estimation methods consistent with DOE Technical Guidelines. In the context of entity-wide reports, this last calculation method is intended only for use when none of the other methods is practicable. 
                    </P>
                    <HD SOURCE="HD2">I. Recordkeeping, Report Certification, and Verification </HD>
                    <P>Reporters under the existing program must certify the accuracy of their reports, but are not required to maintain records. Under the proposed revised Guidelines, the chief executive officer, agency head, head of household or person responsible for the reporting entity's compliance with environmental regulations would certify that reports are complete, accurate and consistent with DOE guidelines, and that sufficient records will be maintained for at least three years to enable independent verification. Reporting entities are strongly encouraged to obtain independent verification of their reports. The proposed Guidelines describe what would constitute such verification, including a description of the types of firms or institutions that might be qualified to independently verify the entity's reports, and the elements of an entity's records and reports that should be verified. </P>
                    <P>The proposed General Guidelines would require reports to EIA that are sufficiently detailed to enable EIA to review and confirm the final emission reduction calculations for each method and output measure utilized, and to review and confirm the rates of conversion used for each category of greenhouse gas covered and for electricity-related use or emissions avoidance, by region. EIA's review of the data submitted would be intended to assure consistency with the requirements specified in the General and Technical Guidelines. This level of reporting would indicate the basic components of each entity's emission inventory and of its entity-wide emission reductions. Entities would be required to maintain more detailed records, sufficient to permit an independent verification. The proposed levels of data reporting and recordkeeping represent a middle ground between the views of stakeholders who favor summary data and those stakeholders who prefer more detailed data that would be the basis for independent verification. </P>
                    <P>The proposal limits the recordkeeping requirement to three years. Of course, reporting entities may keep their records for a longer period of time if they deem it in their interest to do so. </P>
                    <P>The proposed Guidelines would require that the chief executive officer or other senior official of the reporting entity certify the accuracy, consistency and completeness of all reports. In addition, the Guidelines would encourage, but not require, independent verification of all reports. The proposed Guidelines would provide only general guidance on what DOE considers the necessary qualifications of verifiers and the information that they must verify. This guidance is intended to provide some assurance that such verifiers are independent and appropriately qualified, while still giving entities considerable flexibility in the selection of the type of firm most appropriate to perform such an independent verification. DOE invites comments on whether the general guidance provided is sufficient to achieve this objective. </P>
                    <P>While some stakeholders believe that independent verification should be required of all reports, many felt that independent verification is only necessary if entities seek to sell their registered emission reductions and, in such cases, private markets are likely to specify the type of independent verification required. While DOE received many comments that questioned the credibility of many of the emission reductions reported under the existing program, most of these concerns related to the methodology used to calculate the reported reductions, rather than the validity of the data used or reported. While DOE believes that requiring a senior officer to certify reports will provide adequate assurance that the data reported are reliable, the proposed Guidelines would strongly encourage reporters to obtain independent verification. DOE solicits public comment on this approach and on whether further consideration should be given to requiring independent verification of emission reductions prior to registration. </P>
                    <HD SOURCE="HD2">J. Starting To Report </HD>
                    <P>
                        Under the proposed revised Guidelines, entities would be permitted to begin reporting their prior-year emissions and emission reductions at any time. In general, the first full year for which an emissions inventory is available would be considered the entity's base year, although DOE would encourage entities to determine their base year by calculating the average emissions or emissions intensity during a base period of up to four years in length. This flexibility would permit a reporter to select the base year or base period most representative of actual operations. It may also, however, allow a reporter to select the most advantageous base year or base period (
                        <E T="03">i.e.</E>
                        , a period that would enable the reporter to register the greatest amount of reductions). DOE solicits comments on whether this flexibility is appropriate and, if not, what steps might be taken to limit this flexibility. To focus the program on current and future efforts to reduce greenhouse gas emissions, entities would be permitted to register only those emission reductions calculated using a base year no earlier than 2002 (or base period of up to four sequential years ending no earlier than 2002). However, entities may still report emission inventories and reductions for previous years, as long as any prior year emission reductions are calculated using a base year no earlier than 1990 (or a base period no earlier than 1987-1990). To be accepted as entity-wide reports under the revised Guidelines, emission reductions already reported to the 1605(b) registry must be recast to fully comply with the revised Guidelines. 
                    </P>
                    <HD SOURCE="HD2">K. Report Acceptance </HD>
                    <P>Upon receipt, EIA would review all reports to ensure consistency with the revised Guidelines. If EIA determines the report follows the General and Technical Guidelines, and EIA's Reporting Form Instructions, the report would be classified as either an entity-wide report or otherwise, and accepted. </P>
                    <HD SOURCE="HD2">L. Registration of Emission Reductions </HD>
                    <P>
                        Accepted entity-wide reports and reports from small emitters would then be further reviewed to determine if reductions were eligible to be registered. Entity-wide reports and reports from small entities that have used the methods identified in the General and Technical Guidelines, as well as EIA's Reporting Form Instructions, to 
                        <PRTPAGE P="68211"/>
                        demonstrate they have achieved emission reductions after 2002 and have met all other applicable requirements would have the identified reductions registered in the 1605(b) database under the name of reporting entity and the year the reduction was achieved. 
                    </P>
                    <P>
                        Registering only reductions that are achieved after 2002 would focus the program on those reductions most likely to contribute to the achievement of the President's goal for reducing U.S. emissions intensity by 18% between 2002 and 2012. In addition, because all of the data required to register reductions would be relatively recent, it would help ensure that all entities have an equal opportunity to register emission reductions under the new program. Nevertheless, the revised Guidelines would continue to permit entities to 
                        <E T="03">report</E>
                         emission reductions back to 1991, the earliest year permitted by the authorizing statute, and reports that comply with the Guidelines would be made publicly available by EIA. DOE solicits public comments on this approach and any suggestions of alternative means of achieving the objectives outlined above. 
                    </P>
                    <HD SOURCE="HD2">M. Sustaining Entity Reports of Emissions and Emission Reductions </HD>
                    <P>To register emission reductions in any future year, an entity would be required to submit ongoing annual reports that document the net, cumulative emission reductions achieved relative to the entity's base year (or base period). Only additions to cumulative emission reductions (relative to the chosen base year or base period) would be recognized in future years. This requirement would reduce the quantity of emission reductions eligible for registration in future years if the reporting entity experiences a net increase in output-adjusted emissions after beginning to report. This approach would preserve the recognition given to all previously registered emission reductions, even if an entity experienced net emission increases in the future or stopped reporting. DOE solicits comments on this approach and possible alternatives, including those that might permit or require DOE to delete previously registered emission reductions if an entity did not continue to submit annual reports. Ongoing, annual reporting would be required to maintain recognition for registered emission reductions resulting from sequestration. </P>
                    <HD SOURCE="HD2">N. EIA Database and Summary Reports. </HD>
                    <P>The EIA Administrator would establish a public database including all data that meets the definitional, measurement, calculation and certification requirements of the revised Guidelines. The database would provide summary information on each reporting entity's greenhouse gas emissions and its registered emission reductions, by year, according to the categories described above. The database would also provide access to all accepted reports. </P>
                    <HD SOURCE="HD2">O. Cross-Cutting and Other Important Issues</HD>
                    <P>This section discusses various issues that affect more than one provision of the proposed revised Guidelines or were not highlighted in any of the preceding sections. DOE is seeking public comment on all of these issues, and certain specific questions are posed. </P>
                    <HD SOURCE="HD3">1. Entity-Wide v. Sub-Entity or Project-Only Reporting</HD>
                    <P>The proposed Guidelines would highlight the net contribution of reporting entities to reducing greenhouse gas emissions, rather than sub-entity reductions resulting from actions taken in only some parts (rather than the whole) of the entity. This reflects the Administration's interest in fostering broad efforts by corporations, institutions and other entities to reduce their total emissions. Over time, individual companies and other entities often take many actions that either increase or decrease their emissions of greenhouse gases. It is the net effect of all of these actions on an entity's emissions that is the most important indicator of an entity's contribution to the President's goal of reducing U.S. emissions intensity. Under the revised Guidelines, most reporters would be able to register emission reductions only if they could demonstrate they had achieved a net reduction in their total emissions, relative to their physical or economic output. Small emitters, such as households, and some farms, forest operations, and small businesses, would be permitted to register the reductions achieved in just one area of activity, such as building operations or forestry, rather than accounting for all of their emissions, so long as they certify that these reductions are not a product of shifting emissions to non-reporting parts of the entity. In addition, the proposed Guidelines would continue to provide a mechanism for large emitters to report, but not register, the reductions resulting from individual actions or projects affecting a part of the entity's emissions, even if they could not demonstrate that they had achieved a net reduction in their total emissions, relative to their physical or economic output. DOE solicits comments on this approach and on possible alternatives to this approach, including circumstances under which project-based or sub-entity reductions might be registered in the absence of net entity wide reductions. </P>
                    <HD SOURCE="HD3">2. Treatment of Certain Small Emissions </HD>
                    <P>
                        The proposed Guidelines would permit reporters to exclude certain emissions that are comparatively small, as well as all non-anthropogenic emissions. Specifically, an entity could exclude emissions from multiple sources (and multiple gases) as long as the total emissions excluded did not exceed 3% of its total emission inventory or 10,000 tons of CO
                        <E T="52">2</E>
                         equivalent, whichever was smaller. This exclusion is intended to enable entities to exclude small, and possibly widely dispersed, emissions that are likely to be especially costly to monitor and report, but which would have little effect on the total emissions or emission reductions reported. However, this approach has some potential drawbacks. For example, very large emitters, such as large power generators or large energy intensive industries applying this standard would have to account for a very high percentage of their total emissions (in some cases over 99.9%). Accounting for such a high percentage of total emissions could be burdensome and would have little effect on the totals reported. Several possible alternatives exist. One option might be to provide for uniform percentage exclusion, such as permitting all entities to exclude up to 3 percent of their emissions. This could lead some large utilities or industries to exclude large quantities of emissions that would be relatively easy to include in their reports. Another possible alternative is the addition of a minimum percentage exclusion, such as 1 percent. Still another alternative might be to permit firms to exclude up to 3 percent or 10,000 tons of CO
                        <E T="52">2</E>
                         equivalent, whichever is greater. DOE solicits comments on the approach proposed, as well as various alternatives approaches. 
                    </P>
                    <HD SOURCE="HD3">3. Excluding the Effects of Changes in Output on Emissions </HD>
                    <P>
                        The proposed Guidelines would strongly encourage the use of emissions intensity indicators as the basis for calculating emission reductions and would require that any method used to calculate emission reductions ensure that reductions caused by declines in the reporting entity's output be excluded. This would require entities to develop useful physical (and/or possibly economic) indicators of the output associated with the emissions being assessed. For power generators 
                        <PRTPAGE P="68212"/>
                        supplying electricity to the grid, the preferred measure of output is clear: kilowatt hours. Certain large manufacturers also have well-established measures of output that have already been widely used for many years, such as tons of cement. But many product manufacturers may have some difficulty identifying useful output indicators especially if they desire to develop indicators that represent the output associated with a large a number of different processes and products. Broad physical units, such a pounds of product (sometimes used by chemical manufacturers), often encompass a wide range of different products, and a similarly wide range of production processes and product values. As a result, some important shifts between processes or product types may not be captured by such a broad indicator. As an alternative, some entities might consider the use of economic indicators, although analysis of some entity-level economic indicators suggests that they may be significantly affected by changes in market conditions and may serve as poor indicators of production-related changes by individual entities. DOE intends to identify in the Technical Guidelines various output indicators and provide guidance on the selection of appropriate indicators. DOE may specify the use of particular indicators for certain types of economic activity, but is likely to give most reporters the flexibility to adopt the best indicators for their particular circumstances. Given the potential deficiencies of some output indicators, DOE invites public comment on what information entities should be required to provide to justify the selection of their output indicators and what criteria DOE should use to determine whether a particular output measure is acceptable. 
                    </P>
                    <P>A related issue concerns entities that base their emission reductions on changes in their “absolute” emissions. The proposed Guidelines would require such entities to demonstrate that any reported reductions were not associated with declines in the output associated with those emissions. Because entities should only use this approach if they could not develop an output indicator that would enable them to track their emissions intensity, they may have difficulty demonstrating that their output had not declined. Again, DOE is interested in receiving comments on what output measures or other information such entities should be required to provide to demonstrate that their output has not declined and what criteria DOE might use to determine whether the information provided was sufficient. </P>
                    <HD SOURCE="HD3">4. Emissions and Reductions Associated With Electricity Generation and Use </HD>
                    <P>Several key provisions of the Guidelines deal with how entities are to report emissions and emission reductions associated with electricity generation and use. Approximately 32 percent of total U.S. emissions of greenhouse gases are released in the generation of electricity. As there are substantial opportunities to reduce the emissions associated with both the generation and use of electricity, it is important that the program cover both electricity generators and consumers. In doing so, however, it is also important to ensure: (1) That electricity-related emissions and emission reductions are not double counted; (2) that the conversion factors used to translate kilowatt hours into emissions are accurate indicators of the actual emissions associated with the generation of the electricity; and (3) that recognition for reductions is given to those entities primarily responsible for those reductions. Both these proposed General Guidelines and the Technical Guidelines, to be proposed subsequently, will attempt to achieve these objectives. </P>
                    <P>To avoid double counting, the proposed General Guidelines would require users to distinguish between the “indirect” emissions associated with electricity purchases (as well as purchased steam, and chilled/hot water) and their direct emissions. This will enable entity-level emission inventories to include such indirect emissions, while permitting DOE to exclude such emissions from compilations of multiple reports, if desired. In the Technical Guidelines, DOE will specify the factors to be used to convert purchased electricity use to greenhouse gas emissions. For the purposes of emission inventories, DOE is likely to specify a factor based on the average emissions per kilowatt hour for the region in which the electricity was consumed. However, for the purpose of calculating emission reductions associated with reduced electricity demand, DOE may specify an alternative factor, such as one based on the emissions associated with regional electricity supplies at the margin (largely excluding electricity generated by hydro, nuclear power plants and some coal, which tend to be fully utilized, regardless of changes in regional demand for power). These factors might change annually and could be required to be used by all consumers of purchased electric power, unless the reporter could demonstrate special circumstances. </P>
                    <P>
                        There may be two methods for determining emission reductions associated with the generation of electricity. One method might be used to calculate reductions in the emissions intensity of existing power production (
                        <E T="03">e.g.</E>
                        , through fuel switching or increased efficiency) and the other might be used to calculate the indirect reductions (or avoided emissions) that result from increasing the electric power generation from non-emitting or low-emitting sources. DOE is seeking to provide recognition to existing power generators that reduce their emissions intensity, while also establishing a level playing field among producers of new or additional power supplies, and end-users of electricity that reduce their demand. 
                    </P>
                    <P>DOE intends to provide, through its Technical Guidelines, clear direction on how to calculate emission reductions associated with the generation and purchase of electricity. While the specific methodologies and factors to be used have yet to be defined, DOE is soliciting suggested approaches that would achieve the objectives identified, as well as specific recommendations on how to develop the conversion factors described and how to most appropriately distinguish between existing and new power production and emissions. </P>
                    <HD SOURCE="HD3">5. Reporting and Registering Changes in Terrestrial Carbon Stocks </HD>
                    <P>
                        The proposed guidelines would require entity-wide emission inventories to include emissions and sequestration associated with terrestrial carbon stocks. Changes in the amount of carbon stored in sinks within the entity's boundaries over the inventory year would determine the quantities of such emissions and sequestration included in inventories. Entities that meet all of the relevant requirements in the general and technical guidelines may also register year-to-year increases in carbon stocks as “registered reductions.” Ongoing reporting will be required to ensure that any future changes in these stocks are fully reflected in the entity's emission inventories and registered emission reductions. The Department seeks comments on this provision as well as alternatives. For example, one alternative approach would calculate registered reductions as the change in carbon stocks during an inventory year relative to the change in stocks during a base year or period. 
                        <PRTPAGE P="68213"/>
                    </P>
                    <HD SOURCE="HD3">6. Recognizing Emission Offsets </HD>
                    <P>As proposed, the General Guidelines would permit entities to report and register emission reductions achieved by others, as long as the entity that achieved the reductions observed all of the requirements applicable to reporters and the entities involved indicated that they had an agreement stipulating who would report the emission reductions. These provisions are designed to enable and encourage large emitters to support efforts to reduce emissions outside the boundaries of their entities. DOE believes this may be especially desirable when the opportunities for reducing emissions within an entity's boundaries are comparatively limited or costly. However, these provisions raise a number of issues upon which DOE is seeking public comment. </P>
                    <P>Most of these issues concern the information that must be submitted by a reporting entity about the emission reductions achieved by a non-reporting entity. For example, must the reporting entity provide all of the information that the non-reporting entity would have been required to submit directly, including an Entity Statement, an emissions inventory (unless exempted), and an entity-wide assessment of emission reductions (unless exempted)? Must the chief executive officer or other senior manager of the non-reporting entity certify to the accuracy of all of the information reported by the reporting entity? Could a non-reporting entity enter into agreements permitting some of its emission reductions to be registered by one entity and the remainder by one or more other entities? Must the reporting entity demonstrate that it helped finance or manage the achievement of the emission reductions achieved by some other entity? One approach that might avoid many of these potential issues would be to require direct reporting by all entities that generate emission reductions. This approach would ensure that complete reports, submitted directly by the entity that owned the facilities or land that produced the emission reductions, would be available for all registered emission reductions. But requiring direct reports by all entities might discourage emission reductions by entities that are unwilling to report directly and might discourage support for such offset projects by large emitters, such as utilities. DOE solicits comments on the approach proposed and on possible alternatives. </P>
                    <HD SOURCE="HD3">7. International Emission Reductions </HD>
                    <P>
                        The proposed revised Guidelines do not address either the reporting of non-U.S. emissions and emission reductions or the registration of non-U.S. emissions reductions. DOE is soliciting public comments on whether non-U.S. emissions and emission reductions should continue to be eligible for reporting under the revised program, recognizing that the current guidelines provide for reporting of international activities.
                        <SU>1</SU>
                        <FTREF/>
                         DOE is also soliciting public comments on whether non-U.S. emissions and emission reductions should qualify for registration and, if so, what procedures and requirements should be established for registration of such emissions and emission reductions. 
                    </P>
                    <FTNT>
                        <P>
                            <SU>1</SU>
                             Since the current Guideline became effective in 1994, DOE has interpreted the Congressional intent underlying the statute to allow for the reporting of international activities.
                        </P>
                    </FTNT>
                    <P>Many factors are relevant to how non-U.S. emissions and emission reductions should be treated under the program with respect to both reporting and registration. Since 1994, many entities have reported on overseas activities; many companies likely to participate in the revised program have substantial business operations both inside and outside the United States. At the same time, reporting and registration of non-U.S. emissions and emission reductions raise certain issues that do not arise in the context of the reporting and registration of U.S. emissions and emission reductions. (For example, certifying the accuracy of data may be more complicated.) </P>
                    <P>In addition to requesting comment on the overall issue of whether to include international activities, DOE specifically requests comment on the following questions: How would the concept of “entity-wide” reporting be extended to include non-U.S. activities? Should an entity wishing to report non-U.S. emission reductions achieved in its own non-U.S. operations be required to inventory and report on all non-U.S. emissions and to assess changes in its emissions worldwide? Or should such entity only be required to report on its non-U.S. operations in specific countries? What requirements should third-party non-U.S. offsets be required to meet? To be eligible for registration, should reports of non-U.S. emissions reductions require independent verification? What would be the implications, including for participation in the 1605(b) program, if non-U.S. activities were excluded from reporting and/or registration? </P>
                    <HD SOURCE="HD3">8. Relationship of Proposed Guidelines to Climate VISION, Climate Leaders and Other Voluntary Programs To Reduce Greenhouse Gas Emissions </HD>
                    <P>DOE, the Environmental Protection Agency and other Federal agencies have established programs to encourage companies, trade associations and other non-government organizations to take voluntary actions to reduce, sequester, or avoid greenhouse gas emissions. For example, industry participants in DOE's “Climate VISION” program, a Presidential initiative launched in February 2003, and EPA's Climate Leaders program have made voluntary commitments to reduce GHG emissions or emissions intensity by a specified amount, and to monitor and report on their progress. </P>
                    <P>The Administration intends to use the 1605(b) program to document, where possible, the progress of participants in these voluntary Federal programs. This is consistent with the President's desire that the 1605(b) registry be a “tool that goes hand-in-hand with voluntary business challenges * * * by providing a standardized, credible vehicle for reporting and recognizing progress.” However, additional reporting may be required for other specific voluntary Federal programs in order to provide distinct benefits to program participants. </P>
                    <P>DOE is soliciting comment on the merits of using the 1605(b) program for documenting progress of participants in voluntary Federal programs towards meeting their emissions reduction goals. </P>
                    <HD SOURCE="HD1">III. Opportunity for Public Comment </HD>
                    <HD SOURCE="HD2">A. Written Comments </HD>
                    <P>
                        You should submit written comments by February 3, 2004. Because we continue to experience occasional mail delays due to extra processing required for delivery of mail to Federal agencies, we encourage you to submit comments electronically by e-mail at 
                        <E T="03">1605bgeneralguidelines.comments@hq.doe.gov.</E>
                         We will consider comments received after the comment deadline only to the extent practicable. Comments should be submitted to the e-mail or street addresses given in the 
                        <E T="02">ADDRESSES</E>
                         section of this notice. Written comments should be identified on the documents themselves and on the outside of the envelope, or in the e-mail message, with the designation [insert name of rulemaking and docket number]. All comments received and transcripts of any public workshop held will be available for public inspection at the following Web site: 
                        <E T="03">
                            http://www.pi.energy.gov/
                            <PRTPAGE P="68214"/>
                            enhancingghgregistry/proposedGuidelines/comments.
                        </E>
                         Persons without access to the internet can obtain such access to this Web site by visiting the DOE Freedom of Information Reading Room, Room 1E-190, Forrestal Building, 1000 Independence Avenue, SW., Washington, DC 20585, (202) 586-3142, between 9 a.m. and 4 p.m., Monday through Friday, except Federal holidays. 
                    </P>
                    <P>If you submit information that you believe to be exempt by law from public disclosure, you should submit one complete hardcopy and two hardcopies from which the information claimed to be exempt by law from public disclosure has been deleted. DOE is responsible for the final determination with regard to disclosure or non-disclosure of the information and for treating it accordingly under the DOE Freedom of Information Act regulations at 10 CFR 1004.11. </P>
                    <HD SOURCE="HD2">B. Participation in Public Workshop </HD>
                    <P>
                        You will find the time and place of the public workshop at the beginning of this notice. We invite any person who has an interest in today's notice, or who is a representative of a group or class of persons that has an interest in these issues, to participate in the workshop. Because space may be limited, persons wishing to participate in the workshop should inform DOE by identifying the person or persons likely to attend, an e-mail or phone number for follow-up contacts, and providing a brief description of the specific issues of particular interest. This information may be provided electronically at the following Web site: 
                        <E T="03">http://www.pi.energy.gov/enhancingGHGregistry/proposedguidelines/generalguidelines.html</E>
                         or may be provided in writing to the person listed in the beginning of this notice. 
                    </P>
                    <P>
                        DOE will designate a DOE official to preside at the workshop, and may also use a professional facilitator to facilitate discussion. The workshop will not be conducted under formal rules governing judicial or evidentiary-type proceedings, but DOE reserves the right to establish procedures governing the conduct of the workshop. The workshop will be organized so as to encourage the open discussion of specific issues by the range of stakeholders and government representatives present. Prior to the workshop a draft agenda, identifying specific issues for discussion, will be made available at the following Web site: 
                        <E T="03">http://www.pi.energy.gov/enhancingGHGregistry/proposedguidelines/generalguidelines.html.</E>
                         There will also be opportunities during the workshop for the identification and discussion of issues not specifically identified on the agenda. The presiding official will announce any further procedural rules, or modification of the above procedures, needed for the proper conduct of the workshop. Statements for the record of the workshop will be accepted at the workshop. 
                    </P>
                    <P>
                        DOE will make the entire record of the rulemaking, including the workshop transcript, available for inspection at the following Web site: 
                        <E T="03">http://www.pi.energy.gov/enhancingGHGregistry/proposedguidelines/generalguidelines.html.</E>
                         In addition, any person may purchase a copy of the transcript from the transcribing reporter. 
                    </P>
                    <HD SOURCE="HD1">IV. Regulatory Review and Procedural Requirements </HD>
                    <HD SOURCE="HD2">A. Review Under Executive Order 12866 </HD>
                    <P>Today's action has been determined to be “a significant regulatory action” under Executive Order 12866, “Regulatory Planning and Review” (58 FR 51735, October 4, 1993). Accordingly, this action was subject to review under that Executive Order by the Office of Information and Regulatory Affairs of the Office of Management and Budget (OMB). </P>
                    <HD SOURCE="HD2">B. Review Under the Regulatory Flexibility Act </HD>
                    <P>
                        The Regulatory Flexibility Act (5 U.S.C. 601 
                        <E T="03">et seq.</E>
                        ) requires preparation of an initial regulatory flexibility analysis for any rule that by law must be proposed for public comment, unless the agency certifies that the rule, if promulgated, will not have a significant economic impact on a substantial number of small entities. As required by Executive Order 13272, “Proper Consideration of Small Entities in Agency Rulemaking” (67 FR 53461, August 16, 2002), DOE published procedures and policies to ensure that the potential impacts of its draft rules on small entities are properly considered during the rulemaking process (68 FR 7990, February 19, 2003), and has made them available on the Office of General Counsel's Web site: 
                        <E T="03">http://www.gc.doe.gov.</E>
                         DOE has reviewed today's proposed Guidelines under the provisions of the Regulatory Flexibility Act and the procedures and policies published on February 19, 2003. Although section 1605(b)(1) of EPACT mandates a public comment opportunity before Guidelines can be issued, the proposed guideline provisions are policy statements and procedural rules. They are not substantive regulatory requirements that would have an economic impact on small entities. On the basis of the foregoing, DOE certifies that the proposed Guidelines, if promulgated, would not have a significant economic impact on a substantial number of small entities. Accordingly, DOE has not prepared a regulatory flexibility analysis for this rulemaking. 
                    </P>
                    <HD SOURCE="HD2">C. Review Under the Paperwork Reduction Act </HD>
                    <P>
                        The Energy Information Administration previously obtained Paperwork Reduction Act clearance by the Office of Management and Budget (OMB) for forms used in the current Voluntary Reporting of Greenhouse Gases program (OMB Control No. 1905-0194). EIA will prepare new forms and associated instructions to implement the revised guidelines for the program, and it will publish a separate notice in the 
                        <E T="04">Federal Register</E>
                         requesting public comment on the proposed collection of information in accordance with 44 U.S.C. 3506(c)(2)(A). After considering the public comments, EIA will submit the new forms, instructions, and related guidelines to OMB for approval pursuant to 44 U.S.C. 3507(a)(1). 
                    </P>
                    <HD SOURCE="HD2">D. Review Under the National Environmental Policy Act </HD>
                    <P>
                        DOE has concluded that this proposed rule falls into a class of actions that would not individually or cumulatively have a significant impact on the human environment, as determined by DOE's regulations implementing the National Environmental Policy Act of 1969 (42 U.S.C. 4321 
                        <E T="03">et seq.</E>
                        ). This action deals with the procedures and policies for entities that wish to voluntarily report their greenhouse gas emissions and their reduction and sequestration of such emissions to the Energy Information Administration. Because the proposed Guidelines relate to agency procedures and impose no substantive requirement on those entities wishing to report, the proposed Guidelines are covered under the Categorical Exclusion in paragraph A6 to subpart D, 10 CFR part 1021. Accordingly, neither an environmental assessment nor an environmental impact statement is required. 
                    </P>
                    <HD SOURCE="HD2">E. Review Under Executive Order 13132 </HD>
                    <P>
                        Executive Order 13132, “Federalism” (64 FR 43255, August 4, 1999) imposes certain requirements on agencies formulating and implementing policies or regulations that preempt State law or that have federalism implications. Agencies are required to examine the constitutional and statutory authority supporting any action that would limit 
                        <PRTPAGE P="68215"/>
                        the policymaking discretion of the States and carefully assess the necessity for such actions. The Executive Order also requires agencies to have an accountable process to ensure meaningful and timely input by State and local officials in the development of regulatory policies that have federalism implications. On March 14, 2000, DOE published a statement of policy describing the intergovernmental consultation process it will follow in the development of such regulations (65 FR 13735). DOE has examined today's proposed action and has determined that it does not preempt State law and does not have a substantial direct effect on the States, on the relationship between the national government and the States, or on the distribution of power and responsibilities among the various levels of government. No further action is required by Executive Order 13132. 
                    </P>
                    <HD SOURCE="HD2">F. Review Under the Treasury and General Government Appropriations Act, 2001 </HD>
                    <P>The Treasury and General Government Appropriations Act, 2001 (44 U.S.C. 3516, note) provides for agencies to review most disseminations of information to the public under guidelines established by each agency pursuant to general guidelines issued by OMB. OMB's guidelines were published at 67 FR 8452 (February 22, 2002), and DOE's guidelines were published at 67 FR 62446 (October 7, 2002). DOE has reviewed today's notice under the OMB and DOE guidelines and has concluded that it is consistent with applicable policies in those guidelines. </P>
                    <HD SOURCE="HD2">G. Review Under Executive Order 12988 </HD>
                    <P>With respect to the review of existing regulations and the promulgation of new regulations, section 3(a) of Executive Order 12988, “Civil Justice Reform” (61 FR 4729, February 7, 1996), imposes on Federal agencies the general duty to adhere to the following requirements: (1) Eliminate drafting errors and ambiguity; (2) write regulations to minimize litigation; and (3) provide a clear legal standard for affected conduct rather than a general standard and promote simplification and burden reduction. Section 3(b) of Executive Order 12988 specifically requires that Executive agencies make every reasonable effort to ensure that the regulation: (1) Clearly specifies the preemptive effect, if any; (2) clearly specifies any effect on existing Federal law or regulation; (3) provides a clear legal standard for affected conduct while promoting simplification and burden reduction; (4) specifies the retroactive effect, if any; (5) adequately defines key terms; and (6) addresses other important issues affecting clarity and general draftsmanship under any guidelines issued by the Attorney General. Section 3(c) of Executive Order 12988 requires Executive agencies to review regulations in light of applicable standards in section 3(a) and section 3(b) to determine whether they are met or it is unreasonable to meet one or more of them. DOE has completed the required review and determined that, to the extent permitted by law, this proposed rule meets the relevant standards of Executive Order 12988. </P>
                    <HD SOURCE="HD2">H. Review Under the Unfunded Mandates Reform Act of 1995 </HD>
                    <P>Title II of the Unfunded Mandates Reform Act of 1995 (Pub. L. 104-4) requires each Federal agency to assess the effects of a Federal regulatory action on state, local, and tribal governments, and the private sector. The Department has determined that today's regulatory action does not impose a Federal mandate on state, local or tribal governments or on the private sector. </P>
                    <HD SOURCE="HD2">I. Review Under the Treasury and General Government Appropriations Act, 1999 </HD>
                    <P>Section 654 of the Treasury and General Government Appropriations Act, 1999 (Pub. L. 105-277) requires Federal agencies to issue a Family Policymaking Assessment for any rule that may affect family well-being. These proposed guidelines would not have any impact on the autonomy or integrity of the family as an institution. Accordingly, DOE has concluded that it is not necessary to prepare a Family Policymaking Assessment. </P>
                    <HD SOURCE="HD2">J. Review Under Executive Order 13211 </HD>
                    <P>Executive Order 13211, “Actions Concerning Regulations That Significantly Affect Energy Supply, Distribution, or Use” (66 FR 28355, May 22, 2001) requires Federal agencies to prepare and submit to the OMB, a Statement of Energy Effects for any proposed significant energy action. A “significant energy action” is defined as any action by an agency that promulgated or is expected to lead to promulgation of a final rule, and that: (1) Is a significant regulatory action under Executive Order 12866, or any successor order; and (2) is likely to have a significant adverse effect on the supply, distribution, or use of energy, or (3) is designated by the Administrator of OIRA as a significant energy action. For any proposed significant energy action, the agency must give a detailed statement of any adverse effects on energy supply, distribution, or use should the proposal be implemented, and of reasonable alternatives to the action and their expected benefits on energy supply, distribution, and use. Today's regulatory action would not have a significant adverse effect on the supply, distribution, or use of energy and is therefore not a significant energy action. Accordingly, DOE has not prepared a Statement of Energy Effects. </P>
                    <LSTSUB>
                        <HD SOURCE="HED">List of Subjects in 10 CFR Part 300 </HD>
                        <P>Administrative practice and procedure, Energy, Gases, Reporting and recordkeeping requirements.</P>
                    </LSTSUB>
                    <SIG>
                        <DATED>Issued in Washington, DC on November 20, 2003. </DATED>
                        <NAME>Robert G. Card, </NAME>
                        <TITLE>Under Secretary for Energy, Science and Environment. </TITLE>
                    </SIG>
                    <P>For the reasons set forth in the preamble, DOE proposes to amend Chapter II of Title 10 of the Code of Federal Regulations by adding a new Subchapter B consisting of part 300 to read as follows. </P>
                    <SUBCHAP>
                        <HD SOURCE="HED">SUBCHAPTER B—CLIMATE CHANGE </HD>
                        <PART>
                            <HD SOURCE="HED">PART 300—VOLUNTARY GREENHOUSE GAS REPORTING PROGRAM: GENERAL GUIDELINES</HD>
                            <CONTENTS>
                                <SECHD>Sec. </SECHD>
                                <SECTNO>300.1 </SECTNO>
                                <SUBJECT>General. </SUBJECT>
                                <SECTNO>300.2 </SECTNO>
                                <SUBJECT>Definitions. </SUBJECT>
                                <SECTNO>300.3 </SECTNO>
                                <SUBJECT>Guidance for defining the reporting entity. </SUBJECT>
                                <SECTNO>300.4 </SECTNO>
                                <SUBJECT>Selecting operational boundaries for reporting. </SUBJECT>
                                <SECTNO>300.5 </SECTNO>
                                <SUBJECT>Submission of an entity statement. </SUBJECT>
                                <SECTNO>300.6 </SECTNO>
                                <SUBJECT>Emissions inventories. </SUBJECT>
                                <SECTNO>300.7 </SECTNO>
                                <SUBJECT>Net entity-wide emission reductions. </SUBJECT>
                                <SECTNO>300.8 </SECTNO>
                                <SUBJECT>Calculating emission reductions. </SUBJECT>
                                <SECTNO>300.9 </SECTNO>
                                <SUBJECT>Reporting and recordkeeping requirements. </SUBJECT>
                                <SECTNO>300.10 </SECTNO>
                                <SUBJECT>Certification of reports. </SUBJECT>
                                <SECTNO>300.11 </SECTNO>
                                <SUBJECT>Independent verification. </SUBJECT>
                                <SECTNO>300.12 </SECTNO>
                                <SUBJECT>Acceptance of reports and registration of entity emission reductions. </SUBJECT>
                                <FP SOURCE="FP-2">Appendix A to Part 300—Voluntary Reporting of Greenhouse Gases Under 1605(b) of the Energy Policy Act of 1992: General Guidelines (October 1994).</FP>
                            </CONTENTS>
                            <AUTH>
                                <HD SOURCE="HED">Authority:</HD>
                                <P>
                                    42 U.S.C. 7101, 
                                    <E T="03">et seq.</E>
                                    , and 42 U.S.C. 13385(b). 
                                </P>
                            </AUTH>
                            <SECTION>
                                <SECTNO>§ 300.1 </SECTNO>
                                <SUBJECT>General. </SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Purpose.</E>
                                     These Guidelines govern the Voluntary Reporting of Greenhouse Gases Program authorized by section 1605(b) of the Energy Policy Act of 1992 (42 U.S.C. 13385(b)). The purposes of the Guidelines are to establish the procedures and requirements for filing voluntary reports, and encourage corporations, government agencies, non-profit organizations, households and other private and public entities to submit annual reports of their net 
                                    <PRTPAGE P="68216"/>
                                    greenhouse gas emissions, emission reductions, and sequestration activities that are complete, reliable and consistent. Over time, it is anticipated that these reports will provide a reliable record of the contributions reporting entities have made to reducing their greenhouse gas emissions. 
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Registration and reporting options.</E>
                                     An entity may choose to register or report emissions and emission reductions as follows. 
                                </P>
                                <P>
                                    (1) 
                                    <E T="03">Registration.</E>
                                     An entity may have entity-wide emissions and emissions reductions registered by conforming to the requirements of this part, including the registration standards set forth in §§ 300.6 and 300.7 of this part. 
                                </P>
                                <P>
                                    (2) 
                                    <E T="03">Reporting.</E>
                                     If an entity does not choose to report emissions in a manner that conforms to the registration requirements set forth in §§ 300.6 and 300.7 of this part, then the entity may choose to report on any emissions or any emissions reductions by complying with the requirements of this part other than §§ 300.6 and 300.7. 
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Forms.</E>
                                     Annual reports of greenhouse gas emissions, emission reductions, and sequestration must be made on forms or software that are available from the Energy Information Administration of the Department of Energy (EIA). 
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Status of reports under previous General Guidelines.</E>
                                     EIA will continue to maintain in its Voluntary Reporting of Greenhouse Gases database all reports received pursuant to DOE's October 1994 General Guidelines. For the convenience of the readers, those Guidelines are included as Appendix A to this part 300. 
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 300.2 </SECTNO>
                                <SUBJECT>Definitions. </SUBJECT>
                                <P>This section provides definitions for commonly used terms in the Guidelines. </P>
                                <P>
                                    <E T="03">Avoided emissions</E>
                                     means the emissions displaced by increases in the generation and sale of electricity, steam, hot water or chilled water produced from energy sources that emit fewer greenhouse gases per unit than other competing sources of these forms of distributed energy. 
                                </P>
                                <P>Carbon stocks are the quantity of carbon stored in biological and physical systems including: Trees, plants and other terrestrial biosphere sinks, soils, oceans, sedimentary and geological sinks, and the atmosphere. [This term is to be further defined in DOE's Technical Guidelines.] </P>
                                <P>
                                    <E T="03">De minimis emissions</E>
                                     means emissions from one or more sources and of one or more gases that when summed are less than 3 percent of the total annual CO
                                    <E T="52">2</E>
                                     equivalent emissions of a reporting entity or less than 10,000 metric tons of CO
                                    <E T="52">2</E>
                                     equivalent, whichever is smaller. 
                                </P>
                                <P>
                                    <E T="03">DOE or Department</E>
                                     means the U.S. Department of Energy and, as appropriate in context, includes the Energy Information Administration. 
                                </P>
                                <P>
                                    <E T="03">Direct emissions</E>
                                     means greenhouse gas emissions resulting from stationary or mobile sources within the organizational boundary of an entity, including but not limited to emissions resulting from combustion of fossil fuels, process emissions, and fugitive emissions. 
                                </P>
                                <P>
                                    <E T="03">Emissions</E>
                                     means direct and specified indirect emissions of greenhouse gases from any anthropogenic (human induced) source. 
                                </P>
                                <P>
                                    <E T="03">Emissions intensity</E>
                                     means emissions per unit of output—usually the quantity of physical output, but sometimes a non-physical indicator of an entity's output activity. 
                                </P>
                                <P>Fugitive emissions means releases to the atmosphere of greenhouse gases from the processing, transmission, and/or transportation of fossil fuels or other materials, such as HFC leaks from refrigeration, SF6 from electrical power distributors, and methane from solid waste landfills, among others, that are not emitted via a pipe(s) or stack(s). </P>
                                <P>
                                    <E T="03">Greenhouse gases</E>
                                     means: 
                                </P>
                                <P>
                                    (1) 
                                    <E T="03">Carbon dioxide:</E>
                                     CO
                                    <E T="52">2</E>
                                </P>
                                <P>
                                    (2) 
                                    <E T="03">Methane:</E>
                                     CH
                                    <E T="52">4</E>
                                </P>
                                <P>
                                    (3) 
                                    <E T="03">Nitrous oxide:</E>
                                     N
                                    <E T="52">2</E>
                                    O 
                                </P>
                                <P>
                                    (4) 
                                    <E T="03">Hydrofluorocarbons:</E>
                                     HFCs 
                                </P>
                                <P>
                                    (5) 
                                    <E T="03">Perfluorocarbons:</E>
                                     PFCs 
                                </P>
                                <P>
                                    (6) 
                                    <E T="03">Sulfur Hexafluoride:</E>
                                     SF
                                    <E T="52">6</E>
                                </P>
                                <P>(7) Other gases or particles that have been demonstrated to have significant, quantifiable climate forcing effects when released to the atmosphere in significant quantities. </P>
                                <P>
                                    <E T="03">Indirect emissions</E>
                                     means greenhouse gas emissions from stationary or mobile sources outside the organizational boundary of an entity, including but not limited to the generation of electricity, steam and hot/chilled water, that are the result of an entity's energy use or other activities. 
                                </P>
                                <P>
                                    <E T="03">Natural emissions</E>
                                     means emissions that are naturally occurring and produced independent of human actions, including biogenic (produced by biological processes), geologic and potentially other non-anthropogenic sources. 
                                </P>
                                <P>
                                    <E T="03">Net emissions or net entity-wide emissions</E>
                                     means the total net annual contribution of the greenhouse gases specifically identified in section 300.6(f) to the atmosphere by an entity: total, entity-wide emissions, both direct and indirect, minus entity-wide sequestration. 
                                </P>
                                <P>
                                    <E T="03">Net emission reductions or net entity-wide emission reductions</E>
                                     means the sum of all annual changes in emissions, carbon stocks and avoided emissions of the greenhouse gases specifically identified in section 300.6(f), determined in conformance with §§ 300.7 and 300.8 of these Guidelines. 
                                </P>
                                <P>
                                    <E T="03">Offsets</E>
                                     means an emission reduction that meets the requirements of these guidelines, but is achieved by a party other than the entity that reports or registers the reduction. 
                                </P>
                                <P>
                                    <E T="03">Sequestration</E>
                                     means the removal of atmospheric carbon dioxide, either through biologic processes or physical processes, including capture, long-term separation, isolation, or removal of greenhouse gases from the atmosphere, such as through cropping practices, forest and forest products management or injection into an underground reservoir. 
                                </P>
                                <P>
                                    <E T="03">Sink</E>
                                     means an identifiable discrete physical process, occurring at a particular location, set of locations or area, by which carbon dioxide or some other greenhouse gas is sequestered. 
                                </P>
                                <P>
                                    <E T="03">Source</E>
                                     means an identifiable discrete physical process, occurring at a particular location, set of locations, or area, by which a greenhouse gas is emitted. 
                                </P>
                                <P>
                                    <E T="03">Sub-entity</E>
                                     means a component of any entity, such as a discrete business line, facility, plant, vehicle fleet, or energy using system, which has associated with it emissions of greenhouse gases that: can be distinguished from the emissions of all other components of the same entity; and, when summed with the emissions of all other sub-entities, equal the entity's total emissions. 
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 300.3 </SECTNO>
                                <SUBJECT>Guidance for defining the reporting entity. </SUBJECT>
                                <P>A reporting entity must be composed of one or more legally distinct businesses, institutions, organizations or households, although reporters are strongly encouraged to define themselves at the highest level of aggregation appropriate. The legal basis for determining whether a reporting entity or its components are distinct can be derived from any Federal, State or local law or regulation governing the entity, including regulations applicable to corporations, partnerships, cooperatives, government agencies, non-profit organizations, households, or other entities. This legal basis must be described in the entity statement required by § 300.5 of these Guidelines. </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 300.4 </SECTNO>
                                <SUBJECT>Selecting operational boundaries for reporting. </SUBJECT>
                                <P>
                                    (a) An entity must determine, document, and maintain its operational boundary for accounting and reporting purposes. Because of the large number 
                                    <PRTPAGE P="68217"/>
                                    of different operational structures, reporting entities are given some flexibility to set their operational boundaries in a manner that best suits their circumstances. However, all reports submitted should adhere to the following: 
                                </P>
                                <P>(1) To the extent feasible, reporting entities should establish operational boundaries in a manner that is consistent with the entity's existing legal, managerial and financial structure; and </P>
                                <P>(2) The reporting entity should establish operational boundaries that will result in accurate and comprehensive reports of its greenhouse gas emissions and sequestration. </P>
                                <P>(b) In general, a reporting entity should select operational boundaries so as to encompass all emissions and sequestration associated with facilities and vehicles that are wholly owned and operated by the named and defined entity. Emissions from facilities or vehicles that are partially owned or leased, or not directly controlled or managed by the entity, may be included at the entity's discretion, provided that the entity has taken reasonable steps to assure that doing so does not result in the double counting of emissions, sequestration or emission reductions. </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 300.5 </SECTNO>
                                <SUBJECT>Submission of an entity statement. </SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Initial entity statement requirements.</E>
                                     When an entity first reports under these Guidelines, the reporting entity must provide the following information in its entity statement: 
                                </P>
                                <P>(1) The name to be used to identify the reporting entity. This should be the name commonly used to represent most of the activities being reported, as long as it is not also used to refer to substantial activities not covered by the entity's reports. </P>
                                <P>
                                    (2) The names of any parent or holding companies the activities of which will 
                                    <E T="03">not</E>
                                     be covered comprehensively by the entity's reports; 
                                </P>
                                <P>
                                    (3) The names of any large subsidiaries or organizational units that 
                                    <E T="03">will</E>
                                     be covered comprehensively by the entity's reports; 
                                </P>
                                <P>(4) A description of the entity and its primary economic activities, such as electricity generation, product manufacturing, service provider, freight transport, or household operation; </P>
                                <P>(5) A description of the types of operations, facilities, processes, vehicles and other emission sources or sinks covered in the entity's inventories; </P>
                                <P>(6) The names of the entities that share the ownership or operational control of significant facilities or sources included in the reporting entity's report, and certify that, to the best of the preparer's knowledge, the direct greenhouse gas emissions and sequestrations in the entity's report are not included in the 1605(b) report of any of those other entities for the same calendar year; </P>
                                <P>(7) Identification of the first year for which the entity will report emissions and the base year or base period from which emission reductions will be calculated. </P>
                                <P>
                                    (b) 
                                    <E T="03">Reasons for changing the scope of entity reports.</E>
                                     From time to time, entities may choose to change the scope of activities included within the entity's reports or the level at which the entity wishes to report. An entity may also choose to change its operational boundaries, its base year (or base period) or, since many entities are dynamic by nature, other elements of its Entity Statement or reporting methods. For example, companies buy and sell business units, and equity share arrangements evolve. The dynamic nature of economic activity may pose a challenge for the objective of a comprehensive and accurate documentation of greenhouse gas emissions and sequestrations from year to year. In general, DOE encourages changes in the scope of reporting that expand the coverage of an entity's report and discourages changes that reduce the coverage of such reports unless they are caused by divestitures or plant closures. Any such changes should be reported in amendments to the Entity Statement and major changes may warrant or require changes in the reporting entity's base year or base period. The Technical Guidelines under this part provide more specific guidance on how such changes should be reflected in entity reports and emission reduction calculations. 
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Documenting changes in amended entity statements.</E>
                                     A reporter's Entity Statement in subsequent reports should focus primarily on changes since the previous report. Specifically, the subsequent Entity Statement should report the following information: 
                                </P>
                                <P>(1) Significant changes in the entity's organizational (geographic or operational) boundaries. In particular, the entity statement should document: </P>
                                <P>(i) The acquisition or divestiture of discrete business units, subsidiaries, facilities, and plants; </P>
                                <P>(ii) The closure or opening of significant facilities; </P>
                                <P>(iii) The transfer of economic activity to or from specific operations outside the U.S.; </P>
                                <P>(iv) Significant changes in land holdings (applies to entities reporting on greenhouse gas emissions or sequestration related to land use, land use change, or forestry); </P>
                                <P>(v) Whether the entity is reporting at a higher level of aggregation than it did in the previous report, and if so, a listing of the subsidiary entities that are now aggregated under a revised conglomerated entity; and </P>
                                <P>
                                    (vi) Changes in its activities or operations (
                                    <E T="03">e.g.</E>
                                    , changes in output, contractual arrangements, equipment and processes, outsourcing or insourcing of significant activities) that are likely to have a significant effect on emissions, together with an explanation of how it believes the changes in economic activity influenced its reported emissions or sequestrations. 
                                </P>
                                <P>(2) If very substantial changes have occurred, then the reporting entity is required to submit a new Entity Statement that provides a complete and current overview of the entity's operations, facilities and emission sources. </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 300.6 </SECTNO>
                                <SUBJECT>Emissions inventories. </SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">General.</E>
                                     The objective of the entity-wide reporting standard is to provide a comprehensive inventory of an entity's total net greenhouse gas emissions, including all six greenhouse gases listed in paragraph (f) of this section and all emissions and sequestration associated with changes in terrestrial carbon stocks. The reporting entity should report all of the covered greenhouse gas emissions from within the entity, using the methods specified in the Technical Guidelines (to be issued subsequently). Entity-wide reports are a prerequisite for the registration of emission reductions by entities with average annual emissions of more that 10,000 tons of CO
                                    <E T="52">2</E>
                                     equivalent. Entities that have average annual emissions of less than 10,000 tons of CO
                                    <E T="52">2</E>
                                     equivalent are eligible to register emission reductions associated with specific activities without also reporting an inventory of the total emissions. 
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Direct emissions inventories.</E>
                                     (1) Direct greenhouse gas emissions that must be reported are those emissions resulting from stationary or mobile sources within the organizational boundaries of an entity, including but not limited to emissions resulting from combustion of fossil fuels, process emissions, and fugitive emissions. Process emissions should be reported (
                                    <E T="03">e.g.</E>
                                    , PFC emissions from aluminum production) along with fugitive emissions (
                                    <E T="03">e.g.</E>
                                    , leakage of greenhouse gases from equipment). 
                                </P>
                                <P>
                                    (2) Entities should separately report emissions of greenhouses gases from combustion of biomass fuels or biomass-
                                    <PRTPAGE P="68218"/>
                                    based fuels (
                                    <E T="03">e.g.</E>
                                    , wood waste, landfill gas, ethanol from corn, charcoal). The Technical Guidelines (to be issued subsequently) will specify the applicable list of biomass fuels or biomass-based fuels. 
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Inventories of indirect emissions associated with purchased energy.</E>
                                     (1) To provide a clear incentive for the users of electricity and other forms of purchased energy to reduce demand, the consumption of purchased electricity, steam, and hot or chilled water must be included in a reporting entity's inventory as indirect emissions. To avoid double counting among entities, the reporting entity must report all indirect emissions (as defined in § 300.2) separately from its direct emissions. Reporting entities should use the methods for quantifying indirect emissions specified in the Technical Guidelines. 
                                </P>
                                <P>(2) Reporting entities may also choose to report other forms of indirect emissions, such as emissions associated with employee commuting, materials consumed or products produced, although emission reductions associated with such other indirect emissions are not eligible for registration. All such reports of other forms of indirect emissions must be clearly distinguished from reports of indirect emissions associated with purchased energy. The Technical Guidelines also address the reporting of these other types of indirect emissions. </P>
                                <P>
                                    (d) 
                                    <E T="03">Entity-level inventories of changes in terrestrial carbon stocks.</E>
                                     Annual changes in terrestrial carbon stocks should be comprehensively assessed and reported across the entity and the net emissions resulting from such changes included in the entity's inventory of its net emissions. In other words, activities that lead to the release of carbon to the atmosphere must be reported along with activities that sequester carbon. This is necessary to provide an accurate entity-wide estimate of net greenhouse gas emissions. Entities should use the methods for estimating changes in terrestrial carbon stocks specified in the Technical Guidelines. 
                                </P>
                                <P>
                                    (e) 
                                    <E T="03">Treatment of de minimis emissions and sequestration.</E>
                                     Although the goal of the entity-wide reporting Guidelines is to provide an accurate and comprehensive estimate of total entity-wide emissions, there may be small emissions from certain sources that are unreasonably costly or difficult to quantify. A reporting entity may exclude particular sources of emissions or sequestration if the total quantities excluded represent less than 3 percent of the total annual CO
                                    <E T="52">2</E>
                                     equivalent emissions of the entity or less than 10,000 metric tons of CO
                                    <E T="52">2</E>
                                     equivalent, whichever is less. The entity must identify the types of emissions excluded and provide a short justification as to why an estimate was not included in the entity's report. 
                                </P>
                                <P>
                                    (f) 
                                    <E T="03">Covered gases.</E>
                                     (1) Entity-wide emissions inventories must include all emissions of the following greenhouse gases:
                                </P>
                                <FP SOURCE="FP-1">
                                    (i) CO
                                    <E T="52">2</E>
                                </FP>
                                <FP SOURCE="FP-1">
                                    (ii) CH
                                    <E T="52">4</E>
                                </FP>
                                <FP SOURCE="FP-1">
                                    (iii) N
                                    <E T="52">2</E>
                                    O 
                                </FP>
                                <FP SOURCE="FP-1">(iv) HFCs </FP>
                                <FP SOURCE="FP-1">(v) PFCs </FP>
                                <FP SOURCE="FP-1">(vi) SF6 </FP>
                                <P>(2) Entities may also choose to report other greenhouse gases, as defined in section 300.2, but such gases are to be reported separately and any emission reductions associated with such other gases are not eligible for registration. </P>
                                <P>
                                    (g) 
                                    <E T="03">Units for reporting</E>
                                    . Emissions and sequestration should be reported in terms of the mass (not volume) of each gas, using metric units (
                                    <E T="03">e.g.</E>
                                    , metric tons of methane). Entity-wide and sub-entity summations of emissions and reductions from multiple sources shall be converted into carbon dioxide equivalent units using the global warming potentials for each gas. Entities should specify the units used (
                                    <E T="03">e.g.</E>
                                    , kilograms, or metric tons). Where necessary, reporting entities must use the standard conversion factors specified in the Technical Guidelines to convert existing data into the common units required in the entity-level report. Consumption of purchased electricity must be reported by region (from a list to be provided by DOE in the Technical Guidelines). Consumption of purchased steam or chilled/hot water must be reported according to the type of system and fuel used to generate it (from a list provided by DOE in the Technical Guidelines). Purchased energy will be converted to carbon dioxide equivalents using conversion factors in the Technical Guidelines. 
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 300.7 </SECTNO>
                                <SUBJECT>Net entity-wide emission reductions. </SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Assessing entity-wide emission reductions</E>
                                    . (1) Entity-wide reports are a prerequisite for the registration of emission reductions by entities with average annual emissions of more that 10,000 tons of CO2 equivalent. Net annual entity-wide emission reductions must be based, to the maximum extent practicable, on a full assessment and sum total of all changes in an entity's emissions, avoided emissions and sequestration relative to the entity's established base year (or base period), plus any emission offsets. All changes in emissions, avoided emissions, and sequestration must be determined using methods that are consistent with the guidelines described in § 300.8 of this part, and in compliance with all other relevant DOE guidelines. 
                                </P>
                                <P>(2) If it is not practicable to assess the changes in net emissions resulting from certain entity activities using at least one of the methods described in § 300.8 of this part, the reporting entity may exclude them from its estimate of net entity-wide emission reductions. The reporting entity must describe the sources excluded for this reason from the entity's assessment of its net emission reductions, the reasons why it was not practicable to assess the changes that had occurred, and the approximate quantity of emissions or sequestration not assessed. </P>
                                <P>(3) A reporting entity should also exclude from the entity-wide assessment of changes in emissions, avoided emissions and sequestration any emissions or sequestration that have been excluded from the entity's inventory. </P>
                                <P>
                                    (b) 
                                    <E T="03">Assessing the emission reductions of entities with small emissions</E>
                                    . Entities with average annual emissions of less than 10,000 tons of CO2-equivalent emissions are not required to inventory their total emissions or assess all changes in their emissions, avoided emissions and sequestration in order to register their reductions. They may register the emission reductions that have occurred since 2002 and that are associated with certain activities, as long as they perform a complete assessment of the annual emissions and sequestration associated with all of the activities of the same type, determine the changes in the emissions, avoided emissions or sequestration associated with these activities, and certify that the reductions reported were not caused by actions likely to cause increases in emissions elsewhere within the entity's operations. For example, a farmer may report emission reductions associated with tree plantings on a single wood lot, but must assess and report the net sequestration resulting from the farmer's management of all woodlots within the entity's boundaries. 
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Net emission reductions achieved by third parties (offsets)</E>
                                    . Net emission reductions achieved by third parties may be included in an entity-wide assessment of emission reductions as long as: 
                                </P>
                                <P>
                                    (1) The emission reductions reported were calculated using the same method(s) that would have been applicable if the third party that achieved the emission reduction had chosen to report it directly to DOE. 
                                    <PRTPAGE P="68219"/>
                                </P>
                                <P>(2) All of the reporting entities or other parties involved certify to DOE that they have agreed that the reporting entity should be recognized as the entity responsible for the reduction. </P>
                                <P>
                                    (d) 
                                    <E T="03">Adjusting for year-to-year increases in net emissions</E>
                                    . Net annual emission reductions are calculated normally relative to an entity's base year (or base period). However, if the entity has experienced a net increase (relative to the base year) in emissions for one or more intervening years, these increases must be subtracted from net emission reductions reported in future years. 
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 300.8 </SECTNO>
                                <SUBJECT>Calculating emission reductions. </SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Establishing base year (or base period) emissions</E>
                                    . In general, base year or base period emissions are those that occurred over the full year (or average annual emissions over the full multi-year period) immediately preceding the first year of calculated emission reductions. Base year or base period emissions may represent the whole entity, or specific sub-entities, but must be defined so as to correspond to the scope of the chosen emission reduction calculation. To ensure that the summation of entity annual reports accurately represents net, multi-year emission reductions, a specific base year or base period may be used to determine emission reductions in a given future year only if the entity has submitted qualified reports for each intervening year. 
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Calculation methods</E>
                                    . Entities must calculate any change in emissions, avoided emissions or sequestration using one or more of the methods described in this section. All changes must be calculated relative to a base year or base period established by the entity, unless the change results from an offset (
                                    <E T="03">see</E>
                                     subsection 300.7(c)). In general, entities are encouraged to use changes in net emissions intensity as the primary basis for calculating changes in net, entity-wide emissions. 
                                </P>
                                <P>
                                    (1) 
                                    <E T="03">Changes in emissions intensity</E>
                                    . A reporting entity may use reductions in the rate of emissions per unit of output (emissions intensity) as a basis for determining emission reductions as long as the reporting entity demonstrates in its report that the measure(s) of output used in the emissions intensity metric is a reasonable indicator of the physical output or economic value produced by the activity associated with these emissions, and that acquisitions, divestures or changes in products have not contributed significantly to changes in emissions intensity. 
                                </P>
                                <P>
                                    (2) 
                                    <E T="03">Changes in absolute emissions</E>
                                    . A reporting entity may use changes in the absolute (actual) emissions (direct or indirect) as a basis for determining net emission reductions, as long as the entity demonstrates in its report that any reductions derived from such changes were not achieved as a result of reductions in U.S. output, or major shifts in the types of products or services produced. 
                                </P>
                                <P>
                                    (3) 
                                    <E T="03">Changes in carbon storage (for actions within entity boundaries)</E>
                                    . A reporting entity may use changes in carbon storage as a basis for determining net emission reductions as long as the reporting entity uses estimation and measurement methods that comply with DOE Technical Guidelines, and has included an assessment of the net changes in all sinks included in its inventory. 
                                </P>
                                <P>
                                    (4) 
                                    <E T="03">Changes in avoided emissions (for actions within entity boundaries)</E>
                                    . A reporting entity may use changes in the avoided emissions associated with the sale of electricity, steam, hot water or chilled water generated from non-emitting or low-emitting sources as a basis for determining net emission reductions as long as: 
                                </P>
                                <P>(i) the measurement and calculation methods used comply with DOE Technical Guidelines, and </P>
                                <P>(ii) the reporting entity certifies that any increased sales were not attributable to the acquisition of a generating facility that had been previously operated, unless the entity utilized base year generation values derived from records of the facility's operation prior to its acquisition. </P>
                                <P>
                                    (5) 
                                    <E T="03">Project-based emission reductions (for actions within entity boundaries)</E>
                                    . Emission reductions may be determined based on an estimate of the effects on emissions of a specific action, as long as the reporting entity demonstrates that the estimate is based on analysis that: 
                                </P>
                                <P>(i) Uses output, utilization and other factors that are consistent, to the maximum extent practicable, with the action's actual performance in the year for which reductions are being reported; </P>
                                <P>(ii) Excludes any emission reductions that might have resulted from reduced output or were caused by actions likely to be associated with increases in emissions elsewhere within the entity's operations; and </P>
                                <P>(iii) Uses methods that are in compliance with DOE Technical Guidelines. Entity-wide reporters should use this project-based approach only if it is not possible to measure accurately emission changes by using one of the methods identified in paragraphs (a)(1) through (a)(4) of this section. </P>
                                <P>
                                    (c) 
                                    <E T="03">Summary description of actions taken to reduce emissions</E>
                                    . Each reported emission reduction must be accompanied by an identification of the types of actions that were the likely cause of the reductions achieved. 
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Emission reductions associated with plant closings, voluntary actions and government requirements</E>
                                    . Each report of emission reductions shall indicate whether the reported emission reductions were the result, in whole or in part, of plant closings, voluntary actions, or government requirements. 
                                </P>
                                <P>(1) If emission reductions were associated, in whole or part, with plant closings, the report should include an explanation of how such emission reductions did not result from a decline in the U.S. output of the reporting entity. </P>
                                <P>(2) If the reductions were associated, in whole or part, with government requirements, the report should identify the government requirement involved and describe the type of effect these requirements had on the reported emission reductions. </P>
                                <P>
                                    (e) 
                                    <E T="03">Determining the entity responsible for emission reductions</E>
                                    . The entity presumed to be responsible for emission reduction, avoided emission or sequestered carbon is the legal owner of the facility, land or vehicle which generated the affected emissions, generated the energy that was sold so as to avoid other emissions, or was the place where the sequestration action occurred. If ownership is shared, reporting of the associated emission reductions should be determined by agreement between the entities involved in order to avoid double-counting, and this agreement must be reflected in the entity statements filed and in any report of emission reductions. DOE will presume that an entity is not responsible for any emission reductions associated with a facility, property or vehicle excluded from its entity statement. 
                                </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 300.9 </SECTNO>
                                <SUBJECT>Reporting and recordkeeping requirements. </SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Starting to report under the revised Guidelines</E>
                                    . (1) Entities may report emissions and sequestration on an annual basis beginning in any year, but no earlier than the base period of 1987-1990 specified in the Energy Policy Act of 1992. To be recognized under these revised Guidelines, all reports must conform to the measurement methods established by the Technical Guidelines. This requirement applies to entities that report to the revised Voluntary Reporting of Greenhouse Gases Program registry for the first time as well as those entities that have previously submitted emissions reports pursuant to section 1605 (b) of the Energy Policy Act of 1992. 
                                    <PRTPAGE P="68220"/>
                                </P>
                                <P>(2) Entities may submit initial reports or corrected reports for previous calendar years at any time. For example, an entity may choose to begin reporting in 2005 and may choose, at that time, to submit reports on prior year emissions back to 2002. Also, if a change in the emissions calculation method is made for 2005, an entity may submit revised estimates for its previous reporting years to ensure that a consistent method is used across the whole time-series. Entities may also submit revised reports to reflect agreements with other entities regarding the appropriate entity to designate as the entity responsible for certain registered emission reductions. </P>
                                <P>
                                    (b) 
                                    <E T="03">Continuing to report</E>
                                    . Reporting entities are strongly encouraged to report emissions on an annual basis, starting from the first year they submit a report under these revised Guidelines. Annual entity reporting is necessary to ensure that calculated reductions have been sustained over time. If a reporting entity chooses not to submit a report in any given year, the next report made should include reports for intervening years, or the reporting entity must establish a new base year from which to calculate all future emission reductions. Entities that wish to sustain recognition for previously registered emission reductions resulting from sequestration must continue to report annually. 
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">Definition and deadline for annual reports</E>
                                    . Entities should report emissions on an annual basis, from January 1 to December 31, although DOE may grant exceptions to these dates. To be included in the earliest possible DOE annual report of greenhouse gas emissions reported under section 1605(b), entity reports must be submitted to DOE no later than July 1 for emissions during the previous calendar year. 
                                </P>
                                <P>
                                    (d) 
                                    <E T="03">Recordkeeping</E>
                                    . Entities must maintain adequate records for at least three years to enable independent verification of all information reported. Such records must include: 
                                </P>
                                <P>(1) A full description of the process and methods used to gather emissions data; </P>
                                <P>(2) A full description of the process and methods used to calculate emission reductions; </P>
                                <P>(3) The primary data upon which the data included in the any report to DOE was based; and </P>
                                <P>(4) A full description of any internal quality control or other verification measures taken to ensure that the data reported was in compliance with all relevant DOE Guidelines and other measurement protocols. </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 300.10 </SECTNO>
                                <SUBJECT>Certification of reports. </SUBJECT>
                                <P>(a) The chief executive officer, agency or household head, or person responsible for the reporting entity's compliance with environmental regulations must, for each report of such entity, certify that: </P>
                                <P>(1) The information provided to DOE is complete and accurate, in accordance with DOE's revised Guidelines, and is consistent with all prior year reports submitted by that entity (unless otherwise indicated); and </P>
                                <P>(2) Adequate records will be maintained for at least 3 years to enable independent verification of the information reported. </P>
                                <P>(b) If the report has been independently verified in accordance with DOE's Guidelines, the certification of the report by the entity reporting should so indicate. </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 300.11 </SECTNO>
                                <SUBJECT>Independent verification. </SUBJECT>
                                <P>(a) Reporting entities are encouraged to have their annual reports verified by independent and qualified auditors. </P>
                                <P>(1) “Independent”, as used in this paragraph (a), means that the verifiers must not be owned in whole or part by the reporting entity, nor should they provide any ongoing operational or support services to the entity, except services consistent with independent financial accounting or independent certification of compliance with government or private standards. </P>
                                <P>(2) “Qualified”, as used in this paragraph (a), means that verifiers must be certified by independent and nationally-recognized certification programs for the types of professionals needed to determine compliance with DOE's reporting Guidelines, such as the American Institute of Certified Public Accountants, the American National Standards Institute and Registrar Accreditation Board's (ANSI-RAB's) National Accreditation Program, or the Board of Environmental, Health, and Safety Auditor Certification (BEAC). </P>
                                <P>(b) The independent verifier must provide a written description of the relevant qualifications and professional certifications of the persons that performed the independent verification and must certify that: </P>
                                <P>(1) The information provided to DOE is complete and accurate, in accordance with DOE's revised Guidelines, and is consistent with all prior year reports submitted by that entity (unless otherwise indicated); and </P>
                                <P>(2) Adequate records have been maintained by the reporter to enable further independent verification in the future. </P>
                            </SECTION>
                            <SECTION>
                                <SECTNO>§ 300.12 </SECTNO>
                                <SUBJECT>Acceptance of reports and registration of entity emission reductions. </SUBJECT>
                                <P>
                                    (a) 
                                    <E T="03">Acceptance of reports</E>
                                    . Upon receipt, DOE will review all reports to ensure they are consistent with the revised Guidelines. If DOE determines the report follows the definitional, measurement, calculation and certification Guidelines, the report will be accepted. 
                                </P>
                                <P>
                                    (b) 
                                    <E T="03">Registration of emission reductions</E>
                                    . DOE will review accepted reports to determine any eligible emission reductions that were calculated using the reporting entities' base year emissions (no earlier than 2002) or the average annual emissions of its base period ( a period of up to four sequential years ending no earlier than 2002), and to ensure that the reports meet other relevant DOE requirements. DOE will also review its records to verify that the entity has submitted accepted annual reports for each year between the establishment of its base year or base period and the year covered by the current report. DOE will notify entities that the reductions that meet these requirements have been registered. 
                                </P>
                                <P>
                                    (c) 
                                    <E T="03">EIA database and summary reports</E>
                                    . The Administrator of the Energy Information Administration will establish a publicly accessible database composed of all reports that meet the definitional, measurement, calculation and certification requirements of these Guidelines. A portion of the database will provide summary information on the emissions and registered emission reductions of each reporting entity. 
                                </P>
                                <APPENDIX>
                                    <HD SOURCE="HED">Appendix A to Part 300—Voluntary Reporting of Greenhouse Gases Under Section 1605(b) of the Energy Policy Act of 1992: General Guidelines (October 1994) </HD>
                                    <HD SOURCE="HD1">Voluntary Reporting and You </HD>
                                    <P>This program was designed to help you measure and record the actions you take to reduce greenhouse gas emissions or to increase carbon storage in soil or plants. The voluntary reporting program provides an opportunity for you to gain recognition for the good effects of your actions—recognition from your customers, your shareholders, public officials, and the Federal government. Reporting the results of your actions adds to the public groundswell of efforts to deal with the threat of climate change. Reporting can show that you are part of various initiatives under the President's Climate Change Action Plan. Your reports can also record a baseline from which to measure your future actions. Finally, your reports, along with others, can contribute to the growing body of information on cost-effective actions for controlling greenhouse gases. </P>
                                    <P>
                                        We've designed this simple, flexible program to encourage you to accurately record your achievements. The program allows you to define activities you choose to 
                                        <PRTPAGE P="68221"/>
                                        report and to determine how you will estimate the effects of those activities on greenhouse gas emissions and carbon sequestration. 
                                    </P>
                                    <P>We recognize that you must balance your efforts to ensure the accuracy of reported data with your goals of keeping costs reasonable in generating the reports. </P>
                                    <P>We are optimistic that the response to this program will show that voluntary programs can do the job. We have been impressed by the level of commitment to the President's initiatives on climate change. This reporting program provides opportunities to report your achievements and to track your progress as you use your ingenuity and creativity in responding to the challenge of climate change. </P>
                                    <HD SOURCE="HD1">General Guidelines </HD>
                                    <FP SOURCE="FP-2">GG-1 How Are These Guidelines and Supporting Documents Organized? </FP>
                                    <FP SOURCE="FP-2">GG-2 Why Report Under This Voluntary Reporting Program?</FP>
                                    <FP SOURCE="FP-2">GG-3 May I Report and What Should I Report? </FP>
                                    <FP SOURCE="FP-2">GG-4 What Is Involved in Reporting Emissions? </FP>
                                    <FP SOURCE="FP1-2">GG-4.1 Gases and Sources. </FP>
                                    <FP SOURCE="FP1-2">GG-4.2 Use of Existing Information.</FP>
                                    <FP SOURCE="FP1-2">GG-4.3 Scope of Emissions Reporting. </FP>
                                    <FP SOURCE="FP-2">GG-5 How Should I Analyze Projects I Wish to Report? </FP>
                                    <FP SOURCE="FP1-2">GG-5.1 What Should the Project be Compared To? </FP>
                                    <FP SOURCE="FP1-2">GG-5.2 What Effects Did the Project Have? </FP>
                                    <FP SOURCE="FP1-2">GG-5.3 How Do I Estimate Project Accomplishments?</FP>
                                    <FP SOURCE="FP1-2">GG-5.4 What If Two or More Organizations Wish to Report the Same Project? </FP>
                                    <FP SOURCE="FP1-2">GG-5.5 May I Report Through My Trade Associations or Other Third Parties? </FP>
                                    <FP SOURCE="FP1-2">GG-5.6 What Else Will I Be Asked to Report? </FP>
                                    <FP SOURCE="FP1-2">GG-5.7 May I Report International Projects? </FP>
                                    <FP SOURCE="FP1-2">GG-5.8 May I Report Prospective Emissions Reductions? </FP>
                                    <FP SOURCE="FP1-2">GG-5.9 How Far Back May I Report Projects? </FP>
                                    <FP SOURCE="FP1-2">GG-5.10 Must I Take into Account the Different Effects of Different Greenhouse Gases? </FP>
                                    <FP SOURCE="FP1-2">GG-5.11 Is It Necessary to Report Emissions Reductions and Carbon Sequestration Every Year? </FP>
                                    <FP SOURCE="FP1-2">GG-5.12 May I Amend My Previous Years' Reports? </FP>
                                    <FP SOURCE="FP-2">GG-6 What Are the Minimum Reporting Requirements? </FP>
                                    <FP SOURCE="FP-2">GG-7 Can My Data Be Kept Confidential? </FP>
                                    <FP SOURCE="FP-2">GG-8 What Certification Is Required? </FP>
                                    <FP SOURCE="FP-2">GG-9 What Should I Do Next? </FP>
                                    <HD SOURCE="HD1">Figures </HD>
                                    <FP SOURCE="FP-2">GG-1 Careful Project Analysis Requires that you Consider Several Interrelated Elements </FP>
                                    <FP SOURCE="FP-2">GG-2 Standard Projects Utilize Physical and Default Data </FP>
                                    <FP SOURCE="FP-2">GG-3 Reporter-Designed Projects Utilize Your Own Measured or Engineering Data Along with Physical and Default Data </FP>
                                    <HD SOURCE="HD1">Case Studies </HD>
                                    <FP SOURCE="FP-2">1. Rarotonga Coconut Cream, Inc. (industrial cogeneration) </FP>
                                    <FP SOURCE="FP1-2">Project Description and Emissions Reporting </FP>
                                    <FP SOURCE="FP1-2">Reference Case </FP>
                                    <FP SOURCE="FP1-2">Project Effects</FP>
                                    <FP SOURCE="FP1-2">Estimation Methods </FP>
                                    <FP SOURCE="FP-2">2. Rural-Urban Office Managers, Inc. (energy efficiency in buildings) </FP>
                                    <FP SOURCE="FP1-2">Project Description and Emissions Reporting </FP>
                                    <FP SOURCE="FP1-2">Reference Case </FP>
                                    <FP SOURCE="FP1-2">Project Effects </FP>
                                    <FP SOURCE="FP1-2">Estimation Methods </FP>
                                    <FP SOURCE="FP-2">3. Illinois-Ohio Unlimited (new solar-powered electricity generation) </FP>
                                    <FP SOURCE="FP1-2">Project Description and Emissions Reporting </FP>
                                    <FP SOURCE="FP1-2">Reference Case </FP>
                                    <FP SOURCE="FP1-2">Project Effects </FP>
                                    <FP SOURCE="FP1-2">Estimation Methods </FP>
                                    <FP SOURCE="FP-2">4. Black Forest Cake, Inc. (long-term project reporting)</FP>
                                    <HD SOURCE="HD1">General Guidelines </HD>
                                    <P>Because of concerns with the growing threat of global climate change from increasing emissions of greenhouse gases, Congress authorized a voluntary program for the public to report achievements in reducing those gases. This document offers guidance on recording historic and current greenhouse gas emissions, emissions reductions, and carbon sequestration. Under the Energy Policy Act (EPAct) of 1992 Section 1605(b) program, reporters will have the opportunity to highlight specific achievements. </P>
                                    <P>If you have taken actions to lessen the greenhouse gas effect, either by decreasing greenhouse gas emissions or by sequestering carbon, the Department of Energy (DOE) encourages you to report your achievements under this program. The program has two related, but distinct parts. First, the program offers you an opportunity to report your annual emissions of greenhouse gases. Second, the program records your specific projects to reduce greenhouse gas emissions and increase carbon sequestration. Although participants in the program are strongly encouraged to submit reports on both, reports on either annual emissions or emissions reductions and carbon sequestration projects will be accepted. </P>
                                    <P>These guidelines and the supporting technical documents outline the rationale for the program and approaches to analyzing emissions and emissions reduction projects. Your annual emissions and emissions reductions achievements will be reported on forms that are available through the Energy Information Administration (EIA) of the Department of Energy, 1000 Independence Avenue, SW., Washington, DC 20585. </P>
                                    <HD SOURCE="HD2">GG-1 How Are These Guidelines and Supporting Documents Organized? </HD>
                                    <P>In these pages, you will find answers to your questions about who may report, what is involved in reporting, and how to develop a credible project analysis to help you accurately report your achievements. The General Guidelines (GG) illustrate the process for analyzing projects using three hypothetical examples (an industrial cogeneration project, an energy efficiency program, and new electricity generating capacity). </P>
                                    <P>You will also find guidance on such issues as joint reporting (if two or more persons or organizations are responsible for achievements), third-party reporting (through a trade association, for example), international projects, confidentiality, certification, and other elements of the reporting process. </P>
                                    <P>For more specific guidance, you may consult one or more of the supporting documents that discuss sector-specific issues and analytic approaches. The supporting documents, organized in two volumes, contain limited examples of project analysis for the relevant sectors. Supporting documents have been developed as follows: </P>
                                    <FP>• Volume I </FP>
                                    <FP SOURCE="FP1-2">—Electricity Supply Sector (Part 1) </FP>
                                    <FP SOURCE="FP1-2">—Residential and Commercial Buildings Sector (Part 2) </FP>
                                    <FP SOURCE="FP1-2">—Industrial Sector (Part 3) </FP>
                                    <FP>• Volume II </FP>
                                    <FP SOURCE="FP1-2">—Transportation Sector (Part 4) </FP>
                                    <FP SOURCE="FP1-2">—Forestry Sector (Part 5) </FP>
                                    <FP SOURCE="FP1-2">—Agricultural Sector (Part 6). </FP>
                                    <P>Each volume includes appendixes that provide conversion tables and default emissions factors (for various fuels and for electricity on a state-by-state basis). You can use these tables and factors for almost any report you submit. The final appendix in each volume presents a list of greenhouse gases for which the Intergovernmental Panel on Climate Change has developed Global Warming Potentials (an index of the relative effects on climate of different gases). </P>
                                    <HD SOURCE="HD2">GG-2 Why Report Under This Voluntary Reporting Program? </HD>
                                    <P>If you are undertaking activities to reduce greenhouse gas emissions or to sequester carbon, reporting under this program can be valuable to you and to others. It can be valuable to you because it provides a way to present information about your greenhouse gas-related activities to your customers or constituents who are concerned about the issue of global climate change. It can be valuable to others, including the Federal government (to recognize your achievements under various initiatives), decisionmakers and legislative bodies (to inform the public debate on future greenhouse gas policies), and other individuals or organizations (to learn from each other). </P>
                                    <P>You may wish to report under this program for at least three reasons: </P>
                                    <P>
                                        • To Record Emissions and Achievements. You may wish to formally record, in a national database, your greenhouse gas emissions and the results of your activities that reduce or avoid these emissions. Reporting may be part of your participation in programs that recognize your contributions to achieving greenhouse gas emissions goals. These programs include national initiatives such as the Climate Change Action Plan and programs such as Climate Challenge, ClimateWise, and Motor Challenge. However, reporting under this voluntary reporting program is not limited to participants in these programs; you may wish to record the emissions reductions benefits from activities pursued independently of formal recognition programs. 
                                        <PRTPAGE P="68222"/>
                                    </P>
                                    <P>• To Inform the Public Debate. You may wish to provide data which will contribute to more informed public debate on national policy on greenhouse gas reductions. Although a database built upon voluntary reports cannot provide a complete picture of national or sectoral emissions, it could provide credible information on emissions reductions and carbon sequestration projects to evaluate their potential for broader application. </P>
                                    <P>• To Participate in Educational Exchanges. Data reported under the voluntary reporting program may provide useful information to others seeking ways to reduce their own emissions. New, innovative, and more economical means of reducing or avoiding emis-sions may be more widely deployed as better information becomes available. </P>
                                    <HD SOURCE="HD2">GG-3 May I Report and What Should I Report? </HD>
                                    <P>You may report under this program if you initiate, control, or in some other way participate in activities that (1) contribute to greenhouse gas emissions, (2) result in reducing greenhouse gas emissions, or (3) sequester carbon. The activities may be part of your regular operations, pilot studies, prototype projects, or demonstration projects. They may take place in your community, in your workplace, at a location controlled by a third party, or at a foreign location. You must be a legal U.S. entity, that is, any U.S. citizen or resident alien; any company, organization, or group incorporated under or recognized by U.S. law; or any U.S. Federal, state, or local government entity. </P>
                                    <P>DOE encourages you to submit as comprehensive a report as you can. Elements of a comprehensive report include information about both your emissions levels and your emissions reduction projects. Emissions information could include data on the entire organization and all its greenhouse gas activities, including historic baseline emissions data for 1987 through 1990, and annual emissions for subsequent years. Comprehensive information about emissions reduction projects could include both emissions reductions and carbon sequestration projects, emissions factors used to determine reductions, assumptions about the project, and data sources. The extent to which you provide information for each of these elements is determined by your assessment of what is necessary for others to clearly understand your project and its effects. Users of the database will be able to gauge the comprehensiveness of your report relative to these elements. </P>
                                    <P>
                                        You may report both 
                                        <E T="03">direct</E>
                                         and 
                                        <E T="03">indirect</E>
                                         emissions. As the name implies, direct emissions result directly from fuel combustion or other processes that release greenhouse gases on-site. 
                                    </P>
                                    <P>You produce emissions indirectly when your activities cause emissions to be generated elsewhere. For example, a manufacturer would report as direct emissions the carbon dioxide emitted from the stack of its assembly plant. The same manufacturer could report indirect emissions from the electricity used to light that assembly plant, since the electricity use causes emissions to be generated by an electric utility. </P>
                                    <HD SOURCE="HD2">GG-4 What Is Involved in Reporting Emissions? </HD>
                                    <P>Section 1605(b) addresses the reporting of annual emissions as well as emissions reductions and carbon sequestration. You are strongly encouraged, but are not required, to report your greenhouse gas emissions (1) for the baseline period of 1987 to 1990 and (2) for subsequent calendar years on an annual basis. You may wish to report this data for all or as much of your organization as possible, particularly if it would be important to the users of your reports. </P>
                                    <HD SOURCE="HD2">GG-4.1 Gases and Sources </HD>
                                    <P>These guidelines initially provide for reporting four types of greenhouse gases: carbon dioxide, methane, nitrous oxide, and halogenated substances. These are listed below, along with the major activities associated with emissions of these gases. For each gas listed in your emissions report, you should indicate your total emissions; for example, if you report two gases, carbon dioxide and methane, you should report total emissions numbers for both gases. </P>
                                    <GPOTABLE COLS="2" OPTS="L2,tp0,i1" CDEF="s50,r50">
                                        <TTITLE>  </TTITLE>
                                        <BOXHD>
                                            <CHED H="1">Greenhouse gases </CHED>
                                            <CHED H="1">Related activities </CHED>
                                        </BOXHD>
                                        <ROW>
                                            <ENT I="01">
                                                Carbon dioxide (CO
                                                <E T="52">2</E>
                                                ) 
                                            </ENT>
                                            <ENT>Fossil energy combustion, electricity generation and use, industrial processes, forestry and agriculture. </ENT>
                                        </ROW>
                                        <ROW>
                                            <ENT I="01">
                                                Methane (CH
                                                <E T="52">4</E>
                                                ) 
                                            </ENT>
                                            <ENT>Landfill operation, coal mining, oil and gas systems, stationary combustion, animal production. </ENT>
                                        </ROW>
                                        <ROW>
                                            <ENT I="01">
                                                Nitrous oxide (N
                                                <E T="52">2</E>
                                                O) 
                                            </ENT>
                                            <ENT>Stationary combustion, adipic acid production, forestry and agriculture. </ENT>
                                        </ROW>
                                        <ROW>
                                            <ENT I="01">Halogenated substances (for example, CFCs, HCFCs, PFCs) </ENT>
                                            <ENT>Chemical manufacture, use in industrial processes. </ENT>
                                        </ROW>
                                    </GPOTABLE>
                                    <P>
                                        The guidelines and supporting documents do not generally discuss other radiatively enhancing gases. However, after the second reporting cycle (that is, after the 1996 cycle), you will be able to report other radiatively enhancing gases, including nitrogen oxides (NO
                                        <E T="52">X</E>
                                        ), nonmethane volatile organic compounds (NMVOCs), and carbon monoxide (CO). In some cases, the supporting documents contain data such as emissions factors for some of these gases. However, in general, you will have to determine how to evaluate your emissions of these gases. Your report must meet the minimum reporting requirements of the program, as described in Section GG-6. 
                                    </P>
                                    <HD SOURCE="HD2">GG-4.2 Use of Existing Information </HD>
                                    <P>Many organizations keep accurate data on projects that involve energy efficiency, fuel switching, conservation, pollution prevention, waste minimization, and/or carbon sequestration. If you keep related data for other purposes, reporting greenhouse gas emissions effects under this program will be especially simple and straightforward. </P>
                                    <P>Many potential reporters under EPAct 1605(b) already gather and report emissions information. If you already report similar information (for example, to comply with the Clean Air Act Amendments or under another air quality program) or can easily derive it (for example, from data you submit to regulatory agencies, from smokestack monitoring technologies, or fuel use data kept for internal purposes), you are encouraged to use such information to the extent practical in reporting emissions and emissions reductions under this program. However, you must report the information in a manner that is consistent with these General Guidelines. </P>
                                    <HD SOURCE="HD2">GG-4.3 Scope of Emissions Reporting </HD>
                                    <P>You should report on the most comprehensive basis possible to broaden the usefulness of your emissions reports. However, you may define the scope of your emissions reports. In most cases, the needs of your potential audience will dictate the boundaries you draw. If you are able to report emissions for your entire organization, you should consider providing a comprehensive accounting so that your audience can gain a clear understanding of your overall activities. However, reporting total emissions for a single plant or establishment may be more consistent with other elements of your report and may be based on more precise or more readily available data. </P>
                                    <P>Reporting emissions for your entire organization will show the most complete picture of your activities. Entity-level emissions reports can also provide all the data you need to submit reports on emissions reductions at the entity level or can increase the credibility of reports of emissions reductions at an individual project level. </P>
                                    <P>You do not need to report total organization emissions in order to report individual emissions reductions and carbon sequestration projects. In fact, some reporters may not be able to report their organization's or unit's total emissions, because information needed for the baseline years may not be available, or because it is not feasible to estimate their organization's or unit's total emissions even for the current year. Remember, however, that most users of the database will find your reported estimates of emissions reductions more credible if they are accompanied by records of your organization's total emissions for the baseline years 1987 to 1990 and subsequent years. </P>
                                    <HD SOURCE="HD2">GG-5 How Should I Analyze Projects I Wish To Report? </HD>
                                    <P>
                                        Accurate and credible reporting under this program requires sound project analysis. Rigid rules do not exist for such an analysis, and you may define the emissions reductions and carbon sequestration projects that you report. Your project may consist of all emission-producing activities for your organization; several activities, perhaps as parts of an energy efficiency program; or only one activity, undertaken for its projected cost savings (such as a relighting project) or as a pilot project (for example, an experimental industrial process change). Given the broad range of possible types of projects, it is impossible to establish guidance that 
                                        <PRTPAGE P="68223"/>
                                        provides specific rules and appropriate methods for every type of project. The appropriate procedure for project analysis depends on how clearly you can identify the effects of the project, how credibly you can define a basis for comparing greenhouse gas emissions or carbon sequestration with and without the project, and how well you can measure or estimate the effects of your project. 
                                    </P>
                                    <P>While the guidelines provide you with as much flexibility as possible, every report must— </P>
                                    <P>• Establish the reference case to use as a basis for comparison with the project; </P>
                                    <P>• Identify the project's effects; and </P>
                                    <P>• Estimate emissions for the reference case and the project. </P>
                                    <P>Figure GG-1 depicts the overall process of project analysis. Each of these steps is discussed below and in more detail for each sector in the supporting documents. Note that these three elements depend on each other. For example, your choice of a reference case will depend upon both the scope of your project's effects and the data you use to measure or estimate emissions. </P>
                                    <GPH SPAN="3" DEEP="403">
                                        <GID>EP05DE03.001</GID>
                                    </GPH>
                                    <P>In determining the extent of your analysis and reporting effort, you need to match your effort to your purpose for reporting. If you wish to establish a clear record of emissions and emissions reductions, you should perform extensive analysis and provide for retention of sufficient records to support your report. In any case, you will need to certify the accuracy of the information provided in your report. </P>
                                    <P>These considerations and others in the project analysis process are illustrated in these General Guidelines with three hypothetical case studies: An industrial cogeneration project, an energy-efficiency project in a large office building complex, and the purchase of new solar-powered electricity generating equipment. The case studies are intended to be illustrative and by no means address all of the information that may be reported. A basic description of the facts involved in each case follows. These cases will be more fully developed as the discussion of the steps in project analysis proceeds. </P>
                                    <P>These cases are intended to illustrate the range of detail and expense that might be entailed in developing reports of emissions and emissions reductions. The first case involves no emissions reporting and very simple emissions reductions analysis. The second case involves reporting emissions levels for recent years only and moderately detailed emissions reductions analysis. The third example illustrates the most comprehensive report, including emissions reporting for the baseline years 1987-1990 and detailed project analysis. Note that in each case the level of effort and detail reflected in the analysis and report is determined by the reporter's expected audience. </P>
                                    <HD SOURCE="HD3">Case 1: Rarotonga Coconut Cream, Inc.—Project Description and Emissions Reporting</HD>
                                    <NOTE>
                                        <HD SOURCE="HED">Note:</HD>
                                        <P>This example illustrates only one approach to analyzing a project; your analysis, methods, and calculations will vary depending on your particular circumstances, the geographic location of the project, and other factors.</P>
                                    </NOTE>
                                    <PRTPAGE P="68224"/>
                                    <P>Rarotonga Coconut Cream, Inc. (RCCI) is a small food processing plant in Hawaii. In the past, RCCI purchased its electricity from the local electric utility and produced processing steam from a residual oil-fired boiler. While RCCI's production and energy use have been stable for the past seven years, its energy bills have been growing because of increased electricity rates and oil delivery charges to the company's remote location. Company managers anticipate continued increases in electricity costs as the distribution lines have to be replaced and upgraded over the next five years. </P>
                                    <P>RCCI realized it could cut its energy costs significantly if it installed a cogeneration system to produce its process steam and electricity in a single cogeneration plant fueled by distillate fuel oil. Although the distillate is a higher grade fuel than that currently used, its increased cost is more than offset by the economies realized from the combination of the higher efficiency cogeneration unit and the installation of increased storage capacity, allowing the firm to accept larger, less frequent deliveries. Furthermore, distillate is a cleaner burning fuel oil than residual with lower carbon dioxide emissions per equivalent energy input along with enhanced handling properties. Addition of a backup generator would allow the company to disconnect from the utility transmission and distribution system. </P>
                                    <P>One of RCCI's customers, a grocery wholesaler who was visiting the Rarotonga plant, commented that her company was participating in a Federally sponsored energy-efficiency program and reporting the company's contribution to greenhouse gas emissions reductions through the EPAct Section 1605(b) voluntary reporting program. While RCCI was undertaking its cogeneration project primarily for financial reasons, it was also aware that the project had some beneficial environmental effects, including the reduction of carbon dioxide emissions associated with switching fossil fuel use and electricity production. RCCI decided that, in the interest of sharing its experience with the cogeneration project, the company would report the results to the DOE program. </P>
                                    <P>The first decision RCCI had to make was whether to report its annual emissions of greenhouse gases. As a small business whose primary purpose for participation in the voluntary reporting program was to publicize its experience with using a cogeneration system in a remote location, RCCI was interested in containing its costs of reporting as much as possible. A full entity-wide emissions report would need to account for direct emissions from its oil burner, agricultural operations, and transportation fleet, and indirect emissions from its electricity use. Estimation of emissions from these sources back to 1987 could be costly and time-consuming. RCCI managers decided instead to focus their limited resources solely on an evaluation of emissions reductions associated with their cogeneration project.</P>
                                    <HD SOURCE="HD3">Case 2: Rural-Urban Office Managers, Inc.—Project Description and Emissions Reporting</HD>
                                    <NOTE>
                                        <HD SOURCE="HED">Note:</HD>
                                        <P>This example illustrates only one approach to analyzing a project; your analysis, methods, and calculations will vary depending on your particular circumstances, the geographic location of the project, and other factors.</P>
                                    </NOTE>
                                    <P>In the late 1970s, Rural Office Managers built a complex of offices just outside the city of Metropolis. By the mid-1990s, the city had expanded, and the offices, originally designed for low-density occupation, were now experiencing higher density occupation. </P>
                                    <P>In response to the change in its physical surroundings, the company reincorporated as Rural-Urban Office Managers, Inc. (RUOMI). Company officials also realized they needed to update their facilities, particularly their heating, ventilating, and air conditioning (HVAC), system and their lighting system to accommodate the change in use. Coincidentally, the energy planner for Metropolis contacted RUOMI to explain that the city had enrolled in a new state initiative called Energy Efficient Cities (EEC) that challenges cities to reduce commercial-sector energy consumption by five percent. RUOMI agreed to participate in EEC. </P>
                                    <P>While the emphasis of the EEC program was on reducing energy use, participants were also encouraged to report the indirect effect that their energy conservation activities had on greenhouse gas emissions, that is, the reduction in greenhouse gas emissions at the generating plant resulting from reduced electricity use at RUOMI's offices. When RUOMI managers explored the DOE voluntary greenhouse gas reporting program, they discovered guidance on how to measure both energy savings and associated greenhouse gas emissions. Therefore, as their contractor designed the HVAC and lighting project, RUOMI made sure that the contractor collected all the data RUOMI needed to submit a report. </P>
                                    <P>RUOMI had not preserved a complete set of its energy bills from the late 1980s. Although this information could have been recovered from the Metropolis energy utility, RUOMI managers decided not to attempt to report the company's historic baseline, entity-wide emis-sions because the generating mix for Metropolis' electricity supply had changed dramatically since the end of the last decade. However, using the data provided in the DOE guidelines and supporting documents, they were able to derive the direct emissions from natural gas combustion and the indirect emissions associated with electricity use, for the two calendar years just prior to the commencement of their project. RUOMI reported emissions for those two years and for each year thereafter. </P>
                                    <HD SOURCE="HD3">Case 3: Illinois-Ohio Unlimited—Project Description and Emissions Reporting</HD>
                                    <NOTE>
                                        <HD SOURCE="HED">Note:</HD>
                                        <P>This example illustrates only one approach to analyzing a project; your analysis, methods, and calculations will vary depending on your particular circumstances, the geographic location of the project, and other factors.</P>
                                    </NOTE>
                                    <P>Illinois-Ohio Unlimited (IOU) is an investor-owned utility operating and serving customers in three midwestern states. During a recent integrated resources planning (IRP) effort, it recognized an emerging inability to meet a rising midday peak-load demand, even after pursuing an aggressive peak-shaving, demand-side management program. The IRP identified two alternative responses: purchase additional power from the Indiana Plains Project (IPP), an independent power producer that had excess capacity in its natural gas combined cycle units, or install a large array of photovoltaic cells (PVCs) in southern Illinois and Indiana. PVC electricity production was expected to closely match peak-load demands. While the price of PVCs had decreased dramatically as a result of successful Federal and private research, the second option was still more expensive than the first. However, the public utility commis-sions (PUCs) in all three of the states in which IOU reported encouraged the utility to install the PVCs. The PUCs reasoned that soon PVCs would be economically competitive and this was IOU's opportunity to gain experience with the technology. </P>
                                    <P>Both IOU and its PUCs were concerned, however, that the utility might be inadvertently penalized if subsequent Federal regulations should mandate reductions of emissions of greenhouse gases but not recognize IOU's early reduction effort. IOU decided to report the PVC projects through DOE's voluntary greenhouse gas reporting program. Because IOU knew that use of its information in connection with the requirements of future policy debates would demand complete and accurate information, it kept careful records, and in each case followed the most rigorous requirements of the voluntary reporting guidelines. </P>
                                    <P>As part of its reporting process, IOU reported its entity-wide greenhouse gas emissions for each of the four baseline years, 1987 to 1990, and for every subsequent calendar year. These reports included estimates of emissions from generating processes, IOU fleet vehicle emissions, and office and building operations. </P>
                                    <HD SOURCE="HD2">GG-5.1 What Should the Project Be Compared To? </HD>
                                    <P>A crucial consideration in evaluating your project's accomplishments is how well you can establish a reference case—that is, an emissions level against which to measure the effects of your project. Note that, once you construct your reference case for a project, that reference case should remain constant for the life of the project. If you revise your reference case, you will need to revise any previous project reports to reflect the revised reference case.</P>
                                    <P>A reference case is often referred to as the “but for” scenario, as in, “but for this project, emissions would have been  * * * .” Two possible ways to finish this sentence are: (1) “* * * the same as a previous year” (the basic, or historic, reference case) or (2) “* * * different from any previous year” (the modified reference case, which is adjusted from historic or projected data or based on established standards). Each of these cases is discussed below. </P>
                                    <P>
                                        Under this program you may choose between these two approaches. To fulfill your purposes for reporting, you will want your reference case to be clear and understandable. Depending on the nature of and circumstances associated with your operations, a basic reference case (using 
                                        <PRTPAGE P="68225"/>
                                        historic emissions) may provide a suitable benchmark against which to compare project emissions. In other cases, you may determine that a modified reference case is more appropriate. Even if you choose to use a modified reference case, you still may wish to provide your historic emissions data to enable users of the EPAct 1605(b) database to evaluate the reported emissions reductions efforts with respect to a historic baseline. 
                                    </P>
                                    <P>
                                        <E T="03">Basic.</E>
                                         The basic reference case uses only historical data. Emissions from the project or sequestration levels may be compared with the corresponding emissions or sequestration level for some previous year(s), for example, (1) the 1987 to 1990 period, the period that EPAct Section 1605(b)(1)(A) describes as the baseline years for purposes of reporting emissions; (2) the year(s) just prior to commencement of the emissions reductions project; or (3) some intervening year(s) more representative of normal operations. The reference case may be defined as the average annual emissions during some multiyear period or the highest or lowest annual emissions during that time. Alternatively, you could choose a single reporting year (for example, 1990) as the reference case year. 
                                    </P>
                                    <P>
                                        <E T="03">Modified.</E>
                                         The modified reference case recognizes that even in the absence of your project, your future emissions levels may differ from past levels. The emissions or sequestration levels in the reference case may differ from historical levels because of gradual, predictable changes or because of abrupt changes. Gradual changes in emissions might occur because of growth or decline in industrial output, slowly changing technologies, or natural processes, such as natural regeneration of clear-cut forests. In the case of expanding output or operations, you might extrapolate the reference case from past trends and external data to determine what emissions would have been in the year in which the project's effects are being measured. This process may involve using models and adjusting for growth over time. You could estimate the reference case emissions using historic or current-year data and adjusting for future growth by multiplying the historic emissions rate (emissions per unit of production) by the units produced in the reporting year. 
                                    </P>
                                    <P>A modified reference case based on a hypothetical, abrupt, external change presents a greater challenge for the reporter. For example, a reference case for a forest preservation project might be built on the assertion, “The forest would have been cut if we had not taken actions to preserve it.” If you use this type of reference case, you should take extra care to document the facts underlying the case and to build a sound explanation about why this is the appropriate reference case to use in developing your analysis. </P>
                                    <P>Reference cases for projects involving new operations or added capacity may lie between the two extremes of abrupt changes and gradual changes. For these activities, you will also need to exercise care in constructing a credible modified reference case. Use of industry standards or alternatives actually considered in the planning stages will build credibility. For example, if in the construction of a new building you exceed existing building standards for energy efficiency, you could justifiably assert that the reference case for that project is a building that just meets the standards. </P>
                                    <HD SOURCE="HD3">Case 1: Rarotonga Coconut Cream, Inc.—Reference Case </HD>
                                    <P>RCCI decided to use a basic reference case. Managers reasoned that, in the absence of the shift to the distillate oil-fired cogeneration system, they would have continued using the residual oil-fired boiler and purchased electricity. Because its production levels had been constant over the past seven years, RCCI felt no need to modify the historic levels of energy use to reflect expected future trends. Instead, it decided to use an average of its emissions for 1989 and 1990, the earliest two years for which it had energy use records. Consistent with the RCCI project description, the reference case only incorporated the plant's electrical, processing, and steam production systems. </P>
                                    <HD SOURCE="HD3">Case 2: Rural-Urban Office Management, Inc.—Reference Case</HD>
                                    <P>RUOMI chose to use a basic reference case, averaging its emissions for the years 1993 to 1995. There were several reasons for this decision. Because the use patterns and demands of RUOMI's tenants had changed dramatically from 1980 to 1990, the years 1987 to 1990 (or an average of these years), would not have been an appropriate indicator of expected emissions in the late 1990s. However, by 1992, RUOMI had established many long-term contracts with its tenants. Energy-use patterns had stabilized, and there was no reason to expect significant shifts in the foreseeable future. The company chose to average the years 1993 to 1995 because the first three months of 1994 included unusually cold weather and were not indicative of general energy demands. While its emissions reductions would have appeared larger if RUOMI had used only 1994 as a reference case, company officials were informed by the Metropolis energy planner that the reports could lose credibility if they only compared their project's energy use and emissions levels to a worst-year reference case. </P>
                                    <HD SOURCE="HD3">Case 3: Illinois-Ohio, Unlimited—Reference Case</HD>
                                    <P>IOU's project was clearly driven by increased demands for its product. This immediately suggested that past emissions levels would not be a good model of what would have been, but for the project. Therefore, the utility chose to use a modified reference case to reflect the growth in peaking demand it was experiencing. However, IOU also recognized that it was operating in an environment where a company's current emissions are often compared to some historic level. Therefore, IOU decided to report both historic 1987 to 1990 emissions levels, and the modified reference case reflecting its changing customer demands.</P>
                                    <HD SOURCE="HD2">GG-5.2 What Effects Did the Project Have? </HD>
                                    <P>The second major step in project analysis is identifying effects of the project. Your report should address all the effects that you can identify—not just the obvious, intended effects, but also less noticeable, unintended effects. Effects you should consider include activity shifting (moving processes within your organization), outsourcing (purchasing commodities or services you formerly produced), life cycle emissions shifting (upstream and downstream changes in processes or materials used), and market effects (offsets to achievements caused by residual demand). </P>
                                    <EXAMPLE>
                                        <HD SOURCE="HED">Example:</HD>
                                        <P> An electricity conservation project reduces electricity use at an industrial site and associated carbon dioxide emissions at the utility. However, the utility's emissions of other greenhouse gases, such as methane and nitrous oxide, will be reduced as well. In addition, conserving electricity may lead to other effects within the utility's transmission and distribution system. All of these effects should be identified (and quantified, where possible).</P>
                                    </EXAMPLE>
                                    <EXAMPLE>
                                        <HD SOURCE="HED">
                                            <E T="03">Example:</E>
                                              
                                        </HD>
                                        <P>Closing an industrial plant will likely reduce on-site emissions. However, if another plant is opened or expanded to meet market demand for the former plant's products, the increase in emissions from the new plant would at least partially offset the decrease in emissions resulting from the closing. To place the overall effects of the closing in context, emissions associated with the replacement production capacity should be identified and quantified to the extent possible.</P>
                                    </EXAMPLE>
                                    <EXAMPLE>
                                        <HD SOURCE="HED">
                                            <E T="03">Example:</E>
                                              
                                        </HD>
                                        <P>Shifting an activity to another part of your organization or substituting your production of a commodity with its purchase from others may appear to reduce your emissions. Manufacturing a component at a subsidiary's plant, or the purchase of power by a utility for distribution to customers, however, are some examples in which net emissions may not have changed. The emissions associated with the shifted or substitute production activity should be taken into account, regardless of where it occurs.</P>
                                    </EXAMPLE>
                                    <EXAMPLE>
                                        <HD SOURCE="HED">
                                            <E T="03">Example:</E>
                                              
                                        </HD>
                                        <P>Manufacturers can switch from steel to aluminum and claim reductions because working with aluminum results in fewer emissions. However, the production of the aluminum itself creates emissions different from those associated with the production of the steel. Both the on-site changes and the upstream changes should be considered when you analyze whether you have emissions reductions to report under this voluntary reporting program.</P>
                                    </EXAMPLE>
                                    <EXAMPLE>
                                        <HD SOURCE="HED">
                                            <E T="03">Example:</E>
                                              
                                        </HD>
                                        <P>Extending the rotation length or completely precluding harvesting at a given forest location increases the carbon storage services at that site. However, the added sequestration may be largely offset if another site is harvested earlier than it otherwise would have been to meet the market demand for timber that was not met by timber from the first site.</P>
                                    </EXAMPLE>
                                    <P>
                                        Effects you can identify should be reported. These would include any on-site effects resulting from changes in both fuel combustion and electricity use. Off-site effects may be more problematic. In some situations, you may have relationships with customers or suppliers that allow you to both identify and estimate effects that occur outside your organization. If you have or can get such information, you should report it. 
                                        <PRTPAGE P="68226"/>
                                        Effects you can identify but have no data for should be so noted in your report.
                                    </P>
                                    <P>Although quantifying all effects of a project can be difficult, keep in mind that the credibility of your report will depend to some extent on your ability to identify effects. If your targeted audiences can easily identify effects that you have ignored in your analysis, the credibility of the entire report may be in question.</P>
                                    <HD SOURCE="HD3">Case 1: Rarotonga Coconut Cream, Inc.—Project Effects </HD>
                                    <P>It was easy to identify the obvious effects of the cogeneration project: the reduction of direct emissions as a result of switching from residual oil to distillate as the primary on-site fuel and the reduction of indirect emissions associated with reduced production of electricity by the electric utility. However, after giving the matter some additional thought, RCCI realized that other effects were associated with the project as well. For example, the number of fuel delivery vehicle trips was reduced by half with the switch from residual oil to distillate and the increased storage capacity. Line losses and the indirect emissions associated with the very long distribution of low voltage electricity were deemed to be negligible and beyond RCCI's ability to calculate. </P>
                                    <P>RCCI listed each of the effects it could identify, but decided not to attempt to quantify any but the first two effects.</P>
                                    <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s100,15C,xs68">
                                        <TTITLE>  </TTITLE>
                                        <BOXHD>
                                            <CHED H="1">Project effects </CHED>
                                            <CHED H="1">
                                                Contribution to 
                                                <LI>reduction </LI>
                                            </CHED>
                                            <CHED H="1">Significance </CHED>
                                        </BOXHD>
                                        <ROW>
                                            <ENT I="01">Reduce emissions associated with utility electricity production</ENT>
                                            <ENT>+ </ENT>
                                            <ENT>Large. </ENT>
                                        </ROW>
                                        <ROW>
                                            <ENT I="01">
                                                Reduce CO
                                                <E T="52">2</E>
                                                 emissions associated with on-site fossil fuel burning (switching from residual to distillate) 
                                            </ENT>
                                            <ENT>+ </ENT>
                                            <ENT>Medium </ENT>
                                        </ROW>
                                        <ROW>
                                            <ENT I="01">Reduce transportation-related services </ENT>
                                            <ENT>+ </ENT>
                                            <ENT>Small-Medium. </ENT>
                                        </ROW>
                                        <ROW>
                                            <ENT I="01">Decrease indirect emissions associated with line losses </ENT>
                                            <ENT>+ </ENT>
                                            <ENT>Negligible. </ENT>
                                        </ROW>
                                    </GPOTABLE>
                                    <HD SOURCE="HD3">Case 2: Rural-Urban Office Management, Inc.—Project Effects</HD>
                                    <P>RUOMI contracted with Environmental Security Consulting Organization (ESCO), a local energy service company, to evaluate the costs and benefits of several alternative technologies. After careful evaluation of the use patterns and tenant needs in RUOMI's office complex, ESCO provided a list of two dozen potential energy efficiency improvements and the energy savings and costs associated with each. They explained to RUOMI's management, however, that simply summing across all technologies would not provide an accurate assessment of expected energy savings. Many of the equipment changes would interact with each other, some having negative effects on energy savings, others having synergistic effects. Further, the type and extent of the interactions would depend upon actual use patterns as well as seasonal variations and weather patterns. Following ESCO's recommendation, RUOMI contracted for 14 of the items on the list.</P>
                                    <P>Because of the complex nature of the energy changes expected from the modifications, ESCO recommended that the resulting effects of the activities be analyzed as one integrated project. This avoided the difficulty of having to sort out the impact of each equipment change. It also made any evaluation for the DOE voluntary reporting program simpler. Since RUOMI was analyzing the projects at the entity level, emissions reductions could be calculated directly from its emissions report. Therefore, separate identification of each project's effects was unnecessary.</P>
                                    <HD SOURCE="HD3">Case 3: Illinois-Ohio Unlimited—Project Effects</HD>
                                    <P>Identifying all of the effects of IOU's project and reference cases was not a simple exercise. IOU recognized that it needed to consider the effects that its project had (1) on its own operations and emissions, (2) on the emissions of IPP, (3) possibly on the operations of the larger regional power pool, and (4) on the supplier of the PVCs. It was not sure it could accurately estimate all of these effects without incurring unreasonable analysis costs, but it at least wanted to identify them in planning the analysis that would lead to its completed report.</P>
                                    <GPOTABLE COLS="3" OPTS="L2,tp0,i1" CDEF="s100,15C,xls68">
                                        <TTITLE>  </TTITLE>
                                        <BOXHD>
                                            <CHED H="1">Project effects </CHED>
                                            <CHED H="1">
                                                Contribution to 
                                                <LI>reduction </LI>
                                            </CHED>
                                            <CHED H="1">Significance </CHED>
                                        </BOXHD>
                                        <ROW>
                                            <ENT I="01">IPP emissions that would have gone up because of additional power purchases are reduced </ENT>
                                            <ENT>+</ENT>
                                            <ENT>Large. </ENT>
                                        </ROW>
                                        <ROW>
                                            <ENT I="01">PVC manufacturer emissions do go up </ENT>
                                            <ENT>-</ENT>
                                            <ENT>Small. </ENT>
                                        </ROW>
                                        <ROW>
                                            <ENT I="01">Power pool emissions might change </ENT>
                                            <ENT>? </ENT>
                                            <ENT>Unknown. </ENT>
                                        </ROW>
                                        <ROW>
                                            <ENT I="01">IOU emissions do go down </ENT>
                                            <ENT>+ </ENT>
                                            <ENT>Small. </ENT>
                                        </ROW>
                                    </GPOTABLE>
                                    <HD SOURCE="HD2">GG-5.3 How Do I Estimate Project Accomplishments?</HD>
                                    <P>The final major step in project analysis is estimating emissions levels for both the reference case and project case to determine emissions reductions. The guidelines and supporting documents provide you with a wide range of options for obtaining data and defining the methods for estimating your project's effect on greenhouse gas emissions and carbon sequestration. </P>
                                    <P>First, the guidelines and supporting documents recognize three categories of data. </P>
                                    <P>
                                        <E T="03">Physical data.</E>
                                         This is information that describes the activities involved in your project. For example, how many exit lights were replaced? What was the power requirement of the old and the new lights? How many hectares of trees were planted? What species of trees? How many trees per hectare?
                                    </P>
                                    <P>
                                        <E T="03">Default data.</E>
                                         This is information provided by the supporting documents to assist you in evaluating the emissions or sequestration effects of your project. Using default data increases your ease of reporting (in some cases, allowing you to report when you might not otherwise have enough data). However, using default data may decrease precision and, because the defaults may be conservative, your emissions reductions may appear lower than they actually are. There are two categories of default data: 
                                    </P>
                                    <P>
                                        <E T="03">Emissions factors.</E>
                                         These are factors that allow you to convert information about a change in energy use to an estimated change in greenhouse gas emissions. Some emissions factors are rather precise. For example, the change in direct emissions of carbon dioxide from a reduction in methane combustion is essentially constant, regardless of when or where the change took place. Other emissions factors, and particularly those for indirect emissions, are less precise. For example, the supporting documents provide emissions factors for electricity on a state-by-state basis. However, the effect that a change in electricity consumption has on emissions will vary by loca-tion within the state, the time of day, and the season that a change occurs.
                                    </P>
                                    <P>
                                        <E T="03">Stipulated factors.</E>
                                         These are factors that allow you to convert physical data about your project into estimates of changes in energy use, greenhouse gas emissions or carbon sequestration. The guidelines provide this information for a few types of projects where the scope and nature of the project can be clearly defined and where the effects on emissions can be predicted with relative certainty. For example, the supporting document for the forestry sector provides stipulated factors for converting physical data about tree planting into estimates of carbon sequestration. The supporting document for the residential and commercial buildings sector provides stipulated factors for converting information about certain energy-efficiency projects into estimates of fuel savings. These estimates can be combined with default emissions factors to 
                                        <PRTPAGE P="68227"/>
                                        estimate reductions in greenhouse gas emissions.
                                    </P>
                                    <P>
                                        <E T="03">Reporter-generated data.</E>
                                         This is information that you provide which is used to estimate the effects of your project. There are two categories of reporter-generated data:
                                    </P>
                                    <P>
                                        <E T="03">Measured data.</E>
                                         These are data, collected directly from the project or a control group, that you use to estimate your project's accomplishments.
                                    </P>
                                    <P>
                                        <E T="03">Engineering data.</E>
                                         These are data that you derive from various sources, such as engineering manuals, manufacturer's equipment specifications, surveys, academic literature, professional judgment, and computer models.
                                    </P>
                                    <P>Based on these three categories of data, the guidelines and supporting documents recognize two categories of projects: Standard projects, which rely on physical and default data, and reporter-designed projects, which use measured or engineering data that you develop (as well as appropriate default data). You will need to report the category(ies) of data and projects that you choose to use. </P>
                                    <P>
                                        <E T="03">Standard projects.</E>
                                         These are projects for which the guidelines and supporting documents provide the procedures and information to estimate the emissions reductions or carbon sequestration. Reports of these projects rely entirely on physical and default data (
                                        <E T="03">see</E>
                                         Figure GG-2). 
                                    </P>
                                    <P>Not all projects can be described in standard project reports. The supporting documents for each sector delineate, where possible, projects for which emissions factors and stipulated factors are provided, and for which standard project reports can be submitted. You should recognize that default values are often conservative; that is, if you use them, you are likely to underreport your emissions reductions or carbon sequestration. However, if you do not directly measure and monitor or your organization does not have expertise in estimation methods, the default values will allow you to calculate the effects of your activities. </P>
                                    <GPH SPAN="3" DEEP="286">
                                        <GID>EP05DE03.002</GID>
                                    </GPH>
                                    <P>
                                        <E T="03">Reporter-designed projects.</E>
                                         These projects use physical and reporter-generated data, possibly in combination with default data, to estimate their accomplishments (see Figure GG-3). For this type of project, you should be able to indicate the source of all data, and in the case of data you generate, how it was measured or derived. For reporter-designed projects, the supporting documents for each sector provide principles and guidance. 
                                    </P>
                                    <P>Estimation of the emissions effects of many reporter-designed projects will require that you not only gather measured or estimated data, but that you also manipulate this information to derive the emissions levels of your project and reference case. The data manipulation could involve relatively simple calculations or extremely complex modeling. You should be able to identify the nature of the calculations and/or the type/name of the model you have used. In some instances, it may not be possible to estimate emissions for both the project and the reference case. In these cases, identified in the supporting documents for each sector, you may need to measure the emissions reductions directly. </P>
                                    <P>Finally, the emissions reductions or carbon sequestration of your project is simply the difference between your project emissions/sequestration and your reference case emissions/sequestration. </P>
                                    <GPH SPAN="3" DEEP="322">
                                        <PRTPAGE P="68228"/>
                                        <GID>EP05DE03.003</GID>
                                    </GPH>
                                    <HD SOURCE="HD3">Case 1: Rarotonga Coconut Cream, Inc.—Estimation Methods </HD>
                                    <P>RCCI limited its quantitative analysis to the obvious effects; estimation of the annual emissions reductions associated with its project was simple. First, it estimated the annual emissions associated with the project. This was simply its annual distillate oil consumption multiplied by the default emissions factor for distillate oil supplied by the guidelines' supporting documents. Second, for the reference case, RCCI multiplied its reference case annual electricity use by the default electricity emissions factor for its state, multiplied its reference case annual residual oil use by the default residual oil emissions factor, and summed the two to arrive at total emissions for the reference case. Its total reported emissions reductions were the difference between the reference case emissions and the project case emissions. </P>
                                    <P>RCCI was pleased that it was able to do its entire analysis based on data it had readily at hand, that is, its fuel and electricity use records from before and after the project, and the default emissions factors provided by the guidelines. </P>
                                    <HD SOURCE="HD3">Case 2: Rural-Urban Office Managers, Inc.—Estimation Methods </HD>
                                    <P>ESCO, the contractor for RUOMI, had primary responsibility for preparing the voluntary report for the DOE program. ESCO knew that because of the complexity of the project it could not derive estimates using default data provided in the Guidelines' supporting documents. The project managers turned to the supporting document for the residential and commercial buildings sector to identify the recommended methods for gathering data for their type of project. They found that the recommended methods included approaches very similar to ones they had previously used to measure energy savings in complex projects. After a full year of measuring and monitoring, they summarized the energy-use data, and performed calculations to derive the difference between the project energy use and the reference case energy use. </P>
                                    <P>Applying the natural gas and electricity emissions factors supplied as default data, they converted the estimated energy reductions to estimated emissions reductions. </P>
                                    <HD SOURCE="HD3">Case 3: Illinois Ohio Unlimited: Estimation Method </HD>
                                    <P>IOU recognized two distinct parts to its emissions reductions estimation process. First, it needed to evaluate the direct electricity system emissions for both its reference case and project case. Second, it wanted to estimate the emissions associated with manufacturing the PVCs. Tackling this latter point first, IOU contacted a prospective PVC supplier for any information on emissions associated with the PVC manufacturing process. The supplier, it turned out, had commissioned a report that estimated not only the direct carbon dioxide emissions associated with the manufacture of PVCs, but also the emissions associated with the supply of raw materials—steel, aluminum, chemicals, and electricity—that were used in PVC fabrication. Had this information not been available, IOU would have had to decide whether or carry out this study itself or not quantify this effect at all, possibly affecting the credibility of its project report. </P>
                                    <P>IOU then turned to the electricity system emissions effects of its project. The project reduced emissions that would have occurred had IOU purchased its electricity from IPP. Additional production from IPP for daytime peaking would have been generated by a natural gas combined cycle unit. IOU developed a single conversion factor for the emissions per kWh that would have occurred for electricity from IPP's system. This meant that as the peak daytime demand grew over time, IOU would be able to estimate that portion of the emissions for the reference case that was attributable to IPP, that is, how much higher IPP emissions would have been had IOU relied on purchased power. </P>
                                    <P>The new PVC system was designed to meet the growth in demand over the next decade. But because the PVCs would be generating at full capacity immediately, they would actually displace some of IOU's current daytime generating capacity. The marginal unit in IOU's generation equipment was an oil-fired turbine generator. IOU developed a conversion factor for the emissions per kWh that would have occurred from that unit, if its production had not been partially displaced by the solar power system. </P>
                                    <P>
                                        In summary, the IOU emissions reductions estimation consisted of three major components. First, at the start of the project there was an initial emission of carbon associated with the production of the PVC 
                                        <PRTPAGE P="68229"/>
                                        units. This effect was reflected only in the first annual report. While some of these emissions had actually taken place as many as two years earlier, IOU believed it was sufficiently realistic to account them all to the first reporting year. Second, the project emissions also showed a sudden drop in emissions for the oil-fired plant due to displacement of daytime oil-fired generation by the PVCs, whose entire capacity was not initially required to meet midday peak demand. However, as expected, the emissions from the oil-fired plant climbed each year as daytime peak demand grew and increasingly the PVC capacity was used to meet that demand. This increase was reflected in IOU's annual reports. Third, under the reference case, IOU reported constant emissions from its own oil-fired plant and annually increasing emissions from IPP's natural gas combined cycle plant. The emissions reduction each year was calculated by subtracting the project emissions from the reference case emissions. 
                                    </P>
                                    <HD SOURCE="HD2">GG-5.4 What if Two or More Organizations Wish To Report the Same Project? </HD>
                                    <P>You may report activities undertaken in association with others. If you do so, you must identify other potential reporters of the same activity so that the program can account for multiple reports of the same activities. You may wish to make arrangements for reporting with others involved in your project. </P>
                                    <P>Joint activities generally fall into one of two categories. The first category includes one-time transactions that are large enough to require negotiation before the exchange takes place and generally involve a written contract, such as demand-side management (DSM) programs. The second category comprises transactions that take place repeatedly between manufacturers and consumers where negotiated contracts are generally not involved, such as individual purchases of household appliances. </P>
                                    <HD SOURCE="HD3">Three Examples of Joint Activities </HD>
                                    <P>
                                        <E T="03">Demand-side management programs:</E>
                                         When an electric utility undertakes a DSM program, three parties are involved in reducing carbon dioxide emissions: (1) Manufacturers of the energy-efficient equipment, such as improved lighting, refrigeration, and other energy-consuming goods; (2) consumers of electricity (households, commercial operations, and industrial firms); and (3) the utility itself. All three parties may wish to report the reductions in emissions. 
                                    </P>
                                    <P>
                                        <E T="03">High-efficiency automobiles:</E>
                                         EPAct section 1605(b) also suggests that the manufacture of high-efficiency automobile fleets be reportable under this program. On the one hand, the purchaser of a high-efficiency car makes the ultimate decision to reduce emissions related to personal transportation. On the other hand, the automobile manufacturers who shifted their fleet composition are enabling the automobile owners to obtain more efficient automobiles. 
                                    </P>
                                    <P>
                                        <E T="03">Tree-planting agreements:</E>
                                         Some utilities have entered into agreements with landowners to plant trees. The utilities provide funding for establishing the trees; in return the landowners agree to leave the new trees in place for a specified number of years. Both landowners and utilities have played essential roles in carbon sequestration. 
                                    </P>
                                    <P>Where contracts are involved, you may make arrangements to assign the ability to report resulting emissions reductions before they are reported under this program. You are not required to do this sorting out before you report, but, depending upon how you believe this information will be used, you may wish to resolve any questions before reporting. </P>
                                    <P>You may also wish to mutually decide reporting capabilities for purchases. If you can most easily aggregate many small reports, for example, as a manufacturer of high-efficiency automobiles or efficient appliances, you may wish to include, as part of the purchase transaction, an agreement with the consumer that you will report the energy-efficiency information, unless consumers notify you that they wish to do so. </P>
                                    <P>However, for some technologies, consumers are in a better position to estimate actual accomplishments. For example, new automobile owners can better estimate annual vehicle miles traveled and, hence, the fuel and emissions savings associated with the purchase of a high-efficiency car. You need to consider the trade-off between the ease of reporting and accuracy of estimating the emissions reductions when deciding who will report the reduction—the manufacturer, the automobile owner, or both. If parties report separately, each should identify the other as potential reporters of the same information. </P>
                                    <HD SOURCE="HD2">GG-5.5 May I Report Through My Trade Association or Other Third Parties? </HD>
                                    <P>You may wish to explore reporting through another party—for example, through a trade association, civic association, or fraternal organization. Each of the supporting documents discusses third-party reporting as it may apply to particular sectors. </P>
                                    <P>Third-party reporting may be appropriate for a number of reasons. Organizations may be able to provide technical or administrative assistance to you in reporting. Multiple reports may be aggregated to provide a quantity of emissions and reductions which each individual reporter would not choose to report. Furthermore, confidentiality of some data reported may be enhanced by third party reporting. </P>
                                    <P>Third-party reporting may not be appropriate for your purpose in reporting. For example, it does not provide the transparent link to you that is necessary for creating a formal public record of your emissions and achievements for any purpose. </P>
                                    <HD SOURCE="HD2">GG-5.6 What Else Will I Be Asked To Report? </HD>
                                    <P>As part of your report, you will be asked to choose one of three descriptors of the project(s) whose effects you are reporting. This identification will be limited to those provided in the language in EPAct 1605(b): (1) Voluntary reductions, (2) plant or facility closing, and (3) state or Federal requirements. </P>
                                    <P>Projects may be undertaken for other purposes, for more than one purpose, or may have greenhouse gas impacts that were not the reason for implementing the project. You may wish to, but will not be required to, report more detailed information on why you undertook the project. </P>
                                    <HD SOURCE="HD2">GG-5.7 May I Report International Projects? </HD>
                                    <P>Considerable interest has been generated regarding the potential for cooperation among parties in different countries. For example, there may be opportunities for U.S. parties to reduce greenhouse gas emissions and increase carbon sequestration outside the United States, perhaps at lower cost than possible through domestic activities. </P>
                                    <P>Under this program, you may report the relevant results of your activities outside the United States, under the same process applicable to similar domestic activities. Note that you may have special difficulty in analyzing international activities: determining an appropriate reference case, defining project boundaries, selecting appropriate measurement or estimation methods, and obtaining credible data. Special attention should be given to all the identifiable effects of your international activities. </P>
                                    <P>Under the United Nations Framework Convention on Climate Change, nations that are parties to the Convention will determine how cooperative efforts between member nations and their respective citizens (“joint implementation”) will be counted toward meeting each country's commitments under that treaty. The President's Climate Change Action Plan, announced in October 1993, includes a pilot program called the United States Initiative on Joint Implementation (USIJI) designed to help establish an empirical basis for considering approaches to joint implementation. The USIJI program has developed evaluation criteria and will develop emissions measurement and verification methods for international projects accepted into the pilot program. </P>
                                    <P>If you are reporting the results of any international project to this program, you will also indicate whether it has been accepted under the USIJI or under the Convention as an accountable joint implementation project. Reporting the results of an international activity under the EPAct 1605(b) program alone does not bring it under the umbrella of formal joint implementation. </P>
                                    <HD SOURCE="HD2">GG-5.8 May I Report Prospective Emissions Reductions? </HD>
                                    <P>Many projects that reduce greenhouse gas emissions or sequester carbon achieve their results over several years, or even decades. For some of these projects, the accomplishments are evaluated by means of computer modeling or engineering estimates, rather than by direct measurement and monitoring of greenhouse gas emissions and flows. In those cases, the estimation process is generally carried out before the project begins. </P>
                                    <P>
                                        If you have analyzed your project using a method that estimates effects prospectively, you may choose in the first reporting year to report the expected annual emissions reductions or carbon sequestration for future years. However, that information will be maintained separately from the EPAct 1605(b) database. 
                                        <PRTPAGE P="68230"/>
                                    </P>
                                    <P>To have your project accomplishments recorded in the EPAct 1605(b) database, you must certify each year that the project continues to perform as expected. As you certify each year's accomplishments, EIA will transfer the data from the database of prospective accomplishments to the EPAct 1605(b) database. </P>
                                    <P>You may also modify your estimates of past accomplishments at any time for any of several reasons. For example, if events following the commencement of the project are different than expected, you may wish to modify your model to more closely reflect actual events. Alternatively, you may simply find modeling or engineering estimation methods that you believe to be more accurate than those you initially employed. You may even decide to carry out field measurements where you had not initially anticipated doing so. Whatever your reason, you can modify the existing estimates to reflect your more accurate estimates of both your past accomplishments recorded in the EPAct 1605(b) database and your expected accomplishments recorded in the database of prospective accomplishments. However, you should provide clear documentation of how you derived the revised estimate. </P>
                                    <HD SOURCE="HD2">GG-5.9 How Far Back May I Report Projects? </HD>
                                    <P>A primary purpose of the program is to record emissions reductions, not to track when projects were initiated. Therefore, you may report new or ongoing projects that have achieved reductions beginning January 1, 1991. However, for any project, you must establish a credible reference case and retain that reference case for all your reports of that project. If you use historic data to construct your reference case, you should not use data earlier than 1987. If you change your reference case, you must amend any previous reports for that project to account for the amended reference case.</P>
                                    <EXAMPLE>
                                        <HD SOURCE="HED">Example:</HD>
                                        <P>You initiated a project in 1991 that reduced emissions from their 1990 levels. This project is reportable.</P>
                                    </EXAMPLE>
                                    <EXAMPLE>
                                        <HD SOURCE="HED">Example:</HD>
                                        <P>You initiated a project earlier than 1987 that has decreased emissions every year relative to each previous year. You may establish either a basic or modified reference case based on what emissions would have been without the project (using only data from 1987 on), then report the emissions reductions from the project for 1991 and subsequent years.</P>
                                    </EXAMPLE>
                                    <EXAMPLE>
                                        <HD SOURCE="HED">Example:</HD>
                                        <P>You initiated a project earlier than 1987 that reduced emissions to a level that stabilized during (or before) the baseline years 1987-1990. This project would not be reportable, since the reductions were achieved prior to the period covered by the EPAct 1605(b) reporting program.</P>
                                    </EXAMPLE>
                                    <EXAMPLE>
                                        <HD SOURCE="HED">Example:</HD>
                                        <P>You have an ongoing DSM program to encourage replacement of appliances or equipment. You would not be able to report achievements before 1991, but any appliances replaced in 1991 or after that year are new reductions and could be reported.</P>
                                    </EXAMPLE>
                                    <EXAMPLE>
                                        <HD SOURCE="HED">Example:</HD>
                                        <P>You have been installing windmills every year for 10 years. In order to report emissions reductions for 1991, you would need to demonstrate that the 1991 windmill displaced emissions-producing generation. If the windmill replaced another, the project would not be reportable.</P>
                                    </EXAMPLE>
                                    <P>These are relatively straightforward examples when you construct historic reference cases. Your analysis becomes more complex when you wish to construct modified reference cases. In general, you should not use data from years before 1987 except as additional support for your assertion of what modified levels would have been after 1987. </P>
                                    <HD SOURCE="HD2">GG-5.10 Must I Take Into Account the Different Effects of Different Greenhouse Gases? </HD>
                                    <P>Your reports on emissions and emission reductions will include data on greenhouse gases in tons of each gas emitted; you will not be required to calculate the various effects of different gases on climate for this voluntary reporting program. However, you may wish to perform these calculations for your own purposes. For example, you may wish to evaluate the costs of competing proposed projects in terms of the beneficial effects on climate; in order to do so, you may wish to look at these effects using a common index, such as the equivalent effect in tons of carbon dioxide. You may wish to talk about such equivalencies with various stakeholders or for public relations purposes. </P>
                                    <P>The Intergovernmental Panel on Climate Change has developed an index that compares the impact that each gas has on global warming relative to the effect that carbon dioxide has. Information about this index, called the Global Warming Potential (GWP), is presented in Appendix E, along with GWPs for the types of gases covered by this reporting program. If you wish to use the index, remember that it does not take into account some complexities of atmospheric chemistry and that the underlying science is evolving. </P>
                                    <HD SOURCE="HD2">GG-5.11 Is It Necessary To Report Emissions Reductions and Carbon Sequestration Every Year? </HD>
                                    <P>This is a voluntary reporting program. You are under no legal obligation to continue reporting. However, you should recognize that the usefulness of your initial reports may be affected by your participation in the program in subsequent years. </P>
                                    <P>If you report emissions reductions for a period of time, and then fail to report thereafter, the user of the database is likely to assume that your project is no longer reducing emissions relative to the reference case. However, this does not negate the value of the reductions accomplished while the project was in place. </P>
                                    <P>Reporting carbon sequestration projects raises a different type of problem. If you report carbon capture for a number of years and then cease reporting, a database user is apt to assume that the carbon that had been captured has been released back to the atmosphere. This not only limits recognition of any accomplishments that may have occurred following cessation of your reports, but largely negates the value of accomplishments already reported. </P>
                                    <P>You or your firm may find that, following successfully reporting to the voluntary reporting program for several years, you miss one or more years of reporting. If you choose to resume reporting, your initial report should contain information not only for the most recent reporting year, but also, if possible, for all of the intervening years during which you did not report. This will ensure that the EPAct 1605(b) database reflects a continuous record of your activities, thereby increasing the credibility of all your reports. </P>
                                    <HD SOURCE="HD2">GG-5.12 May I Amend My Previous Years' Reports? </HD>
                                    <P>If you have submitted reports under this program but afterwards develop better data (for example through field measurements or utility-specific emissions factors), or better estimation methods (for example, your organization's adoption of standard analytic procedures), you may amend your previous reports. You may also need to amend reports because you have amended your reference case for a particular project. Your amended reports should clearly state your reasons for amendment and the bottom-line difference that results from the amendment. The following case study discusses an instance in which a reporter chose to amend previous reports. </P>
                                    <HD SOURCE="HD3">Case 4: Black Forest Cake, Inc.—Long-Term Project Reporting </HD>
                                    <NOTE>
                                        <HD SOURCE="HED">Note:</HD>
                                        <P>This example illustrates only one approach to analyzing a project; your analysis, methods, and calculations will vary depending on your particular circumstances, the geographic location of the project, and other factors. </P>
                                    </NOTE>
                                    <P>Black Forest Cake, Inc. (BFCI) was a family-owned business that was experiencing extremely rapid growth in demand for its products, which included baked goods produced at 13 sites in five states, catering services at 10 shops in seven states, and equipment rentals at 15 stores in three states. It operated from a total of 23 sites spread across nine states. </P>
                                    <P>The family members and many of their staff were environmentally conscious. While they were delighted with the increased demand for their products, they were concerned to see their energy consumption rising, particularly their natural gas consumption for baking ovens and space heating, and their gasoline use in delivery vehicles. They knew that increased energy use signaled increased greenhouse gas emissions. </P>
                                    <P>Therefore, BFCI decided to voluntarily offset some of the increase in emissions by undertaking a tree-planting (carbon sequestration) project on farmland they owned. They were not interested in receiving official recognition for their effort. They were motivated purely by their interest in environmental protection and a desire to project an image of BFCI as a “good global citizen.” They did, however, want to be sure that their project actually reduced net carbon dioxide emissions, not just appear to do so. Therefore, BFCI decided that its project should at least meet the minimum reporting standards used by DOE in the EPAct 1605(b) voluntary greenhouse gas reporting program. </P>
                                    <P>
                                        In its first report following the establishment of the tree stand, BFCI 
                                        <PRTPAGE P="68231"/>
                                        reported that it had planted the trees and reported information consistent with the guidance provided in the forestry sector supporting document. It also reported that it expected the forest to capture carbon at a rate consistent with the stipulated factors provided by the guidelines' supporting document for forestry. Each year thereafter BFCI confirmed in its report that the project appeared to continue to perform as expected. 
                                    </P>
                                    <P>After eight years of relying on the default stipulated factors, BFCI became engaged in a dialogue with a local environmental group. One consequence of the discussions was that BFCI agreed to measure the standing carbon on its project site in the tenth year to determine whether the project had met the expectations established for the first decade by the stipulated factors. The field measurements, including statistical sampling of both soils and biomass, revealed that the project had actually exceeded expectations by 20 percent. This was attributed to the fact that the original soils were particularly rich in phosphorous and nitrogen. </P>
                                    <P>BFCI amended its previous reports to reflect this new information based on field measurements. The amended reports increased the reported carbon dioxide flows to the forestland by 20 percent in each of the first ten years. BFCI also amended the projected annual carbon capture rates for the second decade to reflect the higher-than-expected performance. BFCI thus transformed its project from a standard project to a reporter-defined project. </P>
                                    <HD SOURCE="HD2">GG-6 What Are the Minimum Reporting Requirements? </HD>
                                    <P>DOE has not established a minimum size for a reporting entity or for the reported emissions, emissions reduction, or sequestered carbon. For some purposes of reporting, such as the exchange of information on pilot projects, a minimum size requirement would limit participation. Similarly, you are not required to complete a full and comprehensive report as defined earlier. However, you must report a minimum set of information. </P>
                                    <P>Whatever the scope of your report, you are required to certify the accuracy of the data you have provided. You must also meet minimum information requirements: </P>
                                    <P>• If you are reporting greenhouse gas emissions, you must clearly identify the facilities that are covered by your report and, for each greenhouse gas covered by your report, clearly identify the gas, the amount of the emissions (expressed in metric tons of that gas per year), and the year of the emissions. </P>
                                    <P>• If you are reporting emissions reductions or carbon sequestration projects, you must be able to describe your project and provide sufficient physical data to allow users of the database to form a clear understanding of the nature and scope of your project, including the cause of the change in emissions or carbon sequestration. You must also identify the location of the project, the reference case for the project, and the effects of the project. </P>
                                    <P>• Whether you are reporting on a standard project or a reporter-designed project, you must be able to identify the sources of your data, the level of change of emissions or carbon sequestration per year, and the year in which the change took place. </P>
                                    <P>• If you are submitting a reporter-designed project report involving direct monitoring and measuring or engineering estimations, you must also identify the techniques used to gather the data and make the estimates. </P>
                                    <HD SOURCE="HD2">GG-7 Can My Data Be Kept Confidential? </HD>
                                    <P>The provisions of section 1605(b)(3) stipulate that “Trade secret and commercial information that is privileged or confidential shall be protected as provided under Section 552(b)(4) of Title 5, United States Code.” In general, information submitted to the Federal government must be made available to the public. This section prohibits release of certain trade secret and commercial or financial information. </P>
                                    <P>You will enhance both the credibility and usefulness of information you report by making it available for public release. More accurate data will increase the value of emissions reductions estimates in terms of public recognition, and widely available information will help diffuse knowledge about cost-effective emissions reductions opportunities. Thus, you should try to avoid labeling reported information as confidential wherever possible. </P>
                                    <P>While a reporter may believe that some of the data voluntarily submitted under this program is entitled to protection under the exclusion, this protection is neither automatic nor complete. You should be aware that, under DOE regulations (10 CFR 1004.11), DOE will evaluate each claim of confidentiality and determine whether or not to disclose the data to the public. Also, data may be released to another Federal agency under certain circumstances regardless of any claim of confidentiality. </P>
                                    <HD SOURCE="HD2">GG-8 What Certification Is Required? </HD>
                                    <P>If you report under this program, you will be required to certify through your signature the accuracy of all the information reported. Therefore, the person who signs the report must be authorized to act as a representative of the reporting entity for these purposes. No independent certification is required, and the Federal government does not plan to certify your reports. However, you may wish to indicate if your data have been verified by a third party. </P>
                                    <HD SOURCE="HD2">GG-9 What Should I Do Next? </HD>
                                    <P>These general guidelines present an overall picture of the reporting process for the voluntary reporting program. You will find more detailed guidance in the sectoral supporting documents for electricity supply, residential and commercial buildings, industry, transportation, forestry, and agriculture. You may have reportable projects in several sectors; you may report them separately or capture and report the total effects on an entity-wide report. If you need the supporting documents, contact United States Department of Energy, 1000 Independence Avenue, SW., Washington, DC 20585. </P>
                                    <P>Reporting forms are available at the following address: United States Department of Energy, Energy Information Administration, 1000 Independence Avenue, SW., Washington, DC 20585. </P>
                                    <P>DOE encourages you to report your achievements in reducing greenhouse gas emissions and sequestering carbon under this program. Global climate change is increasingly being recognized as a threat that individuals and organizations can take action against. If you are among those taking action, reporting your projects may lead to recognition for you, motivation for others, and synergistic learning for the global community. </P>
                                </APPENDIX>
                            </SECTION>
                        </PART>
                    </SUBCHAP>
                </SUPLINF>
                <FRDOC>[FR Doc. 03-29983 Filed 12-4-03; 8:45 am] </FRDOC>
                <BILCOD>BILLING CODE 6450-01-P</BILCOD>
            </PRORULE>
        </PRORULES>
    </NEWPART>
</FEDREG>
